RE
0
O365 Web modifying image paths?
I'm having issues with image paths in outlook 365 web blocking images, even though the domain is on the safe sender list. Inspecting the code, I see a base64 reference instead of the http:// image path that is in the original code, like so:
<img data-imagetype="External" src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAEALAAAAAABAAEAAAIBTAA7" originalsrc="http://(etc...) >
This is not happening in Outlook desktop. Nor is it happening in personal 365 accounts, but is happening in multiple corporate 365 accounts (at different domains.) Any suggestions on how to fix? Thanks!
Experiencing the same thing, @Rachel have you figured out why this happened?
We specified the
srcvalue with an actual URL so I don't think the issue is in the actual email template itself. And when the email is opened in Outlook Desktop App it shows properly.Only when we tried opening the very same email from Outlook Web, the images refuse to load - inspecting the DOM reveals that the original value of the img
srchas now been moved tooriginalsrc- and thesrcvalue has now been changed todata:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAEALAAAAAABAAEAAAIBTAA7- exactly the same value that you have on yours.The fact that we use different images and different CDNs, yet we get EXACTLY the same value for the
srcfeels like an issue on the Outlook Web side.Hi Kevin, glad its not just me! We are currently working under the theory that it might be because our image paths are http and not https. We are testing out that theory. Are you using https?
@Rachel I have posted this on Twitter as well
( https://twitter.com/kevinMario/status/1518835012493225984?s=20&t=d4WX1FYXx6vJKQUKstY5Cg )
and I can confirm that from the screenshot that Sendgrid ( the service that sends our comms ) are using
httpso I'm not sure if that is the problem?Do let us know if your theory worked! :)
Also FYI there is a question on the Microsoft Forums from back in 2020 regarding the same issue we're having. Doesn't seem to be a solution though.
( https://answers.microsoft.com/en-us/outlook_com/forum/all/images-received-in-html-email-are-not-loading/d3899252-0665-49e3-af82-f78112080eb4 )
Hi Kevin,
Thanks for sharing those links. We applied secure paths to one brand and that did solve the problem, but oddly enough, we are seeing the issue resolved on other brands where we had not yet implemented https. Now instead of the b64 src, its putting in an outlook proxy URL:
<img data-imagetype="External" src="https://cosmicimg-prod.services.web.outlook.com/proxy/?u=http%3A%2F%2Fimage.e.domainemailer.com%2Flib%2Ffe8612727362017472%2Fm%2F1%2F2488f64d-4eb6-418a-9572-a8da3df595a3.jpg&t=eyJhbGciOiJSUzI1NiIsImtpZCI6ImpBbHNObGNxYmZyV0tGczJzb2NhMFBLQURobyIsInR5cCI6IkpXVCIsIng1dCI6ImpBbHNObGNxYmZyV0tGczJzb2NhMFBLQURobyIsImlzc2xvYyI6IkJZQVBSMDdNQjU2MDgiLCJzcWlkIjo2Mzc4NjAyMDM3Nzc0NTQ1MDN9.eyJpYXQiOjE2NTEyNTMyMTUsInZlciI6IlNUSS5Vc2VyLlYxIiwic2FwLXZlcnNpb24iOiI1IiwiYXBwaWQiOiJmMjA0MTUwNC0yZjgxLTQ5M2QtYWY4ZC1iNGIzNTBjZWZlNTciLCJpc3NyaW5nIjoiV1ciLCJhcHBpZGFjciI6IjIiLCJ0aWQiOiJkMzAwOGZkNDBkMjA0MThiYmYzMDRlNzBkOTEwYzcyNyIsInNjcCI6IkltYWdlUHJveHktSW50ZXJuYWwuUmVuZGVyIiwidG9wb2xvZ3kiOiJ7XCJUeXBlXCI6XCJNYWNoaW5lXCIsXCJWYWx1ZVwiOlwiQllBUFIwN01CNTYwOC5uYW1wcmQwNy5wcm9kLm91dGxvb2suY29tXCJ9IiwicHVpZCI6IjEwMDMyMDAxNDZGNzMzMzQiLCJlcGtoIjoiZjFQV1NtWWZzbzZsUXhoTiIsIm5iZiI6MTY1MTI1MzIxNSwiZXhwIjoxNjUxMjU0MTE1LCJpc3MiOiJodHRwczovL3N1YnN0cmF0ZS5vZmZpY2UuY29tL3N0cy8iLCJhdWQiOiJodHRwczovL291dGxvb2tpbWFnZXByb3h5LmF6dXJld2Vic2l0ZXMubmV0IiwicGtyIjoiUExPa3ZudGNxTjVFNElTOHFhWWc3TEtWSXlBPSIsInNzZWMiOiJDNWtxOEN2Q1A3RzRrNUlzIn0.fTcH-p7nEFjMpRmCJeGNArzn-JGZzBVCnJH4PKJygDiuS0GXXeNARfJ9gOADWlFyeExnUv7TTnsnMcUxW2Nspf5oywui4GGrmaYp-PZOg_fYXZgxw6PIgTcVptJLaH9mN97nvGA-k4LeLOTTjqPbVMVaPoAsFgEs27YWClJxrwSTZ6d0gqHLn4qDJXLTEySwDzCz4gMfCV5UG56s1TvobbRmPt422UilEjfg2i0_Txm8q2FA5RY1jll_i5Bq7Tf0-OqScYjhDCvNdOzGiWWRiczR4pQQuF-q-MSOt2-3MEsyVNI_S2euNC9Xm3fX6g-FWhEqxWFID3HKMo7qWVtP-g&r=p&s=b" originalsrc="http://image.e.domainemailer.com/lib/fe8612727362017472/m/1/2488f64d-4eb6-418a-9572-a8da3df595a3.jpg" data-imageproxyendpoint="/actions/ei" alt="hero image" width="600" height="328" border="0" style="display:block">
However, some users are still getting the b64 encoding where others are now seeing the proxy URL, on the same email (and same browser, etc). Have you experienced this?