← Back to team overview

vm team mailing list archive

[Bug 285222] Re: IMAP dropping message to crash file, freezing emacs

 

mere user writes:

> while experimenting with this, I suddenly cannot retrieve messages from
> the crash files created with the latest vm, even using 8.0.12.
> strange...

Hi Eli, any update on this?  Did you manage to get VM working again?

If you can copy the crash files away, and examine them in Emacs as
well as VM, there might be some clues in them as to what might be
going wrong.

As a general rule, even if some incoming mail goes to crash box, it
should get processed if you run vm-get-new-mail again.  There should
be no need to switch to a different version of VM to process the crash
box.  Please let me know if you are able to get the crash box messages
in this way in the devo version.

Cheers,
Uday

-- 
IMAP dropping message to crash file, freezing emacs
https://bugs.launchpad.net/bugs/285222
You received this bug notification because you are a member of VM
development team, which is the registrant for vm.

Status in View Mail (aka VM) for Emacs: In Progress
Status in VM (View Mail) for Emacs: In Progress

Bug description:
 affects viewmail
 importance critical 



Hi,

I'm having some problems using emacs 23 from CVS, and VM 591 from the
bzr repo.

First, when collecting messages from my work's IMAP server, they
invariably end up in my mail.crash file, then I have to `vm-get-new-
mail' again to recover the messages.  Note collecting from a another
pop mailbox works fine.

from my *Messages* buffer:
 Checking for new mail for /home/eschulte/mail/mitre...
 Recovering messages from ~/mail/mitre.crash...
 Added to /home/eschulte/mail/mitre
 Recovering messages from ~/mail/mitre.crash... done

Second, VM continually freezes my emacs, at first I thought this was
because it was collecting mail, so I set `vm-auto-get-new-mail' to
nil, but still VM will burn my CPU and freeze my emacs for 5-20
seconds at a time.

Does anyone have any advice for what may be going wrong, or how I can
generate a more helpful error report?

Thanks -- Eric




References