[quote user="Andrew Ampers Taylor"]I remember, a long time ago, David Harris writing that PMail would always be free as he believed in doing his bit to ensure that people all over the world could talk with each other through email

More and more third world countries have access to computers and a huge majority of these have Linux so the poorer countries can keep the cost down.

Alas, all these people cannot use Pegasus. But they can use Evolution and Thunderbird to name just two. So I guess it doesn't really matter in the grand order of things.

Not at all sure what you mean.  I, and many others, are using PMail and Mercury/32 with Linux daily.   Cost's nothing for PMail and nothing for Mercury/32 for personal non-commercial use.  Many, many of these Linux systems are using all sorts of free Windows programs and the free Wine make this possible in any Linux system.  If you really are on low end version of Linux then PMail for MSDOS works quite well in the Linux MSDOS emulator.

[/quote]

Hi,

I had no luck with Pegasus and Wine (neither version 0.9.59, nor 0.9.61, nor 1.0 RC2)

When I close a window (compose mail, for exemple), pegasus just silently exit.
When choosing the mailbox path, pegasus doesn't understand correctly and create a new one where it should use an existing one.

I wonder if some of the beta testers had tested the beta version under wine ? Since David had migrated from Borland to Visual C++, the behavior may be totally different, and maybe Wine is accepting better the binaries ?

If none of you from the beta team has linux on board, it will be a pleasure for me to test it here, if it is something possible.
[my email : sebas_2 (a_t) yahoo (c_om) ]

Wine is in code freeze for bug fix (RC3), I was thinking maybe it would be good to submit a bug report to them for the new Pegasus, if necessary. It would be really nice to see the brand new Pegasus working with the brand new Wine 1.0 :-)

My solutin for now is running Pegasus in a virtual machine (vbox), but it is an heavy solution, I think. I would greatly prefere wine, or maybe use a native mail client, but none of them is as good as Peg !

Best regards,
Sebas

> Hi,
>
> I had no luck with Pegasus and Wine (neither version 0.9.59, nor 0.9.61, nor 1.0 RC2)
>
> When I close a window (compose mail, for example), Pegasus just silently exit.

This one I can confirm, for some reason Wine is interpreting the close windows and close WinPMail.  See Wine bug 10213  http://bugs.winehq.org/show_bug.cgi?id=10213   
There are a couple of other bug reports as well.

That said, I find that simply replying works most of the time and the window close does not close the program.  

> When choosing the mailbox path, Pegasus doesn't understand correctly and create a new one where it should use an existing one.

Strange, both WinPMail and PMail have no problem here for me  using Ubuntu v8.04 and Wine 1.oRC2

>
> I wonder if some of the beta testers had tested the beta version under wine ? Since David had migrated from Borland to Visual C++, the behavior may be totally different, and maybe Wine is accepting better the binaries ?

Nope, same thing with closed beta v4.50 VC15.  The Visual C++ and Borland compliers make no difference. See http://bugs.winehq.org/show_bug.cgi?id=11887

>
> If none of you from the beta team has linux on board, it will be a pleasure for me to test it here, if it is something possible. [my email : sebas_2 (a_t) yahoo (c_om) ]
>
>  
>
> Wine is in code freeze for bug fix (RC3), I was thinking maybe it would be good to submit a bug report to them for the new Pegasus, if necessary. It would be really nice to see the brand new Pegasus working with the brand new Wine 1.0 :-)
>
>  
>
> My solution for now is running Pegasus in a virtual machine (vbox), but it is an heavy solution, I think. I would greatly prefer wine, or maybe use a native mail client, but none of them is as good as Peg !
>
>  
>
> Best regards,
> Sebas

Hi Thomas, tx for the reply :-)
I red the bug-reports you told about, mmmh, so it seems that Peg won't work with Wine for a while. Too bad.

About the fact that Peg was creating a new mailbox when I was giving the path of an existing one, I discovered that a unit letter was needed in the path, even with the option -ROAM. That was the reason. Strange, but ...

About the discussion in the bug report, where Dan Kegel said you shouldn't run Wine as root and you said that there was no reason _not_ to run as root, if you allow me, I must confirm that Dan is right, it is always considerated a very bad and dangerous practice to run users applications as root. The root account is made only for system administration and nothing more. Even if your PC is totally isolated from the word with no network connection, you should have _at least_ 2 accounts, root and thomas (for exemple, of course). No normal linux user would have only the root account, ever. That's why Dan is right when he's asking you not to use root account for debugging wine+peg, since it is an atypical situation which normally never happens. Of course, it is your perfect right to disregards this elementary security rule, but IMHO, you should reconsider your position.

It is this very same security rule that makes that viruses can only attack the user's files, and never the system itself, in opposition with what happens in Windows (this is the explanation why there is no active virus in linux, together with the fact that you have to change the permissions of downloaded files before to be able to run them). Another advantage is that you have absolutly no way to screw the system while you're logged as a normal user.

I hope I will see sometime a linux version of Peg, but it seems unprobable, mainly since David have migrated to Visual C++, bounding Peg's code even more to the windows API. Too bad, GNU/linux is lacking such an excellent email client as Pegasus is. 

Best regards,
Sebas

About the discussion in the bug report, where Dan Kegel said you shouldn't run Wine as root and you said that there was no reason _not_ to run as root, if you allow me, I must confirm that Dan is right, it is always considerated a very bad and dangerous practice to run users applications as root. The root account is made only for system administration and nothing more. Even if your PC is totally isolated from the word with no network connection, you should have _at least_ 2 accounts, root and thomas (for exemple, of course). No normal linux user would have only the root account, ever. That's why Dan is right when he's asking you not to use root account for debugging wine+peg, since it is an atypical situation which normally never happens. Of course, it is your perfect right to disregards this elementary security rule, but IMHO, you should reconsider your position.

Did you read what I wrote?  There is no security problem when there is no access to the outside world unless I'm running virus laden system on my local lan.  This is a test setup, I do not even want to run Linux but I'm testing it because there are a number of people who want to run Mercury/32 and Pegasus Mail on Linux.  There are all sorts of people complaining about the same problem not running as root, running as root ensure this is not a rights problem.  He did NOT provide any technical reason at all that Wine should not be run as root.  If you can convince me that Wine cannot be run as root for technical v/s policy reasons I'd be willing to listen.

I've managed VM, VMS, Unix, Linux, Windows, Novell operating systems and I've had exactly one virus infection in the past 25 years.  This one was brought into the house from one of my kids from school.  If I sound pissed, I am.  I'm trying to get Wine fixed and I get this motherhood and apple pie warning running a system as system admin like I was some kid that just started using a computer last week.

Take a look at the Zimbra Desktop, it looks pretty good to me. Not there yet, but they have plans to have conduits for Palm and Cellphones.

Hi
I make an UP to this thread, since I think it is still in the same state.

I've tried claws-mail in substitution of Peggy under Linux, it is a good proggy, with some nice ideas, but it doesn't beat Pegasus, far from it.

I've tried to use Peg in a virtual machine, it is running ok, but it's too heavy to have to run vBox for a single program.

So the only way still is Wine. I've made a comment on the wine-bug-report, and added a vote for the bug.
Here it is :
[quote]I confirm the shut down of Pegasus when closing some windows (compose,
folder(ctrl-L), user-lookup (F2), telephone message (toolbar), donate
(toolbar), current login (F4), etc...), but with other windows there is no
problem (help, new mail (Ctrl-N), preference, address book, etc...)

The way we close the window doesn't matter (close button, button "cancel",
right-click on windows bar), the result is always the same.[/quote]

Since I don't think there will have any change from the wine-team part (too few users concerned), I come here and propose this :

1)   First of it, I think that all those who are concerned in seeing Pegasus working under Linux should add a vote to the bug at this url, (it is not necessary to make a comment), so the wine developers can see there is more than 5 ppl interested in fixing the bug

2)  Next, I wonder if it is not possible to try to solve it on the Pegasus side, with the David's help.

2-1) Maybe, as there is a beta version out, it would be possible to put some tracker in the code so there is a log and we can see which instruction is guilty and lead the whole program to close, instead the sole window. I mean, for example for the "Send" in a compose msg, to insert a debug instruction "write code line number to log" after each code line beetwen the click of the send buton until the effective closure of the window. So we could look the log and see what was the last instruction executed before exiting.

2-2) If this is too complex to work out, maybe it would be possible to substitute the window type. There is obviously at least three different type of windows. Since the close window action is ending the program with some windows, and not with some others, defining which type is sensible and substituing them by another type could be a solution, I don't know the level of complexity of such task (I hope it is easy)

I have noticed that a type of window is not bundled to the main window, I mean we can drag it out of the main area (exemple "Add mailbox to list" (menu folder), or "selective download" or "About Pegasus" or "Translate Pegasus"), and this one is not sensible to this bug.

There is another type that is bundle to the main area, but can close without exiting (new mail, address book, preferences, etc...)

I've noticed that "network preferences" is from type 1 (unbundled) and "general preferences" is from type 2 (bundled, but not exiting), maybe because David created "Network pref" much after the "General pref"

Ok, I hope I've given some valid tracks. If David could help to put back Pegasus on the Wine track, it would be really fantastic, because except this problem, it seems that it's working quite all right. But as it is actually, it's impossible to work efficiently if the program is exiting at each step.

I'm willing to help in any aspect I could be usefull, of course, if testing is required.

Once more, thanks to you David, your program is really the best one around.

Best Regards,
Sebas

> Hi
> I make an UP to this thread, since I think it is still in the same
> state.
>
> I've tried claws-mail in substitution of Peggy under Linux, it is a
> good proggy, with some nice ideas, but it doesn't beat Pegasus, far
> from it.

Agreed.

>
> I've tried to use Peg in a virtual machine, it is running ok, but
> it's too heavy to have to run vBox for a single program.

Correct.

>
> So the only way still is Wine. I've made a comment on the
> wine-bug-report, and added a vote for the bug.
> Here it is :
>
>
> I confirm the shut down of Pegasus when closing some windows (compose,
> folder(ctrl-L), user-lookup (F2), telephone message (toolbar), donate
> (toolbar), current login (F4), etc...), but with other windows there is
> no problem (help, new mail (Ctrl-N), preference, address book, etc...)

I cannot confirm that closing the windows in PB1 or V4.41 closes the program when in the preview mode.  The preview mode apparently works differently than the classic mode.  I can send mail without closing the program in the preview mode.  I use it daily in sending and receiving mail in conjunction with Mercury/32 an very seldom is there a problem.  

>
> The way we close the window doesn't matter (close button, button
> "cancel", right-click on windows bar), the result is always the same.

Correct, apparently Wine is interpreting the close window as close window and close program.  These are not crashes, they are full program close commands and WinPMail is closed normally, including the update of the ini files and the removal of the lck file.   

>
> Since I don't think there will have any change from the wine-team
> part (too few users concerned), I come here and propose this :
>
> 1)       First of it, I think that all those who are concerned in
>        seeing Pegasus working under Linux should add a vote to the bug
>        at this url, (it is not necessary to make a comment), so the wine
>        developers can see there is more than 5 ppl interested in fixing
>        the bug

There may not be all that many according to what I see.  I certainly could not attract any attention of any of the people in the Wine group.  WineDBG does not help either since this is not considered an error, the program is simply responding to the close command from the OS.

>
> 2)      Next, I wonder if it is not possible to try to solve it on the
>        Pegasus side, with the David's help.

He does not do Linux and/or Wine and has enough problems with MS.  ;-)  If we were able to tell him exactly what command was being improperly interpreted there might be something he could do to fix the Wine bug.  

>
> 2-1)   Maybe, as there is a beta version out, it would be possible to
>        put some tracker in the code so there is a log and we can see
>        which instruction is guilty and lead the whole program to close,
>        instead the sole window. I mean, for example for the "Send" in a
>        compose msg, to insert a debug instruction "write code line
>        number to log" after each code line beetwen the click of the send
>        buton until the effective closure of the window. So we could look
>        the log and see what was the last instruction executed before
>        exiting.

The problem with this is there is tracking code in the program but there is no error.  WinPMail closes a window, this is passed to Wine and the window is closed and then Wine tells the program to close as well.  WineDBG see no errors at all.  The WinDbg does not work with Wine.  I tried using the new debug extension to see if it would at least trigger but it does not see an error.

>
> 2-2)   If this is too complex to work out, maybe it would be possible to
>        substitute the window type. There is obviously at least three
>        different type of windows. Since the close window action is
>        ending the program with some windows, and not with some others,
>        defining which type is sensible and substituing them by another
>        type could be a solution, I don't know the level of complexity of
>        such task (I hope it is easy)

This is NOT at all easy to do.  As you can see from what I experience with Wine v1.6 and Ubuntu v8.04 my closing of windows is different than your closing of windows.

>
> I have noticed that a type of window is not bundled to the main
> window, I mean we can drag it out of the main area (exemple "Add
> mailbox to list" (menu folder), or "selective download" or "About
> Pegasus" or "Translate Pegasus"), and this one is not sensible to
> this bug.
>
> There is another type that is bundle to the main area, but can close
> without exiting (new mail, address book, preferences, etc...)
>
> I've noticed that "network preferences" is from type 1 (unbundled)
> and "general preferences" is from type 2 (bundled, but not exiting),
> maybe because David created "Network pref" much after the "General
> pref"
>
> Ok, I hope I've given some valid tracks. If David could help to put
> back Pegasus on the Wine track, it would be really fantastic,
> because except this problem, it seems that it's working quite all
> right. But as it is actually, it's impossible to work efficiently if
> the program is exiting at each step.
>
> I'm willing to help in any aspect I could be usefull, of course, if
> testing is required.
>
>
> Once more, thanks to you David, your program is really the best one
> around.
>
> Best Regards,
> Sebas

[quote user="Thomas R. Stephenson"]I cannot confirm that closing the windows in PB1 or V4.41 closes the program when in the preview mode.  The preview mode apparently works differently than the classic mode.  I can send mail without closing the program in the preview mode.  I use it daily in sending and receiving mail in conjunction with Mercury/32 an very seldom is there a problem. [/quote]

Not for me. In preview mode (pegasus 4.5b), it exits exactly the same way as in classic mode, and for the same windows.
Nevertheless, I have wine 1.0, because the v 1.1.6 doesn't want to install here for a dependency pb (wine: Dépend: libldap2 (>= 2.1.17-1) ). So I'm stuck with 1.0 and cannot test in the same conditions as you.

[quote]> 2-2)   If this is too complex to work out, maybe it would be possible to
>        substitute the window type. There is obviously at least three

Mmmmh, too bad, that would have been an elegant solution to pass around the wine bug : substitute the windows of type 1 by windows of type 2 or 3. Is it really too time-consuming for David to try to look if this path is workable or not ? Maybe it's a simple matter of a class definition (substituting a C++ class for another one).

Kind regards,
Sebas

But maybe he can look if there is an obvious difference beetwen the

behavior on closing beetwin the culprit type of windows and the other

types (as I defined above, I've noticed at least 3 different types)

I asked him about this quite some time back and he said they all close pretty much the same way.  There is essentially no difference no difference in the way they are closed but there may be things operating under the hood in windows that he does not know about.  Remember both v4.41 with the Borland C compiler and v4.50 with the Visual C++ compiler have the same problem.  I have my doubts if it's anything at all in the actual C code that is causing this but i really suspect that it could be related somehow to the windows calls. 

This is a Wine bug since it's operating well in windows but it's really hard to attract the attention of the people in Wine. 

[quote]Remember both v4.41 with the Borland C compiler and v4.50 with the Visual C++ compiler have the same problem. I have my doubts if it's anything at all in the actual C code that is causing this but i really suspect that it could be related somehow to the windows calls.[/quote]
Yes, but in this case, why is Pegasus the *only* software with this behavior, amongst the very numerous softwares registred in the wine-appdb ?

I would rather suspect a particular library, or something very specific included in Pegasus' code. And even the fact that the passage from Borland to MS compiler didn't change an inch of this weird behavior enhances this theory. There _must_ be a particular call of a particular function that provoques this, even if it's a rare win-API object.

And what about changing the kind of window-type ? Have you already asked David if it was too complex or if it was a possible work-around ?

[quote]This is a Wine bug since it's operating well in windows [/quote]
It's certainly a Wine bug since Pegasus has no problem in Windows. But the Wine point of view could be : "it's a Pegasus behavior since no other app has this problem."
So the point is now to know if Wine will be fixed to work with Pegasus, or if Pegasus will be fixed to work with Wine.
In my opinion, the Pegasus' team (including Peg's users) has more to win in the fixing than the Wine's team.
Even if the logic would lead to say "Wine should fix it", we, Pegasus users, have more opportunities to test and help on this side of the mountain ;-)

[quote]but it's really hard to attract the attention of the people in Wine.[/quote]

They are probably like David : full of work ;-) , and they are probably giving priority for bugs more popular. A bug with only 6 votes is certainly at the bottom of their list.
(and one of the developpers went pissed off when you refused to create an user account (no-root) to test Wine, and desappeared since then.)

So it seems that we are in a no-go situation, and I'll have to go back on testing linux native e-mail clients

It's too bad there is really no track leading Pegasus to a trully multi-platform solution, Linux is missing such a good email client, and it could have given a second youthness to Pegasus.
And this, mainly because Linux' users are more curious about installing programs and have not that stupid habit from the average Win-PC user to take what is already installed (i.e. MSIE-outlook-MSN-WMP) without thinking there are other solutions (Opera-Pegasus-Jabber-VLC, for example :-)

[off-topic]
I'll try Mutt which is sayed to be very powerfull, allthough it's a text-mode program.
My problem is that I need a nomad program on my USB-pendrive for when I'm travelling, and Mutt is certainly no candidate for this. Once more, Pegasus was perfect for this. Maybe I should try if Opera's M2 has made some progress, since Opera is my first browser, it could be a logical solution.

About the Zimbra Desktop Andrew spoke about, I've noticed that it's a Yahoo's soft, and I certainly won't go toward another "à-la Google" software that can spy my emails or habits (well, it's open source, so it won't have hidden spying code, but I guess Yahoo _must_ have something to win with this). Furthermore, it requires 200mb on HD and 256mb RAM !!!
[/off-topic]

You can count on me on any task I could help about this,
Kind regards, 
Sebas.

>> In my opinion, the Pegasus' team (including Peg's users) has more to win in the fixing than the Wine's team.

If we take just this year, then we now know...

• Citroen have moved 250 servers and 20,000 PCs over to SuSE Linux.
• The French Government have moved over 70,000 Police desktops to Ubuntu Linux.
• The Spanish government have put Ubuntu Linux onto nearly half a million Spanish PCs.

There are many more movers over to Linux.

There are two big factors coming up which will move a lot more people over to Linux.

First of all, This banking calamity will never be solved by pouring good money after bad. The governments in Europe and America are not addressing the undermental causes. That is just printing more money, without assets whenever they need it. To give you a clue of what is happening, just imagine you have the only five copies of a rare stamp in the world. They are worth $100,000 each. I find a sheet of 240 identical stamps on my attic, and tell everyone about my find. Now your five stamps will probably only be worth $2,041 each. On a grander scale, this is what is happening to our money. So people's buying power will gradually go down, and FREE will start sounding more interesting.

Secondly, Microsoft is thinking of an annual licence for all their software, rather than an outright purchase. Once that comes into force, people will start looking for alternatives. Expect Apple and Linux to pick up a lot of disgruntled customers, or just Linux of Apple decide to follow suit.

I do appreciate that David just has not got the resources to even entertain Linux. This is a fact. However, one of the great things about Linux is the source code is available and when others work on it, they send in their work to the original writer so he may incorporate the best ideas into the standard program. I can fully understand that this is not an option for most people though.

I miss using Pegasus terribly, but I use a Palm and like my Palm addressbook, diary, memos and tasks updated daily so use Evolution.

Ampers.

Just thinking to something (after having tested more windows closing) : what about if the problem was related with the writing of the current state (destop.pm0 or state.pmj or folstate.pm or ...).

** Test this :

open Peg in preview mode, put in list mode, compose msg, cancel compose (=> close program)
--> Peg reopen in list mode with no msg (it remembers list mode)

open peg, user lookup (F2), close this window (=>close program)
--> Peg reopen without user lookup, it seems it remebered, but try this :

open peg, user lookup, compose msg, cancel compose (=> close program)
open peg (user lookup is still there), close window "user lookup" (=> close program)
--> Peg reopen with user lookup, it is now impossible to get rid of this window, the only way is deleting destop.pm0, so Pegasus doesn't remember that this window has been closed, so the task has not been completed.(thus this is not a normal exit)

*** Other test, even easier  :

- Delete all those files : newcache.pm - mailbox.pm  - hierarch.pm - folstate.pm - cache.pm - desktop.pm0  -state.pmj
- Open Peg, compose msg, cancel.(=> exit program)
All the files have been recreated, except desktop.pm0

So the problem is probably during or just before the writing of desktop.pm0

Maybe you could ask to David if he can look for an instruction after the call of the close procedure, after the remwriting of all config files but before or during the writing of destop.pm0

I've worked hard to find this one, but I think it's worth the effort, we have now a good pist, don't you think so, Thomas ?
Best regards
Sebas

[quote user="Andrew Ampers Taylor"]The French Government have moved over 70,000 Police desktops to Ubuntu Linux. [/quote]... and both the french congress and senate have migrated to ubuntu last year.

I've red an interview of few deputees, they were at first fearing the transition but they were surprised that they had no problem at all (even one completely dummy in computation stuffs), and they found that some task were now even easier than with windows.

[off-topic]
The "funniest" thing is that they are the same that have voted a law against piracy that makes illegal to hear or watch any copyrighted content on linux, or on an open-source software, even if you've legally bought it. So they cannot hear their own Ipod without breaking their own law :-//.
[/off-topic]

Really, Pegasus for Linux would be a great gain for both (Pegasus and Linux)

Is there anyone in this group that really knows Linux and Wine and could provide actual debug information using the Linux/Wine type tools?  This is what is required by David to work around the Wine bugs. He cannot make random changes to a program that works in the hopes that he could fix a Wine problem and not break the program.  We are currently doing this sort of thing with an extension and with WinDbg for the PB1 for Windows.  For myself, and most of the people I know that are using Linux, we are like the normal Windows user, we can use it but can't debug it unless provided specific instructions and someone to actually interpret the results.

As for a native Linux version that's much more of a problem.  Writing a program that is OS neutral requires using a totally different approach than writing a Windows program.  You can do this with PHP, Java and/or another high level language where there is a run time complier available on the OS but this really slows things down.  Maintaining two separate versions of the program is also not an option where there is only david involved in the programming.  This was the basic reason the the Mac version went away a long time ago.

David has offered up support to the Linux community to for someone to develop the Linux version but there were no takers.

> Yes, but in this case, why is Pegasus the *only* software with this
> behavior, amongst the very numerous softwares registred in the
> wine-appdb ?

Is it now.  This Wine bug is only specific to Pegasus Mail because of the way the program is closing.  There can be hundreds of other programs where closing a window also closes the program and maybe the problem is a "fix" put in Wine to close a program that would not close.  

Really hard to make a statement like this without using "all" the other programs.

I did a fast read of this thread, so I am sorry if I missed a mention, but I did not see any mention of the Close method ?  Is it the Window "X" or menu item File|Exit ?

Martin

.

> I did a fast read of this thread, so I am sorry if I missed a mention, but I did not see any mention of the Close
> method ? Is it the Window "X" or menu item File|Exit ?

Any method that closes the window, Irelam. For instance, with the  "compose msg", [x], "send", "cancel" or escape (after the "confirm exit" msg) closes the window _and_ the program (but "save" doesn't have unwanted repercution).

My guess is that something happens during the actualization of the "actual desktop state" (open windows + window sizes) that wine wrongly interprets as an "exit program" method. If we could find which method, it would be easier to submit a bugfix request to the wine's team.

This happens with some windows, not with others (for example, both pref windows or address book don't provoque this bug, but "user lookup" or any "extention" window does it)

> Is there anyone in this group that really knows Linux and Wine and could provide actual debug information using
> the Linux/Wine type tools?

I'm not the ideal person for that, I have no particular skill or knowledge about neither linux nor wine, and very few about C++ (I was a clipper programmer though), nevertheless, if I can help in anyway in this path you can count on me. The problem is that you probably have looked and done what is possible for a normal user. I will search the wine debug documentation to see if I can do something efficient.

Kind regards

> As for a native Linux version that's much more of a problem. Writing a program that is OS neutral
> requires using a totally different approach than writing a Windows program.

The problem is the calls to the API. The logic of the program must be separated from the graphical parts, so the API calls can be managed differently depending of the platform.

> You can do this with PHP, Java and/or another high level language where there is a run time complier
> available on the OS but this really slows things down.

Not necessarly. I agree that Java or other interpreted languages are heavier, and one strongth of Pegasus is its efficiency, so it's not a correct path. And Pegasus cannot be rebuilt from scratch for sure, so it's a no-go way.

There are some languages that produced compiled-linked exes, that don't need runtime lib, and that can manage Mac + MS + *nix environments with the same code. You just have to #define different variables and link different libraries.
For exemple, I used to program a little with xHarbour (which is a 32bits clipper-compatible xBase compiler) that can produce graphical applications in both Windows and Linux, with the very same code.You just have to use a graphical library that allows this (there are several GTs for xHarbour that can manage the API calls, and at least two of them, hwgui and T-gk, can produce Windows and Linux graphical applications with the same code)
Another example was Kylix, which was the Linux version of Delphi.

Of course, I'm not saying that Pegasus should be rewritten in one of those languages, it was just an example.
As C++ is widely supported in *nix world, it must have some pathes of this type that could be explored. It's a pity because the reformulation of the code that David have just done could have been a good opportunity for that. And as I asked in this post of another thread, the choice of Visual-C++, (MS is always trying to push on their own ways that aren't respectfull of establish standards) wasn't probably the best way to go toward the *nix world. 

I know there is a GTK version for windows, so if one manage to make code that runs with it under windows, it runs under linux too
Wine has a lib that can be used to compile a windows code into linux (wine.lib)
That's just two examples, I'm sure there must be some more.

> David has offered up support to the Linux community to for someone to develop the Linux
> version but there were no takers.

Well, that's a very interesting news ! What was his idea of the possible way to do that ? (I've heard that he's not willing to open the code, so he probably has another path one can use to do the migration, hasn't he ?). How did he publish such an idea ? I'm not knowing a lot about open-source development, but I am very surprised that no one jumped on top of such possibility to have a such good email client in the linux world. So maybe there are some better channels that are used in such cases ? What about Sourceforge ? (well, it's for open-source, so I'm not sure it's the correct place)

I remember that few years ago, a Pegasus user said that he could help to migrate if the code was open, but I didn't manage to locate the post in google.group (it was in the Pegasus' nttp newsgroup)

NB : I have re-read my post, and I wonder if my bad english would lead one to think that I'm giving advices to David. It is not the case of course, I'm just wondering some questions, but I cannot express myself with all the nuances I could use if it was my mother language. So please excuse me if you think I'm arrogant, it is definitively not the case !

Best Regards

Sebas

Long time Pegasus user in Windows, so I've been interested in getting it working in Linux under wine. For me there is a simple workaround that I found by accident, and that is Pegasus works fine as long as the wine server is supporting another application. For instance, if you just launch the "configure wine" app, or alrealdy have another application that has wine support, and then launch Pegasus, everything works as expected, wing flaps, sounds, and normal window behavior on downloads, sending, etc.

Ubuntu 8.04, wine 1.1.15, Pegasus v4.31