HN2new | past | comments | ask | show | jobs | submitlogin

It shouldn't be godaddy handing the abuser the email for verification, it should be the abuser handing godaddy it's opt-in-list for verification. This way the reporters identity is never in danger... Of cource it's their fault.


What verification?

The sender obviously had my name on his list, they used that list to send the e-mail. The dispute is that this list isn't really opt-in, and it's hard to imagine any reasonable verification (instead of, say, detailed audit of the sender's internal processes) that could prove otherwise.


Imagine yourself being a highly respected business owner, where your main product is sending personalized newsletters to privacy concerned customers paying you much for their data to stay safe.

Will your argument still stay the same? Are you going to hand in millions of your precious customers email addresses each time to your domain registrant when one of them marks your email as a spam? How are you going to explain later to your customer why he is receiving spam on email address 100mil_worth_customer+news_from_wattengard@gmail.com? That you had to send everyone's address lists each time a spam was reported?


The assumption would be that the registrant acts in a professional manner and only uses the list to verify the complainant's claims.


hashes my friend, hashes




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: