October 2006 (beta 12 and 13):
- There is now support for the IMAP "modified UTF-7" encoding for high-bit characters in MercuryI.
- The Mercury loader.exe has been reworked:
- From this point on, if it detects more than the maximum number of allowable crashes in any period, it will quarantine the current contents of the mail queue in a subdirectory of the queue directory (the name of the subdirectory is the date and time of the crash). It will then try restarting Mercury and if the abnormal terminations continue will only then stop trying to restart the program.
This should deal with the occasional case of a spam that is so badly mangled that it causes Mercury to crash whenever it tries to process it.
- The loader will now also create a log of the restarts it makes, and will be able to send a short mail message to the postmaster after each abnormal restart as well.
July 2006 (beta 10 and 11):
- Mercury now automatically sets its affinity to processor 1 on the system, working around some multi-processor instability issues. A new commandline switch, "-A " allows you to control this behaviour: replace "" with "0" to allow the program to disable affinity and run on all processors (not recommended at this point), or with a bitmask to specify the processor on which Mercury should run.
- A new mail filtering rule action is provided that allows you to insert fragments of text into mail messages (for instance, if you want to add a disclaimer to a message). It will correctly handle plain text, HTML, messages with attachments and any variations thereof. It *won't* handle digests or messages that contain only another message (i.e, MIME "message/xxx" types), nor will it be able to in future. It's smart enough to modify both the text and HTML parts of multipart/alternative messages. In the rule, you provide the name of a file containing the text fragment to add:
if you create a matching file with the same name but the extension .HTM, Mercury will assume that it contains custom HTML data and will use that for HTML messages. If no HTML version exists, it will add the plain text version between <Blockquote> </Blockquote> tags. For HTML messages, the added text is inserted immediately before the </body;> tag, or if there is none, before the </html> tag.
- New delivery status notification code has been added: it should no longer ever generate DSN's for the "<>" address, and there is considerable new code to handle queue synchronization between the DSN generator and MercuryE.
- Mercury allows you now to specify that the reaction to any RBL should be to drop and short-term blacklist the connection. This won't happen until the MAIL FROM command is received (to allow clients a chance to issue an AUTH command), but definitely results in reduction on RBL polling. See the RBL definition editor in the MercuryS "Spam control" page for this.
July 2006 (beta 8 en 9):
- The problem with missing diagnostics in delivery failure notifications should now be fixed.
- You can now have Mercury generate delivery status notifications. These are generated when a message is delayed in the queue for certain predefined periods (the default settings are 3 hours, 24 hours and 72 hours). The DSN is created using a new template file called DWARN.MER (a sample will be included in the release). DSNs can be disabled entirely if you wish, or more usefully, generated only when the sender has a local address or an address served by a local alias.
- The core module configuration dialog has been reorganized so that it now has a new "Mail queues" page bringing all the queue control settings (including the new ones) together. The help has also been updated to reflect this change.
March 2006 (beta 7):
- A small but insidious memory leak that could result in excessive memory use over a longish period of time is fixed. This fix *only* affects sites using MercuryI (memory would be lost on each disconnection from a mailbox).
- There is a dedication for Mercury in memory of Mert Nickerson: you can see this on the "About Mercury" dialog.
December 2005 (beta 6):
- The main change in this version... TER. The TER editor is now implemented in the content control rule editor, this has a number of significant effects, in particular:
- Unlimited file size
- Find and Replace commands (F5 and F6 respectively)
- Multi-level undo on Ctrl+Z
- There is now a rudimentary queue monitor in the core module's console window. It gives a completely accurate snapshot of the queue, updated at two-second intervals.
- The source of the problem the script-kiddies were using to break into MercuryH is found and have been fixed.
November 2005 (beta 5):
- MercuryI should now support the AUTHENTICATE command and the PLAIN SASL method.
- There is a fix to deal with a thread synchronization problem affecting MercuryI, which could result in Mercury crashing at unpredictable intervals (i.e, disappearing and being restarted by the loader) under heavy IMAP loading.
October 2005 (beta 4):
- Mercury can now deliver mail directly to public folders.
This is done using a new type of alias - a "public:" alias, which allows you to associate any e-mail address with a directory on your system. Mercury handles filename arbitration and other delivery issues for you automatically.
So, for example, imagine that I set up this alias:
reports@pmail.gen.nz == public:M:\users\sfolders\reports.mai
once in effect, it would result in all mail sent to reports@pmail.gen.nz being written directly into the public folder shown in the alias as .CNR files ready for accessing using Pegasus Mail.
September 2005 (beta 2 and 3):
- MercuryE now keeps a short-term list of unreachable or unreliable sites and skips over them if it encounters them again during a pass. This should heavily improve performance when there are jobs in the queue that would normally block MercuryE threads repeatedly.
- New jobs are now always inserted at the head of the queue list, so they get attempted before any retries. This should also improve throughput when there are "recidivist" jobs in the queue.
- mercury.exe -s
This tells Mercury to run in "service mode", completely suppressing its user interface. Everything should still work fine, but the only way you can shut it down is using the Task Manager...
May 2005 (beta 1):
- Four new functions have been exposed to Daemons. This change should have flowthrough benefits for SpamWall users.
- A new version of CL32.DLL has been linked into the program for SSL support.
|