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] DRAFT: RIPE proposal - implementation of an abuse monitor system
- Previous message (by thread): [anti-abuse-wg] DRAFT: RIPE proposal - implementation of an abuse monitor system
- Next message (by thread): [anti-abuse-wg] DRAFT: RIPE proposal - implementation of an abuse monitor system
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Thor Kottelin
thor.kottelin at turvasana.com
Thu Apr 8 16:30:36 CEST 2010
> -----Original Message----- > From: anti-abuse-wg-admin at ripe.net [mailto:anti-abuse-wg- > admin at ripe.net] On Behalf Of Bradley Freeman > Sent: Thursday, April 08, 2010 4:45 PM > To: 'Frank Gadegast'; anti-abuse-wg at ripe.net > And if the only benefit is a common abuse alias, hasn't this has > already > been suggested with an abuse@ address in RFC2142 - Mailbox Names > for Common > Services, Roles and Functions which is not RIPE region specific? It is not always obvious which abuse@ domain should be selected for a particular IP address. I like the suggestion of routing reports according to the IP address of the abuse source. -- Thor Kottelin http://www.anta.net/
- Previous message (by thread): [anti-abuse-wg] DRAFT: RIPE proposal - implementation of an abuse monitor system
- Next message (by thread): [anti-abuse-wg] DRAFT: RIPE proposal - implementation of an abuse monitor system
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]