AnonAddy VS mailcheck

With providers like Addy and SimpleLogin it is possible to use your own domain.

> https://addy.io/

This is one of a few reasons I have started to use email forwarders such as AnonAddy.

https://github.com/anonaddy/anonaddy

Not all of my emails have been moved over yet, but over time I plan on depreciating almost if not all of my main emails from logins.

For receive-only e-mails, take a look at addy.io as a free alternative to DDG. It's easier to manage with an account page listing every alias you create, with the option to block if required.

I use https://anonaddy.com/

My only complaint: 90% of the emails coming from AnonAddy, which is the alias service I use for all of my accounts, end up in the spam folder.

AnonAddy - https://github.com/anonaddy/anonaddy/blob/master/SELF-HOSTING.md OR SimpleLogin.io The real issue you are going to face is being able to receive emails on your server. If you are trying to do this at home, most home ISPs block incoming port 25. Even on most cloud providers you will face the same problem.

Anonaddy, basically the exact same product made by different people, can also be selfhosted. https://anonaddy.com/

Not an "instead of" approach, but the best thing I'd implemented when running an ecom site was a typo detector that prompted people to fix their email if it looked wrong, like "[email protected]", "Did you mean [email protected]?".

At the time I used "mailcheck": https://github.com/mailcheck/mailcheck

There appears to be a more modern implementation here: https://github.com/ZooTools/email-spell-checker

It reduced the amount of badly entered emails more than any other approach I tried.

It misses the very common mistake of typing a comma instead of a dot.

Otherwise, yeah, most people would be better served by a library that detects domain typos like https://github.com/mailcheck/mailcheck than spending time on regexes.

The most helpful thing I've used in the real world is something that looks for common typographical errors, even if the email is technically valid.

Like, if the user types "[email protected]", it pops a dialogue asking "Did you mean "[email protected]". But lets them keep what they typed, or do a different fix if needed.

I found some JS called "mailcheck": https://github.com/mailcheck/mailcheck

There are updated clones that use react, vue, etc, instead of jquery.

With a working ecommerce site, this improved the percentage of correct emails more than anything else I tried, and I had tried many things. Because it's a bad situation when you've taken someone's money and have nothing other than a shipping address to contact them if something goes wrong (bad shipping address, out of stock situation, etc).

I somewhat lol'd when the demo allowed "[email protected]" just fine. Guess kickstarter isn't using mailcheck anymore. Looks like it's an open issue:

https://github.com/mailcheck/mailcheck/issues/179

I suppose it depends on what we mean by validate. Running an ecommerce site, I got a lot of mileage out of prompting the customer to fix emails that "looked wrong". We allowed them to proceed if they wanted. A really common one was "[email protected]" when "[email protected]" was wanted. We used a slightly modified version of https://github.com/mailcheck/mailcheck and found it to be really useful.

It does work well. I used a customized version of https://github.com/mailcheck/mailcheck on an ecomm website and the amount of bounces due to typos went way down.