Donate Share

MailManager

File Release Notes and Changelog

Release Name: 2.0.10

Notes:
MailManager

  MailManager allows organisations to manage large volumes of
  email. It helps allocate mail to the right people, provides tools
  for responding to mail quickly, allows full text searching of mail
  and finally produces reports on volumes of mail received and
  performance in responding to it.  Full user documentation is in
  user_guide.pdf and administrator_guide.pdf at http://www.logicalware.com/

Legal Note

  (c) Copyright Logicalware Ltd 2002-2005 logicalware mail
  manager comes with ABSOLUTELY NO WARRANTY. Further details including
  conditions of redistribution are contained in LICENSE.txt
  http://www.logicalware.com/

Supported Platforms

  MailManager is cross platform and has been tested on Linux, Windows
  and Mac OS X. It should run fine on any platform which supports
  Python.

Database

  A relational database is required to store the email. Both PostgreSQL and
  MySQL are supported by this release. For PostgreSQL, version 8.0.x is
  recommended, although the code has been seen to work against version 7.4.x and
  above. Note that MailManager currently doesn't work with PostgreSQL 8.1 --
  this will be fixed in the next release. For MySQL, 4.1.x or above is required,
  and internal testing has been done against 4.1.11. Future release will add
  more database support.

  PostgreSQL must be installed with plpgsql support and the tsearch2 package
  in order to provide text indexing.

  PostgreSQL is available from http://www.postgresql.org/

  Additional documentation on database configuration is available in the docs
  directory. Windows users should consult the additional documentation at 
  http://www.logicalware.org/win32install/ for a walkthrough.


MySQL Support

  MySQL support is now considered to be stable, and no remaining bugs have 
  been found either by our internal testing or by our test suite. As with all
  software, it is still possible that some bugs remain. Where possible, we 
  would still recommend that PostgreSQL be used as opposed to MySQL where 
  there is no compelling reason to choose otherwise. The PostgreSQL support is
  more mature and more extensively tested. 

  In order to use the MySQL support, you must use our own modified version of
  the ZMySQLDA available in the 3rdParty products download at:

    https://sourceforge.net/project/showfiles.php?group_id=85788&package_id=89598

  Hopefully these changes will be merged with the upstream version soon.

  Documentation on installing or configuring MySQL support can be found in the
  docs directory.

  Issues with the alpha release have now been resolved. In  order to implement 
  text searching in MySQL, there are some auxiliary tables which are in MyISAM 
  format. The consistency of these tables is now covered by a test suite. 

  A new attribute, mysql_max_packet_size, has been added to the MailManager
  object, which represents the upper limit of a message in the database. If
  set, this parameter will be used on all MySQL sessions where size is deemed
  relevant, otherwise the system setting with be used. For most distributions
  this is set to 500kb. By default, we are setting this to 50MB. The value of
  this setting can be configured via the Zope Management Interface (ZMI)

  At present, the choice of database back end is fixed at installation time.
  Options to change from one database platform to another may be added in a
  future release.

