Mailing List Archive: SPF: Devel

pyspf changes

Index | Next | Previous | View Threaded

stuart at bmsi

Mar 29, 2007, 12:52 PM

Post #1 of 3 (1870 views)
Permalink

pyspf changes

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-'?

--
Stuart D. Gathman <stuart [at] bmsi>
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.

-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?list_id=1007

gerberb at zenez

Mar 29, 2007, 1:03 PM

Post #2 of 3 (1754 views)
Permalink

Re: pyspf changes [In reply to]

On Thu, 29 Mar 2007, 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 like this. I do think custom keys should be forced to this.

--
Boyd Gerber <gerberb [at] zenez>
ZENEZ 1042 East Fort Union #135, Midvale Utah 84047

-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?list_id=1007

julian at mehnle

Mar 29, 2007, 3:19 PM

Post #3 of 3 (1744 views)
Permalink

Re: pyspf changes [In reply to]

-----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

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads