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_Tech <[email protected]>のメール: > 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: ********************************************************************** 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] **********************************************************************
