The "Refresh new mail folder every xx secs" controls how often the mailbox is checked for new messages that come into the mailbox either by local transfer (local user to user) or by a local mail server like Mercury.
I can confirm that NotSpilt6 and three previous versions all have problems as described by the problem submitter. I am guessing that the problems can be one or more of the following.
1. A message size in the folder exceeds the Microsoft 32 bit filesize maximum. This can occur quite easily if a multi-megabyte attachment occurs in a message.
2. A message contains the byte x'1A' dec(27) which is the marker for separating messages in PMM files. There should not be any such bytes in a message. It seems likely that Microsoft is issuing these bytes as part of Cloud-based Outlook messages and not converting these bytes to Base64 format. All messages are supposed to be 7-bit text/plain.
I am investigating detecting this condition and will create a new version of NotSplit to handle this.
P.S I am on 64-bit Windows 10 , and cannot test on previous versions of Windows systems.
I'll leave the others to address most iof this but as far as different configs goes take a look at the -Y cmdline option, which allow you to have multiple "Pmail.ini" files (by other names of cause) and call them from your shortcut
Easiest way would be make a copy of PMail.ini rename it for your other OS's (W7Pmail.ini, W10Pmail.ini and "maybe" NixPmail.ini) add -Y to your cmdline then make the OS specific changes
If you get the single Mail dir to work under Linux I would love to know the details as I have been trying that on a dual boot (Xp Pro, Ubuntu Xenial, PuppyXenial, Ubuntu Ardvark) netbook without much success (so far)
I don't think the info content will be helpful at this point because your problem my be that configuration files have been copied from the XP install. The info content could all look fine but a copied configuration file could be what is causing problems.
If I were you, I would start with the Win7 machine, take the existing install out of the picture by deleting or renaming c:\pmail, then do a clean install to c:\pmail, multi-user (leaving Admin and adding Ralph (make sure to enable Administrator privileges)). Now copy just data files from the old Ralph mailbox directory to the new one (use the guide). Do the same for Admin if you think you need to. No files should be overwritten during the data copy phase. If you encounter one, stop and research the file.
There is another guide that you might find valuable. It's Han's guide to filenames and extensions. http://www.vandenbogaerde.net then follow the Pegasus Mail information link to the Filenames and extension link.
Once you get it all setup and working you can easily duplicate it on the Win10 box. Copy the entire c:\pmail directory to c:\pmail on the Win10 box. Manually execute c:\pmail\programs\winpm-32.exe to start Pegasus Mail then shut it back down. This will create a registry entry recording the Pegasus Mail program location. Now run the Pegasus Mail v4.72 installer. It will look at the registry entry and default to installing to that location, probably as an upgrade. Let it run. This will "install" Pegasus Mail, creating needed registry entries, menu items, and shortcuts. That should be it except for any configuration differences you wish to make.
I'm also still happy with Peg, and have never been able to understand why even power users seem to prefer to accessing email online, directly thru Gmail or whatever.
We are presently still using ISO-8859-1 without any problems.
But as I wrote, the problem was not the set charset but a corrupted user's pmail.ini file. On any Windows crash or other event, where Pmail didn't quit properly, user's pmail.ini will not be saved. And on new start it seems Pmail generates a "new" pmail.ini with random settings. We experience this behaviour regularly. That's why I saved the pmail.ini files of all of my users for an quick restore on such events. But the first time I'm always searching for other reasons until the user tell me that his Windows was frozen [8-)]
A .PM$ file is a temporary file created by Pegasus Mail when it parses an attachment. What procedure are you using when you forward such an attachment?
I would contact AOL and ask them. Sometimes, their anti-spam mechanisms can be too enthusiastic and the fact you are bulk-sending may be triggering that mechanism. If you contact them you can ask them to whitelist your sending address.
[quote user="Joerg"]A lot of our received html e-mails take some seconds to display because of many embedded external images which have to be loaded from external sources at the time of opening the email. During these seconds Pmail is showing a blank grey windows background only and we could see in the footer that many external things are being downloaded. [/quote]
I use the web interface to access my email accounts when I need to clean house. I've never tried to do it via IMAP but that might be the best option if web access won't work for you.
I've solved the problem. What I did was disable all "Sending STMP" options except for "outbound.att.net" and that did the trick. So feel free to ignore my original message.
The settings are accessed through Tools > Internet options.
Notice the tabs labeled "Receiving (POP3)" and "Sending (SMTP)". Each one opens a window within which you can create host files by using the "Add" button. A host file is simply a file that contains the relevant information for connecting to an email host. A POP3 connection is different from an SMTP connection so each must have its own host file even though it's connecting to the same host.
The simplest form is connecting to one host, retrieving via POP3 and sending via SMTP. In this case, you would need one POP3 host file, which would be created through the "Receiving (POP3) tab, and one SMTP host file, created through the "Sending (SMTP)" tab.
There is a lot of information available through the Help button in the Internet options window.
I'm leaning towards an issue with a printer driver, especially considering that it had once worked.
If the default printer is a network printer consider taking the network out of the picture by adding another instance of that printer as a local printer on a standard tcp/ip port then test with it as the default printer.
Thank you for your fastreply, I am afraid, two correctly configured network- printers are usable from this machine, one of them marked as standardprinter.
I wil report my post so a mod can move it
Edit: I deinstalled and reinstalled both printers and Pegasus MAil is working again on this machine.
Now to check the configuration of all of the other users in the office. Mailboxes are all on the server so maybe I can find the appropriate entry in the .ini and check them that way.