This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/anti-abuse-wg@ripe.net/
[anti-abuse-wg] UCEPROTECT DNSBL possibly abusive practice and RIPEStat Blacklist entries widget
- Previous message (by thread): [anti-abuse-wg] UCEPROTECT DNSBL possibly abusive practice and RIPEStat Blacklist entries widget
- Next message (by thread): [anti-abuse-wg] UCEPROTECT DNSBL possibly abusive practice and RIPEStat Blacklist entries widget
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Randy Bush
randy at psg.com
Thu Mar 4 20:51:18 CET 2021
i think two things are being confused here; what the measurement folk find useful and what the anti-spam folk find useful. the ncc and ripe stat is not supplying the latter. it is the mail operators' choice of which anti-spam techniques to use, and i do that with one hat. but with a different hat i am interested in longitudinal measurement of internet infrastructure, anti-spam services being a small part of it. i suspect that what you really want is (for example) maawg to measure availibility and quality of *all* anti-spam services. while worthwhile, that is not the ripe stat's measurement mission. randy --- randy at psg.com `gpg --locate-external-keys --auto-key-locate wkd randy at psg.com` signatures are back, thanks to dmarc header mangling
- Previous message (by thread): [anti-abuse-wg] UCEPROTECT DNSBL possibly abusive practice and RIPEStat Blacklist entries widget
- Next message (by thread): [anti-abuse-wg] UCEPROTECT DNSBL possibly abusive practice and RIPEStat Blacklist entries widget
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]