2010-01-20 21:53:25 +01:00
|
|
|
[default]
|
2013-09-22 21:40:33 +02:00
|
|
|
# whether gpg-mailgate should add a header after it has processed an email
|
|
|
|
|
# this may be useful for debugging purposes
|
2010-01-20 21:53:25 +01:00
|
|
|
add_header = yes
|
|
|
|
|
|
|
|
|
|
[gpg]
|
2013-09-22 21:40:33 +02:00
|
|
|
# the directory where gpg-mailgate public keys are stored
|
|
|
|
|
# (see INSTALL for details)
|
2010-01-20 21:53:25 +01:00
|
|
|
keyhome = /var/gpg/.gnupg
|
|
|
|
|
|
|
|
|
|
[logging]
|
2013-09-22 21:40:33 +02:00
|
|
|
# file to log to
|
2010-01-20 21:53:25 +01:00
|
|
|
file = /tmp/gpg-mailgate.log
|
|
|
|
|
|
|
|
|
|
[relay]
|
2013-09-22 21:40:33 +02:00
|
|
|
# the relay settings to use for Postfix
|
|
|
|
|
# gpg-mailgate will submit email to this relay after it is done processing
|
|
|
|
|
# unless you alter the default Postfix configuration, you won't have to modify this
|
2010-01-20 21:53:25 +01:00
|
|
|
host = 127.0.0.1
|
|
|
|
|
port = 10028
|
|
|
|
|
|
|
|
|
|
[keymap]
|
|
|
|
|
# You can find these by running the following command:
|
|
|
|
|
# gpg --list-keys --keyid-format long user@example.com
|
|
|
|
|
# Which will return output similar to:
|
|
|
|
|
# pub 1024D/AAAAAAAAAAAAAAAA 2007-10-22
|
|
|
|
|
# uid Joe User <user@example.com>
|
|
|
|
|
# sub 2048g/BBBBBBBBBBBBBBBB 2007-10-22
|
|
|
|
|
# You want the AAAAAAAAAAAAAAAA not BBBBBBBBBBBBBBBB.
|
2013-04-02 21:38:07 +02:00
|
|
|
#user@example.com = <gpg key id>
|
