Starchild Active Member Licensed User Longtime User Jan 11, 2016 #1 I have been trying to use the SMTP object for sending emails. When I send an email with a file attachment the MESSAGE section (from field SMTP.BODY) of the sent multipart email does NOT contain Content-Transfer-Encoding: quoted-printable as part of the message section header. This means that the recieving email program can not decode the "=xx" codes imbedded in the message text. If I use the SMTP object to send a TEXT only message (from field SMTP.BODY) then the "quoted-printable" IS inserted correctly into the header and "=xx" codes are decoded correctly by the recieving program. Can this be resolved please for multipart email transmission. This was a problem for me for b4A v5.20 I have updated to b4A v5.50 I still have the same problem. the NET library is v1.53 I see notes for v1.60 on forum, but B4A v5.50 did not update this library. Still v1.53
I have been trying to use the SMTP object for sending emails. When I send an email with a file attachment the MESSAGE section (from field SMTP.BODY) of the sent multipart email does NOT contain Content-Transfer-Encoding: quoted-printable as part of the message section header. This means that the recieving email program can not decode the "=xx" codes imbedded in the message text. If I use the SMTP object to send a TEXT only message (from field SMTP.BODY) then the "quoted-printable" IS inserted correctly into the header and "=xx" codes are decoded correctly by the recieving program. Can this be resolved please for multipart email transmission. This was a problem for me for b4A v5.20 I have updated to b4A v5.50 I still have the same problem. the NET library is v1.53 I see notes for v1.60 on forum, but B4A v5.50 did not update this library. Still v1.53
Erel B4X founder Staff member Licensed User Longtime User Jan 11, 2016 #2 The B4A version will not have any effect on the behavior of the Net library. The Content-Transfer-Encoding belongs to the "body" part, not to the headers.
The B4A version will not have any effect on the behavior of the Net library. The Content-Transfer-Encoding belongs to the "body" part, not to the headers.
Starchild Active Member Licensed User Longtime User Jan 11, 2016 #3 Erel said: The B4A version will not have any effect on the behavior of the Net library. The Content-Transfer-Encoding belongs to the "body" part, not to the headers. Click to expand... Then how do I pass Content-Transfer-Encoding as part of the body field? It's only a string. Remember is works if no attachment in email. Same BODY text.
Erel said: The B4A version will not have any effect on the behavior of the Net library. The Content-Transfer-Encoding belongs to the "body" part, not to the headers. Click to expand... Then how do I pass Content-Transfer-Encoding as part of the body field? It's only a string. Remember is works if no attachment in email. Same BODY text.
Erel B4X founder Staff member Licensed User Longtime User Jan 11, 2016 #4 It is added automatically. You can download the raw message with POP3 to see it.
Starchild Active Member Licensed User Longtime User Jan 11, 2016 #5 Erel said: It is added automatically. You can download the raw message with POP3 to see it. Click to expand... It is added automatically if NO attachment. But it is omitted if sending with attachment.
Erel said: It is added automatically. You can download the raw message with POP3 to see it. Click to expand... It is added automatically if NO attachment. But it is omitted if sending with attachment.
Erel B4X founder Staff member Licensed User Longtime User Jan 11, 2016 #6 Please try it with v1.61: https://www.b4x.com/android/forum/t...y-android-ftp-smtp-and-pop3.10892/#post-60826 It should be fixed.
Please try it with v1.61: https://www.b4x.com/android/forum/t...y-android-ftp-smtp-and-pop3.10892/#post-60826 It should be fixed.
Starchild Active Member Licensed User Longtime User Jan 11, 2016 #7 Thankyou Erel. All Fixed. I very much appreciate your FAST response.
