As a small user with Mercury (4.73), and with Pegasus (4.61) running independently on 3 workstations (2 of Windows XP and 1 of Windows Vista), I am in the habit - for security reasons - of turning off all machines late every night and switching back on again next morning. This is a long-term practice that has always previously worked without problems. Mailboxes are kept in a \pmail\mail folder on the same machine as Mercury.
However, over the last few months, I have encountered random Pegasus SMTP and POP3 failures from the workstations, which tell me that access is refused by the server. After much scrabbling, I found the reason appears to be that the Mailboxes (in Drive:\Pmail\Mail\Usernames) have become Read-only, which I assume has been done by Mercury, as all mailboxes become affected simultaneously. The problem is found when the individual systems are turned on in the morning and commence polling for mail, so presumably the fault occurs either at boot-up time or during the previous night's shut-down. And it only happens now and again (e.g. every 3-10 days).
I have found my quick and dirty solution is to turn off Mercury, go into Command Prompt, change to the Pmail directory and use DOS to remove the read-only attribute from the whole \Pmail\Mail directory and its sub-directories ("Attrib -r \Pmail\Mail /D /S"). Then everything is hunky-dory until the next time. Getting a bit boring now though. Any good ideas how to prevent this sudden return to "Read-only"?
As a small user with Mercury (4.73), and with Pegasus (4.61) running independently on 3 workstations (2 of Windows XP and 1 of Windows Vista), I am in the habit - for security reasons - of turning off all machines late every night and switching back on again next morning. This is a long-term practice that has always previously worked without problems. Mailboxes are kept in a \pmail\mail folder on the same machine as Mercury.
However, over the last few months, I have encountered random Pegasus SMTP and POP3 failures from the workstations, which tell me that access is refused by the server. After much scrabbling, I found the reason appears to be that the Mailboxes (in Drive:\Pmail\Mail\Usernames) have become Read-only, which I assume has been done by Mercury, as all mailboxes become affected simultaneously. The problem is found when the individual systems are turned on in the morning and commence polling for mail, so presumably the fault occurs either at boot-up time or during the previous night's shut-down. And it only happens now and again (e.g. every 3-10 days).
I have found my quick and dirty solution is to turn off Mercury, go into Command Prompt, change to the Pmail directory and use DOS to remove the read-only attribute from the whole \Pmail\Mail directory and its sub-directories ("Attrib -r \Pmail\Mail /D /S"). Then everything is hunky-dory until the next time. Getting a bit boring now though. Any good ideas how to prevent this sudden return to "Read-only"?