Re: mailcap/content-type bug +patch
[email protected] Wed, 09 Feb 2005 12:00:34 -0500
| Newsgroups | gmane.mail.exmh.devel |
|---|---|
| Message-ID | <[email protected]> |
On Wed, 09 Feb 2005 22:19:42 +1000, Alexander Zangerl said: > (see <URL:http://bugs.debian.org/294212> for the full story) > exmh mangles Content-Types which contain a dot > (like application/vnd.ms-powerpoint). > > i found the problem & fixed it. the original implementation did "sanitize" > the content-type a bit too eagerly: only alphanumerics, the hyphen > and the forward slash survived. rfc2045 is a bit more generous, and > the patch makes exmh follow rfc2045 properly. > > dear upstream cvs committers: could somebody please apply that patch to > the cvs version? Hmm.. that check in the code is my fault. Let me ponder this - the problem is that 2045 "allows" characters that I'm not comfortable in passing (in particular, the ()<> shell metachars). I was quite intentional in being more zealous than rfc2045. I've done a CVS commit to allow the '.' character to pass, to resolve the show-stopper aspect of the bug. _______________________________________________ Exmh-workers mailing list [email protected] https://www.redhat.com/mailman/listinfo/exmh-workers
signature.asc
(application/pgp-signature, 226 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Exmh version 2.5 07/13/2001 iD8DBQFCCkGycC3lWbTT17ARAq5fAKCnihfsdXD/u+mqg2CdfLM9zEg18ACgxpo2 KILqZVpMt+GRW0eXtJ5AZCE= =0Udg -----END PGP SIGNATURE-----