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:4d_tech-unsubscr...@lists.4d.com **********************************************************************
