--On tirsdag, desember 20, 2005 15:41:57 -0500 Carl Hester
<chester@xxxxxxxxxxxxxxxx> wrote:
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.
CypherTrust is right in flagging it as an error. The
application/octet-stream type does not have a boundary parameter, so you
should not be sending it.
RFC 2046 section 4.5.1.
OTOH, CypherTrust is not quite right, because having an extra parameter on
an inner application/* subpart should not change the parsing of the outer
part, even though it has the same name as the parameter on the outer part.
No specific reference, but 2046 section 5.1.2 kind of implies that.
How's that for saying "you're both right and both wrong"? :-)
_______________________________________________
Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf