This release is a pre-release and may not be stable for production use.
collective.memberemails will send email notifications for the steps of the approval process implemented by pas.plugins.memberapproval.
It will send an email to a configurable administrator email address when a user is registered, and it will also send an email to the user when the user is approved or denied.
The emails and the administrator notification address is configured in the “Member registration email settings” control panel at the url <yourhost>/@@memberemails-settings
Contributors
Lennart Regebro, Author
Changelog
1.0a2 (2012-06-26)
Now handles the separation between pending and disapproved statuses.
Checking the login time was not reliable, and is no longer needed.
1.0a1 (2012-05-31)
Initial release
1 maintainer
Metadata
1 maintainer
Release files for collective.memberemails 1.0a2
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 | |
|---|---|---|---|---|
| collective.memberemails-1.0a2.tar.gz | 13.0 kB | Without provenance | Details |
Release files / collective.memberemails-1.0a2.tar.gz
| Download URL | collective.memberemails-1.0a2.tar.gz |
|---|---|
| Size | 13.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5ad991893d618ba4009ab63dd25d40909087be8ae46c8de9ab1e16140c784861
|
|
BLAKE2b-256 checksum How to use checksums |
610a4dc80cef3f054539f77f6bef9f5e03d2018e2fa94c65fa8419ee1c4c8c1b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.memberemails 1.0a2
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.
