Introduction
This package provides an extended content rule “mail” action with many more variable substitutions available, including the name and email address of the content owner, making it possible to email the owner of a piece of content.
It is also possible to provide new “replacers” by writing an interface with an associated adapter and registering a new IMailModel utility. The user is able to pick the replacer to use on the action edit form.
Changelog
0.7 (2016-03-17)
Ported tests to plone.app.testing [tomgross]
Plone 4.3 compatibiliy [tomgross]
Moved to https://github.com/collective/collective.contentrules.mail [maurits]
0.6 (2012-02-23)
Remove an extra From header when calling mailhost.secureSend() [dimboo]
0.5 - 2011-05-20
Added an exception in IVocabularyFactory import for Plone >= 4.1. [lepri]
0.4 - 2009-09-06
Avoid a site error if the mail cannot be sent, e.g. because the mail server is down. [optilude]
Avoid throwing an exception on encoded strings in the replacer. [optilude]
Caught workflow exception when trying to get state on object without any workflow. [tiazma]
Added cc and bcc fields to IMailAction enabling the use of these fields in mail messages [erico_andrei]
Added new variables to IMailReplacer so it is possible to send emails to users with other roles than owner on the object [erico_andrei]
Made sure Archetypes content implements IDublinCore (It’s not the default behavior until AT 1.5.10) [erico_andrei]
Correct action mail fail on try to replace bcc or cc when it returns None [lucmult]
0.3 - 2009/03/24
Added a note in the UI about how to use variables. [optilude]
The ‘source’ field is not required, but would throw an error if not filled in. This is now fixed. [optilude]
0.2 - 2009/03/24
Made the executor fail gracefully if the content being acted upon is not adaptable to the replacer interface. [optilude]
Made the default replacer adapt any Dublin Core-capable content, avoiding an unnecessary dependency on Archetypes. [optilude]
Made the default IMailModel implementation more re-usable. [optildue]
Updated documentation and interface specifications. [optilude]
Fixes actions/configure.zcml in order to play nice with GenericSetup
0.1 - Unreleased
Initial release
Release files for collective.contentrules.mail 0.7
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 |
|---|---|---|---|---|
| collective.contentrules.mail-0.7.tar.gz | 22.9 kB | Without provenance | Details for collective.contentrules.mail-0.7.tar.gz |
Release files / collective.contentrules.mail-0.7.tar.gz
| Download URL | collective.contentrules.mail-0.7.tar.gz |
|---|---|
| Size | 22.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
09e76456e90103f0a31635d7dd6b23b6dcf45e37f23cb242a168d6c9a19e5132
|
|
BLAKE2b-256 checksum How to use checksums |
5fd420b2a2a2928a872a4ceedde480374754498d1ce40765bb402ba559efa182
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.contentrules.mail 0.7
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.
