From: James Henderson <james@lo...> - 2003-11-03 06:28:07
We are delighted to announce the first beta release of MailManager. The
focus of this release has been some major rewriting and structural change
to ensure the robustness and maintainability of the product in its future
post-release development. It was not the intention to add major new
features but two have in fact been introduced, both happy by-products of
the continuing development.
Automatic fetching of mail from POP3 or IMAP4 servers is now integrated in
the product, which should greatly simplify installation. This feature has
arisen from work on an in-house operational support system and is designed
to handle multiple MailManager instances constantly being added, removed,
moved and refreshed. It should therefore go beyond the requirements of
most users. We would be grateful for testing and feedback on this feature
in particular. If, however, you do not wish to use it, it can be disabled
by setting the environment variable MAILMANAGER_NO_CHECKTHREAD to anything
other than an empty string.
Messages can now be exported in the form they were originally sent.
Individual messages or whole tickets can be retrieved, the latter in a
Unix mailbox format. There is as yet no pretty interface for this: simply
call "export" on a ticket or message through the URL. This feature was
made possible by the re-design of the Message class outlined below.
Message instances from the Python email package have always been used both
to parse received messages and for sending replies. The MailManager
Message class is now constructed directly from these instances and
implemented as a wrapper around them. As well as simplifying much code
this allows the retrieval of the user's original mail, a feature that has
always been promised in the documentation.
As a step towards per account security settings there is new folderish
Account class, and all the accounts are stored within a separate folder
called "accounts". Code for the fetching and handling of incoming mail
has been moved into this class.
Code for creating e-mail messages through the web has now been brought
together in a single new module, along with some utility functions for
parsing and sending mails. The new module properly encodes both header
and body text entered in any character set. Most useful for sending
replies to customers, the new functionality is also available when
creating tickets, test messages, and automatic replies and notifications.
Version 2.4.2 of the Python email package that we distributed for the
benefit of those using Zope with Python 2.1 was found to have a bug in
Utils.parseaddr(). A new 3rd Party tarball has been created containing
v2.5.4 of the package, in which the problem is fixed.
The dependency on the MailHost product has been removed. This was not
part of our 3rd Party tarball anyway.
The bugs reported at the end of last week have been noted but are not
fixed in this release. Thank you very much for the reports and we will
fix them very soon.
We are immensely grateful for all the feature requests, bug reports and
other feedback we have received over the last months. We encourage
everyone to test this beta release and give their responses so that a
final release can be produced as soon as possible.