[quote user="pgsmick"]One (only one) of the users has lately experienced frequent crashes apparently at random; sometimes creating mail, sometimes downloading, sometimes sending.  It reportedly happens 2-3 times a day.[/quote]

Any distinct change before this started? An unexpected connection termination? A new AV scanner? A new printer (driver)? A Pegasus Mail update?

[quote user="pgsmick"]In all cases, Pegasus gives the nondescript "encountered an error and had to close" message.[/quote]

Windows generates this message, not Pegasus Mail.

[quote user="pgsmick"]In November, I saw 17 winpm-32.exe events. 14 were just like the above, one was pointing to the same dll but some other address, one pointed to kernel32.dll, and one was simply an "unknown" dll.[/quote]

The known ones are Windows core modules, it's unlikely (though not impossible) they cause the trouble.

[quote user="pgsmick"]Any suggestions about how to troubleshoot further?[/quote]

A couple of , last resort would be generating a crash dump.

The answer that solved the problem for me can be found here:

 

[quote user="Thomas R. Stephenson"]Sounds like something is holding these open or you do not have full rights to the files.  With Win7 User Access Control it's quite possible that you do not have the rights to delete these files in the protected "Program files" directory.[/quote]

At least when running as admin you can do so, but you'd still have to confirm the permission request for doing so.

Well, guys, I'm outta here. My reasons for changing mailers have dissipated, and I just don't have time right now to fool with it. Thanks for all the help. Maybe some other time. You guys are the best!

I misread your last posting, thinking that the error reports had been received.  Apparently that is not the case. 

 I have just filed another error report, and sent separately  a compilation of four error reports.

 Today I was able to bring up the "Junk Mail" folder and sort through it for about two minutes before I encountered an error.  You should have today's error report.

Once again, I appreciate all your help.

Thanks! That solved the problem.

 

{{{hugs}}}

Désirée

> As one of these PNX files seems to contain a virus I would obviously like to delete it, especially if it is some sort of orphaned/unused
> file. But I do not want to mess up Pegasus Mail by deleting files it is expecting to exist.

Checkout Han v.d. Bogaerde's Pegasus mail Links at
He has provided a lot of information on Pegasus Mail for Windows including all filenames and file extensions.

*.PNX         WinPMail v4.0+     

PNX files are the RTF version of the message bodies of any queued and draft messages that contain formatted text. The name part of the file is the same as the corresponding .PMO or .PMX or .PMW file. There should be no .PNX files without a corresponding other file.

I really doubt that this is a virus in the file that has been setting around for 8-9 years, more likely that the anti-virus software is messed up,  but you can delete it.

Hmm, very odd, the user reports it is now working, without (apparently) anything changing.

Sorry to waste your time.

I've marked my question as resolved.

thanks,

Ian.

 

> I am getting a consistent POP3 error on one of my identities but only when I am checking mail for ALL identities.
>  If I become the problematic identity and check mail there is no  error. Even when the error is generated, it still does in fact
>  download the mail from the server which proves the settings are  correct. Even so, I tried deleting the POP3 configuration and
>  re-creating it, but the problem still persists.
> Anyone have any further ideas I can try?

Become that identity and go into the POP3 setup using Tools | Internet options | (Receiving)POP3 and hit the add button.  Go through all of the POP3 setups you see there and edit then to check their configuration.  Delete all those that are no longer necessary.  

Tools,Options,Incoming,Message reader and reset option.

[quote user="irelam"]Wiki should be ok now.  Logging on became a very long process for a while there
[/quote]

Unfortunately, I'm still getting the same error message.  Tried different browsers to make sure it was not a browser-specific problem.

 The error message does not suggest that this is timeout due to slow server response: 

The website cannot display the page

<!-- This row is for HTTP status code, as well as the divider--><id id="http500"> HTTP 500</id><!-- Error Body --> 

Most likely causes:

• The website is under maintenance.
• The website has a programming error.

<!-- What you can do --> 

What you can try:

<!-- refresh page --> 

<noscript id="refreshPage"></noscript>

<!-- back to previous page --> 

Go back to the previous page.<noscript id="goBack"></noscript>

 

 

[quote user="philip e j jones"]

[SNIP]

Referring to the original remedy posted by jss1941, the messages are now in a different folder, and have a different extension.  Is that not true ?

[SNIP]

Regards, Philip

[/quote]

 

Sorry -- .CMM was a typo.  Should have been .CNM.  No changes in extension have taken place.

[quote user="billmac"]Sorry Guys - I found the culprit after some further research. I moved a large CNM file out of the mail directory and all was well. can I now delete this large file? What exactly is it?[/quote]

CNM files contain single messages in the new mail folder.

Michael forwarded your report to me and I've had a look at it.

The core of the problem is that the message is not in a legal format - the end-of-line markers are carriage-return characters on their own, not carriage-return + line-feed as required by the Internet mail standard. Most likely, the customer is using a Macintosh (which uses bare carriage returns for text files) and sending them out using an unsophisticated mail program that doesn't understand that it has to normalize the line endings.

This is one of those areas where you might say "but the web based viewer displays it fine, why can't you?"... Well, all programs are mixtures of compromises, and one of the ones I've made is that I'll tolerate messages with no carriage-returns, but not messages with no line-feeds. It's one of those areas where I balanced performance and maintainability against the need to correct what is demonstrably a rarely-encountered third-party error, and the choice I made means that messages with solo carriage-returns as EOL markers cause problems. I'm sure you'll find that the web mailer has its own sets of compromises and that there are other things that it can't do that Pegasus Mail can - such is the nature of compromise.

Michael and I are working on a way of handling this better, but in all honesty, the more realistic approach would be to see if you can get the customer to lodge a bug report with the developer of their mail program and get it fixed there.

Cheers!

-- David --

There's nothing garbled, it's just the HTML version of a message, and if it displays ok in Pegasus Mail I really wonder why it should not on other people's machines. Note that Pegasus Mail by default pastes in formatted text if available on the clipboard which enables the editor's Rich text option, you can avoid HTML parts from being created by unchecking the Rich text option or using paste special (Ctrl + Shift + V or context menu entry). There are also options for sending plain text messages (Tools => Options => Message formatting) or multipart/alternative (Tools => Options => Sending mail) which might help.

[quote user="Steffan"][quote user="tombell"]

When I send email to myself as a test, Pegasus honors the formatting in the signature except the image which appears as a grey box.[/quote]

That's because Pegasus suppresses images by default. If you right-click in the body of the message, you'll see an option "Show pictures (HTML only)". If you select this option, you'll see the graphic. [/quote]

Provided the signature (or message) contains remote (linked) images this is true, otherwise there must be something else involved ... Make sure the image you select for your signature is displayed in the signature editor before saving and closing, you sometimes need to load images twice for succeeding.

Thanks to Thomas, I can now receive mail! 

It turned out to be Avast anti-virus blocking the sending of the email, probably/possibly changed in an automatic update!

The last place I would think to look!

 

 

I don't think it is the printers, cuz everyone in my office room is connected to the same printer, and they don't have the same problem. If I recalled correctly this started happening after I changed my default copies to self folder and it's name, is there a a way to change it back to default setting?

I will give your suggesstion a try regardless.

Thanks.

[quote user="GramPics"]But the option under Tools> Check Spelling is stilled grayed out.[/quote]

Open an editor window and check again ...

Michael,

 Copying the entire html message seemed to result in having only unformatted text pasted into a new message body.

Bouncing to myself resulted in a complete formatted message that could be read without errors.

Forwarding as an attachment to myself was successful, however the Group Table error occurred when attempting to view the attached html message.

This is the first time this error has occurred for me in quite a long while, so it's not a significant problem for the time being.

Cheers,

Jim