<P>Recently I have noticed that PMail 4.51 does not always behave gracefully when Windows file permissions for *.PMM files are set incorrectly.  </P><P>For example, if you're using a "User Level" Windows account, but Pegasus Mail was originally setup under an "Administrator Level" Windows account, then it is possible that some of the critical Pegasus files (such as *.PMM's) will have their permissions set in such a way that they can only be written/modified from an Administrator Level Windows account.  When this happens, and file permissions get screwed up, Pegaus does not inform the user about these bad file permissions.  PM simply fails to move files to the requested folder, or in the worst case, "copies to self" e-mails disappear forever.</P><P>Bottom Line: Pegasus should evaluate the security permissions of files (such as *.PMM files) and warn the user when it can not complete an operation due to screwed up file permisssions.</P><P>Even more fundamentally, PM should throw out some sort of warning dialog to the end user when file write operations can not complete as expected.</P>