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] Malware/ransomware current live distribution IPs
- Previous message (by thread): [anti-abuse-wg] Malware/ransomware current live distribution IPs
- Next message (by thread): [anti-abuse-wg] Malware/ransomware current live distribution IPs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
andre at ox.co.za
andre at ox.co.za
Fri Jul 1 06:47:16 CEST 2016
On Fri, 01 Jul 2016 10:07:46 +0530 Suresh Ramasubramanian <ops.lists at gmail.com> wrote: > On 01/07/16, 10:02 AM, "anti-abuse-wg-bounces at ripe.net on behalf of > andre at ox.co.za" <anti-abuse-wg-bounces at ripe.net on behalf of > andre at ox.co.za> wrote: > > Client host [hostacc.com] blocked using black.uribl.com; 127.0.0.1 > > -> this "bounce" does not tell the sender how to delist from > > "black.uribl.com" etc. > I am not sure why a URL in the 5xx error is not an acceptable > substitute for, say, a blog post or a longform New Yorker style essay > on who URIBL are, why they’re blocking what’s probably your webhost > etc. > nice is dnsbl.ascams.com - but although 100% accuracy it is only a fresh spam list - this is also what the node messages look like if you were to get your own dnsbl or dnsbl from dumpspam.com have a look at the bounce message & web link dig TXT @dnsbl.ascams.com 247.241.106.184.dnsbl.ascams.com Andre
- Previous message (by thread): [anti-abuse-wg] Malware/ransomware current live distribution IPs
- Next message (by thread): [anti-abuse-wg] Malware/ransomware current live distribution IPs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]