I checked and the date is 10/30/2015.  I haven't experienced any problems with printing, and was surprised to even find the errors in the event monitor. But why would Pmail be waiting on this anyway, when trying to download mail? There are 3 more copies in the WinSxS folder, which is apparently where the Windows update files are stored.  I'm going to try to clean that up in case that's part of the problem.  The Wait chain doesn't specify the path, although I would think it would be only in the C:|Windows directory - WinSxS is a subdirectory.

Virscan 5.2 can be downloaded from http://community.pmail.com/files/folders/pegadd/entry46921.aspx

Features:

  Support for Microsoft Windows Defender (free AV) All OS versions up to and including Windows 10

  Change of Virscan.ini DenyExtensions list (see Virscan.i  in Virscan.zip) 

Martin

Versions 4.7x use a different SSL than previous version which I suspect is causing connections to fail.  An upgrade should be easy but, as you noted, a copy of C:\PMAIL first is prudent.  You might have her go to Help > About Pegasus Mail the click the Info button to confirm the WINPMAIL.EXE directory is indeed C:\PMAIL and that the home and new mailbox directories are in C:\PMAIL\MAIL\user (probably ADMIN).

[quote user="pol098"][quote user="idw"]You might want to check out ...[/quote]Thanks. Could you clarify that a bit please[/quote]

It's pretty easy, just works as a gateway which does all necessary communication with the Exchange server and can be accessed via the localhost address for POP, SMTP and IMAP access.

Download the Windows setup from <http://davmail.sourceforge.net/download.html> and run it, then follow the instructions at <http://davmail.sourceforge.net/gettingstarted.html> and take an additional look at <http://davmail.sourceforge.net/advanced.html> for further options. My setup for SMTP looks like shown in the screenshot below:

The only time I have seen this happen is when forwarding a message that did not have any body content but contained an attachment and the following Forward options were used:

• Edit or make changes to the message before forwarding
• Forward any attachments...
• Include tiny headers

If you don't add/make changes to the body then the result is a message with the body containing only the tiny headers.  The attachment goes along as referenced by the line:

Anhaenge: L:\Temp\WPM$U2CB.PM$ =============================

See , Brian (section 3.3).

[quote user="irelam"]

Happy to help.  Could you describe the problems you are seeing please.  I don't understand what you mean by "Native folder files". 

Just as some background I simply open folders (*.PMM files) as flat text files and extract each message into a separate file. The program is coded to ignore messages that are badly formatted, or more likely messages that are empty (file length zero).  If you want you could send me one of your problem folders to irelam@telus.net, and I will try to process it in diagnostic mode.  If I find that there is a repeatble problem I will try to code around it.

[/quote]

By native folder file I just meant .PMM file.

Looks like your program is also set to ignore attachements greater than 5MB.

Some .PMM folder files are making NoSplit to abort with an "IO error 103"

I have been using pmail for 20 years. These folders are rather large files and contain personal stuff that I'd rather not share like that :-)

Because they contains thousands of messages, I have no idea which ones make NoSplit to abort with this IOerror 103. One of those .PMM file was creating the IO error right away without even converting a single message. After I copied the messages in a new folder. NoSplit was able to do most of these messages from that new folder. Then abort again with the same error.

Can you add a commandline switch to produce some logs that could help figuring what is going on?

[quote user="Xavier"]

If I may barge into your discussion, the initial message mentions that Windows 10 is being used, not Windows 7. ...[/quote]

D'oh!

The old one had a failure that we were hoping to remedy so we moved Pmail to another one so we could keep functioning.

Idw, many thanks for your reply, with IERenderer disabled, Edge is invoked properly.

Moreover, though IERenderer is disabled, I did lose nothing in reading html messages - they seem to render very properly, at least the few (different) ones I tried.

[quote user="AXracer"]Brian, thanks for your response, as In the error message above, the filename is that row of the strange symbols, nothing else, no dot, file type etc. All the fields in the message properties is also different length strings of that same (inverted exclamation points ?) the to: from: subject, etc etc. I have never seen that symbol before so I don't know what to call it. [/quote]

If these are indeed corrupted message files then the only way to deal with them is to delete the associated .CNM files?

[quote user="AXracer"]Also what is AV product? [/quote]

Anti-Virus

[quote user="AXracer"]WTF? Now all those email headers have moved so they are all together in the new mail list??? [/quote]

Probably of function of the new mail sorting.

Hi, thanks for answer.

Yes I can duplicate this error at will. Only if I send a message, without POP3 check/download during the shut down or uncompleted sending process.

I just find out that I made a driver update for my Wacom Tablet (Intuos) today. With the tablet usb connected, I have this error (runtime error 216). Without the tablet connected, no problems.

Yep, exactly my experience, fine in Notepad AND fine when pasted from there into a new message.

Not sure but I think that when I pasted from Notepad into the same message screen (now emptied of visible characters by my select all/ cut/) I was typing backward again.

(What would we ever do without Notepad.)

 Even weirder, the example I pasted into my plea for help appeared "backwards" in the message window but has been corrected in the posted version. Obviously should have had Greenshot do a screenshot instead of pasting text.

And how do you reproduce the effect until you find the cause... a conundrum, or possibly palimpsest... 

One thing that occured to me is that it might have something to do with the "A" key, which is one that gets pressed accidentally (my control key is remapped to be opposite it for faster typing), because Arabic languages are right to left. But nothing I've tried has evoked the boustrephodon glitch yet. 

Thanks for replying, it's always good to know the glitch has attacked someone else!

molly

I always appreciate your insights.

There is so much brain power accessible through this forum that I turn to it when looking for alternate approaches to an issue.  Often an alternative approach proves valuable but sometimes none do.  Either way, I'm grateful for the feedback from anyone willing to take the time to share their thoughts.

In the Folder window header is a button labeled "List" when you are in preview mode and one labeled "Preview" when you are in list mode.  Clicking it changes the view mode.  Preview mode is what you describe as your desired mode.

KSQR,

I'm happy to report your help did the trick, so thank you so much !

Thank you for the very quick reply

Yes I have version 4.72.572. build 5.72 I have used your message reader options and the message seem to open

but I will keep your crash post for future use.

Thank you and the other helpful Pegasus  support team it is AND has been most helpful

Yes, did that. Thank you.

So I now know, having belatedly had a look. Thanks.

Pegasus Mail will run fine on a 64-bit machine.  I have an office full of them (Win7) and a laptop at home (Win10 Home).