Re: Quoted pairs in the test suite

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stuart D. Gathman wrote:
> On Mon, 14 Apr 2008, Julian Mehnle wrote:
> > You cannot expect SPF implementations to safely generate valid RFC
> > 2821/ 2822 local-parts.  You could say "%{l}"@%{d} (with the quotes)
> > in an explanation string, but if the local-part's _value_ was "foo
> > (with the quote), the SPF implementation would generate
> > ""foo"@<domain>, whereas the proper RFC 2821/2822 representation
> > would be "\"foo"@<domain>.
> >
> > It cannot be done reliably.  SPF wasn't designed to do it.
>
> You missed the point.  If %{l} simply echoes the localpart with quoting
> intact, then if the original email was <"\"foo"@example.com>, %{l}
> would expand to "\"foo" (with the quotes), rather than try to undo the
> quoting.

True.

> If mail from was <"foo"@example.com> (with the redundant quotes),
> then %{l} per my suggestion would be "foo".  A similar question goes
> for %{s}, which can leave quoting alone, or try to remove it.

SPF implementations aren't supposed to perform quote removal in e-mail 
addresses or localparts.

> I'm saying that removing the quotes is a lot of trouble, and leaving
> them alone leave %{s} as a valid email (if mail from was to begin
> with).

Agreed.

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

iD8DBQFIA7HqwL7PKlBZWjsRAkfLAKD9BH1e3m4Xk3f4QrSCiEc0SdwXcACfbOmU
+Q0nwUSiOijE/d9G4uMPBEs=
=MKkh
-----END PGP SIGNATURE-----