views:

384

answers:

2

Encrypted email - sounds like a great thing, right? Problem already solved, right? Well... I don't think so and I'm hoping I'm wrong!

To understand what I'm asking, please understand what I'm NOT asking: I am not asking how I encrypt and sign messages sent over public networks. This is a bit different.

I want to set up a mail server where email clients can both read and post and their messages to the mail server encrypted in both directions, preferably using standard clients available at internet cafes, etc, without requirement for specialized software or encrypted port-forwarding a-la SSH.

The key here is that there is a trusted mail server which can deliver email to a community using a local-delivery-agent. One can then send email to and receive from anyone and everyone who also uses that same system without concern for the security of their communications. There's no need to encrypt every message using the public key of every recipient - what pain THAT would be! - and instead all we're talking about here is a bidirectional communication that's encrypted from clients to this system.

Of course, public messages come in unencrypted via the usual port 25 process to all participants of the email server. They may or may not be encrypted as they were - we're not worried about them. Email Clients connect from anywhere and the responding code on the server system encrypts those messages for reading, even though they were sent through the public network in plain text already... This much I can already get fairly easily with encrypting IMAP servers like Dovecot.

What I want to add to this is that connected email clients can send email, encrypted, back to the system of which they are a client wherein that system forwards externally unencrypted, wherever it needs to go. If it's a local mailbox, the message is delivered via a local delivery agent. No keys involved there. The advantage of this design is that there's NO exposure of the email to external, untrusted systems or networks, and if the delivery is local, it's effectively protected end-to-end WITHOUT having a point-to-point hassle of encrypting individual messages in the more typical use.

This would be "god send" because as it is now, it's impossible to send secured mail through clients on the public internet to groups of people within an internal network.

I guess another way to phrase what I’m asking for is: Has someone created a package that gives us the other half of the encryption that IMAP (and POP?) servers already do – that distant clients on untrusted networks can hand-off out-bound unencrypted email through an encrypted link to the server on the other end?

ANOTHER ALTERNATIVE occurred to me: Encrypting SMTP / ESMTP servers that talk mail server to mail server in an encrypted form. (Similarly, clients should be able to hand off unencrypted email through an encrypted link, much as https works.) Anybody know of such a package? This is not quite as good, but an important part of email architecture...

If this doesn’t exist today, it should!

Thanks for your thoughts, pointers, etc.

+3  A: 

Most existing email clients support message submission (either using SMTP or MSA) via TLS/SSL. I just checked in Outlook and Opera and both support it.

And I know for a fact that Courier's email suite supports TLS/SSL for both SMTP and MSA (and IMAP), so it's not an obscure setup; just a little uncommon. And it supports requiring TLS/SSL for any or all protocols.

staticsan
"Courier", eh? I'll look it up - hope it's available on my platform(s)!
Richard T
No, there are no Courier RPMs for Fedora. -frown- This has, however, prompted me to take a second look at the latest Dovecot, which I already have. Also, the post below uses Outlook - that I won't touch! However, if an SSL connection for SMTP is offered in it, maybe they've added it elsewhere... Hmm
Richard T
www.courier-mta.org It compiles on RedHat and it even comes with a .spec file to make your own RPMs. But it's available with apt-get on Debian platforms.
staticsan
+1  A: 
Chase Seibert
The setting you circled pertains to the IMAP server and only works for reading. The other one, regarding SMTP, outgoing, is one I haven't seen - perhaps I've been living in the past! Outgoing (from the client) is what I was asking about, so maybe it's here and I just over looked it in new releases!
Richard T
It turns out that I won't touch Outlook, but Thunderbird now has this feature... Looks like I'll need to check into an SMTP server that encrypts - maybe I've already got it! Tnx for the pointer. Note, though, this WASN'T in there last time I looked!
Richard T