This issue with SMTP and MIME has come up before.  For more information on what is happening refer to the following link sagecity.na.sage.com/.../31586.aspx

Yes - I had read that previously, but that post is from 2008.    I have been in contact with Sage also on this.  You have the ability to attach different kinds of invoices already.   The problem is that they are coding the email into the universal MIME format, or at least using the same format throughout the email.  

The email contains plain text followed by UU-Encoded PDF which makes it an invalid email.

If you want to send UU-Encoded PDFs, then that must be the only content, the message can't contain any other text.   If the message needs to have text and PDFs, then the message needs to be MIME encoded.

So I'm looking for a solution possibly that converts that email into the proper code, before sending the email out.

That was the purpose of referring you to the old post.  It is doubtful that Sage has fixed the issue since it was first documented.  I'm not sure it is even on their radar to address in future versions.

As the old post points out the Sage 500 EmailUtils.DLL routine SendEmailViaSMTP calls to the Collaboration Data Objects (CDO) to set the attachment.  By default the Collaboration Data Objects uses UUencode when creating attachments.  Without a modification to the EmailUtils.DLL to set the MIME that you need, you will need to look at a 3rd party solution such as PDF Blaster to send your attachments in a readable format.  

Thanks so much......Yes Sage acted as if they've never heard of such a thing - I went through 3 support people and of course the problem is on my side so they say.    

I just am shocked that more users don't have a problem.   I can't believe all their users use Exchange, which supposedly does not cause that issue......

Very frustrating - as we like MAS so much - but after implementing electronic invoicing, thinking to save man hours, we are now increasing them because clients can't read the invoicing.  

And of course I don't have the SDK so not able to modify that dll........do you have any other suggestions?

Well other than the two third party solutions mentioned in the earlier post for the issue I referenced, I don't know of anything else.  Maybe someone else has suggestions for that.  You could also check with your reseller to see if they are Sage 500 developers with the SDK code and have them make the necessary modifications to set the proper MIME as well as look into the authentication issue you noted in a separate post.  

I happened to be in the email utility DLL today for version 7.4 and took a quick look at sending emails through SMTP.  To my surprise I see that Sage has hard coded that CDO not use MIME (oCDOsysMail.MimeFormatted = False) within the procedure SendEmailViaSMTP.  I wonder why Sage would have this setting, or is this something that was there before Sage 500 added the capability to send PDFs?

Gosh, too many logins, too many new portals, and what's this "Join Group to post?"  Sorry.

So, the way that I worked around this was to use an internal open smtp relay in queue mode (Linux).

I then have a script that parses the contents of the email queue, decodes the attachment, re-attaches it as MIME, and then recreates the email.  This script is scheduled to run every X minutes, and the queue itself is sent every few hours.

UUEncode is from the package SharUtils, but I think you can use MUNPACK/MPACK as well.  I also use Mutt and Sendmail, but those are certainly can be substituted with other mail servers/clients to suit your preferences.

It's a workaround, a bit brute-forcish, and not the most elegant solution.  But on the other hand, I haven't had to touch it for about 4 years.

I have a couple bits of information about this issue. The first is to try the following around

1 - From Sage 500 ERP, Common Information, Maintenance, CI Setup, Setup Document Transmittal

2 - Remove the contents in the Body Text area and save

3 - From the recipient's Internet Explorer(person who opens/views the attachment), go to Tools, Compatibility View and add the website related to the email address. For example if the recipient is using google or yahoo email addresses, enter google.com  or yahoo.com in the 'Add this website' text box.

4 - Then click Add and Close

The second bit of information is that we are planning to deliver a fix for this issue in the Sage 500 ERP April Product Update. The fix is not the workaround described above, but is a code fix for SMTP.  

The code fix includes a change to the setting oCDOsysMail MimeFormatted = True.

-Tony