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] Fwd: Re: RBL policy
- Previous message (by thread): [anti-abuse-wg] Fwd: Re: RBL policy
- Next message (by thread): [anti-abuse-wg] Fwd: Re: RBL policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
ox
andre at ox.co.za
Tue Jan 31 05:17:57 CET 2017
On Mon, 30 Jan 2017 13:21:54 +0000 HRH Prince Sven Olaf von CyberBunker <svenk at xs4all.nl> wrote: > smtp is just one of many protocols out there, a primitive, fairly > unimportant and severely lacking in terms of security one at that, > and it's protection cannot be a reason for any disconnection -ever-. > This thread is about DNSBL and not about the smtp protocol but the replies helped us all understand why it is important to permanently list entire IP ranges. (Even if the resources change hands) Personally, I think that block times should be increased or become more permanent. Practically and right now, some of the block lists that I feed data into is talking about discontinuing 24 hour blocks completely and moving to much longer block times. Other lists are considering completely discontinuing auto de-listing. The effect of this will mean that abuse@ will have to become more responsive in order to avoid being more permanently listed. Andre
- Previous message (by thread): [anti-abuse-wg] Fwd: Re: RBL policy
- Next message (by thread): [anti-abuse-wg] Fwd: Re: RBL policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]