<p>Please be patient, there will be disruptions to the community service for a few days, because the server farm is being moved, this week (last week of September 2016)<span style="font-size: 10pt;"> </span></p><p>This week the lease contract where all the servers are, is closing down. JM (landlord) will tear down the house in the new year and build apartments on that area. My company is the last to move out, which has to be before october 1st. I've been putting this up as long as possible, but now there is finally a fixed deadline.</p> <p>Therefore I'm moving the servers this week. There will be disruptions to my services from tomorrow tuesday 27th at 17:00 hours (swedish time). The move of the servers start with some smaller servers, then dns, that I've already begun. But the major jobs I have planned for wednesday afternoon and night our local time.</p><p>Cheers / Peter<span style="font-size: 10pt;"> </span></p>
I've released Mercury/32 v4.80 publicly, but I won't be updating the web site or other public sources other than the community until Sunday (my time). The idea is to give the loyal folk on the community a little head-start in getting the new release. Get the release file at .
As another bonus for the community... Starting with v4.80, I've been forced to increase the price of the entry-level license (1-15 users) from $75 to $95, but if you get in and place your order before I update the web pages on Sunday, you'll still only pay the old price.
Version 4.8 is probably the most heavily-tested build of Mercury we've ever brought out, and has a huge amount of version 5 technology already in place. The next stage will be an initial release of version 5 where the user interface is completely separated from the mail engine, which means you'll be able to run the UI and consoles even on systems where Mercury is running as a service that cannot normally interact with the desktop: because this part of the conversion is already largely complete, you can expect to see this initial v5 release before the end of the year.
In the (I sincerely hope) unlikely event that you encounter a problem in v4.80, please post it in the forums here and I or one of my test team will get onto it as quickly as we can.
All my very best regards to you all,
-- David -- David Harris, Author, Mercury and Pegasus Mail.
Some of you may have read about a recently-discovered vulnerability in a product called OpenSSL that is being called the "Heartbleed bug". A good summary of this problem can be read on Brian Krebs' security blog, here:
Builds of Pegasus Mail earlier than v4.7 did not use OpenSSL and are completely immune to this bug.
Pegasus Mail v4.70 uses an affected version of OpenSSL, but the problem is not serious for client implementations - only servers are seriously affected by this problem. Pegasus Mail users can continue to run the current v4.70 build of Pegasus Mail to connect to their normal e-mail servers without any practical risk of being affected by this vulnerability. That said, I have already prepared a patched version of OpenSSL that is immune to the Heartbleed bug, and will be making it available for download as soon as the test team has finished verifying that everything still works normally with it. Pegasus Mail v4.70 users should install the patched version when it becomes available as a simple matter of prudence. Pegasus Mail v4.71, which will be released in the next few weeks, will include the patched build of OpenSSL as a matter of course.
Current builds of Mercury (anything up to and including v4.70) do not use OpenSSL and are unaffected by this problem. Mercury/32 v4.8, which is in the final stages of development at present, *does* use OpenSSL, but will be released with the patched build of OpenSSL from day one.
So, the long and the short of it is that if you're a current user of Pegasus Mail or Mercury, then the Heartbleed bug is not a matter of significant concern to you.
On September 6th, Thomas Stephenson passed away in his sleep. Many of you will have encountered Thomas over the years - for over 15 years now, he has been a major driving force behind Pegasus Mail and Mercury, particularly in supporting those people who use them. Thomas was capable of handling support loads that to this day I can barely understand: having burned myself out on support years ago, it was always a source of ceaseless amazement to me that he could continue offering his help day after day without apparently ever tiring of doing so. In this role, he will be missed.
Thomas was a vocal supporter and driver of the programs. When I had my "meltdown" in 2007, Thomas was one of the key steadying voices who helped me through the bad times, and his input into the shape and form of the programs for over 15 years simply cannot be measured. In this role, he will be missed.
A few years ago, Thomas, and his wife, Donna, visited me in Dunedin, where I live. I had the privilege of spending most of a day with them, showing them around Dunedin and having lunch with them at a little restaurant by the beach. It is surprising how few of my long-term beta testers and supporters I have ever actually met in person - a fact that makes me quite sad any time I think about it, but at least I was fortunate enough to meet Thomas. In the fifteen years that I knew him, I came to regard Thomas as a real friend, and while that would have been true even if I had never had the opportunity to spend some time with him, the memories will be that much stronger and better for having done so. And it is in this role, as a friend, that he will be most missed of all.
To the friends of Thomas R Stephenson: Tom (my dad) passed away last night from end stage lung cancer. He died peacefully in his sleep at home 2 months after his cancer diagnosis. He was joking up until the end.
September 5th 2011: Pegasus Mail v4.62 now available for public distribution
Version 4.62 mainly concentrates on fixing late-breaking
incompatibilities in HTML rendering caused by the release version of
Microsoft's Internet Explorer 9 browser. V4.62 users should experience
reliable, high-quality HTML display using this version, with the quality
of rendering being even higher than in previous versions.
Updated editor V4.62 also uses a heavily-updated version of
the editor module we use, and has numerous changes in the way editing
buffers are constructed, meaning it should now be able to edit and reply
to much more complex HTML message formats than previous versions, and
editing should be much more reliable.
Open link in background You can now Ctrl+Click on any link
in a message to open that link in your web browser without bringing the
browser to the foreground. This allows you to open a succession of links
then work with them when you're ready.
Signatures overhauled The way signatures are handled has
been totally overhauled, and you should now find they work considerably
better when you insert them at compose-time.
Faster POP3 downloads POP3 downloads should be significantly faster when you have chosen to leave mail on the POP3 server.
Finally, quite a few small bugs, some of them quite long-standing, have now been fixed.
We expect this to be the last release in the V4 family of Pegasus
Mail, with the next release being the first iteration of the V5 family, which we plan to release in a staggered pattern to ensure more regular updates.
I apologize to everyone for the length of time it has taken to get v4.62 out the door - many of the changes it required were quite subtle, and testing has taken a lot longer than we initially expected. I am trying hard to adjust the way development is conducted to allow more regular releases to be made, and hope you will bear with me in the meantime.
Pegasus Mail v4.52 is now available for public download.
V4.52 is all about allowing the program to work well under Windows 7: it can now use the new Microsoft mechanisms for registering itself as a system-level mail program (meaning it can be used to launch mailto: links from your web browser), and corrects a number of minor issues in previous versions, in particular the problem with some toolbar buttons either not displaying or displaying incorrectly. There are also some internal reliability fixes to do with the way certain types of folder damage are handled.
Producing a Windows-7-capable version of the program required migrating the Pegasus Mail source code from Microsoft Visual Studio 2003 to Visual Studio 2008: we expected this process to be easy and quick, but we were wrong - Microsoft made it much more difficult than should ever have been necessary. This is the main reason it has taken us as long as it has to get this release out the door. An unfortunate side-effect of this is that Visual Studio 2008 generates applications that cannot be run under Windows 98 or ME. As a result, v4.52 no longer works on these older versions of Windows. As I've noted in the information on the main Pegasus Mail site, we will see what we can do about putting together at least a matching version of v4.52 that *can* run under Windows 98 and ME, but it's clear that we are not going to be able to support these systems for very much longer.
Pegasus Mail v4.52 can be downloaded from the main Pegasus Mail web site, at : it will be made available here on the community as soon as humanly possible.
Pegasus Mail v4.51 is now available for unrestricted public distribution - please visit for downloads and information, or check the download pages here at the community. The release version has had significant work since the public beta at the end of last year, and has some powerful new capabilities, most notably the addition of autofiltering folders.
The release of v4.51 marks the end of one of the most difficult development periods in the history of the program, and it seems appropriate that it should coincide with my attempts to ensure the long-term survival of the package: from here, development should be both easier and faster, and I do not anticipate ever again having such a long delay between releases. Your assistance is crucial to making this happen though, and if you haven't already done so, I would ask that you read the open letter at the main web site and see if you are able to help. To all of you who have already pledged your support, I offer my sincere thanks.
No version of Pegasus Mail has ever been as extensively or exhaustively tested as v4.51 - it's been a huge job, but ultimately rewarding, and my test team and I hope that you really enjoy using it.
A release candidate for Mercury/32 v4.71 is now available at . We intend to make this available only at the community site for a week or so before releasing it on an unrestricted basis.
The big news in v4.71 is the ability to run as a native Windows Service: we (the test team) have been using it extensively in this mode for quite some time and it's really quite cool. There are quite a few other small new features in there, and over 200 fixes and corrections.
Feedback is welcome in the Mercury beta forum here.
2009-02-14 Wiki On-Line Today we welcome you to the all new pmail Wiki!
A Wiki is an on-line documentation repository, where you can contribute. The wiki supports both Pegasus Mail and Mercury MTA, and it is multilingual. Try it out at .
For a while there has been a wish to be able to extend the documentation of Pegasus Mail and Mercury Mail Transport Agent, plus concentrate information from various sources into one general repository. Today we proudly invite all users to contribute into creating the definitive guide to e-mailing in general, and about how the programs work in particular. All this will during 2009 be concentrated to http://wiki.pmail.com
In short time the knowledgebase documentation will be transferred onto the wiki, as well as the official software documentation, including help subsystems and development guides. Currently the closed beta team members concentrate in their free time on merging the documents, but this is a vast task. Pegasus Mail exists in several languages, but Mercury does not. Translation has always been a rather gigantic task. Both programs are used all over the world. Wiki.pmail.com therefore supports multiple languages, and you are all encouraged to pitch in and extend the documentation into your language.
Developers of daemons and extensions are most welcome to publish their how-to guides and accompanying documentation in this one place repository.
The basic idea of a wiki, is that anyone can suggest and contribute to completing the information. Seldom are the ones with deepest information equiped to write guides on how to use things, as the users themselves. At http://wiki.pmail.com anyone can add, correct or extend the information so that it is as comprehensible and complete as can be.
For those not so familiar with wikis, you may want to look at the original http://wikipedia.org site and you'll find a world of information. We have built http://wiki.pmail.com according to the same syntax, and on the same platform - to ease the use and contribution, and it is our hope that the pmail wiki will be of benefit to you all. The wiki contains a sandbox, were you can familiarize yourself with editing and contributing.