We are sending RTF Mails over COM using Word and Outlook functions. Here a code snippet of what is done:

        Set objDocument = objWord.Documents.Open(FileName:=strFileName, ReadOnly:=True)
        Set outMailItem = objDocument.MailEnvelope.Item       
         outMailItem.Save
        retEntryId = outMailItem.EntryID        
objOutlook.Application.Session.GetItemFromID(retEntryId )	
If Not objMail Is Nothing Then
            With objMail
                .To = sEmpfnger
                .CC = sEmpfngerCC
                .BCC = sEmpfngerBCC 
                .Subject = KontaktItem.Betreff
                .OriginatorDeliveryReportRequested = True
                .ReadReceiptRequested = True
                .Importance = KontaktItem.Wichtigkeit
                For lngIndex = 1 To lngUBound
                    If FileDirExist(AnhangList(lngIndex)) Then
                        .Attachments.Add AnhangList(lngIndex)
                             End If
                Next
                .Send
             End With

One of our customers is using Office 2013 and Exchange 2013 and after installing the latest patches a few weeks ago, he is unable to send any mails containing RTF Text.

Exchange returns this error, it seems that the email address is not properly transmitted to outlook, if word is used in the process.

Remote Server returned '550 5.1.0 RESOLVER.ADR.InvalidInSmtp; encapsulated INVALID address inside an SMTP address (IMCEAINVALID-)'

We send email address personATdomain.com, but exchange transforms it to this, as if the AT wasn't transfered in the right codepage:

"'personATdomain.com'" <IMCEAINVALID-+27person+40domain+2Ecom+27ATmy-domain.com>

Doesn't matter, if we send it to internal or external email addresses.

Latest patches have been installed on outlook and exchange, but did not change anything.

If we send the email without using word, directly to outlook, there is no error, but we are unable to send RTF mails.

 Set rMail = rOutlook.CreateItem(0) 

There is also no error, if we enable cachemode in outlook, but since our customer is using terminal server, this is not an option.

It seems, Sage is having a similar issue (articleid=31583)

• Edited by Provis AG 34 minutes ago typo