Cached MIME layout going wrong

[Uday Reddy]

Now that we have a verification step for cached MIME layouts, some funny mismatches are being found.

Here is a MIME layout found for a message (in the Sent folder):

Fundamentals of Databases - Class Test paper
("multipart/mixed" "boundary=/WdrxsL1s4")
 ("text/plain" "charset=us-ascii") desc="message body text"
 ("application/pdf" "name=test1.pdf") ("inline")

But the MIME headers show:

Content-Type: application/pdf;
  name="test1.pdf"
Content-Disposition: attachment;
  filename="test1.pdf"
Content-Transfer-Encoding: base64

How did VM infer that it was an "inline" object?

[Uday Reddy (reddyuday)]

See Bug 740755 for background.

[Uday Reddy (reddyuday)]

This seems to arise only after the message is "presented". The most likely culprit is vm-mime-frob-image-xxxx. What a hack!