Pegasus Mail

As per "V4.3 has been through nearly 60 betas and 14 release candidates, far more than any previous release of the program, and I can count well over 1500 changes in the code. V4.3 is largely about modernizing the Pegasus Mail codebase as a platform for future development, and represents the last version 4 release there will be"

Application Details:

Version: 4.31
Votes: 0
Latest Rating: Bronze
Latest Wine Version Tested: 0.9.45.

Maintainers: About Maintainership

Test Results

Old test results
The test results for this version are very old, and as such they may not represent the current state of Wine. Please consider submitting a new test report.
Selected Test Results

What works

I run Pegasus from a USB stick using the -ROAM option on the command line, this allows me to send and collect mail from any computer.

On my Ubuntu Feisty Fawn computer I run Pegasus using wine , generally speaking it works fine with no obvious problems other than as highlighted later in message.

Geoff Lane

What does not

On occasions Pegasus exits suddenly if receiving or sending mail.

Nothing appears to be lost as it is there when Pegasus is restarted.

I have not narrowed down the problem as on occasions mail will send and receive fine, I think it may be related to the closing of a Pegasus window.


What was not tested

Various other command line options other than -ROAM

Hardware tested


  • GPU:
  • Driver:

Additional Comments

If I can narrow down what makes Pegasus exit suddenly I may be able to adjust my use appropriately.

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
CurrentUbuntu 7.04 "Feisty" i386 (+ variants like Kubuntu)Sep 22 20070.9.45.N/A Yes Bronzean anonymous user 
ShowMandriva 2006 x86_64Jun 11 20060.9.15.Yes Yes Bronzean anonymous user 
ShowUbuntu 5.10 "Breezy" (+ variants like Kubuntu)Apr 02 20060.9.9.Yes Yes Silveran anonymous user 

Known Bugs

Bug # Description Status Resolution Other apps affected

Show all bugs


The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.

Pegasus ShutDown-Problem
by Werner on Wednesday April 19th 2006, 18:28
Version 4.31 has also the "Shutdown" - problem.
No I found a solution; it's not elegant, but useful.

I use the German version of Suse Linux 10.0. At the dialog I use the possibility .
So if I want to exit PegasusMail, first I take the in the file-dialog of pmail, then I close the terminal-window.
After this prozess Pegasus is closed in the normal way and without problems.

Perhaps somebody has a better idea to take this more elegant. I'm only a beginner of Linux, so I try more than I know.
RE: Pegasus ShutDown-Problem
by Werner on Wednesday April 19th 2006, 18:36
Sorry, there was a write-mistake:

it must be called
...At the dialog for possibilites I use the possibility "start in Terminal".

(This is important, because this is the solution!)
RE: Pegasus ShutDown-Problem
by Matthew Strawbridge on Sunday May 21st 2006, 20:36
The program hangs on exit. Werner's solution of starting the program from a terminal and then closing the terminal (thus killing the process) works, but isn't ideal.

Originally, Pegasus was also hanging when I sent mail. I changed Pegasus's options Tools, Options, Advanced Settings so that WSOCK32.dll is loaded always, and this fixed the crash on sending. Note that this is the opposite of the advice given for some of the earlier versions. I haven't added any native DLLs.
RE: Pegasus ShutDown-Problem
by Matthew Strawbridge on Sunday August 6th 2006, 8:03
Further to my previous email, Pegasus does still crash when clicking Send on the email. The email is available in the outbox when you restart Pegasus, and sending it from there works without crashing.
RE: Pegasus ShutDown-Problem
by jay somerset on Saturday April 14th 2007, 21:50
Installed Pegasus 4.41 under CrossOver in Ubuntu 7.04 (Feisty). Everything seems to work fine, EXCEPT Pegasus closes whenever an email is sent, queued, or when the Folders window is closed. This behaviour is independent of whether winsock.dll is specified to be loaded "always" or "on demand". Have not tried involking Pegasus withy the -Z 128 parameter, but from other posts in this forum, I suspect this does not impact the premature closing of the program.

This behaviour is identical on two quite different sets of hardware; an 8-year-old desktop system with one AMD Athlon processor, and a new HP laptop with a dual-core AMD x64 processor. Therefore does not seem to be a 32-bit vs 64-bit issue. Same version of Pegasus works perfectly on both systems; desktop with Win2K and laptop with Vista.