4 ms·
> Just mentioning this because it seems like switching to an email on a custom domain would largely take care of the issue of random people mistakenly using you
by mistersquid 9y ago
> Just mentioning this because it seems like switching to an email on a custom domain would largely take care of the issue of random people mistakenly using your email as well.
There are a number of benefits to receiving email to a custom domain on a server you admin.
1. Everyone gets a tracking email like somecompany.com@mycustom.tld
2. Targets of spam can be blocked at the server level: somecompany_leaked_my_email.com@mycustom.tld REJECT
3. Leaked emails can be changed using a timestamp somecompany.YYYYMMDD.com@mycustom.tld
4. Blocked recipients map to blocked senders so somecompany_blocked.com@mycustom.tld will be notified they are blocked.
EDIT: formatting
- isostatic 9y agoI used to do this 15-20 years ago, ran my own smtp server too, dropped thing via spamassasin, custom email aliases for each sign up, etc etc. The life got too short. Pine was ok for simple emails, but HTML mails and attachments meant moving to a graphical system. Wanting access to mail on the go meant squirrelmail which was inferior to most web mail. Then along came smart phones and I was having to run imap on my server too. I suspect nowadays any emails I sent from my anti server would be scored highly for spam flagging too. In the end I just used gmail. I can count on one hand the number of spams I get each year.
- mistersquid 9y agoNot all blocked senders/recipients are sources of spam. I have a list of senders/recipients I refuse communication with for both personal and professional reasons. Since 2013 I use macOS Server which simplifies the overhead of running a IMAP mail server.