Ok, you're right - ietf are good with technology and set FROM in the mail
transmission to mailing list (which actually causes some spam filters to
think email is forged), but there are mail lists and forwarding systems
that do not do this and set FROM to the original sender.
On 7 Mar 2003, wayne wrote:
In
<Pine(_dot_)LNX(_dot_)4(_dot_)44(_dot_)0303062006490(_dot_)2191-100000(_at_)sokol(_dot_)elan(_dot_)net>
william(_at_)elan(_dot_)net writes:
How is this going to work for asrg(_at_)ietf(_dot_)org email?
Lets say I run this code to check your dnsbl. Now you send email to asrg,
responding to this post, my MTA receives it and goes to your domain
specific dnsbl, it sees that you support it and checks ip address of the
ietf mail server and that ip is not in your dnsbl, so your email is
rejected.
Ah, the email that you are replying to didn't come from my domain, it
came from ietf.org and and a From_ address of asrg(_at_)ietf(_dot_)org(_dot_)
If you
had implemented the check, you would have found that ietf.org doesn't
have a domain specific blacklist, and therefore you should accept
email from asrg(_at_)ietf(_dot_)org(_dot_)
My message to the ASRG list was received by my machine just fine.
(Damn, And I really wanted to read your reply! :)
Yeah, sure you did. ;->
-wayne
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg