<html> <head> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <tt>Hi Suresh</tt> <tt>I was replying to a message on the DB-WG and got this response:</tt> <tt>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 [<a class="moz-txt-link-abbreviated" href="mailto:ripedenis@xs4all.nl">ripedenis@xs4all.nl</a>] blocked using dbl.webradar.datev.de; gesperrt vom DATEV WebRadar, <a class="moz-txt-link-freetext" href="http://webradar.datev.de/lookup?domain=xs4all.nl">http://webradar.datev.de/lookup?domain=xs4all.nl</a>, servertime=Feb 20 02:16:47, server=idvmailin04.datev.com, client=194.109.24.26 </tt> <tt>cheers</tt> <tt>denis</tt> <div class="moz-cite-prefix">On 20/02/2017 14:58, Suresh Ramasubramanian wrote: </div> <blockquote cite="mid:01D877FA-0835-488F-8AD4-B54F676DB42F@gmail.com" type="cite"> <pre wrap="">On 20-Feb-2017, at 2:22 AM, denis <a class="moz-txt-link-rfc2396E" href="mailto:ripedenis@xs4all.nl"><ripedenis@xs4all.nl></a> wrote: </pre> <blockquote type="cite"> <pre wrap=""> It seems like XS4ALL is not able to do anything about being blacklisted. Obviously the message about handling abuse is not getting through.... </pre> </blockquote> <pre wrap=""> It would help if you posted just what bounce and from where. XS4all has historically been quite proactive about abuse handling. </pre> </blockquote> </body> </html>