Open Bug 19352 Opened 21 years ago Updated 11 years ago
MIME support for content-transfer-encoding: binary
Turns out that S/MIME v3 requires implementers to support content-transfer-encoding: binary. We don't support this at all, so we won't interoperate with anyone who sends us a signature part in binary encoding. Note that in order to work with SMTP, the (8-bit) binary part must be enclosed in another (7-bit) base64 encoded part. Although the main reason to implement this part of the MIME spec is for S/MIME, the change would really be in the core MIME code, not in the crypto-specific S/MIME work Not sure when we'll be able to get to this, but we'll need it in order to have a conforming S/MIME v3 implementation.
Summary: [HELP WANTED] MIME support for content-transfer-encoding: binary → MIME support for content-transfer-encoding: binary
Filter on "Nobody_NScomTLD_20080620"
QA Contact: lchiang → mime
You need to log in before you can comment on or make changes to this bug.