Re: mailcap/content-type bug +patch
[email protected] Wed, 09 Feb 2005 23:01:20 -0500
| Newsgroups | gmane.mail.exmh.devel |
|---|---|
| Message-ID | <[email protected]> |
On Thu, 10 Feb 2005 09:21:08 +1000, Alexander Zangerl said: > On Wed, 09 Feb 2005 12:00:34 EST, [email protected] writes: > >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. > > huh? the shell metachars you're mentioning above aren't allowed! That'll teach me to come out of a meeting and answer e-mail before restocking on caffeine. ;) The salient point is that there *are* shell metachars that are permitted by rfc2045 (even if () and <> aren't), and that between the fact that not all shells have the same set of metachars, quoting issues, and all the rest, I decided to be even more restrictive than 2045 demands. _______________________________________________ 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 iD8DBQFCCtyQcC3lWbTT17ARAtwHAJ43bHH1AEAEmQ5bZ1bOvd9Gwed+hQCeI5WX X89An75Q0tMhibiIN/miANc= =wy+B -----END PGP SIGNATURE-----