Introduction
This is a MailHost that stores all mail, if it is from or to a registered user. It’s very primitive now, I expect it to to grow fratures like purging etc in the future, but at the moment there is none.
After installing it through the Plone Control Panel Addons as usual, all sent emails that are sent to or from a registered user will be stored. Each user can se his in and out-box at the http://plonesite/@@my_mailbox URL.
Contributors
Lennart Regebro, regebro@gmail.com
Changelog
1.1.2 (2013-06-06)
Change the action to “Message history” to be clearer about that it’s not a full email system.
1.1.1 (2013-05-08)
Put latest mails on top.
1.1 (2013-05-07)
Changed the logic in what got stored.
1.0.1 (2013-04-26)
Bugfix in the install of the MailBox action.
1.0 (2013-04-26)
Initial release.
Metadata
Release files for collective.mailbox 1.1.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.mailbox-1.1.2.zip | 26.1 kB | Without provenance | Details for collective.mailbox-1.1.2.zip |
Release files / collective.mailbox-1.1.2.zip
| Download URL | collective.mailbox-1.1.2.zip |
|---|---|
| Size | 26.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5b585c277a928dadefcd9f767c1c4696a897849b156fed82174756b1a9d47934
|
|
BLAKE2b-256 checksum How to use checksums |
340057bf0101ba3a6f3ff6652092c95a17c450ff35be1fea5a0e2b16e9433eb6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.mailbox 1.1.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.