A corrupted new message file could be causing a problem during the processing of new messages that Pegasus Mail does during startup. To check this, use a file explorer and navigate to that users new mail directory and move out of that directory all files with the .CNM extension that have a date stamp newer than the last time that user successfully started Pegasus Mail. If that user can now start Pegasus Mail then you know its a bad new message file. Note: A .CNM file of zero size is probably the problem file so remove it and test a startup.
There isn't an easy way identify a bad message file if it's not of zero size. All you can do is to move a few message files at a time back into the mailbox directory testing after each move until you identify the bad file.
If you don't know where that users new message directory is you can first check the default location of C:\PMAIL\MAIL\username. If they're not in the default location you can start Pegasus Mail as one of the other users and click the 'Info" button in Help > About Pegasus Mail. The resulting display will contain the path to the mailbox directories.
BTW, be sure you've allowed Pegasus Mail to sit in the "not responding" state for several minutes before assuming it has crashed. That "not responding" state displays much too quickly, not recognizing that Pegasus Mail is busy with some background task. Processing a large number of new messages and/or new mail filtering could result in the display of "not responding" until the processing is complete.
<p>A corrupted new message file could be causing a problem during the processing of new messages that Pegasus Mail does during startup.&nbsp; To check this, use a file explorer and navigate to that users new mail directory and move out of that directory all files with the .CNM extension that have a date stamp newer than the last time that user successfully started Pegasus Mail.&nbsp; If that user can now start Pegasus Mail then you know its a bad new message file.&nbsp; Note: A .CNM file of zero size is probably the problem file so remove it and test a startup.</p><p>There isn't an easy way identify a bad message file if it's not of zero size.&nbsp; All you can do is to move a few message files at a time back into the mailbox directory testing after each move until you identify the bad file.</p><p>If you don't know where that users new message directory is you can first check the default location of C:\PMAIL\MAIL\<i>username.</i>&nbsp; If they're not in the default location you can start Pegasus Mail as one of the other users and click the 'Info" button in Help &gt; About Pegasus Mail.&nbsp; The resulting display will contain the path to the mailbox directories.
</p><p>BTW, be sure you've allowed Pegasus Mail to sit in the "not responding" state for several minutes before assuming it has crashed.&nbsp; That "not responding" state displays much too quickly, not recognizing that Pegasus Mail is busy with some background task.&nbsp; Processing a large number of new messages and/or new mail filtering could result in the display of "not responding" until the processing is complete.</p><p>&nbsp;</p>
