images not loading into sending email for gmail

This feedback helps spammers to identify which email addresses are real and which ones are not, allowing them to target real email addresses with spam messages. When I previewed my Flow execution I saw that the HTML is constructed properly.Since it is possible to include images fetched from remote servers in email messages, spammers make use of this feature to get a feedback on whether or not someone has opened the email. Replace(variables('var_Body_Str'), outputs('Image_Path'), concat('data:image/png base64,', body('Get_file_content_using_path')?))Īnd basically that did the trick. For that purpose I used the following expression:

In return I received an object, from which I needed to get the “$contents” attribute and using it replace with the original “src” attribute’s value in my newsletter’s body.

Then I used the action to get file contents from SharePoint using its path (split to the absolute site URL and then site-relative URL to the file).I then extracted the image URL, using the following expression (so from its beginning to the closing quote):.Then for each item from that array I checked, whether the string starts from “ http” – if yes that meant the element is an URL to an image.I did that using the “split” action using the ‘ src=” ‘ token (yes, with a quote). First I processed the newsletter’s body, to extract all images paths.

I managed to do it in couple of steps (having in mind that pure regular expressions are not yet available for Flow, vote for them here): 3 – seemed to be feasible in Flow, however I was also aware, that unfortunately most of the e-mail clients do not support it. This old, but still up-to-date post shows support for base64 encoded images embedded in e-mails: The base64 approachĪs I wrote above, that is fairly easy to do. So the approach with showing images inline using the “ cid method” is not very possible in case you want to show more than one file.Īd. You cannot add multiple (you can vote for it here). 2 – Flow allows you to add only one attachment. 1 – it works like a charm, but as I mentioned above – only when user really has an access to the file.Īd. Embedding image using base64 encoded string, and the “ src= data:image/jpeg base64,” (or png, or gif) value of the src attribute ( source).Īd.The “src=cid” (Content-ID) – so the internal linking in the e-mail, if the file is physically attached to the e-mail it can be displayed inline using the “cid” ( source).The “src” attribute pointing to the file hosted somewhere.However, in that approach, if a recipient has no access to the site, where the file is hosted or is not yet logged in, the images won’t show up. The most straightforward approach was to insert them as a URL to the physical file stored in SharePoint (described here). Naturally, newsletters often contain images. I was working on my newsletter’s solution, aimed to automatically send prepared messages hosted in my SharePoint.

Images not loading into sending email for gmail