In 4D starting with v14, 4D no longer limits the lines to 60 chars when you do BASE64_Encode. (it used to do that in v13) As a result, some email servers reject the message (but not always).
After I split the lines in the Base64 encoded blob into 60 chars each (by only using a line feed), the mail was delivered correctly. Interestingly, Gmail put this mail in the spam before, after the correction it doesn’t. Regards, Rudy Mortier Two Way Communications bvba ----------------- > On 09 Mar 2017, at 17:23, Two Way Communications via 4D_Tech > <[email protected]> wrote: > > Hi guys, > > Since my customer is using 4D v15.4 (2 weeks now), he is experiencing > frequent issues while sending e-mails. > > I did have to change SMTP_SetPrefs from (0;1;0) to (1;8;0), but 95% of the > emails are sent correctly. > > For the other 5%, they get an error mail from the provider’s email stating > that the e-mail could not be delivered. > > it says: > > Status: 5.1.1 > Diagnostic-Code: smtp; 501 5.5.4 Syntax error in BODY parameter > > > Has 4D something changed in the headers of outgoing mail messages? What is it > doing different in v15.4? > > > Regards, > > Rudy Mortier > Two Way Communications bvba ----------------- > > ********************************************************************** > 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] **********************************************************************
