Official announcements from either or David Harris.

PiS posted Dec 8 '08 at 12:11 am

Community.Pmail.Com now has native support for the following languages, Dutch, French, German, Italian and Swedish, besides English.

We have also added international Community support forums in Dutch, French, German and Italian. The aim is to make a natural point of interest and a global repository of information regarding the products: Pegasus Mail and Mercury Mail Transport System.

To enable your preferred languague, you have to set your language in your profile. Your profile is reachable by clicking your name, which is displayed at the top right of all community pages.

We've also made some minor changes to the forum names, and merged some quite similar forums into more obvious forums.

It is my personal hope that you find this change easier and more appealing in your use of the forums.

Pmail.Com posted Sep 3 '08 at 3:58 pm

Downloads are now available from the community.

Pegasus Mail Public Beta v4.51 (German)

Please use the Beta forum for any discussions regarding the beta versions.
Forum posts will be moved when they relate to the beta and have been published in the wrong forums. We are aware that moving forum threads creates trouble for those that keep up with unread posts, so please adhere to this policy.

David Harris posted Aug 4 '08 at 3:15 am

As many of you have noticed ( <wry grin> )  the time between releases has in recent years been getting longer and longer, both for Pegasus Mail and Mercury.

The long period between releases does not, however, mean that nothing is happening: there are numerous reasons for the longer development cycles, many of which I have covered in my blogs, and in the background, there are many, many releases of beta versions of the program that are only ever circulated to members of the current closed beta test teams. To give you an example, there have been 22 formal betas of Pegasus Mail v4.5, and numerous informal betas where I wanted to try out a specific feature.

After consultation with my closed test teams, we've reached the conclusion that the community and the quality of the programs would be best served if we opened up the beta testing process: making betas available publicly would allow wider testing, as well as giving a clear, visible indication that the programs are alive and in active development.

