When I receive email with pictures I get an equal number of blank boxes at the beginning of the mail. Is this something that TB is doing or possibly Win 7?
The blank boxes are nothing that I can click on to open, just blank boxes with a little icon in the upper left corner. Today I received an e-mail with 29 blank boxes followed by 29 pictures. Some times I will receive email with pictures with descriptive text and the descriptive text is by itself and the pictures are further down on the page. I have tried to track if this is only occurring from only one contact or ISP but it seems it doesn't matter, I've had this from AOL, AT&T. G-mail, etc.
Chosen solution
My gut reaction is it will be either outlook, or someone using an apple device. iPhone or iPad. There is a couple of places there encoding it grey. Microsoft went one way and Mozilla went the other. There does not appear to be any compromise. both insisting they are following the RFC and the users be damned. This may change now we are under new management with a more "suck it up princess" approach. But first we have to survive the separation from Mozilla. A very slow and painful process. Hindered by the lack of a release engineer or funds to hire one.
Read this answer in context 👍 1All Replies (3)
I think you will find it is from one email client. I am making assumptions. But the usual cause is the image is not encoded correctly to be displayed in the email, so in accordance with the show attachments inline option , the attachments are shown at the end of the email.
Matt, I get this from different people and different ISP's. Could it be that the encoding problem could be originating from the same ISP such that the folks who are forwarding mail to me go it from someone who had that particular e-mail client? Such as AOL?
Chosen Solution
My gut reaction is it will be either outlook, or someone using an apple device. iPhone or iPad. There is a couple of places there encoding it grey. Microsoft went one way and Mozilla went the other. There does not appear to be any compromise. both insisting they are following the RFC and the users be damned. This may change now we are under new management with a more "suck it up princess" approach. But first we have to survive the separation from Mozilla. A very slow and painful process. Hindered by the lack of a release engineer or funds to hire one.