there's a message on [EMAIL PROTECTED] with the subject "This message
crashes Evo" that had an invalid binary email address.

Remove this mesage from ~/evolution/local/Inbox/movemail

Since Evolution was not able to fully import your local spool, it left a
copy in ~/evolution/local/Inbox/movemail so that the next check could
continue and thus not lose mail.

Anyways, this bug has already been fixed in CVS so there should soon be
another release containing a fix.

Jeff

On Thu, 2002-05-02 at 22:48, Rob Brown-Bayliss wrote:
> Hi
> 
> I have just had a problem recieving mail from a local spool.
> 
> I clicked in the send/recieve button, and about 40% of the way through
> importing the system went crazy, chewing up arround 300megs of swap
> space and thrashing the hard disk to bits.
> 
> I waited for several mins to let things calm down and when it was
> obvious they would not I cannned evolution and assumed my mails were
> lost forever.
> 
> Now every time I start evolution, when it gets round to automatically
> checking for mail teh same thing happens (I should point out that at the
> moment there is no mail in the locla spool).  It seems to just go on for
> ever and ever, but the first few mails it recieved before teh first fit
> are imported again which makes me thing there is a copy of the original
> mail spool still hanging around where ever evo copies it too, is this
> correct and can I reclaim the lost emails and maybe find the one causing
> the problem?
> -- 
> 
>   R  Brown-Bayliss
>  ---====<=>=====---
>   http://zoism.org
> 
> _______________________________________________
> evolution maillist  -  [EMAIL PROTECTED]
> http://lists.ximian.com/mailman/listinfo/evolution
> 


_______________________________________________
evolution maillist  -  [EMAIL PROTECTED]
http://lists.ximian.com/mailman/listinfo/evolution

Reply via email to