> Since I had a hang this morning due to aan email with a  large
> attachment file being downloaded, I cannot start PMAIL up.  The normal
> setup sequence is carried out right up to the opening of the MAIL
> folder, that completes, then the program exits.  When the large file
> was hanging Pegasus, I went into the POP3 option to see which file was
> causing the error..  I* found it, and when I tried to delete it,
> everything froze.  I rebooted, and now have this problem.  I'm
> guessing that it is an "in use" lock file file somewhere.  Any
> suggestions as to which one?  There are no zero size files in the
> PMAIL/MAIL/<user> directory. 
Move all of the *.CNM files out of the new mail directory and try again.  It should now open normally.  You can then put the messages back one at a time until you find the problem message.  
It's probaby going to be a really large message.  If you are using content control then I'd recommend that you set a limit on the message size so you are not scanning these large files with encoded attachments.
 
        <div>&gt; Since I had a hang this morning due to aan email with a &nbsp;large</div><div>&gt; attachment file being downloaded, I cannot start PMAIL up. &nbsp;The normal</div><div>&gt; setup sequence is carried out right up to the opening of the MAIL</div><div>&gt; folder, that completes, then the program exits. &nbsp;When the large file</div><div>&gt; was hanging Pegasus, I went into the POP3 option to see which file was</div><div>&gt; causing the error.. &nbsp;I* found it, and when I tried to delete it,</div><div>&gt; everything froze. &nbsp;I rebooted, and now have this problem. &nbsp;I'm</div><div>&gt; guessing that it is an "in use" lock file file somewhere. &nbsp;Any</div><div>&gt; suggestions as to which one? &nbsp;There are no zero size files in the</div><div>&gt; PMAIL/MAIL/&lt;user&gt; directory.&nbsp;</div><div>
</div><div>Move all of the *.CNM files out of the new mail directory and try again. &nbsp;It should now open normally. &nbsp;You can then put the messages back one at a time until you find the problem message. &nbsp;</div><div>
</div><div>It's probaby going to be a really large message. &nbsp;If you are using content control then I'd recommend that you set a limit on the message size so you are not scanning these large files with encoded attachments.</div><div>
</div>