1
0
mirror of https://github.com/moparisthebest/gpgit synced 2024-11-15 21:45:03 -05:00
Go to file
2012-08-04 19:25:23 -04:00
encmaildir.sh encmaildir.sh: Remove third argument, changed default encryption mode to PGP/MIME (gpgit default), no need to specify path to gpgit.pl (assumes it is next to this script), no full paths to binaries, harmonize indentation, rename variables to better names, don't use a temporary file to keep track of program state, remove security vulnerability during which the (encrypted) message could be read by anyone able to read /tmp for a short while 2012-08-04 19:25:23 -04:00
gpgit.pl Handle CID urls that are not surrounded by quotation marks 2011-11-15 13:05:48 +00:00
README Updated to reflect the new behaviour after --encrypt-mode was 2011-03-16 10:51:16 +00:00
TODO Implemented --encrypt-mode and --help arguments. We now default to using 2011-03-13 11:33:39 +00:00

See https://grepular.com/Automatically_Encrypting_all_Incoming_Email

This application takes one argument on the command line. The email address to
look up the public key that the message will be encrypted with. An email
message is piped through the application, and the resulting email is sent to
STDOUT encrypted with the relevant public key. If you provide multiple email
addresses, then the message will be encrypted with multiple keys. There are
several options to do with the type of encryption used, ie PGP/MIME or inline
and these can be discovered by running the script without any arguments to
read the usage information.

If the message is already encrypted, it doesn't get encrypted a second time.

Exim users can use the transport_filter directive in a transport in order to
call this application, like so:

  transport_filter = /bin/gpgit.pl my.email.address@example.com

Procmail users can add a procmail recipe as follows

  :0 f
  | /bin/gpgit.pl my.email.address@example.com

If you call gpgit.pl from a different application, I'd love to hear from you so
I can update this README file.