retitle 330474 mutt: rewrites Content-Length message header in mbox folders to be zero, which subsequently causes mutt to nuke the entire message body thanks
My initial diagnosis of this bug was overly complex. Here's a repro recipe. 1) Open any mbox folder with "mutt -R". (-R means "read-only", you don't have to do this, but it will allow you to observe the bug without destroying your mail folder). 2) Tag one or messages in that folder. 3) Observe the Content-Length headers in the message(s) you've tagged. In most cases of real-world mail, the header value will be non-zero. 4) C)opy the tagged message(s) to a new folder. 5) Quit. 6) Use $PAGER or $EDITOR to view the new folder. 7) Observe the Content-Length headers in the message(s). Note that they are all zero. 8) Observe that the message body (or bodies) is/are still present. 9) Open the new folder with mutt. Don't specify -R this time. 10) Read the message(s) in it. 11) Observe that you can't read the message body. 12) Quit back to the index, and quit mutt. Don't use "exit". We want changes written to the folder. 13) Use $PAGER or $EDITOR to view the new folder again. 14) WHERE THE HELL ARE THE MESSAGE BODIES? Retitled bug accordingly. I stand by the severity of this report. I don't know if it's specific to mbox folders; that's just the only format I ever use. -- G. Branden Robinson | You are not angry with people when Debian GNU/Linux | you laugh at them. Humor teaches [EMAIL PROTECTED] | them tolerance. http://people.debian.org/~branden/ | -- W. Somerset Maugham
signature.asc
Description: Digital signature
