![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
MatthiasAny DNS BL Listing process where those listings are based on complaints would create this.
The issue is that if SPAM HEADERS can have the source addresses forged then the DNS Blocking systems which were listed in those forged headers need to take that into account. So far as I can tell they dont.
Todd Glassey Matthias Leisi wrote:
TS Glassey schrieb:4. effects of DNS caching. if a host is removed from a blacklist it should arguably be removed from all caches instantly, but DNS isn'tdesigned to facilitate that.The use of the term "SHOULD" here has legal implications - since many of these hosts were put into the BL's by Address Spoofing they were in fact NOT where the offensive SPAM was coming from and so placing those hosts there when the real issue is the refusal of the EMAIL Admin to do proper Header Filtration and Validation creates a direct liability.I'm sorry to jump in once more. The paragraph above is simply incorrect. A DNSBL that would be fooled by "address spoofing" would not provide much value. What do you mean by "address spoofing"? Falsified "From:" lines? -- Matthias ------------------------------------------------------------------------ No virus found in this incoming message.Checked by AVG - http://www.avg.com Version: 8.0.175 / Virus Database: 270.9.0/1779 - Release Date: 11/10/2008 7:53 AM
_______________________________________________ Ietf mailing list Ietf at ietf.org https://www.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.