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] RIPE policy
- Previous message (by thread): [anti-abuse-wg] RIPE policy
- Next message (by thread): [anti-abuse-wg] RIPE policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Suresh Ramasubramanian
ops.lists at gmail.com
Wed Mar 9 03:59:12 CET 2011
On Tue, Mar 8, 2011 at 11:29 PM, peter h <peter at hk.ipsec.se> wrote: > I have no problem with blocklists ipv6. Larger chunks however :-) > > I do have problem with abuse, where spam is the dominant factor, often > used as vehicle for other kinds of fraud. At least some blocklists have moved to support v6 listings .. Quoting from http://virbl.bit.nl/ 15-01-2010: We've changed Virbl today, which makes it the first fully IPv6 enabled dnsbl, as far as we can tell. You could already reach Virbl via IPv6 for years, but no IPv6 hosts were served by the nameserver. rbldnsd, on which we ran Virbl before, does not understand IPv6 in its zones. We changed some things today: 1. We implemented a way to list machines with IPv6 and privacy-extensions 2. We switched from rbldnsd to Bind 3. We've changed the website so the changes made in '1' are visible on the website as well -- Suresh Ramasubramanian (ops.lists at gmail.com)
- Previous message (by thread): [anti-abuse-wg] RIPE policy
- Next message (by thread): [anti-abuse-wg] RIPE policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]