- David Peace (Powersoft)
- PowerBuilder
- Tuesday, 21 November 2023 11:59 AM UTC
Hi All
We have converted a clients appliaction to use the new SMTPClient to send emails. They work fine on our environment but in their network the email is being wrapped within another email. This is the explanation we got from their IT.
I believe this issue is caused by the way the source application streams the attachment into the email. We have seen this once before, the issue was resolved at source by changing the way the file was attached to the email.
From what I can remember, it was either Trend (our email security appliance) or Office365 had to nest the streamed attachments in order to scan and present the mail correctly as the attachment was base64 encoded and streamed into the email body rather than being attached normally.
I’m pretty sure the fix for the previous issue was to not base64 encode and stream.
We can see in the email headers that the attachment is indeed base64 encoded into the email body*, we can also see that the email passes through our SMTP server fine and then reaches Trend**.
My suggestion would be to work with the provider to find an alternative attachment process
Anyone got any thoughts, I belive we have always used Base64 encoding for attachments and assume that PB is doing the same. There are no parameters on the addattachment that might give us otpions on this.
Thanks in advance.
David
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.