Community Discussions and Support
Mailbox randomly becoming Read-only

Right. Presumably also when it shuts down. Scripts are on the wrong side of my expertise threshold - but I'll get reading ...

Right. Presumably also when it shuts down. Scripts are on the wrong side of my expertise threshold - but I'll get reading ...

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"?

> 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.

All I can tell you is that neither Pegasus Mail nor Mercury is changing the files to read-only.  You'll have to look elsewhere on the system for the solution.  

<p>> 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.</p><p>All I can tell you is that neither Pegasus Mail nor Mercury is changing the files to read-only.  You'll have to look elsewhere on the system for the solution.   </p>

Ok, thanks. That's a surprise, as I can't think what else would be forcing a change in the attributes of the folders/files. Have to get the thinking cap on again.[*-)]

Ok, thanks. That's a surprise, as I can't think what else would be forcing a change in the attributes of the folders/files. Have to get the thinking cap on again.[*-)]

[quote user="Walshp"]Ok, thanks. That's a surprise, as I can't think what else would be forcing a change in the attributes of the folders/files. Have to get the thinking cap on again.[*-)]

[/quote]

And if you don't find the reason you may want to create a script executed when the server is started ...

[quote user="Walshp"]Ok, thanks. That's a surprise, as I can't think what else would be forcing a change in the attributes of the folders/files. Have to get the thinking cap on again.[*-)] <p>[/quote]</p><p>And if you don't find the reason you may want to create a script executed when the server is started ...</p>
			Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft