Re: mailcap/content-type bug +patch

Alexander Zangerl <[email protected]> Thu, 10 Feb 2005 09:21:08 +1000

Newsgroups	gmane.mail.exmh.devel
Message-ID	<[email protected]>

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!


token := 1*<any (US-ASCII) CHAR except SPACE, CTLs,
                 or tspecials>

     tspecials :=  "(" / ")" / "<" / ">" / "@" /
                   "," / ";" / ":" / "\" / <">
                   "/" / "[" / "]" / "?" / "="
                   ; Must be in quoted-string,
                   ; to use within parameter values

it's actually just a few extra punctuation characters that are
allowed but weren't caught by [:print:] (which is :alnum:).

regards
az


-- 
+ Alexander Zangerl + DSA 42BD645D + (RSA 5B586291)
"I am truly free only when all human beings, men and women,
are equally free." -- Mikhail Bakunin

_______________________________________________
Exmh-workers mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/exmh-workers

signature.asc (application/pgp-signature, 189 B)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFCCprtpy/2bEK9ZF0RAphaAJ40PCL4v9Igd05Jxa4XOWIUqDhsyACfQLYQ
+XbS3/vsz7AZkEtVOPJd/Lw=
=FART
-----END PGP SIGNATURE-----