none
Email body is empty for emails sent from saved .msg file in Outlook 2013 RRS feed

  • Question

  • Hi,

    Last week we've encountered a weird problem.

    In a 2 day period, all of a sudden clients were calling saying that the mails they had send using our program were empty !?!

    (Others were still working)

    We didn't do any updates and it worked the days before so I suspect a Windows Update to be the reason.

    (However, I cannot seem to find out wich one, they are almost all "security updates" ...)

    After a lot of debugging, I found out that this occurs because the mails are in fact .msg files wich we've created.

    (Using a .net VSTO addin)

    I then started outlook in safe mode, created a new email with content and then did a manual save to a msg file using the menu.

    When I opened the file I saw the content, but when i sent it to myself it was empty !?!

    So it is in fact a general problem (and not a programming problem), it simply seems to be Outlook itself ! :-s

    In our software, we work a lot with msg files so this is an urgent problem.

    Is there someone who can help me out with this ?

    Any suggestions / workarounds / fixes are welcome.

    Many thanks,

    Fred

    Monday, August 31, 2015 10:12 AM

Answers

  • Hi Eugene,

    It happens on EVERY MSG-FILE created in Outlook 2013 (version 15.0.4745.1000). By code or directly by the program.

    The steps to reproduce :

    • Open Outlook 2013
    • Create New Mail (by default HTML)
    • Enter body, subject, to, ...
    • Saveas msg-file with Unicode.
    • Do not send mail, just close it.
    • Open the msg file in your explorer (by double clicking it).
    • Content will be visible
    • Click the send button.
    • Mail is sent but body is empty (wich is now also visible in sent items).

    I now found a workaround to solve the problem.

    I've noticed that it worked if I switched the bodyformat to RichtText and back (to HTML) !!

    However, doing it using the mail.BodyFormat property messed up my content if tables were in it.

    I then tried the CommandBars.ExecuteMso() sub wich DID WORK !

    So now I do the following on the load event of my email :

    • inspector.CommandBars.ExecuteMso("MessageFormatRichText")
    • inspector.CommandBars.ExecuteMso("MessageFormatHtml")

    However, if for some reason the user would not use our addin and would like to save to msg then he would have the same problems we've encountered.

    Friendly regards,

    Fred

    Monday, August 31, 2015 2:28 PM

