The perfect forum for discussions or technical questions about Pegasus Mail.
The upgraded V6 of NOTSPLIT is now available at: http://community.pmail.com/files/folders/utils/entry3962.aspx
This update fixes some problems with Windows 10. Pegasus Mail folder has its messages extracted to individual files, for export/Import to other locations or mail applications.
Martin
Thanks caisson for response. I reinstalled Pegasus and it started working immediately.
Perhaps that is the first thing to do when there is a problem, though I do not know how the Pegasus program files (and it has happened with other programs too) should become damaged. No doubt theories in answer to that are manifold, so I'm just happy that all is now well.
Thanks. As it happened my wife found an answer that worked. I renamed state.pmj and recreated my layout. It took 20 seconds.
Try my suggestion from .
thank you Brian,
I happened to browse the board, generally looking for something I need on templates, and came across your message. Am a long time user [DOS and Novell], first at the office and now I am on a pension, using it with Windows10 at home.
Had missed the news that Thomas Stephenson and Jerry Wise had died. Sorry to read that.
Have a good December month and blessings for all your working years to come
Yolanda
If you hadn't said that you have deleted the message from the server I would have proposed that Pegasus Mail never records a successful download so it comes down again on the next POP3 cycle.
At this point I would want to determine whether the issue is with deletion on the server or at the local
level. To do this, the next time you delete the message record the .cnm filename.
When the message appears again check its .cnm
filename. A different filename indicates the message came down again.
It wouldn't hurt to do a system restart immediately after the next delete to clean out any cobwebs that might be affecting this.
BTW, when you delete the message from within Pegasus Mail does it disappear from the new mail folder and appear in the deleted messages folder (assuming deleted messages are being preserved until Pegasus Mail closes)?
Thanks!
I confirm what Brian suggests, though life is too short to test it more than once now. That is, full shutdown (not easy on Win 10), reboot, open Chrome, open Pegasus, send a message, close Pegasus. No error.
David
Yep. We are on our third, and will soon be migrating to a fourth data server (each offering increased storage capacity). The data server is always named . New server is named \\Orion-new and after transfer, the old one is renamed and the new one called \\Orion. Saves a lot of faffing about.
AFAIK, the only formatting options are font, bold, italic, underline, text color, & paragraph formatting.
Enter "Cassy" (no quotes) as your Personal Name in Tools > Options > General settings > Basic settings?
[quote user="irelam"]
Does Verizon have an "auto-forward" function?. ISPs usually have this function to deal with extended absences (ie vacation or sickness etc). This would mean that you would get all incoming mail at Gmail.com.
Martin
[/quote]
Great idea. I'll have to give it a try!
THNX
Weird issue, though ...
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:
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?
