vm team mailing list archive

[Uday Reddy <u.s.reddy@xxxxxxxxxxxxx>]

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...

Visit the directory in dired or something, and rename all the crash
folders to something else so that you don't lose them.  You can always
visit these folders in VM later and save the messages into other
folders.

Reset all your configuration settings to original values and check to
see that you have the original functionality at least.

After you get back to normal, I would like you to set your RMAIL and
.record crash boxes to be consistent with your vm-crash-box-suffix,
i.e., add ".crash" suffix to the folder's name without any other
alterations.  Let us see if that fixes your problem.

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