Inbox.py: SMTP Server for Humans
This is the simplest SMTP server you’ll ever see. It’s asynchronous.
One instance should handle over one thousand emails per second.
Usage
Give your app an inbox easily:
from inbox import Inbox
inbox = Inbox()
@inbox.collate
def handle(to, sender, subject, body):
...
# Bind directly.
inbox.serve(address='0.0.0.0', port=4467)
You can also defer to the commandline:
if __name__ == '__main__':
inbox.dispatch()
$ dasinbox.py 0.0.0.0 4467 [2012-04-28 07:31] INFO: inbox: Starting SMTP server at 0.0.0.0:4467
Installation
Installing Inbox.py is simple:
$ pip install inbox
2 maintainers
Metadata
2 maintainers
Release files for inbox.py 0.0.6
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 |
|---|---|---|---|---|
| inbox.py-0.0.6.tar.gz | 3.2 kB | Without provenance | Details for inbox.py-0.0.6.tar.gz |
Release files / inbox.py-0.0.6.tar.gz
| Download URL | inbox.py-0.0.6.tar.gz |
|---|---|
| Size | 3.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c177729cdefae1c8ee69323f825a71fb1d7aa460bf7662c283e4e66b92bd2047
|
|
BLAKE2b-256 checksum How to use checksums |
f88883a984a22f9ec048428b5a13b070a7a48543ae5992f254eccb48a65dbd72
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for inbox.py 0.0.6
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.
