Re: pyspf changes
Julian Mehnle <[email protected]>
| Newsgroups | gmane.mail.spam.spf.devel |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Stuart D. Gathman wrote:
> This is pyspf specific.
>
> In addition to making get_header() RFC4408 compliant :-}, I have
> provided for adding additional x-name=val pairs to the header.
>
> Typical usage is like this:
>
> gres = 'pass'
> hres = 'neutral'
> self.add_header('Received-SPF',q.get_header(
> q.result,receiver,bestguess=gres,helo_spf=hres),0)
>
> For the custom keys, 'x-' is prepended and '_' becomes '-'. So
> bestguess becomes 'x-bestguess=pass' and helo_spf becomes
> 'x-helo-spf=neutral'.
>
> Is that good? Should I not force the custom keys to have 'x-'?
Yes, I think this is good. If new keys get defined, it should be up to the
SPF implementation (pyspf) -- not the caller! -- to give specific inter-
faces to them. If the caller adds custom keys that aren't known by the
implementation, those should receive an "x-" prefix.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGDDuDwL7PKlBZWjsRArEfAJsGtzIHGgckIAq/z84Kd2d9JKf7YgCfSfSB
/BbqIT++nIjdlfw+OmrHFhY=
=jI97
-----END PGP SIGNATURE-----
-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?list_id=1007