MIME boundary being set incorrectly
Bug #265623 reported by
Tgrace
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNU Mailman |
Invalid
|
Medium
|
Unassigned |
Bug Description
In 2.0.8, if a user has chosen to receive a MIME
digest, the mime boundary is declared as --__--__--
but the actual boundary used is __--__--
This causes problems for some mail servers.
[http://
To post a comment you must log in.
You might be thinking of the plain text digests, which don't
set a boundary parameter on the Content-Type: header (and
actually, the Content-Type: header isn't even multipart0.
Plain text digests uses --__--__-- as a separator, which is
allowed by RFC 934.
MIME digests use a different boundary, which is properly set
and used.