I was experiencing a problem with Pegasus Mail 4.63 crashing at random times several times a day on a Windows 2003 Standard terminal server.  With the valuable help of Michael in der Wiesche (who handles the crash dumps) and David Harris, I was able to isolate the cause to something to do with RasMan.  Here is the stack dump for historical purposes :

ntdll!RtlpWaitOnCriticalSection+0xdf
ntdll!RtlEnterCriticalSection+0xa8
rpcrt4!SECURITY_CREDENTIALS::DereferenceCredentials+0x10
rpcrt4!CLIENT_AUTH_INFO::~CLIENT_AUTH_INFO+0x24
rpcrt4!SECURITY_CONTEXT::`scalar deleting destructor'+0x14
rpcrt4!OSF_CCONNECTION::~OSF_CCONNECTION+0x61
rpcrt4!OSF_CCONNECTION::`vector deleting destructor'+0xd
rpcrt4!REFERENCED_OBJECT::FreeObject+0xb
rpcrt4!OSF_CCONNECTION::FreeCCall+0x9d
rpcrt4!OSF_CCALL::FreeCCall+0x162
rpcrt4!OSF_BINDING_HANDLE::InitCCallWithAssociation+0x7b
rpcrt4!OSF_BINDING_HANDLE::AllocateCCall+0x49d
rpcrt4!OSF_BINDING_HANDLE::NegotiateTransferSyntax+0x2e
rpcrt4!I_RpcGetBufferWithObject+0x5b
rpcrt4!I_RpcGetBuffer+0xf
rpcrt4!NdrGetBuffer+0x2e
rpcrt4!NdrClientCall2+0x197
rasman!RasRpcSubmitRequest+0x1c
rasman!RemoteSubmitRequest+0x30
rasman!PutRequestInQueue+0x23 

The solution ended up being a hotfix from Microsoft that addresses both XP and 2003 in a multithreaded environment :

Gary Thorne

[quote user="Danny"]Hello,

I am using Pegasus Mail v4.41 on two netbooks. Since one year ago on one netbook Pegasus crashes on pressing the reply button. Closing Pegasus and start again before replying works, but is a little bit annoying. On the other netbook there has been no problem although the same installation (installed in a truecrypt container). But since yesterday also on the second netbook the same behavior. Update on v4.63 doesn't solve the problem.[/quote]

Since you can duplicate the issue with the current version I'd like to ask you to provide us with some more detailed information so we may learn about the background of these crashes for fixing them once for all: May I ask you, to install and use the MiniDump extension for providing further details with v4.63 (see )?

[quote user="bfluet"]

Have you tried...

snip snip, snarp

2.  When viewing in fancy (html) view right click in the body of the message and select "Open message in web browser"?

 [/quote]

 bfluet,

#2. Was not aware of this feature, it solved my issue and all will be AOK! 

Where are the duplicate folders? Local or on an IMAP-Server?

Have a look at the folderinformation of those folders (context menue). I understand that the foldernames you see are identical. But: are the folderfilenames (local) or cachefilenames (IMAP) identical?

You may get rid off the duplicate mails in that folders by checking consistency and reindexing the folders (local) or deleting the chachefiles (IMAP). But in my opinion you first should solve the problem of duplicate folders.

The problem with wrapping Urls is that Urls are allowed to be up to 8000 bytes long, which at 80 bytes per line as a standard would be a word with 8000 non blank characters split onto 100 lines on your screen. For an example see Mapquest or Google_Earth urls.

For these long urls it is lucky that Pegasus Mail will allow you to select the url characters then "Open string in a browser" which allows you to pass the Url to your favorite browser.

Martin 

Check out David's latest news update here

[quote user="janhaverkamp"]Ahoj Michael - feeling very honoured to get the response from you personally :-) [/quote]

I'm afraid nobody else would have a good answer for you: I don't really think a lot people are still using encryption at all these days ...

[quote user="janhaverkamp"]The AutoList could be the problem. I had imported the full list of certificates that I got - several thousands of addresses and I will need less than 1% of them...

[/quote]

Just add or keep the ones you need ...

[quote user="janhaverkamp"]

With "disable of enable various features", what do you mean?

As such, I don 't need an AutoList - I now switched off  the Auto Encryption in the configuration -> encoding menu and that gives instant sending again when not encrypted and a bit, but acceptable, waiting time for encyption.[/quote]

That's exactly what I meant and it served its purpose obviously.

Thanks to all for the replies.

As suggested I have used WIn Explorer to identify and delete the PM0 and associated PNX files with PM shut down (having the message folder first , of course!).

The only PM0 file is the current one for the <DESKTOP.PM0 > with today's date.    All appears to work now on opening PM with an empty Draft Manager folder

