Thanks for the reply, John. The problem is that the entire encoding is wrong.
The v15 header is: Content-Transfer-Encoding: 7bit While the v16 is: Content-Transfer-Encoding: base64 I'll look into the encoding options later today. In the mean time I was wondering if anyone else was having the same issue. dave On Wed, Apr 18, 2018 at 10:33 AM, John DeSoi via 4D_Tech <4d_tech@lists.4d.com> wrote: > Maybe this change in 16.3 HF2? > >> >> ACI0097778 "BASE64 ENCODE" command inserts CRLF characters every 40000 >> characters. The new behaviour is that no more CRLF is inserted by the >> command. If CRLF is needed, it's up to the develop to insert it. > > https://bugs.4d.fr/fixedbugslist?Version=16.3_HF2 > > > John DeSoi, Ph.D. > > >> On Apr 18, 2018, at 11:12 AM, Dave Nasralla via 4D_Tech >> <4d_tech@lists.4d.com> wrote: >> >> The problem I am running into is that the body text is now rendered in >> an email like as Base64 Encoded. > > ********************************************************************** > 4D Internet Users Group (4D iNUG) > FAQ: http://lists.4d.com/faqnug.html > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:4d_tech-unsubscr...@lists.4d.com > ********************************************************************** -- David Nasralla Clean Air Engineering ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
