leap.mail
Mail services for the LEAP Client.
More info: https://leap.se
running tests
Use trial to run the test suite:
trial leap.mail
… and all its goodies. To run all imap tests in a loop until some of them fails:
trial -u leap.mail.imap
Read the trial manpage for more options .
imap regressions
For testing the IMAP server implementation, there are a couple of utilities. From the leap.mail.imap.tests folder, and with an already initialized server running:
./regressions_mime_struct user@provider pass path_to_samples/
You can find several message samples in the leap/mail/tests folder.
0.4.1 - 18 Apr, 2016
Features
#7656: Emit multi-user aware events.
#4008: Add token-based authentication to local IMAP/SMTP services.
#7889: Use cryptography instead of pycryptopp to reduce dependencies.
#7263: Implement local bounces to notify user of SMTP delivery errors.
Use twisted.cred to authenticate IMAP/SMTP users.
Verify plain text signed email.
Validate signature with attachments.
Use fingerprint instead of key_id to address keys.
Bugfixes
#7861: Use the right succeed function for passthrough encrypted email.
#7898: Fix IMAP fetch headers
#7977: Decode attached keys so they are recognized by keymanager.
#7952: Specify openssl backend explicitely.
Fix the get_body logic for corner-cases in which body is None (yet-to-be synced docs, mainly).
Let the inbox used in IncomingMail notify any subscribed Mailbox.
Adds user_id to Account (fixes Pixelated mail leakage).
Misc
Change IMAPAccount signature, for consistency with a previous Account change.
Metadata
Release files for leap.mail 0.4.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 |
|---|---|---|---|---|
| leap.mail-0.4.2.tar.gz | 159.9 kB | Without provenance | Details for leap.mail-0.4.2.tar.gz |
Release files / leap.mail-0.4.2.tar.gz
| Download URL | leap.mail-0.4.2.tar.gz |
|---|---|
| Size | 159.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f184fbd81ffda9680cb96b66c0198e5a65b570da017404fb5af8825d350e3ce1
|
|
BLAKE2b-256 checksum How to use checksums |
03a6a698b789e18a8ce5d3933e8d9a912e39de2351feb515d9ff46334dae02e8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for leap.mail 0.4.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.