Re: Why SRS really sucks

>Actually we have one in our default Ruleset saying all evelopefrom which
>are:
>srs*=*.*=*@* should be rejected ...

What I put in my local part is none of your business, and you 
shouldn't assume anything about its meaning.  Suppose I invent a new 
addressing scheme for some purpose here that has nothing to do with 
SRS.  It happens to fit your pattern match, but its not SRS.  You'll 
reject my mail, thinking that I'm doing SRS, when I'm not.  Or 
suppose someone creates a mailbox named "srs==", and my MTA doesn't 
interpret it at all (its a literal username).  Will you reject his mail too?

Neither of these are very likely, but likelihood is not the 
issue.  The issue here is principle, and the principle is that you 
DON'T REALLY KNOW what it means, even if you think you do, and so you 
can't interpret meaning into its parts (beyond a simple equivalence test).


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

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