Re: Anyone using Thomas Maul's Email Component in v16.x?
I've tested emails for first time in v17 today and am seeing similar symptoms to OP. Is there an updated component available and if so, can someone point me to it? Cheers. -- Sent from: http://4d.1045681.n5.nabble.com/4D-Tech-f1376241.html ** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **
Re: Anyone using Thomas Maul's Email Component in v16.x?
Thanks Kirk and Rudy, I'll take a closer look at your suggestions, because some of the emails are still failing. For example, if I attach a file, the file comes through, but the email is blank. I think the email standard is so old and was never intended to do what we ask it to do nowadays. dave On Fri, Apr 20, 2018 at 3:55 PM, Kirk Brooks via 4D_Tech <4d_tech@lists.4d.com> wrote: > Dave, > You know Miyako has posted a number of suggestions and solutions to this > very issue in the last couple of years. He's also got some good stuff on > his github: > > https://github.com/miyako/4d-tips-send-mail > https://github.com/miyako/4d-plugin-gmime > > > 4d-plugin-gmime was particularly helpful for me to work out my own set of > methods for sending HTML emails. > > > On Wed, Apr 18, 2018 at 9:12 AM, Dave Nasralla via 4D_Tech < > 4d_tech@lists.4d.com> wrote: > >> Hi All, >> >> I am updating a system to v16 (16.3 HF2 32bit) from v15.5. The system >> uses Thomas Maul's excellent HTML Email Component. >> >> The problem I am running into is that the body text is now rendered in >> an email like as Base64 Encoded. >> >> Below are two relatively identical emails. One from version 15, and >> one from version 16 (16.3 HF2 32 bit on Mac OS 10.12.6). >> >> These are the raw emails I received with the relevant headers. They >> should render on an email client as a simply HTML email with a link. >> >> Any help would be appreciated. Right now it is a show stopper for >> upgrading. >> >> >> -- >> David Nasralla >> Clean Air Engineering >> >> From v15 (looks normal in an email client): >> >> Message-ID: <5ad75ba5.1c69fb81.9064a.4...@mx.google.com> >> X-Google-Original-Message-ID: <4/18/18$2144749$"No Reply" >> > >> From: No Reply >> X-Google-Original-From: "No Reply" >> Mime-Version: 1.0 >> Content-Type: multipart/alternative; >> boundary="=_NextPart_001_4/18/18_2144749" >> Content-Transfer-Encoding: 7bit >> Date: Wed, 18 Apr 2018 08:52:54 -0600 >> To: dnasra...@cleanair.com >> Subject: File ready for download >> Importance: Normal >> >> This is a multi-part message in MIME format. >> >> --=_NextPart_001_4/18/18_2144749 >> Content-Type: text/plain; >> charset="UTF-8" >> Content-Transfer-Encoding: base64 >> >> VGhlIGZpbGUgQWRoZXNpdmVfR2x1ZV9DaGFydC5wbmcgaXMgY3VycmVudGx5 >> IGF2YWlsYWJsZSBmb3IgZG93bmxvYWQgdXNpbmcgdGhlIGxpbmsgYmVsb3c6 >> IA0NaHR0cHM6Ly9zZWMuY2xlYW5haXIuY29tL2dvZmlsZS9BZGhlc2l2ZV9H >> bHVlX0NoYXJ0LnBuZz9maWxlaWQ9NXptS2hZUUVLQWtCTnplcSANDVRoaXMg >> bGluayB3aWxsIHJlbWFpbiB2YWxpZCBmb3IgMSBkYXku >> >> --=_NextPart_001_4/18/18_2144749 >> Content-Type: text/html; >> charset="UTF-8" >> Content-Transfer-Encoding: base64 >> >> PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMDEg >> VHJhbnNpdGlvbmFsLy9FTiI+DTxIVE1MPjxIRUFEPjwvSEVBRD48Qk >> 9EWT4NVGhlIGZpbGUgPGI+QWRoZXNpdmVfR2x1ZV9DaGFydC5wbmc8L2I+ >> IGlzIGN1cnJlbnRseSBhdmFpbGFibGUgZm9yIGRvd25sb2FkIHVzaW5nIHRo >> ZSBsaW5rIGJlbG93Og08YnI+DTxicj4NDTxhIGhyZWY9Imh0dHBzOi >> 8vc2VjLmNsZWFuYWlyLmNvbS9nb2ZpbGUvQWRoZXNpdmVfR2x1ZV9DaGFydC5wbmc/ >> ZmlsZWlkPTV6bUtoWVFFS0FrQk56ZXEiPmh0dHBzOi8vc2VjLmNsZWFuYWly >> LmNvbS9nb2ZpbGUvQWRoZXNpdmVfR2x1ZV9DaGFydC5wbmc/ >> ZmlsZWlkPTV6bUtoWVFFS0FrQk56ZXE8L2E+DQ08YnI+DTxicj4NDVRoaXMgbGluayB3aWxsIH >> JlbWFpbiB2YWxpZCBmb3IgMSBkYXkuDTwvQk9EWT48L0hUTUw+ >> >> --=_NextPart_001_4/18/18_2144749-- >> >> >> — >> — >> >> From v16: >> Message-ID: <5ad757e8.528c1f0a.7151f.5...@mx.google.com> >> X-Google-Original-Message-ID: <4/18/18$2087269$"No Reply" >> > >> From: No Reply >> X-Google-Original-From: "No Reply" >> Mime-Version: 1.0 >> Content-Type: multipart/alternative; >> boundary="=_NextPart_001_4/18/18_2087269" >> Content-Transfer-Encoding: base64 >> Date: Wed, 18 Apr 2018 08:36:56 -0600 >> To: dnasra...@cleanair.com >> Subject: File ready for download >> Importance: Normal >> >> VGhpcyBpcyBhIG11bHRpLXBhcnQgbWVzc2FnZSBpbiBNSU1FIGZvcm1hdC4N >> Cg0KLS0tLS0tPV9O >> ZXh0UGFydF8wMDFfNC8xOC8xOF8yMDg3MjY5DQpDb250ZW50LVR5cGU6IHRl >> eHQvcGxhaW47DQoJ >> Y2hhcnNldD0iVVRGLTgiDQpDb250ZW50LVRyYW5zZmVyLUVuY29kaW5nOiBi >> YXNlNjQNCg0KVkdo >> bElHWnBiR1VnUVdSb1pYTnBkbVZmUjJ4MVpWOURhR0Z5ZEM1d2JtY2dhWE1n >> WTNWeWNtVnVkR3g1 >> SUdGMllXbHNZV0pzWlNCbWIzSWdaRzkzYm14dllXUWdkWE5wYm1jZ2RHaGxJ >> R3hwYm1zZ1ltVnNi >> M2M2SUEwTmFIUjBjSE02THk5elpXTXVZMnhsWVc1aGFYSXVZMjl0TDJkdlpt >> bHNaUzlCWkdobGMy >> bDJaVjlIYkhWbFgwTm9ZWEowTG5CdVp6OW1hV3hsYVdROVVVOTROV3B0YTJO >> UlMydFZUbGxxUnlB >> TkRWUm9hWE1nYkdsdWF5QjNhV3hzSUhKbGJXRnBiaUIyWVd4cFpDQm1iM0ln >> TVNCa1lYa3UNCg0K >> LS0tLS0tPV9OZXh0UGFydF8wMDFfNC8xOC8xOF8yMDg3MjY5DQpDb250ZW50 >> LVR5cGU6IHRleHQv >> aHRtbDsNCgljaGFyc2V0PSJVVEYtOCINCkNvbnRlbnQtVHJhbnNmZXItRW5j >> b2Rpbmc6IGJhc2U2 >> NA0KDQpQQ0ZFVDBOVVdWQkZJRWhVVFV3Z1VGVkNURWxESUNJdEx5OVhNME12 >> TDBSVVJDQklWRTFN >> SURRdU1ERWdWSEpoYm5OcGRHbHZibUZzTHk5RlRpSStEVHhJVkUxTVBqeElS >> VUZFUGp3dlNFVkJS >> RDQ4UWs5RVdUNE5WR2hsSUdacGJHVWdQR0krUVdSb1pYTnBkbVZmUjJ4MVpW >> OURhR0Z5ZEM1d2Jt >> YzhMMkkrSUdseklHTjFjbkpsYm5S
Re: Anyone using Thomas Maul's Email Component in v16.x?
Dave, You know Miyako has posted a number of suggestions and solutions to this very issue in the last couple of years. He's also got some good stuff on his github: https://github.com/miyako/4d-tips-send-mail https://github.com/miyako/4d-plugin-gmime 4d-plugin-gmime was particularly helpful for me to work out my own set of methods for sending HTML emails. On Wed, Apr 18, 2018 at 9:12 AM, Dave Nasralla via 4D_Tech < 4d_tech@lists.4d.com> wrote: > Hi All, > > I am updating a system to v16 (16.3 HF2 32bit) from v15.5. The system > uses Thomas Maul's excellent HTML Email Component. > > The problem I am running into is that the body text is now rendered in > an email like as Base64 Encoded. > > Below are two relatively identical emails. One from version 15, and > one from version 16 (16.3 HF2 32 bit on Mac OS 10.12.6). > > These are the raw emails I received with the relevant headers. They > should render on an email client as a simply HTML email with a link. > > Any help would be appreciated. Right now it is a show stopper for > upgrading. > > > -- > David Nasralla > Clean Air Engineering > > From v15 (looks normal in an email client): > > Message-ID: <5ad75ba5.1c69fb81.9064a.4...@mx.google.com> > X-Google-Original-Message-ID: <4/18/18$2144749$"No Reply" > > > From: No Reply > X-Google-Original-From: "No Reply" > Mime-Version: 1.0 > Content-Type: multipart/alternative; > boundary="=_NextPart_001_4/18/18_2144749" > Content-Transfer-Encoding: 7bit > Date: Wed, 18 Apr 2018 08:52:54 -0600 > To: dnasra...@cleanair.com > Subject: File ready for download > Importance: Normal > > This is a multi-part message in MIME format. > > --=_NextPart_001_4/18/18_2144749 > Content-Type: text/plain; > charset="UTF-8" > Content-Transfer-Encoding: base64 > > VGhlIGZpbGUgQWRoZXNpdmVfR2x1ZV9DaGFydC5wbmcgaXMgY3VycmVudGx5 > IGF2YWlsYWJsZSBmb3IgZG93bmxvYWQgdXNpbmcgdGhlIGxpbmsgYmVsb3c6 > IA0NaHR0cHM6Ly9zZWMuY2xlYW5haXIuY29tL2dvZmlsZS9BZGhlc2l2ZV9H > bHVlX0NoYXJ0LnBuZz9maWxlaWQ9NXptS2hZUUVLQWtCTnplcSANDVRoaXMg > bGluayB3aWxsIHJlbWFpbiB2YWxpZCBmb3IgMSBkYXku > > --=_NextPart_001_4/18/18_2144749 > Content-Type: text/html; > charset="UTF-8" > Content-Transfer-Encoding: base64 > > PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMDEg > VHJhbnNpdGlvbmFsLy9FTiI+DTxIVE1MPjxIRUFEPjwvSEVBRD48Qk > 9EWT4NVGhlIGZpbGUgPGI+QWRoZXNpdmVfR2x1ZV9DaGFydC5wbmc8L2I+ > IGlzIGN1cnJlbnRseSBhdmFpbGFibGUgZm9yIGRvd25sb2FkIHVzaW5nIHRo > ZSBsaW5rIGJlbG93Og08YnI+DTxicj4NDTxhIGhyZWY9Imh0dHBzOi > 8vc2VjLmNsZWFuYWlyLmNvbS9nb2ZpbGUvQWRoZXNpdmVfR2x1ZV9DaGFydC5wbmc/ > ZmlsZWlkPTV6bUtoWVFFS0FrQk56ZXEiPmh0dHBzOi8vc2VjLmNsZWFuYWly > LmNvbS9nb2ZpbGUvQWRoZXNpdmVfR2x1ZV9DaGFydC5wbmc/ > ZmlsZWlkPTV6bUtoWVFFS0FrQk56ZXE8L2E+DQ08YnI+DTxicj4NDVRoaXMgbGluayB3aWxsIH > JlbWFpbiB2YWxpZCBmb3IgMSBkYXkuDTwvQk9EWT48L0hUTUw+ > > --=_NextPart_001_4/18/18_2144749-- > > > — > — > > From v16: > Message-ID: <5ad757e8.528c1f0a.7151f.5...@mx.google.com> > X-Google-Original-Message-ID: <4/18/18$2087269$"No Reply" > > > From: No Reply > X-Google-Original-From: "No Reply" > Mime-Version: 1.0 > Content-Type: multipart/alternative; > boundary="=_NextPart_001_4/18/18_2087269" > Content-Transfer-Encoding: base64 > Date: Wed, 18 Apr 2018 08:36:56 -0600 > To: dnasra...@cleanair.com > Subject: File ready for download > Importance: Normal > > VGhpcyBpcyBhIG11bHRpLXBhcnQgbWVzc2FnZSBpbiBNSU1FIGZvcm1hdC4N > Cg0KLS0tLS0tPV9O > ZXh0UGFydF8wMDFfNC8xOC8xOF8yMDg3MjY5DQpDb250ZW50LVR5cGU6IHRl > eHQvcGxhaW47DQoJ > Y2hhcnNldD0iVVRGLTgiDQpDb250ZW50LVRyYW5zZmVyLUVuY29kaW5nOiBi > YXNlNjQNCg0KVkdo > bElHWnBiR1VnUVdSb1pYTnBkbVZmUjJ4MVpWOURhR0Z5ZEM1d2JtY2dhWE1n > WTNWeWNtVnVkR3g1 > SUdGMllXbHNZV0pzWlNCbWIzSWdaRzkzYm14dllXUWdkWE5wYm1jZ2RHaGxJ > R3hwYm1zZ1ltVnNi > M2M2SUEwTmFIUjBjSE02THk5elpXTXVZMnhsWVc1aGFYSXVZMjl0TDJkdlpt > bHNaUzlCWkdobGMy > bDJaVjlIYkhWbFgwTm9ZWEowTG5CdVp6OW1hV3hsYVdROVVVOTROV3B0YTJO > UlMydFZUbGxxUnlB > TkRWUm9hWE1nYkdsdWF5QjNhV3hzSUhKbGJXRnBiaUIyWVd4cFpDQm1iM0ln > TVNCa1lYa3UNCg0K > LS0tLS0tPV9OZXh0UGFydF8wMDFfNC8xOC8xOF8yMDg3MjY5DQpDb250ZW50 > LVR5cGU6IHRleHQv > aHRtbDsNCgljaGFyc2V0PSJVVEYtOCINCkNvbnRlbnQtVHJhbnNmZXItRW5j > b2Rpbmc6IGJhc2U2 > NA0KDQpQQ0ZFVDBOVVdWQkZJRWhVVFV3Z1VGVkNURWxESUNJdEx5OVhNME12 > TDBSVVJDQklWRTFN > SURRdU1ERWdWSEpoYm5OcGRHbHZibUZzTHk5RlRpSStEVHhJVkUxTVBqeElS > VUZFUGp3dlNFVkJS > RDQ4UWs5RVdUNE5WR2hsSUdacGJHVWdQR0krUVdSb1pYTnBkbVZmUjJ4MVpW > OURhR0Z5ZEM1d2Jt > YzhMMkkrSUdseklHTjFjbkpsYm5Sc2VTQmhkbUZwYkdGaWJHVWdabTl5SUdS > dmQyNXNiMkZrSUhW > emFXNW5JSFJvWlNCc2FXNXJJR0psYkc5M09nMDhZbkkrRFR4aWNqNE5EVHho > SUdoeVpXWTlJbWgw > ZEhCek9pOHZjMlZqTG1Oc1pXRnVZV2x5TG1OdmJTOW5iMlpwYkdVdlFXUm9a > WE5wZG1WZlIyeDFa > VjlEYUdGeWRDNXdibWMvWm1sc1pXbGtQVkZQZURWcWJXdGpVVXRyVlU1WmFr > Y2lQbWgwZEhCek9p > OHZjMlZqTG1Oc1pXRnVZV2x5TG1OdmJTOW5iMlpwYkdVdlFXUm9aWE5wZG1W > ZlIyeDFaVjlEYUdG > eWRDNXdibWMvWm1sc1pXbGtQVkZQZURWcWJXdGpVVXRyVlU1WmFrYzhMMkUr > RFEwOFluSStEVHhp > Y2o0TkRWUm9hWE1nYkdsdWF5QjNhV3hzSUhKbGJXRnBiaUIyWVd4cFpDQm1i > M
Re: Anyone using Thomas Maul's Email Component in v16.x?
Be careful: it used to be the case that a CRLF was put every 80 chars or so (can’t remember the exact number) At some point (v15?) this was no longer the case: no CRLF’s at all. At least here in Belgium, it caused a lot of problems because the software at the internet provider’s side didn’t interpret this in the correct way, which caused the e-mails to be unreadable. Regards, Rudy Mortier Two Way Communications bvba > On 18 Apr 2018, at 18:33, 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 4 >> 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 > ** ** 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 **
Re: Anyone using Thomas Maul's Email Component in v16.x?
Hi Magnus. Wow. The original Tech Note was published over 9 years ago! http://kb.4d.com/assetid=75229 I've asked Thomas to republish it again somewhere. It's a testimony that it's been used for so long. dave On Fri, Apr 20, 2018 at 12:50 PM, Magnus Torell via 4D_Tech <4d_tech@lists.4d.com> wrote: > Dear Dave or Thomas, > > I would also very much appreciate the component (and source) > for v16 / 17. I use it heavily in v15R5 and preparing for an upgrade > and have noticed that my component is not working in v16/17. > > I did some tweaking on the version I got. Can't remember what, > but maybe I need to do it again. I am not sure, but maybe I did a > transfer of one method to the host ...rewriteURL... or something. > > So please if a link could be made public I am most thankful. > Maybe some useful changes also have made its way in to the latest... > > > Best Regards > Magnus Torell > > > > -- > Sent from: http://4d.1045681.n5.nabble.com/4D-Tech-f1376241.html > ** > 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 **
Re: Anyone using Thomas Maul's Email Component in v16.x?
Dear Dave or Thomas, I would also very much appreciate the component (and source) for v16 / 17. I use it heavily in v15R5 and preparing for an upgrade and have noticed that my component is not working in v16/17. I did some tweaking on the version I got. Can't remember what, but maybe I need to do it again. I am not sure, but maybe I did a transfer of one method to the host ...rewriteURL... or something. So please if a link could be made public I am most thankful. Maybe some useful changes also have made its way in to the latest... Best Regards Magnus Torell -- Sent from: http://4d.1045681.n5.nabble.com/4D-Tech-f1376241.html ** 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 **
Re: Anyone using Thomas Maul's Email Component in v16.x?
Hi Tim, Thanks for your post. I did look at your forum link, and yes, I was seeing the exact same thing. Unfortunately, none of their work-arounds worked for me. I still would end up with a Base64 encoded email being presented to the user. This morning, Thomas Maul emailed me with a link to his current component, and said he was able to successfully send an email - and it worked for me! He doesn't remember making any changes specifically, but said he could have easily changed his code over the years, and the same goes on my end. If I have time later, I want to compare the key routines to see what made the difference. Either way, it's working for me now. Thanks for you input - always appreciated! dave On Wed, Apr 18, 2018 at 1:51 PM, Timothy Penner via 4D_Tech <4d_tech@lists.4d.com> wrote: > Maybe it's related to this: > http://forums.4d.com/Post/EN/21192530/1/21206974#21192531 > > -Tim > > > > ** > 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 **
RE: Anyone using Thomas Maul's Email Component in v16.x?
Maybe it's related to this: http://forums.4d.com/Post/EN/21192530/1/21206974#21192531 -Tim ** 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 **
Re: Anyone using Thomas Maul's Email Component in v16.x?
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 4 >> 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 **
Re: Anyone using Thomas Maul's Email Component in v16.x?
Maybe this change in 16.3 HF2? > > ACI0097778"BASE64 ENCODE" command inserts CRLF characters every 4 > 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 **
