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/[email protected]/
[anti-abuse-wg] 2019-04 Discussion Phase (Validation of "abuse-mailbox")
- Previous message (by thread): [anti-abuse-wg] 2019-04 Discussion Phase (Validation of "abuse-mailbox")
- Next message (by thread): [anti-abuse-wg] 2019-04 Discussion Phase (Validation of "abuse-mailbox")
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
furio ercolessi
furio+as at spin.it
Tue Oct 1 17:27:58 CEST 2019
On Tue, Oct 01, 2019 at 03:15:02PM +0100, Carlos Friaças via anti-abuse-wg wrote: > > On Tue, 1 Oct 2019, Nick Hilliard wrote: > > >There isn't a major problem with the RIPE NCC testing abuse > >mailboxes on a purely advisory basis, but the RIPE abuse working > >group has no authority to > > I'm sure you meant the RIPE *anti*-abuse working group :-))) Smile, yes, but up to a point. The group is certainly called anti-abuse, but participation is open to all the stakeholders, so it should be safe to assume that both communities are present and active. In fact, it is not too uncommon to see posts from representatives of service providers well known in the security community for knowingly providing services to cybercrime. This may be stating the obvious, but as far as I am concerned very little real antiabuse work can be done here because of this reason. furio ercolessi
- Previous message (by thread): [anti-abuse-wg] 2019-04 Discussion Phase (Validation of "abuse-mailbox")
- Next message (by thread): [anti-abuse-wg] 2019-04 Discussion Phase (Validation of "abuse-mailbox")
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]