Introduction
collective.overridemailrecipients forwards all mails sent from Plone. Use this package on testing and development environments where you want to test emails sent thru Plone, but not want to use the real addresses.
This package is always active by patching MailHost. The recipient(s) in the ‘To’ header are replaced by ‘plone@localhost’ or a configurable mail address.
Features
All emails sent thru the Plone mailer are forwarded to one mail address
Bcc and Cc headers are stripped
Installation
To your buildout.cfg, add:
eggs =
...
collective.overridemailrecipients
After that, just install via the “Add-on” controlpanel.
Usage
After installation this packages is configurable thru the site setup
Email address, this address is used to forward mails to
Enabled or disable or disable mail forwardind
TODO
Add to, cc and bcc in forwarded mail
Contributors
Pawel Lewicki <lewicki@gw20e.com>
Kim Chee Leong <leong@gw20e.com>
Changelog
1.0.2 (2013-03-08)
Re-added missing tests.
1.0.1 (2013-03-08)
Added test module, accidentally removed it from version control
1.0 (2013-03-08)
Initial release
4 maintainers
Metadata
4 maintainers
Release files for collective.overridemailrecipients 1.0.2
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.overridemailrecipients-1.0.2.zip | 28.6 kB | Without provenance | Details for collective.overridemailrecipients-1.0.2.zip |
Release files / collective.overridemailrecipients-1.0.2.zip
| Download URL | collective.overridemailrecipients-1.0.2.zip |
|---|---|
| Size | 28.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2788b485dc658a19b5d8175bd5be73443cb8f3c7f07af7975daa74de12637e61
|
|
BLAKE2b-256 checksum How to use checksums |
09f800a6fb9b936b78fd15b8bb404e2db9dd85cf191967d9a1f991dbd5523210
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.overridemailrecipients 1.0.2
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.
