vm team mailing list archive

[mere user <emacs_user@xxxxxxxxxxx>]

Hi Uday, indeed, this is great progress, and the documentation is very
clear about the need to specifying a full path.  sorry for not noticing
this!

things are nearly perfect now, but I think there may still be a problem.
when I set the crash box address using the full path and read mail, the
mail still is left in the crash box rather than being read into the main
box and presented by vm.  however, the good news is that when I press g
in the vm buffer (that is, call vm-get-new-mail again), the crash box is
now read and moved over.

this is good enough for me to be able to use the development version,
but perhaps there is still a minor bug there?

cheers,

-- 
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: Incomplete
Status in VM (View Mail) for Emacs: Incomplete

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