What's new in Mercury/32 v3.31?

What's new in Mercury/32 v3.32?

August 2002: Mercury/32 v3.32 is primarily a bug-fix release: it corrects a problem in the MercuryE and MercuryC SMTP clients that could lead to crashes when messages with pathologically long lines were processed, and has a wide range of corrections and enhancements to the MercuryI IMAP4 server: sites making use of the IMAP server module should regard v3.32 as a mandatory upgrade. There is also a new Compliance page in the MercuryS SMTP server that allows you to reject certain types of message before they even make it into your mail queue, and the MercuryE SMTP delivery client can now generate transcripts, which provide reasonably effective proof of delivery for messages. Click here to go to the downloads page, where you can retrieve Mercury/32 v3.32

What was new in Mercury/32 v3.31?

May 2002: Mercury/32 v3.31 is a major upgrade of the system, including new protocol modules and some very powerful new features. If you are unfamiliar with Mercury/32, you may want to examine a general overview of the program by clicking here.

IMAP: MercuryI, the Mercury/32 IMAP server module, is now a standard component of the Mercury/32 release. Long in development, MercuryI allows IMAP4rev1-compatible mail clients such as Pegasus Mail, Mulberry and Outlook to access entire mailbox structures in a managed way.
Policies: This powerful new feature allows you to create your own external tasks to examine mail messages. Mercury provides support for things like attachment unpacking - all you do is put together a script, batch file or program that does the processing you need, then tell Mercury how to invoke it. As an example, it takes about 10 minutes to create a virus scanning policy to check all your mail for viruses, even if the virus scanner does not understand Internet message encodings. Policies are found on their own page in the Mercury Core Module configuration dialog, and there is extensive help for them in the help file.
Content control: Are you sick to death of spam? So are we. Mercury now has one of the most comprehensive content examination and control features we could put together. Using the new content control option, you can apply tests of aribtrary complexity to incoming mail and take any of a number of actions based on the results. A clever weighting system allows you to aggregate a number of points with varying levels of importance during the evaluation. A default rule set is included that catches about 80% of the unwanted mail passing through Pegasus Mail Central these days - all you have to do is turn it on and decide on the action you want to take.
Blacklist overhaul: Mercury now allows you to create a practically unlimited number of blacklist definitions (for services such as the RBL, or ORDB), and the functionality available for testing the returns from those blacklists has been thoroughly updated.
NetWare support: A new NDS-mode enabler has been included with this version: the new enabler allows you to specify an object that Mercury should try to look up in the NDS database before starting any mail transaction. This approach, while a little rough and ready, allows Mercury to work reliably in an environment where servers are occasionally unavailable.
Programmable autoresponders/autoreplies: Mercury now allows you to set up multiple automatic replies and have the correct one chosen based on factors like the day of the week, the time of day or the current date.
Numerous bug fixes: Many, many small problems have been addressed, especially in the MercuryE end-to-end SMTP delivery module.

Go to the downloads page to download this version
<< Return to the Pegasus Mail home page