ftw.notification.email
This package is an extension for ftw.notification.base providing email notification after editing a content.
See ftw.notification.base for further details.
Usage
Add ftw.notification.email to your buildout configuration:
[instance]
eggs +=
ftw.notification.email
Install the generic setup profile of the package
Links
Copyright
This package is copyright by 4teamwork.
ftw.notification.email is licensed under GNU General Public License, version 2.
Changelog
2.2.0 (2019-09-16)
Add content ID support [Nachtalb]
2.1.0 (2016-11-30)
Add optional support for ftw.activity. [jone]
Fire new INotificationEmailSentEvent when sending emails. [jone]
Drop support for Plone 4.1 and 4.2. [jone]
2.0.10 (2016-02-01)
Fix email template. The sender was listet twice in the email footer [elioschmutz]
2.0.9 (2014-10-07)
Fix bug when building emails with an actor / reply-to header. This sems to be a regression from the refactoring in 2.0.8. [jone]
2.0.8 (2014-09-29) BROKEN!
Refactor email composing to use Header objects instead of strings. [tschanzt]
Update French and English translations. [jone]
2.0.7 (2013-11-15)
Send email address instead if id to journal. [mathias.leimgruber]
2.0.6 (2013-08-28)
Register a default subject and attachment adapter for dx types. [mathias.leimgruber]
2.0.5 (2013-04-17)
Drop Plone 4.0 compatibility. [jone]
Plone 4.3 compatibility. [jone]
2.0.4 (2012-05-24)
Fix bug which caused notification to be sent to “None” if there is no CC recipient selected. [jone]
2.0.3 (2012-05-09)
Fixed upper/lower case in StoneageHTML dependency to make version pin work. [buchi]
2.0.2 (2012-03-26)
Fixed translations [mathias.leimgruber]
2.0.1 (2012-03-26)
Fixed email subject adapter. Raised UnicodeDecodeError if Umlauts are used in site.Title() oder object.Title() [mathias.leimgruber]
2.0 (2012-03-05)
Add possibility to add attachments to an email. [mathias.leimgruber]
Added translation in mail subject. This package does not work for Plone 3 anymore! [Julian Infanger]
Fixed test setup. [timon.tschanz, jone]
1.0.5 (2011-09-08)
Added Test for ftw.notification.email [timon.tschanz]
1.0.3 (2011-05-31)
Added SubjectCreator adapter. Added propertiestool.xml modified notifier.py [timon.tschanz]
1.0.2 (2011-04-19)
Fix subject encoding. [mathias.leimgruber]
1.0.1 (2011-01-25)
Save notification in Journal, using ftw.journal. [mathias.leimgruber]
1.0 (2010-12-22)
Fix translations [mathias.leimgruber]
0.6 (2010-11-30)
Implement CC notification. [mathias.leimgruber]
Update translations. [mathias.leimgruber]
0.5 (2010-10-26)
Make subject of the notification email customizable through a property. [jone]
Fix bug when no recipient is selected. [vba]
12 maintainers
Metadata
12 maintainers
Release files for ftw.notification.email 2.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ftw.notification.email-2.2.0.tar.gz | 25.0 kB | Without provenance | Details for ftw.notification.email-2.2.0.tar.gz |
Release files / ftw.notification.email-2.2.0.tar.gz
| Download URL | ftw.notification.email-2.2.0.tar.gz |
|---|---|
| Size | 25.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3d461554fb18a317eebaa784abc5184d9a5f3effe5e59c185b0fb36f208453f0
|
|
BLAKE2b-256 checksum How to use checksums |
b7871932be10cfa4daf4f78918cad4559b1633fa77905527aa6236e44df89700
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.30.0 CPython/2.7.15
|
Security for ftw.notification.email 2.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
