7 ms·
When you let someone else handle your email, they own your email. There is no postal secrecy law, no rule against reading. They can touch, modify or delete acco
by belorn 14y ago
When you let someone else handle your email, they own your email. There is no postal secrecy law, no rule against reading. They can touch, modify or delete according to their whims. It's their email now.
So I am not that very surprised to hear a news article like this. It makes perfectly sense with the current mentality. It also adds another nail in the coffin about idea that "only a machine is reading my emails. Why should I care about that?".
Hopefully this will encourage some people enough to run their own mail servers. It's far less problematic than most people think it is. Maybe it was hard to install and configure this in 1990s, but this is 2013. You buy a domain name, install a Debian machine, and do:
aptitude install postfix
aptitude install postgrey
Afterward one follows any one of the many simple guides to install either a webmail (roundcube most commonly), or go to (http://www.postfix.org/docs.html http://www.postfix.org/docs.html). If a spam gets through, install blacklisting or spamassassin. Easy 3 step guides exist for both.
It always surprises me that people can use a software library with complicated, half insane API's, but can't follow a single page of simple single steps installation. It's not hard and you get the bonus of actually owning your own emails again. If you are a company, this should not even be a question. If the options are to give away all your emails and customers emails to a third-party and thus lose all ownership to them, or asking a sysadmin/programmer to spend 5-10-30m tops to do an email installation, the answer should be obvious.
- plg 14y agoyes yes yes! I 100% agree. It would be interesting to hear from someone with some legal knowledge. I suspect in many countries it's the case that if you host your email with a third pary (iCloud, gmail, FB, etc) you give up some rights to privacy ... whereas if you host your email on your own server that you physically control, for example in your personal home, your rights to privacy are greater. Even on Ubuntu Server it's very very easy to setup a mail server. Linode has guides, and there are others on the interwebs as well. Just make sure to implement a regular backup regime. In my experience IMAP to my own mail server is WAY faster than dealing with Gmail (even web interface).
- pyre 14y agoNote that if you host on a shared machine or a VM, then law enforcement is still likely to see it as your host's box with your data on it, rather than your box with your data on it. The most conservative approach would be a co-located machine that you own (i.e. your physical property, so they probably need a warrant) or on a machine in your home.
- secure 14y agoIn my experience, it is not so much the installation itself, but the regular maintenance and the many subtle errors that can occur, which make running your own email server NOT as trivial as you make it sound :). As for a few examples: 1. Mailservers around the world have different degrees of strictness in what they accept. Some require the sender’s mailserver to have a valid and matching PTR and A/AAAA (!) DNS records. Others don’t care. Some check black lists, some don’t. Some even resolve the MX record of your sender domain, connect to it and try to start delivery of an email to ensure your address is valid. 2. By default, postfix doesn’t warn you about undeliverable messages for quite some time (a week is the default, I think). So if there is any error in your config (e.g. I changed my DNS resolver config, then didn’t restart postfix), your mails will be stuck without any notice, for a number of days. 3. If there are SSL certificates invoked, they should be valid. Some mail servers will not use TLS at all, some will fall back to plain text, others will cancel delivery if your certificate is invalid. These are just a few examples I have encountered recently, but every time they happen I am incredibly frustrated that emails either did not reach me (usually I detect that quickly) or are not delivered (detected only after a few days).
- haroldp 14y agoI agree with both of you. Mail is hard, not easy. We should host our own email anyway, because the alternatives suck. I wonder if there is a "Mail Admin Best Practices" doc floating around the web yet?
- shocks 14y agohttp://37signals.com/svn/posts/3096-behind-the-scenes-giving-away-the-secrets-of-email-delivery http://37signals.com/svn/posts/3096-behind-the-scenes-giving... This is pretty good. :)
- pyre 14y agoThere have been a couple of "setting up a mail server" howtos come through here. I recall one that was huge in the depth that it went into (the depth also made sure that I never got around to reading it).
- 14y ago
- revelation 14y agoIt's very very problematic. With all the spam, your mail server is not going to be trusted by any major providers. Their weak heuristics have no problem banning your 1 user mailserver, but they have gmail whitelisted to not ever ban them.
- rwmj 14y agoIn practice this is nonsense. I have run my own email server since 1999 and "trust by major providers" has not been a problem for me.
- ux-app 14y agoI guess this is one of those YMMV cases. I could never deliver to hotmail addresses no matter how many hoops I jumped through. Also: how do you know you've never had deliverability issues? If the server on the receiving end is blocking your mail it will happen silently.
- jrockway 14y agoI agree with you. Most professional email services have much less aggressive blacklisting than single-user email services run by their single user. In many years of running my own server, this was never a problem. I checked blacklists on a somewhat regular basis but was never in them. And people I sent mail to usually replied, which means they are either psychic or my mail got delivered. (The problem comes when you start sending spam, of course, which is what many people do get blacklisted for.) The problems with running your own email server are spam and the time it takes to keep things running. All the other issues are trivially solved.
- supercoder 14y agoAgreed, this is the biggest barrier to running your own mailserver. Even if you think deliverability is good for 95% of mail servers there's always some ISP that won't cater for you. So you're constantly having to be monitoring the logs to ensure your emails are being delivered.
- 14y ago
- baby 14y agoI actually tried many times to setup a mail server on my debian machine but never could find a good tutorial. I gave up because I lack the time. edit: I just tried again, for more than a couple of hours. First I had to guess that I had to install MDB2_Driver_mysql. Set up a DNS to match my /var/lib/roundcube and now I'm struggling to understand how I could sign-in since he didn't create any user for me.
- belorn 14y agoRegarding MDB2_Driver_mysql, I point towards (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544694 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544694). If you want to use mysql and not default sqlite, use debian package roundcube-mysql and it will install the dependencies for you. As for users, roundcube uses imap and thus do not create new users. Anyway, GL, and if you want to have some fun, try out PostgreSQL.
- luchs 14y ago>When you let someone else handle your email, they own your email. There is no postal secrecy law, no rule against reading. They can touch, modify or delete according to their whims. It's their email now. In Germany, email is actually protected by the Fernmeldegeheimnis [1], even while the email is saved on the provider's server. The reasoning behind that [2] seems to be that the mail server's storage is part of the communication process, no matter how long the data sits there. [1] http://de.wikipedia.org/wiki/Fernmeldegeheimnis#E-Mail http://de.wikipedia.org/wiki/Fernmeldegeheimnis#E-Mail [2] http://www.bundesverfassungsgericht.de/pressemitteilungen/bvg09-079.html http://www.bundesverfassungsgericht.de/pressemitteilungen/bv...
- veidr 14y agoYou are absolutely right about owning your own email, but it is also worth pointing out that no email provider in their right mind would irrevocably, silently delete emails based upon this insane criterion (where a movie script attachment contained a scene where a character views an ad for legal porn). But Apple isn't in their right mind. They have never understood the cloud, they still don't, and every single Internet service Apple has ever produced, from eWorld to .Mac to Mobile Me to iCloud has utterly sucked gigantic balls. Which makes relying on Apple to handle your email a lot crazier than relying on say, Google, Yahoo, Rackspace Mail, Tuffmail, etc.
- sdizdar 14y agoOr maybe we need "dropbox for email" YC S13 company.
- martinced 14y agoThe biggest issue is your domain getting blacklisted for whatever reason. It may look like the name of another spammer's domain name. The server you rent may be colocated on a rack with a spammer's box (or a box owned by spammers) and have weird reverse IP SNAFUs. Your very server may not have the latest 0-day patch and bet 0wned by script kiddies and, bam, again... Blacklisted. Note that I do NOT know much about email servers and that is precisely the point. I eat iptables rules for breakfast, I can set up a Debian server from scratch and I can certainly configure a mail server. But there's more to it than meets the eye. Been there, done that. And we got burn. I don't know "why", but all I know is that we had problems! tl;dr: 30 team person startup and we tried to use our own mail server. Too many problems. We moved to Google Apps for domain and all our problems were fixed...
- belorn 14y agoAt conferences, especially security conferences, I tend to ask if anyone ever heard of a Debian base installation being hacked if it has auto-updates or is manually updated once a week. So far, my count is 0 and when asking self-proclaimed hackers, they also tend to agree that Deiban stable installation is very secure. The installation I got from 1999 is still running, and the count of breakins are 0. to add on that, it has no firewalls. I kind of wonder what happened that caused your server to be hacked. Insecure password? As for using a previous owned spammer domain, I strongly question that logic. Black lists tend to be both conservative and done by copy-pasting. A blocked domain abcd will not block abc or abcde. If the block lits do not see mails from abcd within a month or so, they also tend to remove them to clear up space. This time frame is also way below common domain name expire dates. Regarding reverse lookup, I assume that 30 team startup bought a company network contract from the ISP. Such deals should include support and static IP, which mean reverse lookup is a single email away from being done. Co-location contract might be different, but I wouldn't know.
- padmanabhan01 14y ago//" install a Debian machine, and do: aptitude install postfix aptitude install postgrey install either a webmail (roundcube most commonly), or go to (http://www.postfix.org/docs.html http://www.postfix.org/docs.html). If a spam gets through, install blacklisting or spamassassin.// You seriously think this is simple for non IT people?
- mikegioia 14y agoIt't even that simple for IT people. I've been working with email servers for years and ensuring deliverability was a NIGHTMARE.
- belorn 14y agoNo, I don't think this is simple for non IT people. Same goes for my web site code, or my python projects, or my shell scripts. If I gave either of those to an non IT person, they would have no clue what is going on. This is as expected, as most people require some expertise to do technical work. I would have no idea how to fix the electrical system in a car, but I do expect that the mechanic knows how to figure it out if it one broke. Same, I expect a sysadmin or a programmer has the expertise to follow single steps installation guides.
- bithive123 14y agoIf you have enough experience or make enough simplifying assumptions, anything is trivially easy. But it doesn't take much imagination or experience to see that bootstrapping your own email isn't trivial. For instance, I defy you to buy a domain name and a hosted debian machine without maintaining an existing email account. As a developer / sysadmin who used to host his own mail and uses complicated half insane APIs every day, I know that even things that are reliable and easy to set up (such as debian servers) require maintenance and all the work and planning that goes into making something secure, reliable, and performant. I don't see how anyone with experience could contend with a straight face that running a network service like email is a set-and-forget proposition. I remember having to brush up on my mail stack every time I needed to troubleshoot a problem, and over time it became clear that I had over-prioritized hosting my own email. Edit: It's a fine hobby project though, as long as you're honest with yourself about what you're undertaking.
- jacquesm 14y ago(1) use public email account to buy domain + hosted debian box (2) set up mail server, create account(s) (3) reset public email account with domain registrar + hosting facility to newly set-up email addresses (4) kill public email account You only need one for a very short while to bootstrap your own email server, you don't need it forever.
- jasonlingx 14y agoYou're missing his point... But I'll bite, if your mail server goes down - and it will - you now have no email. You can't email your hosting support. You try to log in to your host control panel to do a reboot or raise a ticket but forgot your password. You can't get the reset email. Somehow you manage to login and raise a ticket but won't get any email notifications when the technician responds asking for your server id number...
- icebraining 14y agoGet a VPS from another provider (e.g. EC2), restore system from backups, update MX records.
- joe_the_user 14y agoI agree we should be more serious about email privacy. But "There is no postal secrecy law, no rule against reading." Seems like something of an exaggeration. See: http://en.wikipedia.org/wiki/Electronic_Communications_Privacy_Act http://en.wikipedia.org/wiki/Electronic_Communications_Priva...
- jrockway 14y agoI've written about this before, but I used to run my own mail server and it's no cake walk. I used to do greylisting with spamd and ended up silently losing quite a lot of email. (Many mail hosts do not re-send from the same IP, meaning messages essentially get stuck forever.) Doing spam checks at DATA time and rejecting obviously bad emails outright seemed much more effective and less dangerous. I never managed to get Spamassassin to do this, but auto-rejecting languages you don't read also cuts down on spam a lot. (I missed out on a consulting opportunity because the client's host of choice seemed to be a known spammer and my mail server's filtering was too aggressive about trusting blacklists. I chose to silently-reject those types of messages, so nobody got a bounce. Fortunately, someone was nice enough to ask me about it out-of-band so at least I was able to turn off greylisting and blacklisting before losing much more mail.) I never found an imapd that scaled to having a lot of messages in a folder, so I ran a cron-job to move mail offline after 2 weeks (for mailing lists) and 1 year (for INBOX). Similarly, I never found a good client to use; Gnus had a very cryptic configuration that I could never believe worked, and mutt was not Emacs-y enough. Reading my email mostly consisted of waiting for Gnus and deleting spam. (I never figured out a good way to get Gnus to move messages marked as spam somewhere so that I could run a cron job to automatically train Spamassassin on the known-bad emails. For search, I used HyperEstraier: http://sourceforge.net/projects/hyperestraier/ http://sourceforge.net/projects/hyperestraier/ You set it up to run the ingestion program as a cron job every 10 minutes, and then you get a CGI that will show you matching emails for your query. Of course, you can't actually click the links and go anywhere unless you set up some sort of web-based email viewer. I never found anything I liked so I lived without webmail. (There are lots of options. All difficult to configure and probably riddled with security holes.) Once your server is up and running, you need a secondary MX and a backup plan for your email. (I used Dyn.com's secondary MX hosting service. A lot of spam comes in through the secondary MX, so you can't just implicitly trust it. This involves more configuration.) Finally, spam filtering uses a lot of CPU and RAM, so you have to pay for a rather expensive virtual machine. Linode's $40/month plan seemed mostly adequate. I don't really like composing email in the web browser, but I've gotten used to it and $5/month for Gmail and $0/month of my time screwing around with spam filters seemed like a good tradeoff.
- X-Istence 14y ago
- mindcrime 14y agoHopefully this will encourage some people enough to run their own mail servers. It's far less problematic than most people think it is. Maybe it was hard to install and configure this in 1990s, but this is 2013. You buy a domain name, install a Debian machine, and do: Thanks, but no thanks. I just went in the opposite direction a couple of months ago, switching to a paid Google Apps account so they can handle email for us. I couldn't be happier. Our Postfix / Cyrus / Squirrelmail setup worked fine, but then the server got compromised and taken over by spammers, out IP got blacklisted by most everybody, and right in the middle of trying to fix all that, I got sick and wound up in the hospital. When I got home, I sat down to start trying to fix this mess and had an epiphany "WTF am I doing this? Hosting email servers is not a core competency for us, there is no competitive advantage to be gained here, and Google Apps is fairly cheap." I switched over the same night and haven't looked back. After fighting with Postfix and Friends on and off multiple times over the past decade, I'm out. I want no part of hosting email, now, or probably ever again. I have much, much, much better uses for my time than fixing broken email servers. It always surprises me that people can use a software library with complicated, half insane API's, but can't follow a single page of simple single steps installation. I have yet to find an email setup that can be described as "following a single page of simple single steps installation". And even if I could, I still don't want to, because there just isn't any real point to it. Email delivery is a commodity, not a core competence. Outsource the hell out of that shit, IMO.
- niggler 14y agoThere are a few things to note here: 1) in some industries (like in finance) the regulatory requirements make it near impossible to use external email services. For example, there needs to be a record of every email sent out of accounts in the company that needs to be presented to regulators when they demand it. 2) People within the same company may slip up and send emails to coworkers that shouldn't be read outside the company. When you run the email servers, no other party reads them. It stays in the family, so to speak. When you use google or whatever service, they get a peek at the emails. 3) AFAICT Gmail is not HIPAA compliant, making it inappropriate for health care businesses.
- 14y ago
- nonamegiven 14y agoPutting a scalpel in your drawer is a simple one-step operation. Anyone can install a scalpel. Using it effectively, and knowing the dark corners of scalpeling, is quite another thing. It would be easy to get into deep trouble with a scalpel.
- jasonlingx 14y ago> spend 5-10-30m tops to do an email installation Hahahahahahhahahahahhahahahahhah
- namuol 14y agoAs an alternative, are there any secure email services on the web we can use instead?
- ben0x539 14y agoThis is only slightly more reasonable than handing people an axe and sending them into the woods because their landlord won't fix a leaking pipe.