J
John Coutts
After reviewing both proposals in some detail, I have come to the conclusion
that Microsoft's CallerID proposal is inherantly flawed. Why? Because SPF
operates at the SMTP stage using the MAIL FROM: address. The flow of garbage
(alias Spam) is stopped before it is even transmitted. CallerID on the other
hand, operates on information that occurs after the DATA phase has begun. The
garbage has already been transmitted, and the spam engine will probably ignore
any error messages sent subsequently. This in turn encourages background
processing and leads to futile attempts to bounce the message.
Microsoft may have unlimited bandwidth and resources, but I don't.
J.A. Coutts
that Microsoft's CallerID proposal is inherantly flawed. Why? Because SPF
operates at the SMTP stage using the MAIL FROM: address. The flow of garbage
(alias Spam) is stopped before it is even transmitted. CallerID on the other
hand, operates on information that occurs after the DATA phase has begun. The
garbage has already been transmitted, and the spam engine will probably ignore
any error messages sent subsequently. This in turn encourages background
processing and leads to futile attempts to bounce the message.
Microsoft may have unlimited bandwidth and resources, but I don't.
J.A. Coutts