I know gmail and hotmail have introduced their own image proxies. I have sent email with simple img tag with src
and gmail converts it like this
Original URL is the direct URL to the image. In the attached image, you can see the request and response headers for this image.
<strong>Problem: Please let me know what steps should I take to make this image visible inside gmail.</strong>
PS: I am facing the same issue with hotmail as well.Answer1:
<strong>I think I have figured out the GoogleImageProxy issue.</strong>
I have answered this in another question as well ( <a href="https://stackoverflow.com/questions/28965219/images-inside-gmail-email-not-being-displayed" rel="nofollow">images inside gmail email not being displayed</a> ).
This is something related to CACHING concept. suppose, you have recently deployed your php code on your server but you forgot to upload images. you tested once with your email logic. your system generated an HTML email. When this email will hit the gmail server GoogleImageProxy will try to fetch and store the images from your site to its own proxy server. while fetching the images, GoogleImageProxy found some 404 statuses against your missing images and 403 against some protected images. GoogleImagesProxy has stored these statuses into its own proxy server.
Now tried to open your email, you noticed some 404 statuses against your images. This is something understandable. You immediately realized that you forgot to upload some images, so you uploaded them to your server. and also you have fixed some permissions against protected images.
You are all done now. Now you try to run your php-email script once again. As a result you receive another email in your Gmail or Hotmail inbox. you had fixed all the issues with your images. Now the images must be displayed in your email content. but you are still unable to see the images.
Ah, possibly you forgot to clear your browser's cache. Clear your browser's cache and load the gmail or hotmail page once again. But the result will be still the same. Try to apply dozens of fixes/patches and try to run your php-email script a thousands time. But the result will be still the same. No improvement.
<strong>THE REAL PROBLEM</strong>
What the hell is going on? Let me explain it to you. Go to your access log and try to find requests from GoogleImageProxy. You'll be surprised to see that there will be only 2 or 3 three requests from GoogleImageProxy depending on the number of different images used in your email. GoogleImageProxy never tried to fetch images Even after you have fixed the issues with your images by uploading missing images and setting permissions for protected images. Why? Clearing your browser's cache has no impact. GoogleImageProxy will never fetch the fresh images even for your newer email because the images are now cached into GoogleImageProxy along with their last status code and not cached in your own browser's.
GoogleImageProxy has set its own expiry date for the images. I think one month. so now the fresh copy of images will be fetch after expiry date. I mean after one month. You can not force GoogleImageProxy to fetch the images. But its important for you to display images in your email. What can be the solution?
Following is the only way to force GoogleImageProxy to fetch your images<ul><li>Rename your images to something else with png, jpg or gif extensions only.</li> <li>Don't use any kind of query string in your image url like "?t=34343"</li> <li>your image must include png, jpg or gif as an extension.</li> <li>your image url must be mapped onto your image directly.</li> <li>If you need to use some proxy url for your protected images then your</li> <li>response must include the proper header like "content-type:image/jpeg"</li> <li>File extension and content-type header must match</li> <li>Status-code must be 200 instead of 403, 500 etc</li> </ul>
Try to repeat the whole process for every run of php-email script. because every time GoogleImageProxy will cache your images and you'll have to repeat the same process for every new try.
Hopefully this will fix the issue for most of the people. In my case this has fixed the issue.Answer2:
hese are embedded images. You send an image as an attachment and then use it in your img element like: . Gmail transforms the "cid" link to its internal file storage link and that's why it gives element.
This is one of two common ways to have images within email.
The other way is to keep images in your hosting and send img elements with external links: <a href="http://yourdomain.com/yourimage.png" rel="nofollow">http://yourdomain.com/yourimage.png</a> I strongly recommend to use the second approach especially if you expect to have a lot of images in your email. I had problems with attached images display on Gmail which I couldn't solve.Answer3:
Make sure your <strong>from</strong> address is a real valid email and not in the form
I'm using Amazon SES to send emails, and inlining some but not all images as attachments. For me it was the non-attachments that were breaking.
Eventually I realized I was using a 'fake' email for the from field.
My real email is
To make it easy to filter emails in gmail I used the
+ syntax to create a 'fake' email for testing purposes.
This works great, except it seems to be changing the behavior of the spam/image filter. My image tags ended up completely stripped of the
As soon as I switched back to using the actual email then all the images showed up.