Hi all,
i just started implementing the topwiz smtp object solution into my code.
I am connecting to o365 without any problem, sending works also.
only my mail is being send like this , the whole content of the mail is viewable in the body of the mail... The attachment is not there, yet the base6 encoded string appeaers in the body as well as all the other settings of the smtp object (from , to , subject )
i think i must be missing a parameter somehwere, anyone have any idea ?
i am using the gn_smtp.SendTlsMail() function on PB2017 R3.
TIA
John
From:
To:
Subject: =?utf-8?B?Vk9MR0JSSUVGSkUg?=
=?utf-8?B?LyA=?=
=?utf-8?B?TEFJU1NFWiA=?=
=?utf-8?B?U1VJVlJFIA==?=
=?utf-8?B?OiA=?=
=?utf-8?B?MTEwMDg5LUZPUlRZLVQxLSA=?=
=?utf-8?B?LSA=?=
=?utf-8?B?MTlCRTEwMTAwMFQ3ODk1NTgyIA==?=
=?utf-8?B?LSA=?=
=?utf-8?B?MTlCRTQyNjI3OTY2MzA1NTAwMg==?=
Date: Mon, 14 Oct 2019 10:27:14 +0200
Message-ID: <6C479C33$EE5C$11E9$4494$2407650@sotiauxint.eu>
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="000_6C479C34-EE5C-11E9-4494-24070B800000"
This is a multi-part message in MIME format.
--000_6C479C34-EE5C-11E9-4494-24070B800000
Content-Type: text/plain;
charset="iso-8859-1";format=flowed
X-Mailer: TopWiz PowerBuilder SMTP Object
Content-Transfer-Encoding: 7bit
document
--000_6C479C34-EE5C-11E9-4494-24070B800000
Content-Type: application/pdf;
name="FL-19BE101000T7895582.pdf"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="FL-19BE101000T7895582.pdf"
JVBERi0xLjUKJeTjz9IKNiAwIG9iago8PC9MZW5ndGggNSAwIFIvRmlsdGVyL0Zs
YXRlRGVjb2RlPj4Kc3RyZWFtCnicxVldb924ESXgt7sBmm5unCbxAnpINnHblflN
Cu3TwrE3QVDHjp14EfepHwssksLNS39Ef0D/bs8MSUn3XknW9W63uMAVh5LIM0PO
mRlKVhK/s+OFquj3+YeFrIOu/gX51ULyTfQpUztfGedraSunXQ1BNbXR1ee/Ld4u
dNR1tFWQsbax0ngMd4xdv+9DoPfLfU3CyvtW17p3O8Z0W2EoHatgDN1QWvGlm94A
EOCF4GoZq08DPVkmAMFXH2lKvK8wCiAbz++s9xgTamuLTO+0JkoNGE3SG7CVp9Eb
BfQObV8pm8F/m23Iz7JdZRWtqhvNc/5zoWoplYn8UGlrFeiBxtUqNrb6y6duIb49
XxwchaqpG1+d/537z/+6+PBcfCGuPos7Ykc8Fa/Fy30Vn4uX4jtxgZ4TcYj/N5BO
xXvcPcN1B9dTccnyifhu/8/nrxYvzhenrDV06dllDbCsm8YpZRhRK9Ci0cpjZzg9
A/Fz8QTzE4ITcQ1kX+2f/7gFgCB1bAGwoGB9mFxFWmg3C8HXbIl3sMFha5d3sMy1
+D7b6hLXE7IP9x/jWqx5jKcv0TrdHnvErmyxs6CVrm0V4WQ+NivQ8QbcEPvK8875
Bq1AYykdanhj6aDNeZr0hAn0ipYHsPTvhcfv6jmAexEhNsIlUcEKQfj5GtAe1dK1
+5Xaynt6IDS2bmQYVEBaF4sK0jnySfY313as6LCxVg6r8gpr9IbX4Bi238H6XPAK
vEP/e8hHWJM3+F2i75D39iHuXOCNL1fu3cnOMql0S3xMPR6+COLYpJ5CTXB4Gwfv
M++Mv840Nf32KO/lwROrjmODU47c59FHb4+xnbWB2TpE8F1s2O3UXL6jlwNANRjM
os8ZouS242PXgeG5o7yxLpcX3lf/KKwQZNOxAgkFaoRyADjACpGU7++0pXiA/bIU
9/B/H/9LsYe9RfJXkB/hf4nrRk+7mWb6kA+tC6GpjEsBUCJeDfLnGk4w/lPy4Hvi
MeO5Lx4CyX2x3A8WOmzB50CgvFMFDbeV4YAWaE+YwQC0CSfPDESEaU/cFVf7QgvH
oSiIP+43+jk6Ax65u2W4sY3pwg0LBaDEvsN789Z1L5nsARuLFm4P14diF4B
I will try to test this , but not easy to have customers changing regional settings on their server :)
TIA
John
We should expect regional settings on any machine are beyond our control. However, it may be something else that triggers O365 to misbehave. Decimal comma and BOM prefix are just roots of many evils.