Bugzilla

I've sort of been able to duplicate the problem using the reporter's msg1 email fixed up by appending a larger image to it that exceeds the mime "fetch on demand" threshold which is 30,000 bytes. However, I only see a problem if I have the setting "View Attachments Inline" turned off. The original msg1 email setting in inbox still displays the image but when I do a reply, I only see the text in the message and no image or attachment links. Also, it happens on the first reply.  If I send the message (to myself) I see only imap urls in the source and not the actual image data, and the received message is only text.

If I increase the fetch on demand threshold to 300,000, the reply shows the complete message including image and, when sent, the received message shows the complete message and source shows the image data and not just imap urls.

Typically when the setting for "view attachments inline" is set and all the mime parts of the message are viewable inline, the whole message is fetched.  So I'm curious to know if the reporter has "Display attachments inline" set or not. I can see the message being fetched in parts in the gmail imap:5 log so it appears that it is not set.

Reporter, also the message I attached will probably always work because the image is less than 30000 bytes.

P/S: While working on caching issues I think I have seen this problem before.

I've sort of been able to duplicate the problem using the reporter's msg1 email fixed up by appending a larger image to it that exceeds the mime "fetch on demand" threshold which is 30,000 bytes. However, I only see a problem if I have the setting "View Attachments Inline" turned off. The fixed up msg1 email setting in inbox still displays the image but when I do a reply, I only see the text in the message and no image or attachment links. Also, it happens on the first reply.  If I send the message (to myself) I see only imap urls in the source and not the actual image data, and the received message is only text.

If I increase the fetch on demand threshold to 300,000, the reply shows the complete message including image and, when sent, the received message shows the complete message and source shows the image data and not just imap urls.

Typically when the setting for "view attachments inline" is set and all the mime parts of the message are viewable inline, the whole message is fetched, all in one piece.  So I'm curious to know if the reporter has "Display attachments inline" set or not. I can see the message being fetched in parts in the gmail imap:5 log so it appears that it is not set.

Reporter, the message I attached will probably always work because the image is less than 30000 bytes.

P/S: While working on caching issues I think I have seen this problem before.

I've sort of been able to duplicate the problem using the reporter's msg1 email fixed up by appending a larger image to it that exceeds the mime "fetch on demand" threshold which is 30,000 bytes. However, I only see a problem if I have the setting "View Attachments Inline" turned off. The fixed up msg1 email setting in inbox still displays the image but when I do a reply, I only see the text in the message and no image or attachment links. Also, it happens on the first reply.  If I send the message (to myself) I see only imap urls in the source and not the actual image data, and the received message is only text.

If I increase the fetch on demand threshold to 300,000, the reply shows the complete message including image and, when sent, the received message shows the complete message and source shows the image data and not just imap urls.

Typically when the setting for "view attachments inline" is set and all the mime parts of the message are viewable inline, the whole message is fetched, all in one piece.  So I'm curious to know if the reporter has "Display attachments inline" set or not. I can see the message being fetched in parts in the gmail imap:5 log so it appears that it is not set.

Reporter, the message I attached will probably always work because the image is less than 30000 bytes. According the imap log, your image was about 90K bytes so it exceeds the threshold for fetch on demand.

P/S: While working on caching issues I think I have seen this problem before.