---------
A tool to show the subjects of new mails in your Maildir hierarchy.
usage: mw.py [-h] [-c CONFIGFILE] [-d] [box [box ... ]]
optional arguments:
box ... List of mailboxes to examine
-h, --help show this help message and exit
-c CONFIGFILE, --configfile CONFIGFILE
Config file to read (default: $HOME/.mwrc)
-d, --debug Enable printing of debug info to stderr.
Notes
-----
Mw does not care about the actual Read/Unread flags fo your messages, it
only cares if the mail is in the new/ subfolder of a box. This means that
it only shows mails that have not yet been moved to cur/. Some mail clients
move *all* mails they encounter to cur/ and just ste the unseen flag for
them. Those mails will *not* be shown by mw.
Mw tries hard to parse Subjects, but not everybody knows how MIME works.
hence, mw sometimes displays "(none)" or may replace unprintable characters
with question marks (depending on your setting of "unprintables" in .mwrc).
This is /not/ a shortcoming of mw, but of the senders mail infrastructure.
That said, mw usually shouldn't throw error messages at you for this; if
it does, please contact the author.
Author: Tobias Klausmann <klausman () schwarzvogel.de>
License: GNU GPL-2
Metadata
Release files for mailwatch 0.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 |
|---|---|---|---|---|
| mailwatch-0.2.tar.gz | 11.6 kB | Without provenance | Details for mailwatch-0.2.tar.gz |
Release files / mailwatch-0.2.tar.gz
| Download URL | mailwatch-0.2.tar.gz |
|---|---|
| Size | 11.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1e489737704f61fa0df4fbaf4e022186e4158b10ef8e944011bc901c27c79060
|
|
BLAKE2b-256 checksum How to use checksums |
e7ee82aec570bf5eedc49f1aae83c1fd04ff1b7a185cdba57af125e4a7fb1eb0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for mailwatch 0.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.