Accordingly, after the release of Pegasus Mail v4.5 (which will be very soon now - we're testing release candidates at present), I will be opening the beta process. Most betas will be made publicly available on this community for both programs, and forums will be provided for feedback. Betas will be provided without support, typically will not include installers, and will be intended to be installed only by experienced users.

Watch this space for further announcements.


-- David --


UPDATE - 30 July 2008: Top marks to Ironport - they got onto me very rapidly and have been extremely helpful. It now appears that this problem is a combination of an ISP who is blacklisting his own netblocks (doh!), and a slightly ambiguously-worded error response from the Ironport appliance involved. It appears at this stage that the problem is an isolated occurrence, and that there is no cause for concern. But I want to reiterate how wonderful it is to encounter a large vendor this responsive - excellent work, Ironport.

----------------------------- Original posting below -------------------------------------

It's been brought to my attention that a large company that develops anti-spam mail server appliances, Ironport (, may have begun rejecting mail sent by Pegasus Mail because it erroneously believes Pegasus Mail is a spam generation program. [:(] [8o|]

We're still investigating this and will keep you informed, but for now, if you find at any stage that you get a mail message returned to you with a 554 diagnostic that talks about your message not being accepted because of the "poor reputation of the MTA" you're using, please let us know on the forums.

If anyone here knows how to get in touch with Ironport Systems (their web site is essentially purely a marketing site and has no technical value), we'd also be very grateful if you could let us know.

-- David --

David Harris posted Jul 3 '08 at 8:53 am

A new kit for the development of Mercury/32 Daemons (or plugin processes) is now available for public release from our web site. This kit allows programmers to create Daemons that integrate tightly into the Mercury environment, extending its capabilities. As examples, the SpamHalter, GrayWall and ClamWall plugins shipped with Mercury are all Daemons.

For more information on the Mercury/32 Daemon Development Kit, please visit our web site at .


-- David --

David Harris posted Jul 3 '08 at 8:52 am

Mercury/32 V4.62 is now available for public release.

V4.62 fixes a problem in v4.61 where sites who had not turned on the new "DST-Proof UID" feature in the MercuryP POP3 server could get duplicate message downloads under certain circumstances. It also includes some adjustments to the installer program during upgrades, and has some minor internal changes to the Daemon interface for future development.

Mercury/32 v4.62 can be downloaded from our official download pages, at .


-- David --

David Harris posted Jun 22 '08 at 5:07 pm

Mercury/32 v4.61 has now been released for public consumption - please visit for more information and downloads.

I apologize for the rather delayed release - we've had a very frustrating sequence of last-minute problems come up, all of them fairly small, but significant enough to justify holding the release while they were fixed.

The new feature list for this release appears at the end of this message.

Cheers to all!

-- David --


V4.61 includes a large number of minor fixes (over 300

by our count), and some notable new features:

  • Notifications and alerts

     If you purchase (or have already purchased) a

    license for Mercury, you can now enable automatic checks

    for new releases and updates, security bulletins and

    general information about the program. To take advantage

    of this feature, see the new Alerts and notifications

    option on the Mercury Configuration menu..

  • Lingering Mailboxes  This

    is a new performance option for the MercuryI IMAP server,

    especially aimed at people using "stateless"

    IMAP clients such as webmail packages. When it is turned

    on, Mercury defers breaking down the memory image of

    the mailbox when an IMAP connection terminates; if a

    new connection for the mailbox arrives before the standdown

    period has elapsed, it can be reused at once, hugely

    reducing the startup time for IMAP connections. Enable

    this option in the "Files" page of the "Core

    module" configuration dialog.

  • IMAP INBOX now cached

     The Mercury IMAP server now caches the IMAP inbox,

    meaning that connecting to it will be significantly

    faster than in previous versions.

  • IMAP Server performace


     Server performance, particularly

    when opening large folders, has been dramatically improved.

  • DST-proof POP3 UIDs

     Because of a long-standing bug in Windows, the

    MercuryP POP3 server in the past reported different

    UIDs for messages after a change in Daylight Savings

    Time, resulting in clients re-downloading messages they

    had already seen. This problem has been fixed in v4.61,

    but the fix is disabled by default, because enabling

    it will cause one last re-download. You can turn it

    on whenever you're ready in the MercuryP configuration


  • MB_MLSS heavily improved

     MB_MLSS, the MercuryB module that allows web-based

    management of mailing list subscriber settings, has

    been heavily overhauled. It now has options allowing

    subscribers to retrieve their passwords if they have

    forgotten them, and to change settings for all lists

    to which they are subscribed. As well, users can now

    select lists from drop-down controls instead of typing

    in their names (if you have 50 or fewer lists), and

    the service manipulates mailing lists directly, rather

    than going through the Maiser mail server interface.

  • Mailing list password auto-assignment

     Mercury's mailing list manager can now be instructed

    to auto-assign passwords for new subscribers to mailing

    lists. This, combined with the new capabilities of the

    MB_MLSS module (see above) makes mailing list management

    easier and more secure.

  • SMTP server enforces size


     In previous versions of

    Mercury, the SMTP server could be told to refuse incoming

    messages larger than a particular size, but only if

    the connected client used the ESMTP SIZE declaration.

    In v4.61, MercuryS now refuses *any* message larger

    than the size you specify, whether or not there is a

    SIZE declaration. This change *might* confuse some older

    SMTP client programs (we expect this to be a very rare

    occurrence if at all), but has become increasingly important

    in the age of spam and mail-borne viruses.

  • POP3 Server completely


     The MercuryP POP3 server

    has been totally overhauled, and is now substantially

    faster than in previous versions.

  • POP3 login-time listing


     This powerful new feature

    allows users to control the messages the Mercury POP3

    server will show them by adding a simple command to

    their POP3 username... For example, if you only want

    to see urgent messages from the ""

    domain, you would login to your POP3 mailbox as username

    (urgent, The constraints that are

    available are described in more detail in the Mercury

    manual and online help. We anticipate this feature

    being especially useful for people who use cellphones

    or other low-grade connectivity devices to check their


  • MSendTo commandline mailer

     This new utility allows you to send mail from

    the commandline. It is quite sophisticated, and can

    generate a wide range of message types, including digests

    and unlimited numbers of MIME attachments. MSendTo can

    be used in scripts or called from programs to send mail

    via Mercury.

  • Threading in the core module

     In the past, the Mercury core module has been

    single-threaded (meaning that it can only ever be doing

    one thing at a time). With increasing processing of

    mail via external processes such as Mercury policies,

    SpamHalter, Content Control, filtering rules and so

    on, the time it takes to process a message in the queue

    has been getting longer and longer. As of v4.61, the

    Mercury core module now supports limited threading (it

    runs up to seven worker threads), which significantly

    improves queue throughput on heavily-loaded systems.

  • Many, many fixes,

    including problems with IMAP UIDs being lost or duplicated

    after crashes, problems with the loader queue quarantine

    message being delivered multiple times and others.

As well, a comprehensive new developer guide and sample

code for people interested in developing their own Mercury

Daemons is nearing completion and will be made available

in the next few weeks: an announcement will be made here

when it is released.


In recent days we see a lot of attempts to utilize the issue that the above patches mend.

If you notice within Loader.Log (found in your server directory) that recently states multiple rows of "Restarted Mercury after apparent abnormal termination" you should suspect that you have been hit by attempts of exploit. Within MercuryS.Logs (depends on how you have set logging) you may find parallel log entries (same date and time as Loader.Log entries) stating multiple AUTH CRAM-MD5 - then you know you are hit - and should as soon as possible mend your system.

Lastly, within the MercuryS console window, you may see a connection as the attached image, hanging for a long time, - then you know you have been hit by people trying to exploit your un-updated Mercury.

So - Regard the updates as highly critical since it forces your server to restart if you are using the loader utility.

I personally thank David for his expediate attendance to this issue.

David Harris posted Jun 16 '07 at 3:44 am

Mercury/32 v4.51 is now publicly available.

Although on the surface v4.5 will not appear markedly different from v4.01, "under the hood" it's quite a different story. The code has been heavily reworked in almost every area, focusing heavily on robustness, reliability and performance.

A download link and list of new features in v4.5 is available at

Starting with this release of Mercury, the licensing model for the program has changed. Mercury remains completely free for non-commercial use, but commercial users will need to purchase a license if they wish to continue using it after a 60-day evaluation period. We have attempted to produce a licensing program that is both very inexpensive, and completely non-intrusive. Details and pricing can be found here:

Please note that if you have a current support subscription at any level under the old Pegasus Mail Support Consortium arrangement, you are automatically entitled to a Mercury site license at no charge - please contact me directly to arrange this.

A personal note: I'm acutely conscious that it has taken an abnormally long time to get this release done. One of the lessons I have learned from the problems in getting v4.5 complete is that I need to open up the beta testing process so that more people have greater access to betas and patches more often. I will be developing a strategy for this over the next couple of weeks.

Any problems or issues arising from this release can be raised either on the public mailing list at, or in the Community forums at our community web site,


-- David --

David Harris posted May 11 '07 at 3:31 am

I apologize in advance for what might seem like shameless panhandling, but I could use some assistance...

Is there anyone out there with a Novell NetWare 6.5 Server+10 user license (or larger) that they no longer use and might like to donate to a good home?  The declining use of NetWare means that the costs of sustaining my subscription to Novell's developer forums is becoming unjustifiable, but if I cancel my subscription I'll need a formal license I can install to allow for ongoing support and any further development that might be required.

Alternatively, if there is an organization out there that feels generous enough to donate the cost of a license, I'd be most grateful for the support.

If you can assist in either way, please .

And now, back to normal service...


-- David --

Sub Categories
Hide topic messages
Enable infinite scrolling
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft