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] an ISP can't do anything?
- Previous message (by thread): [anti-abuse-wg] an ISP can't do anything?
- Next message (by thread): [anti-abuse-wg] an ISP can't do anything?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
denis
ripedenis at yahoo.co.uk
Mon Feb 20 15:36:50 CET 2017
Hi Suresh I was replying to a message on the DB-WG and got this response: The message could not be delivered, the mail server at idvmailin04.datev.com [193.27.49.132] said: <<< 554 5.7.1 Service unavailable; Sender address [ripedenis at xs4all.nl] blocked using dbl.webradar.datev.de; gesperrt vom DATEV WebRadar, http://webradar.datev.de/lookup?domain=xs4all.nl, servertime=Feb 20 02:16:47, server=idvmailin04.datev.com, client=194.109.24.26 cheers denis On 20/02/2017 14:58, Suresh Ramasubramanian wrote: > On 20-Feb-2017, at 2:22 AM, denis <ripedenis at xs4all.nl> wrote: >> It seems like XS4ALL is not able to do anything about being blacklisted. Obviously the message about handling abuse is not getting through.... > It would help if you posted just what bounce and from where. XS4all has historically been quite proactive about abuse handling. -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/anti-abuse-wg/attachments/20170220/a2d0ecb1/attachment.html>
- Previous message (by thread): [anti-abuse-wg] an ISP can't do anything?
- Next message (by thread): [anti-abuse-wg] an ISP can't do anything?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]