On to the next thing....
When Pegasus Mail starts up it populates the new mail folder by processing all new mail files. A new mail file is not necessarily associated with a message that just arrived. Every message in the new mail folder is an individual file, a "new mail" file. These files have a .CNM extension. A corrupted or zero byte new mail file might be causing the problem.
The first step is to use a file explorer to look in the mailbox directory for any zero byte .CNM files. Delete any that are found then try starting Pegasus Mail.
If that's not it, you'll need to move all of the .CNM files out of the mailbox directory. If you keep a large number of messages in your new mail folder, start by moving out just the .CNM files date stamped after the problem began, then trya startup. If it still hangs, move them all out then attempt a startup.
A successful startup indicates a problem with one of the moved .CNM files. The only way to identify the specific one is by moving small blocks of them back at a time, testing between each move until you have failure, and then narrowing it down to a specific file within that block of files. This can take a bit of planning and record keeping if you have a large number of new message files.
Good luck!
<p>On to the next thing....</p><p>When Pegasus Mail starts up it populates the new mail folder by processing all new mail files.&nbsp; A new mail file is not necessarily associated with a message that just arrived.&nbsp; Every message in the new mail folder is an individual file, a "new mail" file.&nbsp; These files have a .CNM extension.&nbsp; A corrupted or zero byte new mail file might be causing the problem.
</p><p>The first step is to use a file explorer to look in the mailbox directory for any zero byte .CNM files.&nbsp; Delete any that are found then try starting Pegasus Mail.&nbsp;
</p><p>If that's not it, you'll need to move all of the .CNM files out of the mailbox directory.&nbsp; If you keep a large number of messages in your new mail folder, start by moving out just the .CNM files date stamped after the problem began, then trya startup.&nbsp; If it still hangs, move them all out then attempt a startup.</p><p>A successful startup indicates a problem with one of the moved .CNM files.&nbsp; The only way to identify the specific one is by moving small blocks of them back at a time, testing between each move until you have failure, and then narrowing it down to a specific file within that block of files.&nbsp; This can take a bit of planning and record keeping if you have a large number of new message files.</p><p>Good luck!</p><p>&nbsp;</p>