Re: Re: SRS: is there a stable implementation for postfix yet?

>It is also very unlike that Spammers find out what your secret subdomain is
>...

s/very unlike/extremely likely/

Spammers, and hosts that sell email lists to spammers, code their 
MTAs to generate lists from incoming MAIL FROM: addresses, among other things.

Encoding something in the domain part is pretty stupid, anyway.  Many 
filtering/delivery rules are written based on domain.  Suddenly, all 
those rules out there become invalid because I've changed the domain 
part of my outgoing mails.  When my clients send out mail, it goes 
all willy-nilly inexplicably, and I wind up having to explain my 
goofy setup, and having people make special exceptions for me in 
_their_ implementations, which probably won't often happen.

The local part is the right place to encode something to check when 
it comes back.

Suppose I change my SRS implementation so that my tags are 
different.  Say, tx3*=*.*=*@tx3.net (instead of 
srs*=*.*=*@tx3.net).  Then your policy wouldn't apply to me.  Now 
suppose everyone using SRS did this.  What do you do then?  Violate 
another RFC 2822 by rejecting all mail containing "="?  Then I could 
just change the SRS separator... :P



--
-- =========================
Tom Lahti
Tx3 Online Services

(888)4-TX3-SVC (489-3782)
http://www.tx3.net/
-- =========================