Apache2 0 52 centos server at dating ru port 8080

After all, you don’t really want to move off of GMail / Google Apps. Not only that, but it is actually going to be better than GMail, from a purely features perspective.

It might surprise you to learn that people continue to develop email server software in a post-Google-apps world, and that the state of self-hosted is much better than you remember.

It’s 2013; people have been getting TLS into wide adoption for awhile now. You’re going to build a modern, 2013, e-mail stack. Let’s just say, that’s a lot more forgiving than running Apache.

The people who have designed e-mail software are, on the whole, people with a lot more problems than you.

I measured it, and that’s a third of my ham volume. Doesn’t hosting your own mail require beefy hardware to deal with the spams? I get a lot of mail, and this is my graph: Doesn’t it go down a lot though?

And Google isn’t a special snowflake; any reasonably-configured mail will be encrypted over the wire. Getting up in the middle of the night to do server reboots and that? RFC 2821 requires that mail servers try for “at least 4-5 days” to deliver your mail.

If you’re complaining about government spying on the Internet, or in a gathering of programmers, and you won’t take to do anything about it, then you’re a hypocrite, full-stop. However, these people are not aware of just how much e-mail goes over TLS.I will personally come to your terminal and demand the return of your complain license. For example, if you follow this guide, every message to or from a GMail / Google Apps account goes over TLS.

rusariadna.ru

70 Comments

  1. Pingback:

  2. eric   •  

    What is pretty cool is that you can browse and search members and see what they are up to thanks to their status feed.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>