Hi Jeffrey, I am seeing this as well with build 16R4.216142. From my testing, it seems that when you specify the default encoding with SMTP_SetPrefs and with SMTP_Charset(0,0), whatever you pass as the email body actually gets Base64 encoded. So, if you were already encoding your message body before adding it with SMTP_Body, what ends up being sent is doubly encoded.
-Jim On Thu, Aug 31, 2017 at 11:54 AM, Jeffrey Kain via 4D_Tech < [email protected]> wrote: > Anyone else seeing Base64 encoding not working correctly in the version 16 > of 4D Internet Commands? > > We haven't debugged this 100% yet, but it seems to be adding some > incorrect padding characters to the base64 text depending on the length of > the source message, which causes mail clients to not decode the messages > correctly. > > Unfortunately, UTF-8 + Base64 is the new default in 4DIC, so if you just > whip up some code using the defaults it's not going to work. > > UTF-8 and quoted-printable seems fine as a workaround > > Anyone else seeing this? > ********************************************************************** > 4D Internet Users Group (4D iNUG) > FAQ: http://lists.4d.com/faqnug.html > Archive: http://lists.4d.com/archives.html > Options: http://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:[email protected] > ********************************************************************** ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
