Slashdot Mirror


Pegasus and Mercury Circling the Drain

Daemon Duck writes "One of the web's oldest and most respected email clients is flickering out of existence. Pegasus mail and its companion SMTP server, Mercury32, have been discontinued due to lack of funding for the ongoing development. On the website, the author David Harris states that if some funding becomes available he would consider opening the source code or continuing the development."

52 of 217 comments (clear)

  1. Why not open it now? by Cerberus7 · · Score: 2, Insightful

    If the funding has dried up, and he's prepared to move on to other things, why not open it? Pegasus was my first mail client, and I for one would like to see it bloom as an open source package rather than die a slow, horrible death as abandonware.

    --
    I don't know about you, but my servers run on the power of cotton candy and happy thoughts. -Anonymous Coward
    1. Re:Why not open it now? by Secret+Rabbit · · Score: 2, Funny

      No shit! It's like this guy is looking for a bribe to open the code.

    2. Re:Why not open it now? by Anonymous Coward · · Score: 5, Insightful

      To think that the project will automatically bloom by virtue of it becoming open source seems a bit presumptuous to me. Sure, it will definitely help towards it remaining a viable project, but taking a look at all the dead unmaintained projects in SourceForge tells me that having it open source is by no means a guarantee that it will bloom.

  2. What does funding have to do with making it open? by Zontar_Thing_From_Ve · · Score: 3, Interesting

    I went to the web page and see that, as reported by Scuttle Monkey, the author says he might continue working on it or make it open source with some funding. What does funding have to do with making it opern source? He could make it open source today if he really wanted to. It just seems to me that he's yet another guy who's pissed off that he can't make a living off the internet, so he's holding his source code hostage. I have to admit I know nothing about his program, but I fail to see the connection between open source and him getting paid.

  3. Opening the Source by TrailerTrash · · Score: 2, Informative

    From TFA:

    if sponsors could be found to provide modest ongoing funding, I would be happy to
    continue developing the programs, and would even consider opening the source.

    -------------

    Does it cost to open the source? It's not as simple as opening a SourceForge account and posting the source under the GPL?

    1. Re:Opening the Source by morgan_greywolf · · Score: 3, Insightful
      Does it cost to open the source? It's not as simple as opening a SourceForge account and posting the source under the GPL?


      Lots of people seem to be asking this, but the question that they don't ask is this: is the source to Pegasus and Mercury 100% an original creation of David Harris? If not, he may have to pay off other authors who wrote libraries or other code written by Harris. One reason so much of the Netscape source code had to be rewritten to produce Seamonkey (and ultimately Firefox), aside from so much of it being crufty, is that there was a ton of third-party code that came from Sun and other companies.

    2. Re:Opening the Source by heroofhyr · · Score: 5, Informative
      Here's a note I found in Google, but comes from the Pegasus site:

      As discontent with Microsoft's "business practices" grows, we have seen unprecedented interest in alternative solutions for operating systems and applications. As a natural consequence of this, I have received numerous, or maybe even innumerable requests for a Linux version of Pegasus Mail. As a corollary to these requests, I have had a lot of people suggest that I also move to an Open Source basis for maintaining the Pegasus Mail and Mercury source code.

      In the past, I have taken a cautious "wait-and-see" approach to the idea of Open Source. I am now willing to accept that it is a valid model, and that it is producing some genuinely excellent packages (such as FireFox, of which I am inordinately fond). Ideologically, I believe that Open Source and I are a good match, and I would like to consider going that way.

      There are still some major problems with the idea of going Open Source though: the most important is "How do I survive in an Open Source environment"? While Pegasus Mail and Mercury do not require a huge amount of money to develop and support, the fact remains that they *do* require a level of funding, and I am not entirely sure how this would work within an Open Source model. I feel it is significant that the majority of Open Source initiatives are either funded externally (Mozilla), or basically not funded at all (OpenLDAP, OpenSSL): it seems to me that while Open Source is an excellent technical solution to the problem of large-scale development using widely-spread teams, the area of Open Source business modeling is one that still has not been completely resolved.

      The other major issue with Pegasus Mail is that it uses a proprietary third-party product as its core editor, and I would not be able to take that product with me into an Open Source environment. The same problems do not exist with Mercury, because I have written every line of the package myself, but with Pegasus Mail, the problem is significant.

      So, there you have it: I am now favourably disposed to the idea of moving towards Open Source, but have to overcome some important issues before I go down that track. I am actively considering the issues and hope I can find workable solutions (such as a large, friendly, wealthy sponsor) in the not-too-distant future.

      Hopefully this update to my position will reduce the amount of hate-mail I have received in the last three years from Open-Source zealots. While I understand the passion and admire the zeal of these people, I would suggest that a positive approach is always going to work better than trying to rip out my liver and feed it to the dogs. After all, this *is* my baby - I have been working on these programs and providing them free of charge for over fifteen years now, and I don't believe it's too much to ask if I expect a little basic human courtesy.

      If you have suggestions and are willing to present them to me in a positive, encouraging manner, I will be happy to receive them.

      David Harris
      Owner/Author, Pegasus Mail and Mercury Systems,
      April 20th 2005.
      --
      brandelf: invalid ELF type 'KEEBLER'
    3. Re:Opening the Source by jfengel · · Score: 2, Insightful

      Theoretically, he could open the parts that he owns and leave it to other developers to replace the bits that he can't give away. Or ask you to download them yourself, the way you have to download lame separately from Audacity due to licensing issues.

      Nobody ever guaranteed that any particular piece of open source would compile.

    4. Re:Opening the Source by Andrewkov · · Score: 2, Insightful
      and I don't believe it's too much to ask if I expect a little basic human courtesy.

      You must be new here.

  4. Evolution in action by Generic+Guy · · Score: 3, Insightful

    One might be inclined to think Pegasus is flickering out of existance because is isn't open source. I remember early on moving from Pegasus to Eudora email because Eudora's simplicity and features were better. When Eudora became an advertisement-laden mess, the open source Thunderbird showed up to fill the gap and I haven't looked back. Now Thunderbird offers in-place spell-check and other features which were considered very advanced just a few years ago. Evolution in action.

    --
    { - Generic Guy - }
    1. Re:Evolution in action by i.r.id10t · · Score: 3, Funny

      No Evolution is that outlook like email app that comes with gnome...

      --
      Don't blame me, I voted for Kodos
    2. Re:Evolution in action by 99BottlesOfBeerInMyF · · Score: 3, Insightful

      Now Thunderbird offers in-place spell-check and other features which were considered very advanced just a few years ago.

      I can't help but express my disappointment that this is still an issue. Spellchecking should not be implemented on a per-application level. It should be implemented at an OS level and offered as a service to all applications (along with other such services). I mean sure it's nice to have spellchecking in your mail client and your word processor, but what about your chat client? What about in vi? What about in your Web browser and calendar and graphics program. More importantly, why should you have to train dictionaries for all of these programs separately? I already taught my layout program that MPLS isn't a misspelling, why should I have to do it again and again? And what about my grammar checker? Should I wait another four years until they add that to Thunderbird? What about online dictionary lookups, and thesaurus, and language translations, and bibliography references? All these things I can do today in most programs on Mac OS X, which is great, but it is high time Linux and Windows caught up. That would be evolution in action.

    3. Re:Evolution in action by Spacejock · · Score: 2, Insightful

      The best solution is to install spell checking in the brain. You can get a grammar checker, too.

      The downside is that they take ages to install and don't run with computer-like efficiency.

    4. Re:Evolution in action by patio11 · · Score: 3, Funny

      One thee pus said thee bran disambiguates butter.

    5. Re:Evolution in action by 99BottlesOfBeerInMyF · · Score: 2

      I, personally, don't want spellchecking in my OS, unless its a subsystem/service that can be disabled. I almost never spellcheck (not much of what I write is important enough to justify it) and I don't want to incur any operating system overhead. I just want it to make sure my applications don't crash!

      That's the point of implementing these at the OS level. One chunk of code running per function rather than on per function per application. Globally disabling and installing services is easy and if you don't use it in an app, it doesn't cost you anything. So maybe you couldn't care less about spellchecking. How about an MD5 checksum service? I have one of those installed. How about removing Windows style line endings? I have that too. How about looking up the highlighted function in the online docs? Application designers don't know everything you're going to do. By making the system modular everyone can install those services that they want/use and disable those they don't.

    6. Re:Evolution in action by 99BottlesOfBeerInMyF · · Score: 2

      You can have that now on linux, if you stick to KDE. (I imagine you can also have it if you stick to gnome) I have my mail client, web browser, IM program, word processor etc. with working spellcheck using the same dictionaries and, internally, the same component.

      The problem is this only works for KDE applications that know about the component beforehand (called Kparts) and specifically include it. As a result, sure a few integrate spell checking, but there is no way to tailor this for other functions the user may want. On OS X these are drop in services (literally you drop them in the Services directory) and all programs that use the native APIs can use services that apply to those APIs. That means even if the creator of my IM program did not think I'd use a grammar checker, if I install one I still can use it in my IM client. The same goes for a dictionary/thesaurus lookup, online reference lookups, language translations, bibliography auto-formatting, etc. Application developers cannot know all the functions I will and won't use, nor even what functions will be available. Maybe some commercial software I buy includes excellent translation of English to and from Japanese. The creator of Kopete can't assume most people will have this software, and can't build it into Kopete. On the other hand, on OS X, Apple may know nothing about this commercial translation app, but if the app provides that translation as a service, iChat can use it anyway.

      Kparts is better than nothing, but it is, in my opinion, insufficient. Building on the assumption that developers will know better than users what components each user will want, need, and have available is a very poor assumption.

  5. Pegasus for windows by Claws+Of+Doom · · Score: 2, Interesting

    It was a godsend for me when I first found it. Working for a rural publisher meant we got *big* files down our 56k line. The ability to see and manipulate the mail queue for those of us not fortunate enough to be on *nix was truly empowering. There was no webmail, no alternative. We had been downloading 30Mb files overnight to try and get at our email... Heh. Good old simple "viruses come on floppies" days :)

  6. well then... by macadamia_harold · · Score: 4, Funny

    It is official; Slashdot now confirms: *Pegasus is dying

    One more crippling bombshell hit the already beleaguered *Pegasus community when /. confirmed that *Pegasus market share has dropped yet again, now down to less than a fraction of 1 percent of all clients. Coming close on the heels of a recent /. survey which plainly states that *Pegasus has lost more market share, this news serves to reinforce what we've known all along. *Pegasus is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.

    You don't need to be a Kreskin to predict *Pegasus' future. The hand writing is on the wall: *Pegasus faces a bleak future. In fact there won't be any future at all for *Pegasus because *Pegasus is dying. Things are looking very bad for *Pegasus. As many of us are already aware, *Pegasus continues to lose market share. Red ink flows like a river of blood.

    There can no longer be any doubt: Pegasus is dying.

    1. Re:well then... by Pegasus · · Score: 4, Informative

      No, I'm not dying. I'm very much alive.

      In fact, I've just changed jobs and got a new pair of wings :)

  7. Re:long time user. by eln · · Score: 5, Insightful

    That's just it of course: Pegasus was a great product for its time, but has failed to keep up with competitors. Nearly everyone has already switched over to Thunderbird or something else. Pegasus is being replaced by technologically superior products, and now the developer can't find anyone willing to pay him to develop it anymore. This is no real surprise.

    The post is really just an attempt to get some money. The fact that he would continue to develop it if he were paid probably goes without saying. However, he's also saying he would "consider" opening the code if he were paid enough, suggesting that if no donors come forward, he would simple delete the code and completely kill the product. This suggests to me that he's not really interested in open sourcing anything, but that he'll write that he will (if paid) in order to increase his chances of getting press on open source-centric sites like Slashdot.

  8. Is it so complicated? by cascadingstylesheet · · Score: 4, Insightful

    >I have to admit I know nothing about his program,
    >but I fail to see the connection between open
    >source and him getting paid.

    1. One or more people want it to be open-sourced.

    2. The author (like you, unless perhaps you are
    a monk) wants money.

    An exchange either will or won't happen.

    If there aren't enough people in #1 above, or if they
    don't want it badly enough to pay, then maybe he will
    eventually give it away for free, like something that
    wouldn't sell in a garage sale or on EBay.

    He doesn't have to give his work away for free if
    he doesn't want to.

    1. Re:Is it so complicated? by Anonymous Coward · · Score: 2, Informative

      David Harris has NEVER made any money selling the product - he has always made his money from support contracts - so the lack of money isn't the reason he won't open source it.

      Here's a link to his official statement about Pegasus Mail and open sourcing it:

      http://www.pmail.com/sundry/pmlinux.htm

      I corresponded with him for a while, exploring the possibility of open sourcing it. He really has problems letting anyone else touch his code. I think it's almost a phobia, or just an attitude that "Nobody else could possibly code as well as he [thinks he] does."

      Also, he seems to have little or no experience working as part of a coding team, and constantly mentioned the "communication problems" he'd have to deal with. He also pointed out that the code would need cleanup before others could make progress on it, but (to me) that begged the question of why he didn't clean things up long ago - Pegasus had a good share of bugs still unpatched in later versions when I quite using it somewhere in v3.2.

      He also only wanted to "open source" it on his terms - a far cry from any existing Open Source licence. From my discussions with him, his idea of a license is: The code is his property, Anything another coder adds to it is also his property, Only he can distribute the product (including make any money from it). As I mentioned to him, that's not an attitude that will go anywhere in the open source community.

      Finally, as he mentioned in an article he had on his site - he doesn't think that any quality product has emerged from any open source project. Since his only experience is with DOS, Novell, pre-OSX Macs, and Windows - I'm not surprised.

      He did amaze me for years - singlehandedly developing and supporting Pegasus Mail (for DOS, Netware, Mac OS, and Windows), the Mercury mail server (for Windows and Netware), and related utility programs.

      Sometime back, pre-OSX, he decided to drop the Mac version despite the fact that a large chunk of his userbase was Mac users in educational environments. He dropped it because Apple dropped supporting Netware - but he could have kept developing the product for Mac and just have his Mac users user its existing standard Internet mail capabilities. Then he dropped the DOS version, then the Netware versions. Now he's dropping the whole thing.

      I think the root of the problem is that he has refused for years to bring any other coders into the work, and now is reaping the results.

      FWIW, his website contents are still up there, accessible through Google.

  9. Re:What does funding have to do with making it ope by Zigg · · Score: 4, Insightful

    He may be considering the inevitable time investment that would come from helping people actually understand the released source. Or (though less likely), there may be IP rights involved.

  10. They would have been long gone by now... by Anonymous Coward · · Score: 2, Funny

    ...but BSD was plugging up the drain hole. Or so I've been told from time to time.

  11. Re:What does funding have to do with making it ope by micromuncher · · Score: 2, Insightful

    Moving something to open source and give it a chance at survival is a lot of work. I tried to move a bunch of my libraries to open source only to discover a total lack of documentation; not just API but architectural. If its put out without polish, its DOA.

    --
    /\/\icro/\/\uncher
  12. Correct me if I'm wrong... by grasshoppa · · Score: 2, Insightful

    Correct me if I'm wrong, but doesn't the lack of funding indicate that nobody wants to use it anymore? Free market in action and all that?

    Further, what would Pegasus do that thunderbird or outlook doesn't do? Would it be better money spent writing custom plugins for thunderbird?

    --
    Mod me down with all of your hatred and your journey towards the dark side will be complete!
  13. Re:What does funding have to do with making it ope by LWATCDR · · Score: 3, Insightful

    "What does funding have to do with making it open source? He could make it open source today if he really wanted to. It just seems to me that he's yet another guy who's pissed off that he can't make a living off the Internet, so he's holding his source code hostage."

    I used to use this program a long time ago. It was a very good program.

    1. Holding it hostage? He wrote it so he can do with it what he wants.
    2. He did a lot of work. He would like to get paid for his work so funding is important. Things like food, mortgage, health care....

    So it comes down to this. He will sell his work to the community if they pay him. It is his work so he has that right. If no one wants it enough to pay for it he is going to walk a way. If you don't like it use thunderbird.
    These programs have been around for a long time. I used it on a Novell V3 system for email.

    --
    See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
  14. Re:Never heard of it by markhb · · Score: 5, Informative

    Well, it's important because David Harris has been producing a very high-quality gratis email client for Windows for nearly 17 years, funded entirely by voluntary manual purchases and support subscriptions, and he cannot do so any longer. For an idea of exactly how advanced the capabilities of Pegasus Mail are, take a look at his still-available-if-you-know-where-to-look Overview page, and especially at the "history of Pegasus Mail" link thereon.

    So far as opening the source goes, I'd love to see it happen (actually, I'd love to see someone hire him to run it as an open-source project), but I don't know how dynamic a community could be forged around a Win32 codebase that I understand to be optimized for performance and minimum resource use over modularity, portability, and ease of future development.

    --
    Save Maine's economy: write stuff down. All comments are exclusively my own, not my employer.
  15. Well, old dinosaurs always whither... by Pig+Hogger · · Score: 4, Informative

    Old dinosaurs wither...

    Pegasus mail was great when it started. Then a Windows version emerged, with was potent, flexible and useful, despite some quirks (you could not select anything less than a line in message text -- this gave me the habit I still follow to put URLs in e-mails on a single line without unrelated text).

    But it is obviously a product that evolved by slapping-on additions haphazarldy; the configuration was nothing but unified. Related features were spread accross several configuration screens amongst several configuration options, without a grand master plan.

    In the end, it was a sorry kluge that was easily replaced by other clients (Eudora, Thunderbird) who eventually evolved to Pegasus' capabilities, but without the configuration nightmare.

    So it arrived at it's natural end of life. It cannot compete against nimbler and swifter clients, so it now belongs in the annals of internet paleontology as a reverable footnote, much as the Great Eastern does in steamship paleontology or The Rocket in locomotive paleontology.

    R.I.P. Pegasus, you won't be forgotten, but certainly not missed.

    It's time to move on. Perhaps Mr Harris could bring his expertise and experience to Thunderbird, where he would be more than welcome.

  16. Re:long time user. by LWATCDR · · Score: 4, Informative

    Gee he has provided this software FREE of CHARGE for 16+ years. While he never said what the problem was the Author is claiming that he is having some money problems and is no longer going to have the time to work on this program.
    He would have to do a lot of work to open source it since he is using a third party editor component he is offering to take it open source if he can make a living at it. I guess he could just toss the code out to the wolves after striping out the editor but it would honestly just die at that time.

    --
    See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
  17. A rather hasty reaction by Control-Z · · Score: 4, Insightful

    I subscribe to the Mercury mailing list and last week David Harris (the author of Mercury and Pmail) posted a message about the future semi-commercial direction Mercury would take in 2007. There was one follow-up post that complained (in a polite way) about having to pay and David, in my opinion, went off the deep end. That same day he posted on pmail.com that they were both discontinued.

        The only money he ever asked for Mercury was for a set of manuals. I never needed a set of manuals, Mercury is easy to set up and use, and of course the mailing list is a good resource. I think a Donate button in Pegasus and Mercury would have kept him much more interested. As someone on the Mercury list said, if Pegasus Mail has 1 million users and everyone donated a dollar, that would make things much more interesting. Mercury was stagnating, new versions were few and far between.

    1. Re:A rather hasty reaction by King_TJ · · Score: 3, Interesting

      I think "it takes money to make money" is still as valid a saying as ever. The problem David Harris has is shared by MANY software developers out there. They initially get motivated to "build a better mousetrap", and they succeed. Their product is adopted by millions of users (often because it costs them nothing to use it, but has obvious benefits worth the switch and learning curve). Over time, the author feels that he/she deserves financial compensation for the now highly-regarded product and becomes disenchanted with the situation. Development stagnates, and new products overtake it.

      To overcome this, I think the real answer is to invest some money in advertising a newer, more advanced version of the software product. (The old one can then serve as a "lite" version, maintained simply to help keep your "brand" alive, and to introduce new people to the product's existence.) Otherwise, you can't really break free of the "development/ascent/decline" lifecycle that all products undergo.

    2. Re:A rather hasty reaction by FLEB · · Score: 2, Informative

      Trillian, Doom (and a thousand other Shareware titles), MS Outlook (via Express), Winamp (although I don't know if that's "succeeding" or merely "subsidized")

      --
      Information wants to be free.
      Entertainment wants to be paid.
      You just want to be cheap.
  18. Takes some work to open source something. by www.sorehands.com · · Score: 3, Insightful

    You can't just open source software, there is work to do to open source it. First, you have to inspect the licenses of any module/code that you include to make sure that it is open sourceable. You also have to have a build system in place that works with open source. Is it truly open source, if you have to buy Microsoft's Visual Studio to build it?

    I finally got the source code for Post Road Mailer (native OS/2 application). Before I can start working on it, I have to build a project file for Visual SlickEdit, then linting (or is it de-lint) it, then port it over to Watcom or Gcc. There may be some legal some issues that prevent me from open sourcing it, but I hope to get it working well enough to start distributing it -- legally, free as in beer.

  19. More details here by alexgieg · · Score: 2, Interesting

    You can find more detailed information on this move the following link, by a Pegasus Mail beta tester:

    http://www.vandenbogaerde.net/pegasusmail/dh_upd1. html

    By the way, I'd love to see Pegasus Mail open sourced. It's a marvelous e-mailing package. It's UI isn't the most intuitive around, but once you get used to it, it becomes a very powerful tool for your mail needs. Many years ago I evaluated a lot of e-mail softwares, including Eudora, and ended up choosing Pegasus Mail. It's really worth it.

    I would surely help if a fund for purchasing and open sourcing it was established.

    --
    Conservatism: (n.) love of the existing evils. Liberalism: (n.) desire to substitute new evils for the existing ones.
    1. Re:More details here by peeping_Thomist · · Score: 2, Interesting

      From http://www.vandenbogaerde.net/pegasusmail/dh_upd1. html:

      "I will probably never be able to describe just how horrible it has been to be me for the last three or four years, and I certainly will not insult you now by attempting to do so; suffice it to say that anything must be better than this dubious existence. [...] I will be shutting persephone down for an indeterminite period while I try to work out whether I have a future."

      That sounds to me like the guy is borderline suicidal. It's sad.

      --
      Anything worth doing is worth doing badly -- G.K. Chesterton
  20. There's nothing wrong with making money. by Kadin2048 · · Score: 2, Insightful

    I guess he could just toss the code out to the wolves after striping out the editor but it would honestly just die at that time.

    Not sure why he wouldn't do this at least to begin with; I think it would quiet a lot of the skeptics (myself included) who aren't particularly swayed by the thought that he would "consider" making it open source given appropriate funding. Stripping out the editor but opening the rest might actually be a good way to spur development because it gives a tractable problem to some other programmer: figure out a way to shoehorn an existing open-source editor, or a new one, in place of the one that's been removed. Sounds like a good thesis project for a comp-sci student somewhere.

    I don't fault the guy for wanting to make money, I really don't. (I work on closed-source software to pay the bills, and we don't even give it away free-as-in-beer.) But he's not going to win any friends by holding the code effectively hostage; since he's not known as being an OSS developer, he's going to have to take the first step if he wants to receive funding from people who are ideologically motivated in that direction. A good first step would be opening up whatever code is his to release in whatever form it's currently in, just to prove that he's not playing Pit and the Pendulum with the Delete key on the whole project.

    --
    "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
    1. Re:There's nothing wrong with making money. by LWATCDR · · Score: 5, Insightful

      "Not sure why he wouldn't do this at least to begin with; I think it would quiet a lot of the skeptics (myself included)"
      Why should he care what you think? Honestly your post is a great example of why he would do it.
      If he just released the code in a currently unusable form all that would happen is people would complain about how crappy it is. That is the problem with most free software users lately. They feel that by using a free program they are doing the authors a favor.
      Frankly I just hope he hits delete. Hell he is even helping write migration tools for current users free of charge.
      What a bunch of ungrateful people users are.
      I hope him all the best and thank him for the gift of his time and talents.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    2. Re:There's nothing wrong with making money. by fait · · Score: 2, Interesting

      Frankly, I would be just as happy if he made Mercury commercial software. Many of his supporters, myself included, have already told him that we would be willing to pay an annual fee or pay for each upgrade or something like that. Mercury is a wonderful home-user MTA and I know of several companies (the one I work for included) that use it as well. It's easy to setup and has good 3rd-party spam filtering built for it. It's worked well for me for several years.

  21. Yes, I'll miss Pegasus by rueger · · Score: 2, Interesting

    In the year since I moved to an Apple machine I've come to understand how solid and useful Pegasus Mail had become. In twelve months I've moved from Apple Mail (which I found much too limited), to Eudora (what a bizarre interface, at least for me) to Thunderbird, and now to Gyazmail.

    Each of these lacks at least a couple of must have features that I used extensively on Pmail. Thunderbird tries hard, but it always seems that the feature that I need most isn't quite finished.

    Gyazmail comes close, but still has some gaping weaknesses, like the apparent inability to add addresses to the Addressbook from within the program, and a good Search function.

    Ultimately Pegasus was probably best loved by those who live and breathe e-mail, and who need power and flexibility, as well as reliability. yes it was free, but it was one of those programs that I would have paid for because it suited my needs so well.

  22. Re:nothing to do with... by Anonymous Coward · · Score: 2, Informative

    Mercury corrupted large amounts of my email at port.ac.uk and caused me absolute nightmares. I'm tempted to open a bottle of champagne tonight to celebrate it going down the drain.

  23. Gratis vs. Libre by Per+Abrahamsen · · Score: 3, Insightful

    > Gee he has provided this software FREE of CHARGE for 16+ years.

    Which kind of demonstrate why I prefer to use free software vs. merely gratis software. Free software will live on as long as their is an interest, while merely gratis software depend solely on the owners ability to find a way to justify continuing the work on it.

  24. A dying breed.... by shaneh0 · · Score: 2, Insightful

    The BlitzMail system at Dartmouth is also being replaced. There is a real sense of loss when these things get replaced, at least for geeks like me. I probably spent as much time blitzing people as I did with any of my classes. These systems--and on campus Blitz is basically your number 1 conduit to other students--are really serving the role of a "3rd Place" that coffee shops and bars and such try to fill. It will be like the day that MySpace goes offline: People spent hundreds and hundreds of hours with it. It's an important character in the history of your life.

    Will the day ever come that we treat works of great software engineering with the same reverence that we treat 'traditional' forms of engineering? If someone unearthed an Abacus they would giddily rush it to their local museum. If they unearthed pristine copies of VisiCalc floppies they would probably be pissed off that somebody buried trash in their back yard.

  25. Dear David by Henk+Postma · · Score: 2
    Thank you very much for a Pegasus Mail, so solid, so powerful, and my email program exclusively from 1992 to 2005, when I finally completely ditched my windows partition in favor of running Ubuntu exclusively. I had been running Pmail under wine from 2003. I really loved the filtering system, it was wonderful!

    I am sorry to see you won't be continuing the program. Open sourcing is a nice idea, but my guess is it will then become a weak Eudora or Thunderbird copy.

    I wish you all the best in your future. So long, and thanks for all the fish!

  26. I don't blame him. by Rob+T+Firefly · · Score: 4, Funny

    If his code looks anything like mine, he's just too damn embarassed to show the world his tangled mess of strings, variables, and "Mystery Science Theater 3000" references that can only be called "code" due to its inarguable existence as electronic data that someone could tentatively try to run through a magical compiler if one were extraordinarily optimistic that the whole wretched thing would somehow do something not all that far from its intended function without damaging anything or anyone else near the computer desk physically or emotionally.

  27. Re:long time user. by LWATCDR · · Score: 2, Insightful

    "Yes; I understand that at shut-down the author doesn't want to suddenly incur large bandwidth fees and he could get hit with a lot of requests for the final version after making such an announcement,"
    Why?
    I have no idea why he is shunting down but stated that he is have some money problems. You also don't know what is happening in his life that forced him to stop this free development.
    So you have gotten years of use out of this program and you paid how much? He is offering continued support to those that have paid for subscriptions until there subscriptions expire.
    Seems to be that you for some reason think that you are owed something for using a free program.
    It just boggles my mind. Heck you can even keep using the version you have for as long as you want. You have lost nothing.

    --
    See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
  28. Re:long time user. by monkeydo · · Score: 2, Informative

    You can still download it.

    --
    Si vis pacem, para bellum
    The only thing more annoying than a Libertarian is an (un|mis)informed Libertarian
  29. Open Letter to David Harris by arete · · Score: 2, Interesting

    I've just heard on Slashdot about the end of Pegasus Mail and Mercury. Being often in the Linux and OS X worlds, I liked PMail and it seemed extremely well written, but I was never the most hardcore user. I never had a need to use Mercury. I'm also a professional developer.

    If you'll bear with me for a moment, I'll explain why I think you should probably Open Source these products. Not because it's good for the world, but because it's good for YOU. (I do think your creations have been good for the world, and I do think open sourcing them would be good for the world, but that isn't my main point.)

    I wouldn't tell someone selling commercial software and making a big profit that it'll be better for them if it's Open Source. Indeed, if you promptly get a substantial monetary offer for continuing it or for selling the codebase I can understand why you might do that. But if you don't get one promptly, people are going to start migrating away in droves - so the chances are going to rapidly go down, not up.

    You have basically two assets: A codebase and a userbase. (I'll include publicity with your userbase.) There are also many free competitors to your products. You have tough decisions to make that seem to involve: How can I turn these assets into money? Simply closing it down doesn't get you any money.

    You could open source this project with minimal cost. As I understand there may be portions you can't release that way, simply remove them. With some luck, enough people will want to help that they'll fix it. If you strike while the iron is hot and you still have many users, I think this is quite likely. If it doesn't happen, you aren't out anything but a few hours work, and the world has your code. If so few people cared about it, you probably weren't going to get any more for it. But if it does happen:

    1. You can continue to release new versions of the software, even if you do minimal work on it yourself. By keeping it alive, you set yourself up to continue getting support contracts, and you'll still be the prime source for them. (If you aren't charging enough for the support contracts, that's an independent problem...)

    2. Since you have already created the majority of the code, you can use a MySQL type dual license, which would allow you to release embedded versions of the code for someone else to wrap into a closed-source pay product. This is a niche that a pure-GPL product can't fill.

    3. You could even simply put up some ads on the site.

    --
    Looking for freelance Actionscript (Flash/Flex) or ColdFusion work and/or freelance developers. Email me, put Slashdot
  30. Re:long time user. by jonadab · · Score: 4, Informative

    > That's just it of course: Pegasus was a great product for its time, but has failed to
    > keep up with competitors. Nearly everyone has already switched over to Thunderbird
    > or something else

    Failed to keep up? You're out of your chair.

    If you compare Pegasus and Thunderbird side-by-side, Thunderbird looks positively feature-impoverished. If people have switched from Pegasus to Thunderbird, it is because they were no longer willing to be tied down to MS Windows. Running on other operating systems is the *one* meaningful feature Thunderbird possesses that Pegasus does not.

    Going the other way, there are many downsides to Thunderbird, the most significant being that its filtering is nowhere near the same ballpark with Pegasus Mail's filtering. It doesn't have flow control. It can't filter based on status flags like has-been-read, has-been-answered, or cetera. It can't filter based on time elapsed since receipt (e.g., leave unread messages in the inbox for up to ten days, then move them to another folder based on these rules...). It can't highlight a message so that it shows up a different color in the list. It can't form-reply. It can't launch an external process to handle certain messages. Et cetera, ad infinitum, ad nauseam, ad bedlam.

    Besides the filtering, there are a number of other useful features missing from Thunderbird too, but that one is really the biggie. If your mailreader can't presort your mail for you, whatever else it's going to do to save you time is going to pale by comparison.

    Heck, even *Gnus* (the mailreader that has every feature *including* the kitchen sink, and a learning curve to match) is missing some of Pegasus Mail's more useful features, features that Pegasus Mail has had since 1996.

    Pegasus Mail didn't fail to keep up, in terms of development or features. What happened is two things:

    First, and most important, it failed to be ported to the operating systems that are used by power users who crave powerful software with powerful features. A great many former Pegasus Mail users no longer use Windows. Wine didn't mature fast enough, and users were forced to find other mailreaders that would run on the OS they wanted to use. Choice of mailreader, even a really great mailreader, was not a strong enough factor to drive the choice of operating systems.

    Second, it lost the end-user market when operating system makers started bundling cheesy half-baked mailreaders with the OS. But it shares that trait with most other mailreaders, except for the bundled ones and the ones that were never aiming for the end-user market in the first place (e.g., Gnus).

    I understand why *development* of Pegasus Mail has stopped, in the absense of funds. But it would be nice if it could continue to be distributed for another couple of years. It's still quite a good ways ahead of the dev curve. Thunderbird will catch up with it in time, but based on its progress to date it could be another five or ten years.

    Meanwhile, I'm now stuck with no decent option to recommend to people who don't want to fight a learning curve (to adopt e.g. Gnus) and aren't satisified with Yet Another Lame Outlook Clone (e.g., Thunderbird).

    If bandwidth costs are the problem, he could have just given permission for others to distribute the unchanged binaries.

    I suspect what's really going on is that he hopes somebody offers to buy the source. Frankly, I hope so too. I've been hoping so for a while. If someone were to manage to port it to *nix/X11, I'd be a very happy man.

    --
    Cut that out, or I will ship you to Norilsk in a box.
  31. Re:What does funding have to do with making it ope by Wilk4 · · Score: 2, Interesting
    well said. (both you and the parent poster (LWATCDR))

    David Harris has certainly provided an excellent set of email tools for *many* years now (17?) *for free*, being supported financially by *optional* support contributions and sales of manual (any other means?)

    Remembering from the 'old' days when I used to help run our dept novel server for 120+ users, his programs were better and safer than many out there for years, and has always had powerful features. (both the email clients and email server) They were certainly better than the expensive and crappy email options offered by Novell at the time. I'm sure they have heavily influenced all of the other email clients & servers by the powerful features they introduced as well as their strong emphasis on security. I'm very sorry to hear that financial support for it has dwindled to this point, and I'm very sorry to see pmail go.

    David Harris certainly deserves our thanks and respect for his many years of work and of providing his software for free, not the carping and accusations of motive seen here. (which seems to be mostly by those who have never even used his software, or heard of it?)

    Open source has some great advantages, (especially for the user who doesn't have to do any work) but, like David's current model of development, it doesn't offer any guarantee of an income. Not everyone can work for free, especially full-time. Before carping at him, feel free to assign your trust fund over to him first. ;-) ... or try walking a great many miles in his shoes...

    I'm sure that setting up his software tools as open source projects would entail some significant amount of up-front work, and possibly continuing efforts. His code is his, and it's certainly *more* than fair to ask for financial support or compensation in order to donate it to the public domain, and to put even more time, expertise and effort into the transition.

    Anyway, thanks David, for your many years of effort, excellent software, and your generousity in sharing it with us for free.

    I'm sorry it had to end for you on the down note that the past few years have evidently been.

    Disclaimer: Yes, I've used Pegasus Mail for many years, though I've been using thunderbird lately. We're still using Pmail at home. And yes, I've put my money where my mouth is, sending financial contributions to DH several times. (though smaller than I would have liked to be able to)

  32. Re:For the love of God, let it die! by qralston · · Score: 2

    You misunderstand. (Perhaps I wasn't clear in my original post, so I'll attempt to clarify.)

    The group in which I worked provide core computing services for the entire university; that is, we made <user@example.edu> email addresses work. We did not use Mercury Mail; we used Solaris machines running sendmail and AMDS. The core mail infrastructure had to handle 30,000+ users, and had to be available 24x7x365, because it was what most people used.

    Some departments deployed their own mail systems; e.g., <user@ee.example.edu>. Most of them made no attempt to coordinate with us, and with university politics being what they are, we couldn't compel them to cooperate with us. Since virtually no departments (outside of CS and IS) had people familiar with unix/sendmail systems in-house, Mercury Mail was a popular choice.

    In other words, Mercury Mail was appealing to precisely the type of people who shouldn't have been running it: people who lacked enough expertise with Internet mail systems to recognize that the defaults were extremely dangerous.

    You missed my point about the default settings. Other than shipping as an open relay by default (which no respectable MTA had done for years), most of the "poor defaults" were necessitated by the fundamental design flaws of Mercury Mail. We'd get pushback from departments when we asked them to set the queue processing interval to, say, every 15 minutes, instead of every 5 seconds. ("But we want our mail to go out right after we press the send button!")

    I'm sorry, but any supposed MTA that is incapable of maintaining any state about its own mail queue is simply a toy, not a real MTA. Unfortunately, Mercury Mail was a toy that had just enough functionality to be truly dangerous.

    I did point out the more egregious shortcomings of Mercury Mail to David Harris via email. I never received a response. I didn't expect to, either: I was pointing out misfeatures, not bugs. The latter can be easy to fix, but misfeatures are fundamental design flaws, and are very difficult to fix. (To this day, I still don't know if Mercury Mail was ever redesigned to associate state with queue entries. It wouldn't surprise me if it still doesn't.)

    I'm not disputing that Mercury Mail might have been useful to small groups without enough expertise to run "real" mail infrastructures. But for those of us who did run real mail infrastructures, Mercury Mail was an agonizing curse. IMHO; its death is not only well-deserved, but a decade late. (I generally dislike giving Microsoft credit for anything, but Exchange is an order of magnitude better than Mercury Mail.)

    (For the record, I have no opinion on Pegasus; I never used it, and never had issues with others who did. My vitriol is reserved solely for Mercury Mail.)

    --
    Your bank is insolvent.
    Taking Money Back
  33. Re:Says something about motivations. by fait · · Score: 2, Insightful

    Let's be completely clear here. David has never charged for his software. The only income he made off this is for the manuals purchased and his tech support. There is no and never has been a cash cow in support licences. As it was pointed out on the Mercury mailing list, we probably put a dent in his manual purchases by the help we offered. Cash cow indeed.