vm team mailing list archive

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

mere user writes:

> I think the problem may be that the crash file is created in ~/Mail/ but vm
> is then looking for it under ~/
> regardless of its extension, when I move the crash file to ~/, vm finds it
> there.  
> does this help?

Thanks, Eli.  I think that must be the problem.  In your
vm-spool-files setting, you didn't give the full path name for the
crash box.  If you give the full path name, you should be fine.  

I am downgrading the bug report now.  Please get back to us if this
doesn't cure the problem.

Cheeers,
Uday

** Changed in: viewmail
       Status: In Progress => Incomplete

** Changed in: vm
       Status: In Progress => Incomplete

** Changed in: vm
   Importance: High => Low

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