RE: Cascaded Rewriting

> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Stephan Menzel
> Sent: dinsdag 12 april 2005 16:41
> To: [email protected]
> Subject: [srs-discuss] Cascaded Rewriting
>
> Hello,
>
> I am planning to use libsrs2 for our mail system. It will
> replace our own rewriting scheme.
> My question is, what happens if cascaded encoding appears using srs.
> In particular, is it possible to feed an address into srs_reverse,
> it is properly decoded, but still encoded (by SRS means)? Double
> encoding. Is that possible with SRS?

When you re-code an existing SRS0 address, you essentially promote it to
an SRS1 address. This address can be reversed by srs_reverse. Whether you
can reverse the ensuing SRS0 address depends, of course, on whether you
signed it yourself (or have the key).

> Will the decoded sender address be definitely valid when no error occured
> or do I have to check afterwards in case I might have to do
> it again.

The result of srs_reverse may be an SRS0 address itself. So, yes, if you
want to reverse that too, a second pass would be required. Since there is
no promoting SRS1 addresses to SRS2, etc, every reversal step should take
a two-pass maximum.

N.B. This all refers to the default "Guarded" scheme.

- Mark 
 
        System Administrator Asarian-host.org
 
---
"If you were supposed to understand it,
we wouldn't call it code." - FedEx