forwarding a mail + attaching a file
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
VM |
Fix Committed
|
Medium
|
Uday Reddy |
Bug Description
Rene reports (viewmail-info, 2012-04-01):
With VM 8.2.0b I recently ran into the following problem when
forwarding a mail and attaching a file.
The indications I get when composing the message are alright:
1. vm-forward-message [ATTACHMENT forwarded message, message/rfc822]
2. vm-attach-
But actually what is being sent is:
,----
| Content-Type: message/rfc822
| Content-
| Content-
`----
which is ok for the forwarded message part.
On the other hand, here is what is sent for the attached file:
,----
| Content-Type: message/rfc822
| Content-
| filename="foo.doc"
| Content-
`----
which is not exactly what you'd expect.
Related branches
Changed in vm: | |
milestone: | 8.2.0 → 8.2.90a |
Changed in vm: | |
milestone: | 8.2.90a → 8.2.89a |
Changed in vm: | |
milestone: | 8.2.89a → 8.2.0b1 |
no longer affects: | vm/8.2.x |
Changed in vm: | |
milestone: | 8.2.1a → 8.2.0 |
Changed in vm: | |
milestone: | 8.2.1a → 8.2.90a |
Seems to be a problem only when forwarding a message and attaching a document.
There is a MIME error when trying to preview the message composition:
("message/rfc822") desc="document" ("attachment" "filename=UCU Form - Email.doc")
("error/error") desc="MIME part missing header/body separator line" ("attachment")
The problem was present in VM 8.2.0a, but not 8.1.93a. Bisecting...
Present in rev. 1164, but 1163 is ok.
The silly case of an uninitialized variable inside a loop.