Other Requirements

  If you are using the Windows installer all of the following required software
  will be installed for you automatically.

  MailManager is a Zope product. Zope 2.7.5 or later is required, as earlier
  versions of Zope contain a memory leak in the session code which will make
  MailManager unreliable. Zope is available from http://www.zope.org/ .
  MailManager should now work correctly with Zope 2.8.x, so long as you are
  using the latest release (at least 1.4.2) of FileSystemSite, though most
  of our testing still happens on the 2.7.x series, so your mileage may vary.

  CookieCrumbler version 1.1 or later is required, available from
  http://hathaway.freezope.org/Software/CookieCrumbler

  Epoz version 0.5.1 or later from:
  http://www.zope.org/Members/mjablonski/Epoz/

  FileSystemSite 1.4.2 or later from:
  http://www.infrae.com/download/FileSystemSite

  mxDateTime version 2.0.3 or later is required:
  http://www.egenix.com/files/python/mxDateTime.html

  PlacelessTranslationService version 1.0 or later from:
  https://sourceforge.net/projects/collective

  Strip-o-Gram version 1.4 or later is required:
  http://www.zope.org/Members/chrisw/StripOGram/ 

  TimerServer 0.1 or later is recommended but not required:
  http://dev.legco.biz/products/timerservice/

  ZopeScheduler 0.2 or later is recommended but not required:
  http://dev.legco.biz/products/ZopeScheduler/

  For PostgreSQL support, the following is also required:

    psycopg including ZPsycopgDA version 1.1.21 or later from:
    http://initd.org/projects/psycopg1

  For MySQL support, the following are also required:
 
    MySQLdb version 1.2.0 or later from:
    http://sourceforge.net/projects/mysql-python/  

    ZMySQLDA from our own 3rdParty package:
    https://sourceforge.net/project/showfiles.php?group_id=85788&package_id=89598

  CookieCrumbler was written by Shane Hathaway.
  Epoz was written by Maik Jablonski.
  FileSystemSite is by Kapil Thangavelu and Zope Corporation.
  mxDateTime was written by eGenix.com Software GmbH.
  psycopg is by Michele Comitini and Federico Di Gregorio.
  Strip-o-Gram was written by Chris Withers.
  PlacelessTranslationService was written by Lalo Martins & Zope Corporation.
  TimerServer and ZopeScheduler were written by Nikolay Kim.
  MySQLdb and ZMySQLDA were written by Andy Dustman.

  For convenience these eight products are in the 3rdParty package. To
  install the just need to be put into Zope's products directory and
  then Zope should be re-started. If you plan to use TimerServer refer to
  its INSTALL.txt file for its slightly different installation procedure.


Client Requirements

  A web browser is required to use MailManager. To access all of the
  features, including the built-in HTML editor, you will need to use
  Internet Explorer 5.5 or later, Mozilla 1.3.1 or later, Netscape 7.1
  or later, or Firebird/Firefox 0.7 or later.

  MailManager has also been tested on Safari, Konqueror 3 and Opera 7,
  and is fully functional other than the HTML editor.

  Please let us know through the bug tracker on SourceForge if you
  find any browser issues.

MailManager Installation

  Finally, MailManager itself needs to be installed.  (Since v1.0 an
  installer has been available for Windows (see below) but the
  following paragraphs should still be useful for Windows users to
  explain some of the options offered by the Windows installer.)

  Start Zope and login to the Zope Management Interface (ZMI). This will
  usually be at the address http://127.0.0.1:8080/manage

  From the 'Add' menu select 'Z Psycopg Database Connection' and create a
  connection with the id 'mailmanager_db'. Make sure that "Use Zope's Internal
  Date Time" is checked.

  MailManagers can now be added by selecting 'MailManager' from the 'Add' menu.
  For the purposes of these install instructions we will assume that MailManager
  is added with the id 'mailmanager' but it can of course be called anything.

  Optionally you can specify a schema when you install MailManager. PostgreSQL
  schema allow you to have multiple MailManager instances sharing a single
  database. In most cases you can simply leave this field blank.

  You can now log into MailManager by visiting
  http://127.0.0.1:8080/mailmanager

  The next stage is to get mail into MailManager. There are two
  different approaches: getting mail from a POP3 or IMAP server, and
  forwarding mail directly into MailManager. These methods can be
  mixed, so some accounts can get their mail while others have mail
  forwarded.

  Get Mail Method (ZopeScheduler)

    To use the get mail method, login into MailManager, create some
    accounts though the Settings tab and set routing to 'Get from
    server'.

    Go into the Zope Management Interface (ZMI) and select 'Zope Scheduler'
    from the 'Add' menu. Within the scheduler you will need to select a path
    which would be '/mailmanager' in our example and then select a frequency.
    Mail will then be collected from the POP3 or IMAP server(s) at that
    frequency.

  Get Mail Method (Classic)

    Mail is fetched by calling the getMail method of the MailManager
    instance.  For example, if you installed MailManager with the id
    'mailmanager' in the top level directory of Zope then you can call
    getMail by visiting http://myserver:8080/mailmanager/getMail.

    To ensure that getMail is called regularly you can setup a cronjob,
    or equivalent on your platform, to call the MMGetMail.py script, say
    every 10 minutes. You will need to set the MM_URL constant in the
    script to the actual URL of your MailManager instance.

  Forwarding Method

    To use the mail forwarding method, login into MailManager, create
    some accounts though the Settings tab and set routing to 'Incoming
    mail forwarded to Account'.

    Next configure your mail system to call the MMMailIn.py script when
    new mail is received (or MMMailIn-Qmail.py script if you use
    Qmail). You can normally do this though a .forward file. You will
    need to set the MM_URL constant in the script to the actual URL of
    your MailManager instance.

