Please excuse me if this is not the correct place to ask this question. We are currently using libraries which send our mail in this format: -------------------------------------------------------------clip (Misc headers) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=_622_1135029170_19710" To: <chester@xxxxxxxxxxxx> Subject: AP File Export Return-Path: systemadmin@xxxxxxxxxxx X-OriginalArrivalTime: 19 Dec 2005 21:56:36.0943 (UTC) FILETIME=[156365F0:01C604E7] --=_622_1135029170_19710 Content-Type: text/plain; charset="us-ascii" --=_622_1135029170_19710 Content-Type: application/octet-stream; boundary="=_622_1135029170_19710" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="AP File Export.dat" --=_622_1135029170_19710-- ----------------------------------------------------------------clip I believe this looks OK, but CypherTrust IronMail sees this line as a MIME violation: Content-Type: application/octet-stream; boundary="=_622_1135029170_19710" CypherTrust says the same boundary cannot be redefined. I believe this line would be OK if the boundary was removed altogether or if the boundary was unique and appropriately closed. I am unable to find anything in the RFCs that tells me whether CypherTrust or our mail libraries are wrong. Thanks for any help. _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf