what you could do
is compose an email with a similar structure manually,
send to self and compare the headers with the one created by code.
the gobbledygook headers are probably not involved,
focus on the boundary and the content-type that defines each part.
> 2018/09/03 8:14、Pat Bensky via 4D_Te
Hi Miyako,
To be honest, that stuff is all gobbledygook to me :) I have no idea what
to look out for, that would indicate a problem.
Can you see anything obvious in this header info:
Mime-Version: 1.0
X-Spam-Cmauthority: v=2.2 cv=bZkbaKHB c=1 sm=1 tr=0
a=dalC6LMGHhPl1sqVw4/W9Q==:17 a=a4z1OhtcX
I agree in that of all the possible violations,
bad header information
seems most likely.
you might want to send the same message to a non-yahoo account,
receive with an email client (not web) and examine the raw SMTP source.
***
When we send multipart emails to Yahoo addresses, they either bounce or
simply disappear into the universe.
When they bounce, they have an error
Remote host said: 554 Message not allowed - [299]
Looking up that error message isn't very helpful;
"You'll receive an SMTP error or failed delivery mes
4 matches
Mail list logo
