Reply to comment:

Anonymous
<div class="content legacycomment"> <blockquote> <p> &nbsp; </p> <p> <span style="font-family: Arial;"> I am trying to find the bottom of the pit that opens with this suggestion: </span> </p> <p> &nbsp; </p> <p> <em> <span style="font-family: Arial;"> &quot;Another great feature would be a feedback API that gives users the opportunity to send you </span> </em> <em> <span style="font-family: Arial;"> feedback about accuracy of email addresses </span> &quot; </em> </p> <blockquote> <p> <sup> &deg; </sup> </p> </blockquote> <blockquote> <p> </p> </blockquote> </blockquote> <p> First of all, I think the RIPE NCC is not managing the registered eMail addresses. That's the responsibility of the maintainer for a particular entry. So if we collect such information it should rather be forwarded, or made available, to the responsible party. </p> <p> &nbsp; </p> <p> The other, and imho more fundamental aspect here is: are resource holders really required to receive or accept electronic mail from everyone and her dog? </p> <p> &nbsp; </p> <p> My personal opinion is: <strong> no </strong> . </p> <p> &nbsp; </p> <p> Not having email configured at all, not accepting email from some necks of the woods, and such, seems to be a perfectly valid decision to me. YMMV. </p> <p> &nbsp; </p> <p> All the best, </p> <p> Wilfried </p> </div>