> "trust is a two-way street. If people don't trust us with their email address, I don't think it's fair for them to expect us to trust them with an account on our service"
Solid justification for disallowing them. My service doesn't even send a reply-verification to users (but Free users get a CAPTCHA... sadly) and just assumes validity. Perhaps I ought to integrate it at some point, but personally I hate having to click to verify my email address. Comes back to trust, again.
If you don't need their email address why do you even ask for it? In my mind reply-verification is mostly for account recovery purposes. If they fat-finger their email address they will never know it until they also forget their password. At least, that is what I experienced on the one app I deployed that didn't verify email addresses (but did need to send notifications to them).
Solid justification for disallowing them. My service doesn't even send a reply-verification to users (but Free users get a CAPTCHA... sadly) and just assumes validity. Perhaps I ought to integrate it at some point, but personally I hate having to click to verify my email address. Comes back to trust, again.