Regards

Rodney Fry

My goal with the incoming mail box is to try and always have it empty. Make use of filters to spread the emails to appropriate folders. That's the whole idea behind being able to define folders and filters to push stuff.

Also consider the  Default Mail Folder and the option to push read mail that falls through all of inbox the filters to that folder. That will save already filtered but not moved emails from passing though the filters again and again.

Make sure "AutoFiltering" is turned off for that catch-all folder too.

I sounds like the Win8 install of Pegasus Mail is working in a new mailbox and not the one used by the Win7 installation.  In the Win8 install of Pegasus Mail, go the Help menu and select About Pegasus Mail... Click the Info button then look for the following entries to see what Pegasus is working with:

WINPMAIL.EXE directory:
Home mailbox location:
New mailbox location:

Pegasus Mail does not provide a way to open a folder when a new message arrives. It is designed for all mail to come into the new mail folder (for which there are several different new message notification methods) and then be distributed to folders.  That being said, the versatility of Pegasus Mail allows the filtering of new messages directly to folders but this circumvents the built in new message notification functions.  To address that issue Pegasus changes the color of folder names in the folder list to green if they contain unread messages in addition to displaying the message count of read:unread messages.

As for IMAP connections, the only notification of new mail that I am aware of is when the connection is to a Pegasus Mail or Mercury/32 mailbox.  In this case the new mail notification method configured in Pegasus Mail also applies to the new mail folder of the IMAP connected mailbox. 

Have you tried running Pegasus Mail in List mode?  List mode allows you to configure the Pegasus Mail desktop with open folder windows. 

The hierarch.pm file is user specific.  There will be one in each users mailbox folder.  There shouldn't be one in your main PMAIL folder.

[quote user="TheSwitchOver"]Sounds easy ... and I got that email from Han ... but it is not as easy as it sounds ... do the two programs have top be open or is this a back end event and when I try to drag and drop nothing seems to work properly, meaning nothing happens.  I don't mean to be troublesome but consider me a complete novice when trying to figure this out.[/quote]

 Identify the Windows directory that contains the Eudora mailbox

With Pegaus Mail open, open the Folder window (no need to do this if you use Preview mode). 

While the Folder window or Preview window is active click the Folder pull down menu and select Add mailbox to list

Enter the path to the Eudora mailbox directory, give it a name then click OK.

The Eudora mailbox should now be visible at the bottom of the Pegasus Mail folder list.

[quote user="TheSwitchOver"]I also tried to use a converter from Dragon Computer consulting ... I have added pmm folders to the back end in the pmail folder, but it does not translate into folders in the program ... am I putting these in the wrong place.  You have to take into account that their program was writen in 1997.[/quote]

The pmm files would need to be added to a mailbox folder while Pegasus Mail is closed.  If Pegasus recognizes the new pmm files they will be added to the folder list.  It's possible that Pegasus doesn't recognize them as valid folder files.  Exporting then importing would be the next thing to try.  You may need to manipulate the exported file to make the field format match what Pegasus will be looking for on import.

I have not yet tried your suggestions but tas soon as I return to te office I will.

I'll let you know the results. Thanks for your help.

Arnold

Obviously, but as I don't need this persistent reminder (and I doubt I am the only one), there should be a toggle by which those of us who wish to eliminate this can do so.  Just sayin'.

An update of sorts...

A partial success... one WinXP PC I upgraded to IE8 and that solved the problem.

Tthe MiniDump is running on the server that's serving most of the WinXP PCs that are having the trouble, and I am waiting to hear if that catches any problems. Those PCs are running IE8 so that removes the instillation as a cure for the trouble that's happening there.

I haven't installed Pegasus locally on a PC yet.

Thanks, Jerry, that did the trick.  Bobbie

Thanks, Jerry. I guess I'll ignore it unless it happens again. :) 

There is some malformed spam making the rounds that is crashing Pegasus Mail with a C++ error but it is occurring immediately when these messages are attempted to be added to the new mail folder.  This is quite different from what you are experiencing but I thought it worth sharing.  The Subject of these crasher messages is very long and contains UTF-32 and UTF-16 encoded content.

Here's an example:

Subject:

=?ascii?B?RlJFRSAgVHJhbnNVbmk=?==?utf-32?B?b24sIEVxdWlmYXggICBhbmQgRXhwZXJpYW4gICBTY29yZXMgIERlbGl2ZXJlZCA=?==?utf-16?B?IAAgAEkAbgBzAHQAYQBuAHQAbAB5ACEA?=

The only solution to this particular problem is to locate the offending .cnm file and remove it from the mailbox directory.

The server is not accepting that password.