I exclusively use CR - Char(13), I never use Char(10) in combination, and never had this issue until v16.
From the documentation for v16 and v15 SMTP_SetPrefs: Parameter = lineFeed, Type = longint, Description: 1 = [default] Add, 0 = Don't Add, -1 = No Change SMTP servers recognize the end of a line to be a combined carriage return/line feed (CR/LF) character pair. This differs from most Mac applications, which view a single carriage return as the end of line/paragraph marker. I guess the above confused me, since it says "Add" not "Remove" for the linefeed parameter, and specifies CR/LF as the expected value, despite the other text you quoted stating that the value of 1 will remove the LF. In any case, like you, I have never used the LF character. However, as soon as we implemented v16, we started having these issues. We are using a Gmail hosted mail server, and we do not have these issues when the recipient receives the email when it is first sent and they have an Apple Mail client, but it is wrong on our Gmail webmail client, and any users that are not using Apple Mail have the same problems now. Quite a mystery. I'm wondering if we can still use the v15 plugin with v16.4 of 4D, I think Keisuke Miyako mentioned this for someone else having issues with the Internet Commands plugin. JJ > On Nov 1, 2018, at 6:18 PM, [email protected] wrote: > > > >> On Nov 1, 2018, at 3:22 PM, Janet Jonas via 4D_Tech <[email protected] >> <mailto:[email protected]>> wrote: >> >> We recently switched to v16 and found out today that our plain text emails >> are no longer getting a linefeed added to the carriage returns in the body >> of plain text we send out. After looking at the commands, specifically >> SMTP_SetPrefs, adding a linefeed is the default setting still in this >> version, but it does not work as it did in v15. In fact, I was depending >> upon the defaults, and all was fine. I just explicitly added the >> SMTP_SetPrefs command to try to overcome this problem, but it did not work, >> either. > > I have never used SMTP_SetPrefs and did not see any changes or problems > upgrading from 15 to 16. I have always generated email text using carriage > return only. > > What you stated above seems counter to what the documentation says it does: > "A value of 1 (default setting) will replace all carriage return/line feed > pairings with carriage returns for you." > > To me that says CRLF will be replaced with CR. What line endings are you > using when you generate the body text? > > John DeSoi, Ph.D. > > ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
