11 ms·
I've been thinking for a while that there should be a movement to allow people running mailservers at their home again. "Again" as in get other actors in the f
by znpy 8y ago
I've been thinking for a while that there should be a movement to allow people running mailservers at their home again.
"Again" as in get other actors in the field to allow/ease that: spamlist managers should stop blocking residential address by default and make it easier to appeal. ISPs should make it possible and easy to get a reverse-ptr with every fixed ipv4 allocation.
In this monitoring age I want to be able to handle my private conversations (and my data) on my own iron (running somewhere in my house).
All this impediments to running your own mailserver and take back control of your own data really look like a push towards state-/corporate-backed espionage of individuals.
It's not 1995 anymore, most of us have an internet connection well capable of sustain enough mailboxes for a whole family.
- snowwrestler 8y agoIt seems like there might be an opportunity here, for a hybrid service comprised of "client" software installed on your own hardware, which actually hosts and runs the email inbox, and central server-hosted software that takes care of configuring the client and all the associated authentication schemes. The server-hosted software would never see the actual emails; it would just manage the provision of email service. Perhaps the server could store locally-encrypted inbox backups too. If the service was responsibly run, it could even "vouch" somehow for the email inboxes it provisions. So even though the emails come from, like, Comcast ISP address space, other ISPs would recognize a trustworthy source of email. (Dynamic IP provision would complicate this part.) But the big question is... what's the addressable market?? It would likely be even more expensive than something like ProtonMail. You're not going to build much of a business off of 347 neckbeard paranoics. (I joke with love.)
- ouid 8y agotheres a lot more than 347 of those
- tzs 8y ago> The server-hosted software would never see the actual emails; it would just manage the provision of email service ... > If the service was responsibly run, it could even "vouch" somehow for the email inboxes it provisions. So even though the emails come from, like, Comcast ISP address space, other ISPs would recognize a trustworthy source of email. (Dynamic IP provision would complicate this part.) If you are willing to to let the server-hosted software have some visibility into your mail traffic (but not the content), there's a way to handle this that would not have problems with dynamic IP addresses [1]. Briefly, whenever your email client needs to send a mail through your Comcast outgoing SMTP service, it would first contact the vouching service and provide a hash of the message ID of the message it is about to send (and maybe the from address?). The vouching service would verify that it is talking to one of its legitimate customers, and then return a line for the client to put in the header of the outgoing mail. This line would contain a copy of the message ID hash (and from address?), a timestamp, the client IP address, and would be signed using a key of the vouching service. The client puts that line in the header and sends the mail through Comcast. The SMTP server that Comcast relays it to can look at that line, check the signature, and if it verifies it can compare the information in that line to the corresponding information in or derived from the rest of the header. If the information all matches and the timestamp is in the recent past, accept that the mail really came from the person it claims to be from. This would give the vouching service get a good idea of how much email you send and when you send it, and also give them hashes of your message IDs, so it is not ideal. A problem with this is this it depends on every SMTP service that Comcast might relay your mail to (such as the SMTP server for every domain you send mail to) being set up to verify the signature of the vouching service you use. This would be a pain in the ass. This could be addressed by having the verification of the signature and header data done at your ISP's (e.g, Comcast's) SMTP service. That way you just have to pick a vouching service that Comcast recognizes. Comcast would then do the check on your outgoing mail to see that you have used a vouching service they recognize and the data matches. They can then add a header that says they believe the mail is verified. For any mail that they cannot verify thusly, they can add a header that says it is not verified. Now instead of having to know about and trust your vouching service, the SMTP servers of the domains you mail to just have to trust Comcast. That seems much more likely to come about. If Comcast (and other residential ISPs) were willing to do this, why bother with third party vouching services? Why not handle the whole thing themselves? One reason would be that providing vouching service requires getting more involved with the details of the customer's setup than an ISP might want to deal with. They might not want to have to deal with support questions dealing with how to get the vouching plugin or whatever working with the various email clients and operating systems customers use. [1] Maybe...I've not sat down and tried to actually design the protocols for this. This is just off the cuff.
- _jal 8y agoI'd absolutely be all for it - I've been running my mail server since the 90s, and used to run it out of my closet. There are two major, somewhat interlocking problems, though: home users with compromised machines currently represent the population of home "mail servers" (spam malware) at the moment. Selling this involves convincing mail administrators that not simply blackholing all of what is currently a cesspool is a good idea. That's not easy. The second problem is that fixed-IPs, open well-known ports and DNS have become a product differentiator for ISPs. Those are "business" features; dumb ole' consumers don't "need" them. I don't see any compelling argument that would convince either prong of that trap - hell, I agree with you, but as a mail admin both professionally and personally, the first one gives me hives, thinking about the years of work it'll take to re-stabilize a functional antispam infrastructure to handle it. And after that, you need to convince Comcast to change their revenue-extraction plans and generally be less dickish. If just you want a mail server now, your best bet is a cheap VM somewhere. It can be really low-end and cheap.
- loup-vaillant 8y agoDynamic IP is a bummer, but outright closing ports is a direct violation of net neutrality. It's baffling that it's tolerated at all. An ISP's job is to forward IP packets. Not read them. TCP/UDP ports number are the content of those IP packets—not the meta data. Filtering based on such content is already a form of discrimination. What's next, deep packet inspection? Some ISP filter by default, but they do this at the router level, and you can either configure or change the router. That's okay, possibly even beneficial. Blocking at the backbone level however is just evil.
- walrus01 8y agoCounterpoint: Unless you've been in network engineering for an ISP with tens of thousands or more residential customers, you have no idea how much spam/abuse/trojaned PC traffic comes from residential users. There's a very good reason why ISPs block some of this, for the protection of their own users. It's even necessary to block port 139 windows file sharing or people will connect PCs with totally open file shares straight into their cable or DSL modems. It's a real headache. The average HN user is in like the 99.9th percentile of residential internet users. HN users, give them a proper DIA feed, sure. Everyone else, I'm wary.
- DonHopkins 8y agoThere should be a home email server called "Buttery Mail".
- secabeen 8y agoIt would probably be easier to just build an AMI for one of the existing mailserver-in-a-box systems to proxy email via an AWS t2.nano instance. You can run a t2.nano with a 3-year reserved instance for $30/yr, and then proxy all your mail to and from your home server on non-standard ports.
- walrus01 8y ago> I've been thinking for a while that there should be a movement to allow people running mailservers at their home again. This will be really hard, because unless you're willing to give home users actual permanently assigned static IP addresses and treat them like medium sized businesses (IP space SWIP to customer, etc), any given /27 to /23 sized v4 DHCP pool of residential customers is going to have a ton of abuse coming from clueless people running infected routers, virus/worm/trojan infected home PCs, etc on it. Getting the average residential ISP to do proper rDNS for your IP address is impossible in many places. Therefore when recipient SMTPd are scoring the IP space reputation of your residential netblock, your home mail server is going to be mixed in with all the shit.
- flurdy 8y agoI did run mailserver(s) at home for a while in early 2000s. Proved difficult when I once went on holiday as I switched it off and then it got flooded with emails (mostly spam) when I got back (from backup mxs run by friends). Had my ISP call me as worried my PC was on a botnet due to sudden traffic. Explained I was running Linux, and they immediately said: "thats fine then have a nice day". Thought perhaps they would need more detail but no. ¯\_(ツ)_/¯ As others have said. Today's cheap nano-esque cloud instances (with swap disk enabled) on AWS and similar is easier to have running 24/7, and less risk it will burn your house down...
- brightball 8y agoIMO you still can if you have a static IP. As far as I know, dynamic IP addresses are one of the strongest filters for a lot of spam. Have a static IP and properly setup your SPF, DKIM and DMARC...you should be good to go.
- LinuxBender 8y agoYou would need to convince your ISP to allow you to modify your PTR. There are many servers that implement one form or another of the S25R methodology [1]. That is, simple regex against your FCrDNS to see if you are a generic network device or generic home user. The page I am linking to is an example of the concept, but many anti-spam tools implement this in varying degrees. [1] - http://www.gabacho-net.jp/en/anti-spam/anti-spam-system.html http://www.gabacho-net.jp/en/anti-spam/anti-spam-system.html
- jedberg 8y agoI'm curious as to what privacy you think you'd gain from storing your mail at home? Unless everyone encrypts everything they send you, most likely most of that mail will go through a government monitored connection at some point. It wouldn't be that hard for them to reconstruct your mailbox if they wanted to. Also, why not keep it on a hosted server somewhere? You could encrypt it at rest to prevent anyone coming in and getting the data, which would make it as private as storing it at home. And then you don't have to worry about deliverability or backup power as a nice side bonus.