Windows Installer

  The Windows installer bundles MailManager with Python, Zope and the
  other Zope products it depends upon.  It allows configuration of the
  first MailManager instance and of the first Account in that
  instance.

  It is known to have the following limitations:

  o The Zope service that it may install does not work properly.

  o There is meant to be an option to install using an existing Python
    installation but this has not been fully implemented yet.

  o When it launches the browser at the end of installation the server
    may not be ready yet.  This is easily handled by refreshing once
    the server is ready, but it would be better to launch a static
    README with a link to the server, as Zope does.

  o Not all the possible account settings are configurable through the
    installer.

  o It does not guard against illegal value for settings.

  o The larger wizard image is distorted.

Chinese, Japanese and Korean Email

  If you want to be able to read email with Chinese, Japanese or Korean
  encodings you will need to install the CJKCodecs which are available from
  http://cjkpython.i18n.org

  These codecs are only required for Python 2.3 as they are included in Python
  2.4 and later.

Test Tickets

  You may wish to generate some Tickets for testing purposes. Visit
  http://127.0.0.1:8080/mailmanager/GenerateMail and you will be presented with
  a form allowing you to specify how many test Tickets you want to generate.
  You must have set up at least one Account before generating test Tickets.

Upgrade

  The procedure for upgrading is the same as for installation. However after
  the upgrade you must visit the Zope Management Interface (ZMI) and on each
  MailManager click on the 'Migrate' tab to ensure that all of the ticket and
  account information is migrated to work with the new version. You should back
  up your data first.

  Note that if you upgrading from MailManager 1.0 or earlier you must ensure
  that the BTreeFolder product is installed until you do the migration.

Further Information

  Further information is available from the Help screens within
  MailManager and from the User and Administrator Guides.

  Subscribe to the MailManager Users mail list for discussion, help and
  announcements of new versions at
  http://lists.sourceforge.net/lists/listinfo/mailmanager-users


Changes: Version 2.0.10 * SECURITY FIX - Added in fix for security issue Postgres encoding security hole (#1494281) The code in the 2.0.9 and previous releases may be vulnerable to this issue, depending on your postgres configuration. The exploit may allow an attacker to alter data in the SQL database and gain access to the web interface as an administrator. You are strongly advised to upgrade. Version 2.0.9 * BUG FIXES - Cite last cites the wrong message (#1471644) - Formatting broken on templates for HTML (#1477664) - No HTML response for HTML Required (#1472881) - Selecting No change results in a failure (#1467786) - Automatic addition of attachments (#1459924) - Importing fails with alternative timezone (#1485389) - UI Allows creation of empty groups (#1486433) - getMail raises postgres index error on addMessage (#1492488) Version 2.0.8 * BUG FIXES - Non existant refresh value leads to security error (#1466274) - Cannot create HTML tickets (#1466223) - Archive and Restore functionality broken (#1452514) - Unicode from addresses break incoming mail (#1440861) - Changing format away from HTML generates a Zope error (#1460216) - Email sent from Macs/Linux to Windows aren't formatted (#1440850) - Valid tags are stripped from HTML on sending (#1460262) - Encoding Error with signatures (#1440862) - Installing test suite data fails (#1463368) - Fixed issue with non-ascii filter condition (#1438720) - Cite last includes only replies now (#1369571) - Direct cycles of support_of are not allowed now. (#1353210) - Tickets without a subject no longer result in a permissions error (#1436863) - Test dataset has broken messages (#1422365) - Account and User drop downs now work with Internet Explorer (#1410232) - Ticket date is set to application server date by default (#1444200) - Test suite no longer generates testsuite.log unless set in config Version 2.0.7 * BUG FIXES - Fixed the setting of next ticket id for MySQL, no longer silently ignores the option on mailmanager creation and fixes migration (#1412787) - Send and Close, Send Reply, Send and Hold and Add Note have all been considerably refactored. This resolves the problem reported where outbound messages had been silently discarded (#1415497) - getMail could potentially drop incoming messages whilst collecting from POP3 accounts. This has now been corrected, and a test case now exists which reproduces the existing problem and demonstrates it being fixed. (#1422985) - i18n fix - on the ticket modify screen "closed" is no longer displayed as "open" when languages other than English are used (#1423422) * IMPROVEMENTS - Massive improvements to the test suite. Version 2.0.6 * IMPROVEMENTS - We're now using html2text (included) instead of stripogram for converting HTML to its plain text equivalent (when sending out HTML mail, we also include a plain text alternative for those who can't read HTML messages). This results in far prettier plain text conversion. * BUG FIXES - Notify user/group flags can now be set/cleared correctly on account preferences (#1404595). - Improved address validation. Well, it's now a bit more lax, but it's completely conformant to RFCs 2821 and 2822 (#1396051). - MySQL: Default categories are now set up at installation (#1392386). - HTML parts of multipart/alternative messages are now encoded as UTF-8 rather than, bizarrely, being forced into ISO-8859-1 (#1368283). - Make sure the user is informed about *why* test data cannot be removed (#1345788). Version 2.0.5 * NEW FEATURES - Tickets can now be created by sending an email (RFE 859117) - Italian translation. * BUG FIXES - MySQL: Adding a user fixed (#1382479) - MySQL: Users are now migrated correctly (#1378323) - MySQL: Attachments can now be of virtually any size (#1378224) - MySQL: MailManager will now start when psycopg is not present (#1378209) - MySQL: The first message ID is now 0, fixing migration from MM11 (#1364247) - PostgreSQL: Migration works even if response target update fails (#1374603) - Search now works for users in all timezones (#1375345) - Reports and delete tickets works in all timezones (#1381828) - The test data now sets 'routing' on the accounts (#1375764) - Fixed parsing of mails containing NULL characters (#1370866) - MMImport.py script now uses new URL (#1378385) - To: field left empty when sending email (#1377027) - Create Ticket fails when logged in as customer (#1369356) Version 2.0.4 * BUG FIXES - Prevent multiple users replying to the same ticket by accident (#1371269) - Filters got broken in 2.0.3, change reverted (#1372814) - Attachments now set the Content-Type header correctly on download (#13369349) - Template names with trailing whitespace now work (#1363768) - Set sql_charset on the mailmanager object during migration. (#1369347) Version 2.0.3 * BUG FIXES - Be more careful about adding and removing the test data (#1353112, #1345788). - Improve the Unicode support with the MySQL back end (#1338614). - Support of can now be removed with MySQL back end (#1338603). - Fixes to the response target settings (#1336398, #1337506). - setSession correctly clears the offset and always redirects to Tickets (#1350429). - Offer MySQL back end as a migration option (#1340301). - Tickets now correctly marked as unread with MySQL back end (#1344827). Version 2.0.2 * BUG FIXES - Ignore the showHTML information in the session for plain text emails. Reapplied previous bugfix (#1242337) - Resetting response target to None now updates database (#1336398) - Reports for targets fixed (#1337506) * IMPROVEMENTS - Now has setupdb script for MySQL users - Split off setupdb code, now available as separate module - Added in documentation for MySQL configuration Version 2.0.1-release * BUG FIXES - Disk usage screen now fixed for empty instances (#1244446) - Initial Manager use now has correct roles set (#1324878) - Altering roles now works correctly (#1324876) - Update of response target now works correctly (#1324935) - Removing notification flag for users/group now works correctly (#1315000) - Migration now works correctly for 1.1 instances (#1291113) - Setting response targets no longer generates an error (#1324884) Version 2.0.1-rc2 * BUG FIXES - No longer depends on psycopg due to import statements - Migration fixes for MySQL users - Fixed some scoping issues causing ZSQL methods to break due to acquisition. * IMPROVEMENTS - SQL Directory no longer uses FileSystemSite.DirectoryView meaning that the SQL methods can be overridden by 3rd parties. - Test suite now has added hooks for overloading object types Version 2.0.1-rc1 * BUG FIXES - Test suite now covers text search cache consistency, cleared issues with MySQL's mysql_max_allowed_packet variable - Postgres support now appears stable Version 2.0.1-beta1 * BUG FIXES - Merged in all of the changes between 2.0r6 and 2.0r7 - Fixed the index bug which was resulting in duplicate tickets being displayed on the list page Version 2.0.1-alpha1 * NEW FEATURES - Adds in initial MySQL support - SQL methods given addition parameters to deal with new MySQL support - Vastly improved test suite - regression test suite for the database code. Version 2.0r7 * BUG FIXES - Subsequent pages for search were not being returned due to misuse of the SESSION variable. These are now handled correctly (#1276412) - Categories and templates were moved entirely to SQL. Upgrade needs a migration to function correctly. (#1276414) - listTicket method now correctly searches for subjects - Fixes a Unicode handling error in the MailMixing class, which could potentially block up incoming mail * IMPROVEMENTS - Postgres installation documentation rewritten - Changes to loading of test datasets - Test data set improved, now covers more functionality Version 2.0r6 * BUG FIXES - Fixed the positioning of the order by section of the listTickets query, fixes broken ordering for search. - The listCategories SQL method was broken, which was used by the Reports pages. Reports for categories other than category0 were broken. Version 2.0 * BUG FIXES - Fix the security declaration of checkPOP3SSL(). Version 2.0 RC 3 * NEW FEATURES - Introduce some generalisations, ready for MySQL support in 2.0.1 - Beginnings of epydoc API documentation. * BUG FIXES - Update the version number on migration. (#1229769) - Robustify the autoreply code to deal with fatal errors. (#1240870) - When a new message comes in with a ticket id in the subject line, verify that the ticket already exists instead of assuming that it does. (#1240711) - Format the email address in the To: field for replies. (#1230837) - Ignore the showHTML information in the session for plain text emails. (#1242337) - Record the logged in user who sent a reply to a ticket. (#1242958) Version 2.0 RC 2 * BUG FIXES - multipart/alternative mail with both an HTML and a plain text body now only display one of them at a time (1227265) - Disk usage is now displayed correctly for 0 bytes (1227745, 1227753) - Migration updates the mm version - Create ticket works again (1227744) Version 2.0 RC 1 * BUG FIXES - Stripogram can now be installed as a Python product in site-packages (1226633) - Reply-To: header is used in favour of From: (1226156) - Notifiction emails can handle non-ASCII subject lines (1224784) - URLs are now accurate on notification emails (1224756) - Character encodings set correctly on all web pages (1224731) - Send & Close now goes to the next ticket (1224164) - Improved date parsing (1223755) - Respond By: now displayed for tickets with a response target (1222528) - Attachment titles are now decoded correctly (1223974) Version 2.0 Beta 2 * BUG FIXES - Make the email validation less strict. (1283401) - Customers can no longer have email addresses which are used by an account. (1216414) - Migration: Drop filters which refer to unknown users/groups. (1216361) - Migration: Be more careful about coercing dates into ISO8601. (1216534) - Clarified notification email setup. (1217403) - Fixed Chinese translation. (1215645) - Store time zone information in the pgsl database. Version 2.0 Beta 1 * NEW FEATURES - Added a Chinese translation. - Add some documentation for creating the Postgres database and point to detailed docs on the Windows installation process. - Updated the help files to reflect the new version's feature set. * BUG FIXES - Make mbox exports have a more meaningful filename. - Deal with RFC2047-encoded headers correctly. (1212035) - Make the disk usage a bit more friendly. (1213604) - Sanitise outgoing HTML mail (mostly to remove malicious Javascript). (1211895) - Epoz now has a white background on all browsers. (1208912) Version 2.0 alpha 2 * NEW FEATURES - Support for retrieving POP3 mail over SSL (RFE 1204236) - Optionally notify all in a group of new messages (RFE 1208284) * BUG FIXES - Help tab no longer visible after logout (1207656) - Adding a MailManager instance now creates an initial user (1207022) - Changes to users such as adding a signature no longer clear password (1207017) - HTML tickets work properly (1205720, 1205717) - Time to close tickets recorded (1204825) - Reply to all button improved (1204805) - Reassignment notification added (1204372) - Groups redesigned (1204312) - Adding/removing attachments no longer clears other form fields (1204272) - Date translations fixed (1204268) - Templates fixed (1204267) - Overdue tickets function properly (1203141) - Performance v. account report fixed (1196685) - GetMail fixed (1196606) - Referential integrity broken on mm_message table (1194418) - Login link on logout page fixed (1204811) - Signature handling improved (1204877) - HTML email fixed (1204987) Version 2.0 alpha 1 * NEW FEATURES - A complete redesign using PostgreSQL as a replacement for the ZODB in order to improve performance and scalability. - Can now use SMTP servers that require a login (RFE 939720) Version 1.1 * NEW FEATURES - Internationalization of the help documentation. * BUG FIXES - Make sure that sending mail out is the last thing done, which should reduce the window where a ConflictError would cause duplicate emails to be sent. - Soft bounce messages in MMMailIn{,-Qmail}.py if the error was anything other than a MessageParseError. Otherwise we wind up hard-bouncing (instead of retrying) on a ConflictError. Version 1.1-rc5 * BUG FIXES - Comptatible with Zope 2.6/Python 2.1 again Version 1.1-rc4 * BUG FIXES - Standard attachments fixed (1110435) - Clear supporter link fixed after i18n problem (1110436) Version 1.1-rc3 * NEW FEATURES [Unfortunately it was essential to add the following features at this late stage for commercial reasons.] - Added archive/restore tickets (RFE 953290) - Create ticket can now have multiple attachments (RFE 987700) - Replies can also have multiple attachments (RFE 859141) - Standard set of attachments can be stored on the system (RFE 985469) * BUG FIXES - Edit of mail headers now works properly (RFE 859102) - Fixed broken migration Version 1.1-rc2 * BUG FIXES - Now possible to add/edit account without SSL (1090041) - Spam tickets no longer appear on the 'New' tickets list Version 1.1-rc1 * NEW FEATURES - Users notified on re-assignment of tickets (RFE 978035) - Internationalisation (i18n) added ready for translation to other languages. - Support for SSL connections to remote IMAP server. - Any mail headers may be used in filters (RFE 859102) * BUG FIXES - Report graphs now work for user-defined categories (978404) - File downloads now work when there is a space in the filename (985150) - Remove support ticket feature fixed (985677) - Users no longer notified if spam is received (1059104) - Spam no longer displayed on default ticket listing views - Templates with names ending in a space may now be deleted/edited (1003514) Version 1.0 No changes from 1.0-rc2 Version 1.0-rc2 * NEW FEATURES - Batch classification of tickets. (RFE 859114 and 957719) * BUG FIXES - Migration works when filters are of mixed formats. (945956) - Migration works when groups are of mixed formats. (945959) - Messages from mailer-daemon with a real name do not cause a loop. (952864) - Works on Firefox for Mac when reply has no attachment. (963291) - Report graphs work for more than 200 tickets in a period. (964144) Version 1.0-rc1 * NEW FEATURES - Choice of date format. (RFE 869827) - Choice of timezone (currently only on Unix). (RFE 869827) - Script to import mail from Unix mailboxes. (RFE 903031) - Shortcut icon. - Importing of tickets enabled. * IMPROVEMENTS - Added global error slot and adjusted settings screens to use it. (873232) - Message response form fields remembered in request. - An instance's children may be migrated even when it is not. * BUG FIXES - Mail check thread delays till Zope is ready in 2.7 as well. (835642) - GroupSettings page template works with new-style groups. (887785) - Problems sending mail caught and reported to the user or logged. (892947) - Message ID added to outgoing messages. (895039) - Newlines in the Cc field no longer break the JavaScript. (904033) - Private notes and replies no longer lose headers in migration. (904076) - Private notes may no longer have a To field. (912534) - Ticket ownership transferred when user deleted. (925344) - Customers are persistent. (930654) - Sending files with a bad mime type does not cause an exception. (934133) - HTML templates no longer have extra breaks added. (934235) - MailManager.getMail() returns an empty string on success. (934902) - Add customer form checks fields are filled. (938631) - Fixed links to AccountSettings page. (938678) Version 1.0-b4 * BUG FIX - Fixed error when a new thread is started and notification is on. Version 1.0-b3 * NEW FEATURES - Supporter mechanism for associating tickets fully implemented. - URLs in messages rendered as hyperlinks. - Filters can assign to groups as well as users. * IMPROVEMENTS - Assigned agent mailed at every new message in ticket, customer only when he starts a new ticket. This reverses the previous behaviour. - Tickets can be re-opened by arrival of a new message or through Ticket Details box. - Migration version distinguished from product version. - Group now a class; ensures that group members are assigned to evenly. - By default users only see tickets assigned to them. - Export (view raw messages) link added to Ticket index page. * BUG FIXES - Account signatures are now used. - HTML setting on auto replies and templates respected. - Agents can be deleted. - Several others (see SourceForge bugs 859030 to 873233). Version 1.0-b2 * NEW FEATURES - Migration - HTML messages may now be viewed. - Most recent search results always available. - Response target added as option in filters and create ticket screen. * IMPROVEMENTS - More robust ticket navigation (works with virtual hosting, "prev"/"next" links always available, "list" goes to batch containing current ticket). - Improved handling and presentation of attachments. - Help screens updated (not quite finished). - Improved interface to reports (still needs work though). - All character sets displayed correctly (as far as the browser's fonts allow). - Mail fetching scripts have an option to specify MailManager's URL . - Search by from name no longer requires exact match. - Much Python code removed from page templates. * BUG FIXES - Overdue ticket view and searches for overdue tickets now work. - Automatic mail checking continues after product is refreshed. - Numerous others (see SourceForge bugs 832932 to 858688). Version 1.0-b1 - Dependence on MailHost product removed. - Message class now wraps Message object from Python email package, allowing mails to be retreived in their original form. - Automatic mail fetching introduced. - Code for creating e-mails through the web brought together in a new module and handling added for text entered in any character set. - Each account is now a separate folder, ready for per account security settings. - Fetching and handling of incoming mail moved to new Account class. - Self service interface to allow customers to manage their own tickets. - Better handling of HTML emails. - Create ticket now has more sensible defaults. - Users now deleted properly. - Calculates an approximation of disk space used. - Added Property Managers to ease debugging. - Users with 'Settings' access can no longer view ZMI. - Numerous bug fixes. Version 0.96 - By default, shows newest tickets first rather than oldest - The subject of a ticket can now be changed - If more email is added to a read ticket it goes back to being unread (bold) - Advises if an attachment is of a dangerous type (for Windows users) - Attachments now download with original filename & security improved - Browser bug in IE prevented selection of user on tickets screen (797221) - Two extra user definable categories added - Code tidied up & minor bug fixes Version 0.95 - Added a 'Spam' status and amended reports, tickets & filters accordingly - Can now delete spam tickets without closing them (783289) - Now handles AppleDouble attachments correctly (787671) - POP3 mailbox lock removed if there is an error (787677) - IMAP mailbox lock removed if there is an error - Mails that can't be processed are now stored raw rather than deleted - Added 'priority' and 'assigned' to Search screen (785360) - Basic export of reports to Excel implemented - Now record and report on times to close as well as times to respond - Other minor fixes Version 0.94 - Ticket status is displayed correctly in all circumstances - Adding attachments when creating a ticket thru the web now works as expected. - Users can be notified of new tickets in all circumstances (783955) - Allow selection of fields to display on tickets screen (783863) - Added submenu to the Create ticket screen - Other minor fixes Version 0.93 - Improved attachment handling and display - Improved ticket navigation (now back/list/next on ticket view) (780783) - Fixed a bug in the reporting graphs where the last day in the month could be missed - Added an auto refresh option for tickets screen (feature request 781294) - By default tickets created through the web are assigned to the logged in user, rather than the first user alphabetically - Improved outgoing mail - More advanced standard filter - Tightened up security - Help button now context sensitive Version 0.92 - Adding a user with the Reports permission now works as expected (779986) - Account deletion now works properly (779989) - Admin password now hidden on the Add MailManager page (779987) Thanks to Ronan Amicel for spotting these four bugs. - Ticket deletion system improved. - Supporting tickets system now works better. Version 0.91 - Fixed the Account Help screen. Now displays properly and text is accurate. - Fixed the 'Change details' section on a ticket screen so the user the ticket is assigned to is displayed by default. Also ensured user names are displayed in alphabetical order. - Categories can now be deleted. Deleted categories will still appear in Reports, System Settings and on the Search page until every ticket with that category has been deleted from the system. Thanks to Kevin Gill for spotting these bugs. Version 0.9 The first open source release of MailManager. Based on the commercial version however with some major changes: - Uses the Zope Object DB instead of an external relational database. This changes the performance, it is faster in some areas and slower in others. It makes the product much easier to install. - Use of HTML to generate the graphs. Not as attractive as the commercial version but saves the difficulty of installing extensions which were not stable on all platforms. - Improved text editor. Epoz is used to provide rich text editing allowing easy creation of HTML mail. - Improved text indexing. Greatly expanded query options. - Bug fixes. A number of minor bugs were fixed.