User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3 Build Identifier: Thunderbird 1.0.6 If you use IMAP to retrieve a message of size > 30K, the textual body of the message is replaced with the message: This body part will be downloaded on demand The user is left with no means of retrieving the body of the message. The bug only appears when the message is sent to a (gnu mailman) mailing list, it does not appear when the same message is sent directly to the list subscribers. The mailman software is version 2.1.5 (recent). The bug only appears when the message is retrieved via IMAP, when using POP-3 Thunderbird displays both the body and attachment without a problem. The bug seems to relate to the "Mime Parts on Demand" feature, referenced here: http://www.mozilla.org/quality/mailnews/tests/sea-mn-mpod.html Reproducible: Always Steps to Reproduce: 1. compose an email with some body text and an attachment so that the size of the message is greater than 30k 2. subscribe to a mailing list managed by gnu mailman 3. post the message to the list 4. read the message received from the list via IMAP Actual Results: Instead of seeing the body text of the original posted message, you see: This body part will be downloaded on demand The attachment is present. Expected Results: It should have shown the body of the message, or at least provided some means of accessing it. Inspection of the message in the cyrus mail store shows that the body text is present. Thunderbird is replacing it with: This body part will be downloaded on demand This bug has not been tested with user agents other than Thunderbird, so it is conceivable that the bug relates to the cyrus implementation of IMAP, rather than Thunderbird. The cyrus version is recent (a few months old), debian version 2.1.18-1.

This message is taken directly from the cyrus mail store. It shows the bug when retrieved via IMAP (but POP-3 appears fine).

Duplicate of/related to bug 215313 -> Core bug 149771 and/or bug 265022 -> Core bug 246415?

(In reply to comment #2) > Duplicate of/related to ... bug 149771 or ... bug 246415? Quite likely. Leni Mayo: See the potential workaround at bug 149771 comment 31 -- if that works for you, please mark this bug as a dupe of that one.

No response from reporter, duping. *** This bug has been marked as a duplicate of 149771 ***