Re: Why SRS really sucks

> This isn't a matter of degree, its all-or-nothing. You're 
> either compliant, or you're not.
 
You see this too much in black and white :-)
 
Think about:
Many RFCs were made in times of good old internet was just beginning to
exist,
some even before.
If their creators would have been aware of all todays problems, they had
shurley
made some things very different to what they are today.
 
>Example:
 
The example was just here to demonstrate, that it can make sense
to violate RFCs, as long as you know, what you are doing :-).
 
>This means your example is perfectly legitimate mail handling,
 
No it is not conform to RFCs - you re not allowed to say bye bye
if a Sender gets a 5xx rcpt, you have to let him start the Data
Phase for the previously allowed rcpt .....
 
But in the real world most newer MTAs do so :-)
 
>S: mail from: SPAMTRAP@senderdomain
 
>What comes next? Will you reject this mail? Can you be certain it 
>is not a valid email?
 
That depends on the policy.
If you have a rule in it which says block all envelope froms beginning with
spam:
Then YES, otherwise NO :-)
Actually we have one in our default Ruleset saying all evelopefrom which
are:
srs*=*.*=*@* should be rejected ...
 
Hope you see its not the Product which is not conform to RFCs, 
it is a policy made decision not to accept mails having such envelope froms
:-)
Since you can make the policy on your system, it is your choice if you
follow RFCs or not ...
 
-- 
 
Johann Steigenberger 
Blacklistmaster at UCEPROTECT-Network 
http://www.uceprotect.net