MailArchive
What is MailArchive?
MailArchive is a product that can let the browse a mail archive in Unix MBOX format or connect to an IMAP account. The product resyncronises every ten minutes when the mail files change. It is therefore maintenance free. The product is tested on Zope 2.12, but can be made to work on Zope 2.6.
How to use it
First you install Products.MailArchive in the Products folder and restart Zope. You will now be able to create objects of the type “MailArchiveFolder” The form will ask you for some fields: the id, title, path to mail archive directory on the local disk, IMAP connection values. You need the “Add MailArchiveFolder” permission in order to add a MailArchiveFolder. Upon creation of this object, all the MBOX files inside this mail directory will be added to Zope.
For more complete instructions read docs/INSTALL.txt
Dependencies
This package works with Zope 2.12 and Python 2.7.
How to test it
Set up the environment variabiles for your Zope server in the ‘run_tests.bat’ file Run the tests using the ‘run_tests.bat’ file.
Linux users should do the same operations on run_tests.sh
Changelog
2.1 - (2020-03-03)
Change: Add jenkins badges [valentinab25]
2.0 - (2020-02-25)
Change: Develop #110159 [alecghica]
1.9 - (2020-02-14)
Change: Implement automatic release [valentinab25]
1.6 - (2020-02-14)
Feature: added support for Python 3 and Plone 5.2 [alecghica refs #110155]
Feature: updated Jenkins pipeline [alecghica refs #110159]
1.5 - (2016-06-07)
Fixed pypi issues
Fixed typos
Turn MailArchive into an IMAP client [chiridra]
1.4 - (2016-06-07)
Feature: cron job method added [chiridra refs #72719]
Feature: do not call update archives from front end [chiridra refs #72719]
Feature: added flag for forcing arhive update after save in Properties tab [chiridra refs #72719]
1.3 - (2016-06-06)
Removed version.txt [nituacor]
Fixed mbox zope id. [chiridra refs #72719]
1.2 - (2016-06-06)
Feature: Turn MailArchive into an IMAP client - add support for IMAP accounts - fixed encoding problems - fixed attachments download - cleanup [chiridra refs #72719]
1.1 - (2016-05-30)
Initial release
Release files for Products.MailArchive 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 |
|---|---|---|---|---|
| Products.MailArchive-2.1.zip | 61.7 kB | Without provenance | Details for Products.MailArchive-2.1.zip |
Release files / Products.MailArchive-2.1.zip
| Download URL | Products.MailArchive-2.1.zip |
|---|---|
| Size | 61.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e8f5aa8a072cc7af15c141dcdd465739dc42500c3a63d3915319571aeb95d1bb
|
|
BLAKE2b-256 checksum How to use checksums |
a811b7ffdc164973ca6495d01db0136d0d6641e879251054863e169539179444
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.15.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/44.0.0 requests-toolbelt/0.9.1 tqdm/4.42.1 CPython/2.7.17
|
Security for Products.MailArchive 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.
