Hi,
We are having problems with getting embedded images to load on mobile phones.
We are using Aspose.Words in order to create a word document (using mailmerge).
We can use the documents "save' method to convert the document to several formats.
We have tried Docx, Pdf and Mhtml, with al these formats the images are visible in
the generated document when we open the document with an appropriate viewer
(or send it as an attachment via email). This seems to indicate that we are
correctly inserting the images into the document.
When we send document as the body of an email(we save the Aspose.Words.Document as mhtl)
however, the images may, or may not, be there depending on who/what is receiving the mail.
When the recipient is a windows/outlook client, the images are embedded correctly.
When the mail is send to a mobile phone (either a W7 or IPhone) only an empty box is shown.
From experience I know you guys like to have code samples to work with,
however, since the generation of the documents and the sending of the mail
are done in seperate parts of our system, extracting working code
(without making a mistake) will be quite hard.
The two parts of the system pass the data around as a Byte[] and as mentioned above,
the images DO show up in outlook. Which leads me to believe the code is correct,
and before I go into the trouble of extracting all the code,
I ask if there might be something obvious we are missing?
Kind regards,
Verne.
Note: we are using the following versions.
Aspose.Email 2013.01.25
Aspose.Words 2013.01.31
Images also seem to load in Outlook WebAccess.
Hi Verne,
I am sorry for the delayed response.
I am carrying some tests and request you to spare me little time. I will soon share my findings and write back here on the forum.
Thanks for your patience and understanding in this regard.
Hi,
I can understand your position, and I am trying not to be worried, however, the email system is an essential part of our current project, which involves a particular, quite well known social website. The projects is also scheduled to launch early next week and this little problem has caught us quite off-guard. (We have been testing mostly with Windows clients, which worked fine.)
I am not saying this to put any pressure on you (well, I am a little bit), I am asking for quick feedback, so that we can decide whether to stick with our current approach, or that we need to switch to a backup plan.
Kindly awaiting your response,
Verne.
Hi Verne,
We are sorry for the trouble caused to you.
As part of my current research on this, I was able to observe the issue by viewing the email on iPhone and I am carrying out some more tests in this regard. I have taken up this issue with our development team and will soon get back to you about our findings in this regard.
Hi Kashifv,
Great!
Reproduction is the first step towards a solution.
Please let us know when you have an estimate or a fix.
(as mentioned, we do have a some urgency.)
Regards,
Verne.
Hi Verne,
We have this issue in past as well and we found it to be an issue at smartphone end. It is not a bug of Aspose.Email as Aspose sends HtmlBody of message correctly, without any changes. However we are logging this issue so that it can be investigated again.
This issue is logged in our issue tracking system as NETWORKNET-33681.
We will write back you as soon as some feedback is received from the developers.
I did a quick Google search.
Perhaps this is helpful?
http://stackoverflow.com/questions/1520067/embedded-images-in-html-email-not-displaying-on-mobile-phones
It mentions that the ‘content type’ is important.
Honestly, I am just guessing here but there are a few worried looks here in the room.
Hope it helps,
Verne.
Hi Verne,
Thank you for sharing your findings.
I have logged these in our issue tracking system against the logged issue. It may be useful in further investigation towards the resolution of this issue by development team. In case of any further information in this regard, I’ll update you here accordingly.
Hi,
I know from experience that you guys generally say very little once a ticket number
has been issued, only to fix the problems a few days later. The first part is
understandable and the second actually quite impressive.
However, I kindly urge you to be a bit more forthcoming with information.
As I've mentioned in previous posts, we are rapidly approaching the deadline
on our project. For us this means that we need enough information to make a decision.
Could you please let me know the status of this issue,
if it is considered a priority or not, and/or if a quick solution
(workaround/hack/alternative) is likely in the near future?
I understand that you, nor we, can control all the email clients in the world,
so if this is an technical limitation, we might just have to accept that.
Right now, for us, the most important part is to know.
Kind regards,
Verne.
Hi Verne,
We are sorry for the inconvenience you are facing continuously.
Normally, customer issues are served on first come first served basis, unless customer has PS (Priority) or ES (Enterprise) support that can prioritize their issues for resolution.
Anyways, I have discussed your concerns with our development team and would like to share with you that this issue has been scheduled for next week due to some other high priority tasks. We’ll be able to share the status of this issue by mid next week or at most end of next week. Once the investigation is complete and I have something for you to share, I’ll write back here to let you about the status. I have also logged your concerns against the logged issue for reference to our development team.
Hi,
A quick reminder that we have not received any information yet, something we did not get around last week because all the preparations for launch day. Which is tomorrow.
We were however forced to go live with a less than optimal user experience, any ideas on when we can address that issue?
Kind regards,
Verne.
Hi Verne,
Thanks for contacting Aspose.Email support team again.
I have checked the issue status and found that its planned in our upcoming release expected before first half of April, 2013. You will be automatically notified once the new version is released and available online.
Please feel free to write us back if you have any other query related to Aspose.Email.
Hi Aspose team,
We are now live with Kroodle, first Facebook insurer in the world. Allthough it’s a softlaunch, there is a lot of attention in the media; internet, newspaper and radio.
Therefore I would like to discuss this issue to get some more priority. We are getting recommendations about other solutions which are able to show embedded pictures in mobile mail. We would very much like to stick with Aspose.
Please contact me on:
email: djk@verne.nu
skype: djk.verne
to have a chat about the status and options.
regards,
Dirk-Jan Klinkhamer
Hi Dirk-Jan Klinkhamer,
We are aware of your concerns and appreciate your association with Aspose.
I already discussed the status of this issue with our development team yesterday, and would like to share with you that this issue is currently under investigation (not in queue). Hopefully, we’ll be in a position to share its status during this week. In case, we get to a fix for this problem, we can manage to provide a quick fix version to you.
The priority of this issue can be increased if you subscribe to our Priority or Enterprise support. But as the issue is already under process of investigation by our development team, I would suggest to please spare us a little more time for completion of our investigation.
Please let me know if you want to opt for Priority or Enterprise support, I’ll be glad to assist you further accordingly.
ok, we’ll wait for your reply. Keep us posted.
Hi Dirk-Jan Klinkhamer,
Thank you for your patience.
We have almost completed our investigation and would like to share with you that we have identified the reason for this problem. For embedded images to be displayed properly on iPhone, the should refer to Content-ID instead of file name in the HtmlBody of the message. e.g.
img src=“image.001.jpeg” should be img src="cid:352b5d49-1427-45e3-acb7-57edf7db3f38"
Until the fixed version is available for this problem, you can try any of the following work around methods for proper display of embedded images on iPhone. Please try it at your end and let us know your feedback.
Method 1
Document wordDocument = new Document(@"testdoc.docx");
MemoryStream mhtmlStream = new MemoryStream();
wordDocument.Save(mhtmlStream, SaveFormat.Mhtml);
// Load the MHTML in MailMessage
mhtmlStream.Position = 0;
MailMessage message = MailMessage.Load(mhtmlStream, MessageFormat.Mht);
message.From = "from@gmail.com";
message.To = "to@aspose.com";
message.Subject = "Testing Workaround method 1";
foreach (Aspose.Email.Mail.LinkedResource linkedResource in message.LinkedResources)
{
linkedResource.ContentId = linkedResource.ContentLink.ToString();
}
message.HtmlBody = message.HtmlBody.Replace("<img src=\"", "<img src=\"cid:");
Method 2
// Invoice.doc contains embedded images
Document wordDocument = new Document("testdoc.docx");
MemoryStream mhtmlStream = new MemoryStream();
wordDocument.Save(mhtmlStream, SaveFormat.Mhtml);
// Load the MHTML in MailMessage
mhtmlStream.Position = 0;
MailMessage message = MailMessage.Load(mhtmlStream, MessageFormat.Mht);
message.From = "from@gmail.com";
message.To = "to@aspose.com";
message.Subject = "Testing Workaround method 2";
foreach (Aspose.Email.Mail.LinkedResource linkedResource in message.LinkedResources)
{
string oldStr = string.Format("<img src=\"{0}\"", linkedResource.ContentLink);
string newStr = string.Format("<img src=\"cid:{0}\"", linkedResource.ContentId);
message.HtmlBody = message.HtmlBody.Replace(oldStr, newStr);
Hello Aspose Team,
Fantastic, it is working.
It turned out we needed version 2 to get it to work.
We have not completed extensive testing yet, but we are off to a good start.
Thank you very much.
I'll keep you posted might we run into further problems.
Again, thanks.
The issues you have found earlier (filed as NETWORKNET-33681) have been fixed in this update.
This message was posted using Notification2Forum from Downloads module by aspose.notifier.
Okay, we are going to check it out.
We have discovered that the images do not show up when the mail resides on out (slightly ancient Exchange) mail server. However, considering our target demographic and the fact that G-mail is working correctly, we do not see this as a problem.
Kind regards,
Verne.