All replies

  • I suggest you try uninstalling (on a test system) the most recent updates to Outlook 2013 one by one and checking after each uninstall if the problem has been resolved.  When functionality has been restored it seems likely that the most recently uninstalled update was the culprit.  If uninstalling Outlook 2013 updates doesn't resolve the issue then you follow the same procedure with other recent Office 2013 updates.

    You could also use System Restore to bring a test system back to a point before the most recent updates were installed.  After making sure that the use of MSG files was functioning properly you could work forward in an attempt to find the responsible Outlook/Office 2013 update.

    WORKAROUND:

    Open Outlook and drag and drop the MSG file from the file system folder  into the Outlook Drafts folder.

    Open the message from the Drafts folder, make any changes and then send the message.


    • Edited by RLWA32 Monday, August 31, 2015 11:56 AM
    Monday, August 31, 2015 10:57 AM
  • Hello Frederick,

    Why do you need to deal with .msg files? Most probably there is an alternative way for getting the job done. What is your final goal?

    Are you able to reproduce the issue with a sample .msg file? Or does it depend on a particular property/setting?

    Could you please describe the exact steps for reproducing the issue? 

    Also please specify the build number of your Outlook.

    Monday, August 31, 2015 12:42 PM
  • Hi Eugene,

    It happens on EVERY MSG-FILE created in Outlook 2013 (version 15.0.4745.1000). By code or directly by the program.

    The steps to reproduce :

    • Open Outlook 2013
    • Create New Mail (by default HTML)
    • Enter body, subject, to, ...
    • Saveas msg-file with Unicode.
    • Do not send mail, just close it.
    • Open the msg file in your explorer (by double clicking it).
    • Content will be visible
    • Click the send button.
    • Mail is sent but body is empty (wich is now also visible in sent items).

    I now found a workaround to solve the problem.

    I've noticed that it worked if I switched the bodyformat to RichtText and back (to HTML) !!

    However, doing it using the mail.BodyFormat property messed up my content if tables were in it.

    I then tried the CommandBars.ExecuteMso() sub wich DID WORK !

    So now I do the following on the load event of my email :

    • inspector.CommandBars.ExecuteMso("MessageFormatRichText")
    • inspector.CommandBars.ExecuteMso("MessageFormatHtml")

    However, if for some reason the user would not use our addin and would like to save to msg then he would have the same problems we've encountered.

    Friendly regards,

    Fred

    Monday, August 31, 2015 2:28 PM
  • Thank you for sharing the solution for other forum readers!
    Monday, August 31, 2015 3:13 PM
  • What worked for me (I had problems with messages created from OFT files) was to reset the HTMLBody property followed by a call to Save. Doing that twice seems to do the trick. Talk about voodoo..

    Dmitry Streblechenko (MVP)
    http://www.dimastr.com/redemption
    Redemption - what the Outlook
    Object Model should have been
    Version 5.5 is now available!

    Tuesday, September 1, 2015 5:57 AM
  • It looks like it might be a bug from a recent update.  Following from patchmanagement.org:

    Problem with Windows Update KB3055012 and email templates - Microsoft 
    Community:
    http://answers.microsoft.com/en-us/office/forum/office_2013_release-outlook/problem-wi \
    th-windows-update-kb3055012-and-email/85f90120-5e10-489e-a670-da399b5732be?page=2&auth \
    =1
    
    "
    
    I created an email template with a form in it to sent specific info.
    
    It worked just fine until after August Windows Updates. After that all 
    the body of the email desapears completely if sent in HTML format, but 
    if I don't sent it in that format the form disappears.
    
    I looked for the possible reasons like disabling add-ins, changing 
    default themes or fonts, even changing outlook profile but nothing 
    worked, so I started to uninstall updates specific to Outlook 2013 and 
    the first one was KB3055012. After uninstalling it, everything went back 
    to normal."
    
    =======
    "Thank you all for providing the additional details.  I was able to 
    repro using the steps SvenOpdebeeck provided.  The issue has been 
    submitted as a bug and the Outlook Product Team is investigating.  I'll 
    post back when I know the fix will be available."
    
    

    Tuesday, September 1, 2015 6:45 PM
  • Hi guys,

    I'm sorry to bother you again ...

    Seems like the above method did the trick for Outlook 2013, but now we have Outlook 2016 users who are encountering the same problem except ... the solution wich worked for OL 2013 don't seem to work for OL 2016. :-s

    Same problem :

    OL 2016 seems to have problems with sending emails directly from saved .msg files.

    They do seem to be sent, however, the receiver gets an empty email. (The email is also saved empty in the 'Sent Items')

    This problem is making our software useless ...

    Anyone ???

    Friendly regards,

    Fred

    Friday, February 5, 2016 12:57 PM
  • Did you try to reset the HTMLBody property and call Save (twice)?

    Dmitry Streblechenko (MVP)
    http://www.dimastr.com/redemption
    Redemption - what the Outlook
    Object Model should have been
    Version 5.5 is now available!

    Friday, February 5, 2016 1:23 PM
  • Hi Dmitry,

    Thanks for your response.

    What exactly do you mean by "resetting the HTMLBody" ??

    Many thanks in advance,

    Fred

    Monday, February 8, 2016 7:39 AM
  • MailItem.HTMLBody = MailItem.HTMLBody
    MailItem.Save
    MailItem.HTMLBody = MailItem.HTMLBody
    MailItem.Save
    


    Dmitry Streblechenko (MVP)
    http://www.dimastr.com/redemption
    Redemption - what the Outlook
    Object Model should have been
    Version 5.5 is now available!

    Monday, February 8, 2016 1:39 PM
  • I've seen the same problem and found this article 

    According to this, the problem is there if you have KB3055012 installed. Some suggests to remove this update, but with patch routines it will be applied again. Another suggestion is to use *.otf format and save as a mail template. 

    I have tested the KB3114500 and this update seems to fix the issue.

    I find it strange that none of the Microsoft KB articles describes that the issue is fixed (KB3085579 or KB3114500)

    Regards,


    Michael Møller

    Tuesday, February 23, 2016 8:24 AM
  • MailItem.HTMLBody = MailItem.HTMLBody
    MailItem.Save
    MailItem.HTMLBody = MailItem.HTMLBody
    MailItem.Save


    Dmitry Streblechenko (MVP)
    http://www.dimastr.com/redemption
    Redemption - what the Outlook
    Object Model should have been
    Version 5.5 is now available!

    Where to put this?
    Thursday, June 21, 2018 7:22 AM
  • What is your code that fails?

    Dmitry Streblechenko (MVP)
    http://www.dimastr.com/redemption
    Redemption - what the Outlook
    Object Model should have been
    Version 5.5 is now available!

    Thursday, June 21, 2018 2:58 PM