Introduction

The PGP Forwarding Server is a server that receives e-mail on behalf of a user, encrypt it automatically and sent it off the users' real e-mail account.

Here is a little illustration:
General operation

World view

The PGP Forwarding Server has a somewhat simplistic view of the world. We have basically a part of the world where things can be transferred in plain text. And we have a part of the world there things must be encrypted.

The world is divided. Sigh.

It is up to you to decide how big those parts are. Maybe the "Insecure world" is the whole internet. Or just people living in some undemocratic country. Maybe the "Free World" is the whole internet or just the people working in your local network?

We don't care. Just keep in mind that the working axiom is that there we don't can encrypt the e-mail whole traffic, so we care at least about this traffic where we have incluence.

Why not just encrypting everything?

Now, the question is, why can't we encrypt e-mail traffic completely? Because of real world constraints. Just to name a few:

However, if you are the boss of an enterprise you could train your exterior sales clarks on how to use PGP. And you can install the PGP Forwarding Server in your company and then everything in your country would be able to safely communicate with your travelling salesmen. Your accountant, your secretary, your tech department, and of course yourself.

So you see, by investing effort at the right place you will benefit from a great leverage effect all over your organisation.

PGP and SSH

No matter how big those areas are, a user of the PGP Forwarding Server needs to communicate via safe channels with the server. This is currently done by either PGP or SSH.

How a user communicates safely

Address hiding

When a user sends a message throught the server the server translates the real address of the user.

Your e-mail address get's shielded away

If this would not happen, then Aunt Mary would accidentally send plain text to the user.

Ups ... plain e-mail