I agree with Henrik. The fact is that Pmail actually changes the "last update" (not only the "last accessed") timestamp of its mailbox files and sets the Archive attribute on them even when doing just a search on them, ie not changing their contents in any way.
This is annoying because the files appear as having been modified even if they are not, and any decent backup software is therefore going to copy them unnecessarily. (I routinely use "robocopy" but every other copy or backup package gets fooled the same way).
I can confirm that this behaviour has been there since many years, say I noticed it at the time of Windows 95. And it's not a matter of OS, its Pegasus which does it.
I believe this happens because when opening a mailbox Pegasus obviously cannot know in advance whether the user will be going to modify its contents or not, and therefore always opens the file in "Read+Write" mode thus forcing the underlying OS to set the "last update" timestamp to the current date and time and the and Archive flag to the "true" state.
To see what I mean just try this: open a command shell in your mail folder, reset the files' Archive attribute with "attrib -A *.*", run Pegasus, do a simple global text search in the mailbox content, close Pegasus. You will see ("attrib *.*") that all the .PMM files (and many other too...) have been "modified" by this read-only operation, ie they now have their Archive attribute set and "last update" timestamp updated.
Regards,
Corrado
<p>I agree with Henrik. The fact is that Pmail actually changes the "last update" (not only the "last accessed") timestamp of its mailbox files and sets the Archive attribute on them even when doing just a search on them, ie not changing their contents in any way.</p><p>This is annoying because the files appear as having been modified even if they are not, and any decent backup software is therefore going to copy them unnecessarily. (I routinely use "robocopy" but every other copy or backup package gets fooled the same way).
</p><p>I can confirm that this behaviour has been there since many years, say I noticed it at the time of Windows 95. And it's not a matter of OS, its Pegasus which does it.</p><p>I believe this happens because when opening a mailbox Pegasus obviously cannot know in advance whether the user will be going to modify its contents or not, and therefore always opens the file in "Read+Write" mode thus forcing the underlying OS to set the "last update" timestamp to the current date and time and the and Archive flag to the "true" state.
</p><p>To see what I mean just try this: open a command shell in your mail folder, reset the files' Archive attribute with "attrib -A *.*", run Pegasus, do a simple global text search in the mailbox content, close Pegasus. You will see ("attrib *.*") that all the .PMM files (and many other too...) have been "modified" by this read-only operation, ie they now have their Archive attribute set and "last update" timestamp updated.</p><p>Regards,</p><p>&nbsp; Corrado</p><p>&nbsp;</p>