Image inserted into mail body not displayed if the message is autosaved as Draft
Problem reported by Ionel Aurelian Rau - 3/25/2019 at 5:56 AM

This is a problem that has plagued us for a long time and we were unable to put our fingers on it 100% of the time. Bottom line is: in some cases, we send mails composed in WebMail and which have an image inserted in the mail body, but after it`s sent the picture is not displayed in any mail client including WebMail.

Today we have been able to come up with a 100% way to reproduce the problem and these are the steps:
  1. Using WebMail, create a new mail (a pop up will appear with the compose mail view)
  2. Right away, enter some text in the mail body and insert a picture (normally we Copy/Paste one from a Word or Excel). Write some more text in the mail body.
  3. Wait until the mail is autosaved as draft -> is is very important! Check that the mail has appeared in the Drafts folder to make sure
  4. Send the mail after is has been autosaved as draft
  5. Observe that the picture you inserted in the mail body is not displayed, but is replaced by a placeholder (depends on the mail client)
We send tens of these emails on a daily basis to partners and is causing us a lot of grief because some would be able to see the picture and some not. Now we know that if we send the mail before it`s autosaved as draft, the picture will display, but if it gets autosaved, then the picture is swallowed by a black hole, never to see the light of day.

Hope this is enough information for you to reproduce and fix the problem - looking forward to a new version containing the fix.

This is tested also with the latest SM 17 version: Build 7016 

3 Replies

Reply to Thread
Ionel Aurelian Rau Replied
I know this is not that important, but can we at least get a confirmation that indeed this is a bug and will be solved at some point?
Employee Replied
Employee Post
Ionel, I was able to reproduce the behavior. I have added it to our bugs list.
Ionel Aurelian Rau Replied
Great, thanks for the info! I know your developers are busy and this is not that urgent, but it`s good to know you plan to have it fixed when possible in a future build.

Reply to Thread