5 ms·
One trick I like is that you can use `account+<tag>@example.com` and a lot of services will consider it a separate e-mail address, even though MTAs will transfe
by drbawb 9y ago
One trick I like is that you can use `account+<tag>@example.com` and a lot of services will consider it a separate e-mail address, even though MTAs will transfer it to the same account; this has the added benefit of being easy to filter for on your e-mail client. I also use this tactic when signing up for web services that I anticipate will spam me. (I import a lot of merch from China/Japan; their unsubscribe systems tend to be insanely broken / borderline user hostile. Each such account gets a unique tag so that I know which service is spamming me.)
Alternatively if you want ultimate trust just run your own mailserver and set up as many aliases as you want! For $5/mo you can get a Linode box to do it, and I've yet to get an IP from them that is on an e-mail blacklist. They have great documentation[1], the most important thing is to just make sure your SMTP server requires authentication & refuses to relay for remote hosts. SPF/DKIM are necessary to get past modern spam filters, but frankly if you've ever setup a TLS cert you can probably manage to setup DKIM just fine.
[1]: https://www.linode.com/docs/email/postfix/ https://www.linode.com/docs/email/postfix/
- giancarlostoro 9y agoI was just about to comment with this suggestion. A friend of mine uses it for gmail and its great for filtering as you suggested.
- midispring 9y agoI used this trick for years. However, there are downsides. For example, sometimes a service will let you sign up with this just fine, but later when you need to do something else (such as password reset) or a phone agent has to enter it... it chokes. Not to mention after some time passes you may forget what the special bit was and have to fall back to searching your email. Being regimented about the naming system helps, but it's not foolproof. I'm using this trick less and less nowadays and just entering my plain email to avoid these hassles... especially for things like real life accounts. For possibly shady characters and account email consolidation, still a great trick!
- simcop2387 9y agoThis is why I have my own domain. I have a catch-all email box that just accepts everything and can make up emails on the spot, service@example.com. It makes things a lot easier down the road if I have a problem with my current provider as I can change the MX records at will. This means though that my DNS service must be under another domain for safety though but that's less of an issue.
- GrinningFool 9y agoDo you have anything written about the components & configuration, by any chance?
- leipert 9y agoThat is actually pretty easy. 1. register domain at a registrar that supports email catch all (I use namecheap, not affiliated) 2. setup email catch all (https://imgur.com/a/PTlzv https://imgur.com/a/PTlzv) with redirect to your "real" email 3. write email to foobar@example.org -> get's redirected to your "real" email This has the big advantage that you can change your real email account (I switched away from GMail two years ago) quite easily, you can track who leaks your address and filter more easily. But be prepared to leave some people stunned, I registered at my electricity provider with electricity@example.org or at my hairdresser with hairdo@example.org
- GrinningFool 9y agoThanks! (Belated)
- simcop2387 9y agoIn my case I'm using an old grandfathered free google apps setup. So I don't have anything to really setup/configure myself. I know it's possible to do it with postfix and other mailing agents. https://www.cyberciti.biz/faq/howto-setup-postfix-catch-all-email-accounts/ https://www.cyberciti.biz/faq/howto-setup-postfix-catch-all-...
- djsumdog 9y agoI would recommend not using Linode and realize your e-mail will be terribly unreliable if you run your own e-mail server (even if you setup DKIM, SPF and DMARC. Google/Microsoft don't give a shit about any of that). I wrote a post about this a while back: http://penguindreams.org/blog/how-google-and-microsoft-made-email-unreliable/ http://penguindreams.org/blog/how-google-and-microsoft-made-... I've considered moving to Vultr since they block SMTP/25 by default and individual customers have to get it enabled (which seems like it should reduce false positive spam classification as more e-mail providers).