I feel your pain.
Some user just stubbornly don't accept that they got the wrong email address.
For such normal use case, I use Amazon SES as my transactional email sender.
They deliver bounce reports in various channel (including HTTP) via their SNS service.
See more info about it here:
https://aws.amazon.com/blogs/messaging-and-targeting/handling-bounces-and-complaints/
Once you got the bounce report, which contains the email address, you'll know that the email does not exist.
This works great in every project I encountered so far. It has a little acceptable limitation though, you can't tell unless you try sending an email.
If you design your application in a way that users can resend confirmation emails. You'll able to provide a nice and friendly notice there.
--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/cbab3ba7-58a4-49f8-9d39-611428f0788b%40googlegroups.com.
No comments:
Post a Comment