-----Original Message-----
From: owner-spf-discuss(_at_)v2(_dot_)listbox(_dot_)com
[mailto:owner-spf-discuss(_at_)v2(_dot_)listbox(_dot_)com] On Behalf Of
Hannah
Schroeter
Sent: woensdag 1 december 2004 18:13
To: spf-discuss(_at_)v2(_dot_)listbox(_dot_)com
Subject: Re: [spf-discuss] Ignoring rejected mail?
Hello!
On Fri, Nov 26, 2004 at 02:05:09PM +0000, Mark wrote:
[...]
SRS is based on the 'what-goes-around-comes-around'
principle; or, rather, 'what does not go around should not
come around'. I have been using SRS for a good year now,
and primarily for the purpose of detecting fake DSNs.
AFAIR, you're using the SRS format for what amounts to something
equivalent to non-digest SES,
That would be a correct assessment.
just with more overhead (you encode your
domain twice IIRC, once in the real domain position, once in the
original-domain part of the SRS additions).
I.e. you use
SRS0+aaaa=bb=asarian-host(_dot_)net=user(_at_)asarian-host(_dot_)net,
if I'm right (aaaa and bb being the "signature" and timestamp).
I'm not sure what you mean by encoding 'twice', though. The RHS of the
address is essentially just slapped on as the name of the forwarding
domain, so as to form a real email address.
But it is a little known fact, that, as far as encoding/decoding is
concerned, the RHS domain name of an SRS address is totally irrelevant!
"SRS0=GVNzlx65=OR=asarian-host(_dot_)net=admin(_at_)example(_dot_)com" will
'reverse' just
the same as something with my real domain (if you have the secret, of
course). The encoding is all in the LHS of the address. But you cannot
send out LHS parts-only, of course. :)
- Mark
System Administrator Asarian-host.org
---
"If you were supposed to understand it,
we wouldn't call it code." - FedEx