Re: Testing SRS

On Mon, 2004-06-07 at 16:06, Stephen Carr wrote:
> Dear List
> 
> I am about to implement SPF - so far short periods of testing when the 
> mail traffic is low seem to be OK .
> 
> I was hoping you could point me to a document that has the procedures 
> to undertake a full test of SPF and SRS before I make the system live. 
> End users are very touchy about loosing emails.
> 
> Thanks in advance
> Stephen Carr

As far as implementing SPF, step one is to publish records making sure
to end your SPF records with ?all.  If you are very paranoid, you can
end them with +all.  This ensures that even if the mail is invalid
(fails to pass the network space or conditions that you described with
your query) it will still make it through.  This is a good way to test
when you have SPF applying headers to each email.

Once you have confidence that its doing that, and you are seeing PASS
where you should, and FAIL where you should and so on and so forth, you
might wish to change the +all to ?all.  It is not recommended to change
to -all yet as we need to reach critical mass first or else you will
likely loose mails for those who have not yet heard about or implemented
SPF.

For SRS, you could have a look at libsrs wich is an ANSI C
implementation of SRS which you can compile and then inside of the tools
directory (providing all compiles well) you will find a tool called srs
(short for SRSQuery).  You can feed this binary arbitrary values to help
understand what happens to an email address as it works its way through
the SRS process.

If you wish to code with libsrs, you can use the source code of SRSQuery
to see how the API works.

code3 tools $ ./srs -z
SRS Query v0.3 - James Couzens <[email protected]>

From: ([email protected]) 
to: ([email protected])
which forwards to: ([email protected])

HOSTA Send: envelope-from: ([email protected])
HOSTB Rewrite: envelope-from: ([email protected])
HOSTC Rewrite: envelope-from:
([email protected])
HOSTD Rewrite: envelope-from:
([email protected])
HOSTB Bounce: envelope-from: ([email protected])
HOSTB HMAC VERIFIED : enevelope-from: ([email protected])

Rewrite executed in 0.193 seconds

I would also recommend reading all of the available information linked
from http://spf.pobox.com under the heading "Sender Rewriting Sceheme".

In addition to this you will find invaluable the information available
elsewhere on the spf site.  Any questions you have that don't involve
placing XML in DNS records by all means, ask away!

Cheers,

James

-- 
James Couzens,
Programmer
-----------------------------------------------------------------
XML is WRONG, and here it doesn't BELONG.
Neither in SPF, nor inside of DNS,
its fat and its bloated and so I express:
JSON - "The FAT FREE alternative to XML"
http://www.crockford.com/JSON/xml.html
-----------------------------------------------------------------
http://libspf.org -- ANSI C Sender Policy Framework library
http://libsrs.org -- ANSI C Sender Rewriting Scheme library
-----------------------------------------------------------------
PGP: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBD3BF855

-------
To unsubscribe, change your address, or temporarily deactivate your subscription, 
please go to http://v2.listbox.com/member/[email protected]

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

iD8DBQBAyW8rUGWbXgIxVC0RAlc0AKCi9FWF3fSQVU1wAZ6sel5moAT+iQCg01ta
/QWrhl1Tf6zmpGqfgN8H9wk=
=fWhJ
-----END PGP SIGNATURE-----