Then I sent e-mail from new gmail account to my email server and simply responded and it went to spam. Recently I did an experiment and created a few gmail accounts and sent some riduculously spammy messages full of typical keywords in between those gmail accounts, and they were all successfully delivered. I can put a message in the error response, that will be reliably relayed to the sender by the sending system. I'm thinking of solving it by blacklisting domain, so that senders at least know that I can't respond to them. You can fit all IPv4 addresses into a 512MB database. It's not like that's a problem technically. They should just block IP addresses that are actually sending SPAM. Microsoft blacklists entire subnets because there are spammers in the same IP range. Eh, my userbase communicates with exactly one SBC user ATT can bite me. has been rejecting me for over a decade despite there being zero spam ever having been emitted by my domain. If you want to do this, I recommend starting with making sure you have a clear mental model of mail server architecture, especially where it touches other things (DNS, DKIM, spam filters, local delivery, probably IMAP, maybe LDAP, maybe databases, etc.) Without a clear idea of the dataflow and reasons for different decision-points, you're going to have a very bad time troubleshooting things. Mail server setup for the uninitiated does look a little daunting, especially if you're more accustomed to "all-in-one"-ish software. I could understand complaints about lots of weird hoops to jump through to get mail from your server accepted elsewhere - that has become harder over time - but there's a very short list of things that need to be done to avoid being hijacked. I'm in the same boat - been running my own mail since the 90s. There are way too many out-dated guides awash in the sea of information. Until then though we need more guides like this for us poor souls who do go down this route. I dunno how useful it will be to others but at least it will keep my gray hairs at bay, I hope, when it's ready for use. So that hopefully more people can run their own infrastructure without prematurely aging. I was so frustrated the last time my mail server went down that I started writing an SMTP protocol handler in Haskell with the intent of writing a MTA with the goal of minimizing configuration and being secure and resistant to attacks by default. Configuration that will soon be exploited in strange ways. Configuration that has real consequences and causes spooky action at a distance. And you have to learn a tonne of crap in order to manage it. And then you're scrambling to figure out how the spammers managed to exploit your setup this time. Then your email doesn't work and you could be missing out on important communications. It's horrible.Īctually it's fine until it's not. To say the least I wouldn't recommend it even to my worst enemies.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |