**WARNING**Re: gpgme: encrypt/decrypt
John A. Martin
jam at jamux.com
Tue Aug 16 22:51:19 CEST 2005
>>>>> "Michael" == Michael Nguyen
>>>>> "Re: **WARNING**Re: gpgme: encrypt/decrypt"
>>>>> Tue, 16 Aug 2005 12:44:17 -0700
Michael> From: "Albrecht Dreß" <albrecht.dress at arcor.de>
>> Am 16.08.05 20:22 schrieb(en) Michael Nguyen:
>>> I'm creating a Postfix content filter for the company that
>>> automatically does GPG encryption/decryption on incoming and
>>> outgoing corporate mail.
>> This sounds like an ineresting idea!
Michael> First, I want to thank you for the response.
>> However, are you sure you want to do this on the *mta* level?
>> Most mua's
Michael> The CEO has requested this because he wants GPG to be
Michael> standard at the company and doesn't want to have any spin
Michael> up time for any of the employees. He feels that it has
Michael> to be as transparent as possible. If this is implemented
Michael> right, no one will never know it's happening.
How about just turning on Postfix's TLS support? Maybe with SMTP-AUTH
as well? Then perhaps gpg for end-to-end privacy? Use the tool that
fits the job. Avoid a lot of problems.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 154 bytes
Desc: not available
Url : /pipermail/attachments/20050816/a35fa23e/attachment-0001.pgp
More information about the Gnupg-devel