Bugzilla

Although there are non-obvious workarounds for this, the basic problem here is that if you have no offline store and your messages exceeds the allocated memory cache or you have cache.memory disabled (the default for >=78) and you have an attachment that is inherently not inline (like a zip or pdf) and you have fetch parts on demand turned off, the part number for the attachment, e.g., [2], is never fetched when it is saved. Also, the full message, [], is not re-fetched. Only the message body, [1], is re-fetched.

However, when the attachment is **opened** the full message **is** re-fetched and the attachment appears correctly in the application.

So the question is why is the imap access method different between "open" and "save-as" when accessing an attachment?

Although there are non-obvious workarounds for this, the basic problem here is that if you have no offline store and your messages exceeds the allocated memory cache or you have cache.memory disabled and you have an attachment that is inherently not inline (like a zip or pdf) and you have fetch parts on demand turned off  (the default for >=78), the part number for the attachment, e.g., [2], is never fetched when it is saved. Also, the full message, [], is not re-fetched. Only the message body, [1], is re-fetched.

However, when the attachment is **opened** the full message **is** re-fetched and the attachment appears correctly in the application.

So the question is why is the imap access method different between "open" and "save-as" when accessing an attachment?

Although there are non-obvious workarounds for this, the basic problem here is that if you have no offline store and your messages exceeds the allocated memory cache or you have cache.memory disabled and you have an attachment that is inherently not inline (like a zip or pdf) and you have fetch parts on demand turned off  (the default for >=78), the part number for the attachment, e.g., [2], is never fetched when it is **save-as**'d. Also, the full message, [], is not re-fetched. Only the message body, [1], is re-fetched.

However, when the attachment is **opened** the full message **is** re-fetched and the attachment appears correctly in the application.

So the question is why is the imap access method different between "open" and "save-as" when accessing an attachment?

Although there are non-obvious workarounds for this, the basic problem here is that if you have no offline store and your message size exceeds the allocated memory cache or you have cache.memory disabled and you have an attachment that is inherently not inline (like a zip or pdf) and you have fetch parts on demand turned off  (the default for >=78), the part number for the attachment, e.g., [2], is never fetched when it is **save-as**'d. Also, the full message, [], is not re-fetched. Only the message body, [1], is re-fetched.

However, when the attachment is **opened** the full message **is** re-fetched and the attachment appears correctly in the application.

So the question is why is the imap access method different between "open" and "save-as" when accessing an attachment?