Re-send captured emails using SMTP
This tool, ‘mailreplay’, is intended to help in testing email pipelines by reading captured emails from files, figuring out the sender and recipient, and re-injecting them to localhost:25 using SMTP. (If the captured emails have a final recipient on a different system than localhost, you need to make sure that the MTA is blocked from sending the emails out into the world during testing.)
An initial envelope From line is used as the sender, if available. Otherwise, the email header From: field is used. The email header Received: fields are used to figure out the envelope recipient.
Many other tools exist that will read an an email from file and send it using SMTP, but they all seem to have in common that they need to be given the recipient address on the command line, and by default will use the logged-in user as the sender address. For email pipline testing purposes, when a varied set of senders and recipients are desired, this doesn’t scale easily, hence this tool.
Changelog
Version 0.2.0 (06 Mar 2019)
There’s now enough usage experience to bump this to Beta
Added a manpage file.
Improved handling of the case when there’s no Received headers in the replay message.
Metadata
Release files for mailreplay 0.3.0
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 |
|---|---|---|---|---|
| mailreplay-0.3.0.tar.gz | 40.9 kB | Without provenance | Details for mailreplay-0.3.0.tar.gz |
Release files / mailreplay-0.3.0.tar.gz
| Download URL | mailreplay-0.3.0.tar.gz |
|---|---|
| Size | 40.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4b32b958edbf5ea28ae39adb0ced52267b37c73c0180007f31f2527d6339e0a8
|
|
BLAKE2b-256 checksum How to use checksums |
4d5dff376cc133977c7615aff67d730f202f97df6ff203928368eabf98c57e55
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Python-urllib/2.7
|
Security for mailreplay 0.3.0
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.
