forked from Disroot/gpg-lacre
106 lines
3.9 KiB
Text
106 lines
3.9 KiB
Text
[default]
|
|
# Whether gpg-mailgate should add a header after it has processed an email
|
|
# This may be useful for debugging purposes
|
|
add_header = yes
|
|
|
|
# Whether we should only encrypt emails if they are explicitly defined in
|
|
# the key mappings below ([enc_keymap] section)
|
|
# This means gpg-mailgate won't automatically detect PGP recipients for encrypting
|
|
enc_keymap_only = no
|
|
|
|
# Whether we should only decrypt emails if they are explicitly defined in
|
|
# the key mappings below ([dec_keymap] section)
|
|
# This means gpg-mailgate won't automatically detect PGP recipients for decrypting
|
|
dec_keymap_only = no
|
|
|
|
# If dec_keymap_only is set to yes and recipients have private keys present for decrypting
|
|
# but are not on in the keymap, this can cause that mails for them will be
|
|
# encrypted. Set this to no if you want this behaviour.
|
|
failsave_dec = yes
|
|
|
|
# Convert encrypted text/plain email to MIME-attached encrypt style.
|
|
# (Default is to use older inline-style PGP encoding.)
|
|
mime_conversion = yes
|
|
|
|
# RFC 2821 defines that the user part (User@domain.tld) of a mail address should be treated case sensitive.
|
|
# However, in the real world this is ignored very often. This option disables the RFC 2821
|
|
# compatibility so both the user part and the domain part are treated case insensitive.
|
|
# Disabling the compatibility is more convenient to users. So if you know that your
|
|
# recipients all ignore the RFC you could this to yes.
|
|
mail_case_insensitive = no
|
|
|
|
# This setting disables PGP/INLINE decryption completely. However,
|
|
# PGP/MIME encrypted mails will still be decrypted if possible. PGP/INLINE
|
|
# decryption has to be seen as experimental and could have some negative
|
|
# side effects. So if you want to take the risk set this to no.
|
|
no_inline_dec = yes
|
|
|
|
[gpg]
|
|
# the directory where gpg-mailgate public keys are stored
|
|
# (see INSTALL for details)
|
|
keyhome = /var/gpgmailgate/.gnupg
|
|
|
|
[smime]
|
|
# the directory for the S/MIME certificate files
|
|
cert_path = /var/gpgmailgate/smime
|
|
|
|
[mailregister]
|
|
# settings for the register-handler
|
|
register_email = register@yourdomain.tld
|
|
mail_templates = /var/gpgmailgate/register_templates
|
|
# URL to webpanel. The server should be able to reach it
|
|
webpanel_url = http://yourdomain.tld
|
|
|
|
[cron]
|
|
# settings for the gpgmw cron job
|
|
send_email = yes
|
|
notification_email = gpg-mailgate@yourdomain.tld
|
|
mail_templates = /var/gpgmailgate/cron_templates
|
|
|
|
[logging]
|
|
# For logging to syslog. 'file = syslog', otherwise use path to the file.
|
|
file = syslog
|
|
verbose = yes
|
|
|
|
[relay]
|
|
# 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
|
|
host = 127.0.0.1
|
|
port = 10028
|
|
|
|
[database]
|
|
# uncomment the settings below if you want
|
|
# to read keys from a gpg-mailgate-web database
|
|
enabled = yes
|
|
name = gpgmw
|
|
host = localhost
|
|
username = gpgmw
|
|
password = password
|
|
|
|
[enc_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.
|
|
#you@domain.tld = 12345678
|
|
|
|
[dec_keymap]
|
|
# You can find these by running the following command:
|
|
# gpg --list-secret-keys --keyid-format long user@example.com
|
|
# Which will return output similar to:
|
|
# sec 1024D/AAAAAAAAAAAAAAAA 2007-10-22
|
|
# uid Joe User <user@example.com>
|
|
# ssb 2048g/BBBBBBBBBBBBBBBB 2007-10-22
|
|
# You want the AAAAAAAAAAAAAAAA not BBBBBBBBBBBBBBBB.
|
|
#you@domain.tld = 12345678
|
|
|
|
[pgp_style]
|
|
# Here a PGP style (inline or PGP/MIME) could be defined for recipients.
|
|
# This overwrites the setting mime_conversion for the defined recipients.
|
|
# Valid entries are inline and mime
|
|
# If an entry is not valid, the setting mime_conversion is used as fallback.
|
|
#you@domian.tld = mime
|