VM

Encoding corrupts the INBOX file

Bug #397917 reported by anakreon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
VM
Fix Released
Undecided
Unassigned

Bug Description

The error message I get is:
vm-decode-mime-encoded-words-in-string: Wrong type argument: stringp, =\?iso-2022-jp\?Q\?
VM version is: 8.0.12
Emacs
GNU Emacs 22.3.1 (i486-pc-linux-gnu, GTK+ Version 2.14.7) of 2009-03-31 on raven, modified by Debian

Vm is installed as a debian package.

After this error, I can not read new mail, nor the old ones. For all operations, I get the error message shown above.
This is the third time I end with a useless INBOX file. I hope there is a solution to this problem.

I will be able to provide any additional information by Monday.

Revision history for this message
Mikko Huhtala (mhuhtala) wrote :

I'm getting hit by this at an increasing frequency. It's making VM quite painful to use. The corrupted inbox can be fixed by looking up the last message that appears in the Summary buffer and then editing the inbox in fundamental mode and remove the following message (that is, if you don't mind deleting the offending message).

Is this whole project dead? The last changes to the stable code were over six months ago and to the development branch nearly a year ago. It seems no bugs have changed status in about a year.

I've been using VM since 2000 and I'd hate to change email clients, but the current state of VM on Emacs 23 is getting unbearable.

Revision history for this message
Uday Reddy (reddyuday) wrote :

If you have bzr installed, please pull the latest revision from the 8.0.x branch, as explained in the README file. I believe that the latest revision works but Rob never released it. -- Uday

Changed in viewmail:
status: New → In Progress
Uday Reddy (reddyuday)
Changed in viewmail:
status: In Progress → Fix Committed
Uday Reddy (reddyuday)
Changed in vm:
status: New → Fix Released
milestone: none → 8.0.13
Changed in viewmail:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.