On Sat, 16 Jan 1999, Sergiusz Pawlowicz wrote:
> my mutt sends mail in this way:
(...)
> Content-Type: multipart/signed; boundary=LXqH7sWsIplhrbjF; micalg=pgp-md5;
> protocol="application/pgp-signature"
This is fine. The boundary is "LXqH7sWsIplhrbjF", not "LXqH7sWsIplhrbjF;".
> mhonarc said:
(...)
> <DD>Could not process message with given Content-Type:
> <CODE>multipart/signed; boundary=LXqH7sWsIplhrbjF;
> micalg=pgp-md5;protocol="application/pgp-signature"</CODE>
> Content-Type: multipart/signed; boundary="LXqH7sWsIplhrbjF;"
> micalg=pgp-md5; protocol="application/pgp-signature"
If ";" is part of the boundary string, then the value must be quoted. But
now the syntax is not fine. There must be a separating ";" between
parameters. That is, this would be fine:
Content-Type: multipart/signed; boundary="LXqH7sWsIplhrbjF;";
micalg=pgp-md5; protocol="application/pgp-signature"
> why? mutt sends non-standard MIME mail? bug i mhonarc?
The missing information is the actual boundary used by mutt. Without that
information you can't answer your question.
-----------------------------------------------------------------
Mats Dufberg [EMAIL PROTECTED]
