Introduction
slc.mailrouter bridges the gap between zope and email. It is based on the same idea as products such as mailboxer: a script is invoked by your mail transfer agent (postfix, exim) and the body of the email is passed to this script on stdin. This is then communicate to zope using an http post, where it is parsed and handled.
This package implements the smtp2zope script.
Metadata
Release files for slc.smtp2zope 2.1
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 |
|---|---|---|---|---|
| slc.smtp2zope-2.1.tar.gz | 3.8 kB | Without provenance | Details for slc.smtp2zope-2.1.tar.gz |
Release files / slc.smtp2zope-2.1.tar.gz
| Download URL | slc.smtp2zope-2.1.tar.gz |
|---|---|
| Size | 3.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bf7357bacfebc551c4c8cc0f62328e1f39b03db4e861acbc669a85b087b61524
|
|
BLAKE2b-256 checksum How to use checksums |
6815c6d12f1d90a9a5d71f927a79d7f1acdf88cbe867febbc7487dbf0f753543
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.5.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.61.0 CPython/3.8.0
|
Security for slc.smtp2zope 2.1
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.