[quote user="Thomas R. Stephenson"]

FWIW, your anti-virus software is being changed and updated almost daily and you can never tell when one of these will break your system.  Turn it off or do not allow it to scan any of the Pegasus Mail folders or config files.  If you do not one of these days it's going to find what it thinks is a virus in a PMM file and delete it. This in fact just happened with one of the Pegasus Mail beta tester using AVG 8. You can do what you want but a-v software actually causes a lot more problems than it solves when it comes to Mercury and Pegasus Mail.

[/quote]

Hi Thomas,

You might be right, but it is not acceptable to switch-off the permanent on-access scanning engine of our av software. Further our av software (F-Prot) is a very fast scanner not like e.g. Symantec, which is very slow. Unfortunately it's not possible to lock out some special folders from scanning. May be a solution is to prevent the pmail.ini files from overwriting by adjusting the write permissions (NTFS). But than no user is able to change any settings subsequently.

regards

Joerg 

Hi community,

We are using Pegasus in local mode together with Mercury. All Pegasus client installations are running on Windows machines while Mercury has been installed on a MS Server 2003 machine. The Pegasus user mailboxes are located on the server. Since some days some of our users (not always the same users) report that their local Pegasus has lost all user settings and starts with an empty Pegasus screen. Of cource now it's possible to go to the folder administration and open the connected mailbox folders - that means the mailbox including all subfolders are ok. But all the settings are not available and must be set again. In the meantime a have saved all INI files from the users for a quick re-setting.

Has anybody an idea why the INI files will be updated/changed from time to time?

regards from Germany

Joerg
 

If for some reason  WinPMail can't find the pmail.ini file on startup it will build a new one.  The normal reason for this to happen is something else has the file open (typically anti-virus software) when WinPMail tries to open it.  A flaky connection to the mail directories could also cause this but I'm betting on the a-v software as the cluprit.

You should not be running auto-protect against the Mercury/32 and Pegasus Mail directories.  

[quote user="Thomas R. Stephenson"]

If for some reason  WinPMail can't find the pmail.ini file on startup it will build a new one.  The normal reason for this to happen is something else has the file open (typically anti-virus software) when WinPMail tries to open it.  A flaky connection to the mail directories could also cause this but I'm betting on the a-v software as the cluprit.

You should not be running auto-protect against the Mercury/32 and Pegasus Mail directories.  

[/quote]

Hi Thomas,

When Pmail is creating a new pmail.ini then this will overwriting the existing ini automatically without promting me?

Yes, there is a a-v software running on each client machine. But the a-v software checks only those files which are just loaded into the Client RAM. That means the client has already red the file or is presently reading the file. Furthermore we are using this configuration since many years without such problems.

regards

Joerg 

When Pmail is creating a new pmail.ini then this will overwriting the existing ini automatically without promting me?

Automatically since this is the same as a new user starting without a pmail.ini in place.

 

Yes, there is a a-v software running on each client machine. But the

a-v software checks only those files which are just loaded into the

Client RAM. That means the client has already red the file or is

presently reading the file. Furthermore we are using this configuration

since many years without such problems.

If the a-v is running it will grab any file touched by the mail program on any mapped drive.   If it locks out the mail client when it's trying to open the pmail.ini then that's when the client will create a new file since it did not find the old one. 

FWIW, your anti-virus software is being changed and updated almost daily and you can never tell when one of these will break your system.  Turn it off or do not allow it to scan any of the Pegasus Mail folders or config files.  If you do not one of these days it's going to find what it thinks is a virus in a PMM file and delete it.   This in fact just happened with one of the Pegasus Mail beta tester using AVG 8.  You can do what you want but a-v software actually causes a lot more problems than it solves when it comes to Mercury and Pegasus Mail.