list-defaults.yml 5.37 KB
Newer Older
paz's avatar
paz committed
1 2 3 4 5 6 7 8
# Setting default values for newly generated lists. Once a list is created it
# is not affected by these settings but has its own set of options in the
# database.
#
# The configuration format is yaml (http://www.yaml.org).
#
# Options are listed with the behaviour encoded in the database schema.

georg's avatar
georg committed
9
# Only send out encrypted emails to subscriptions?
10
# (This setting does not affect resend-messages.)
paz's avatar
paz committed
11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28
send_encrypted_only: true

# Allow only encrypted emails? If true, any other email will be bounced.
receive_encrypted_only: false

# Allow only emails that are validly signed? If true, any other email will be
# bounced.
receive_signed_only: false

# Allow only emails that are validly signed by a subscriber's key?  If true,
# any other email will be bounced.
receive_authenticated_only: false

# Allow only emails being sent from subscribed addresses? If true, any other
# email will be bounced.
# NOTE: This is a very weak restriction mechanism on which you should not rely,
#       as sending addresses can easily be faked! We recommend you to rather
#       rely on the `receive_authenticated_only` option. Setting the
georg's avatar
georg committed
29
#       `receive_authenticated_only` option to true, will authenticate senders
paz's avatar
paz committed
30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45
#       based on the signature on the mail, which is the strongest
#       authentication mechanism you can get.
#       This option could be useful, if you would like to have a closed
#       mailinglist, but could not yet get all subscribers to properly use GPG.
receive_from_subscribed_emailaddresses_only: false

# Allow only emails that are validly signed by a list-admin's key.
# This is useful for newsletters, announce or notification lists
receive_admin_only: false

# Which headers to include from the original mail.
headers_to_meta:
- from
- to
- cc
- date
46 47
- sig
- enc
paz's avatar
paz committed
48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64

# Preserve the Message-IDs (In-Reply-To, References) from the incoming email.
# This setting can lead to information leakage, as replies are connectable
# and a thread of (encrypted) messages can be built by an eavesdropper.
keep_msgid: true

# Which keywords ("email-commands") should be restricted to list-admins?
keywords_admin_only:
- subscribe
- unsubscribe
- delete-key

# For which keywords should the list-admins receive a notice whenever it
# triggers a command.
keywords_admin_notify: 
- add-key

paz's avatar
paz committed
65 66 67 68
# Footer to append to each email that is sent to a subscribed address. Will not
# be included in messages to non-subscribed addresses.
internal_footer:

69 70
# Footer to append to each email that is sent to non-subscribed addresses. Will
# not be included in messages to subscribed addresses.
paz's avatar
paz committed
71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95
public_footer:

# Prefix to be inserted into the subject of every email that is validly signed
# by a subscribed address.
subject_prefix:

# Prefix to be inserted into the subject of every email that is *not* validly
# signed by a subscribed address.
subject_prefix_in:

# Prefix to be inserted into the subject of every email that has been
# resent to a non-subscribed address.
subject_prefix_out:

# Drop any bounces (incoming emails not passing the receive_*_only-rules)?
bounces_drop_all: false

# Drop bounces if they match one of these headers. Must be a hash, keys
# and values are case insensitive.
bounces_drop_on_headers: 
  x-spam-flag: yes

# Send a notice to the list-admins whenever an email is bounced or dropped?
bounces_notify_admins: true

96 97 98
# Include Autocrypt header into emails?
include_autocrypt_header: true

paz's avatar
paz committed
99 100 101 102 103 104
# Include RFC-compliant List-* Headers into emails?
include_list_headers: true

# Include OpenPGP-Header into emails?
include_openpgp_header: true

georg's avatar
georg committed
105
# Preferred way to receive emails to note in OpenPGP-Header
paz's avatar
paz committed
106 107 108 109 110 111 112
# ('sign'|'encrypt'|'signencrypt'|'unprotected'|'none')
openpgp_header_preference: signencrypt

# Maximum size of emails allowed on the list, in kilobyte. All others will be
# bounced.
max_message_size_kb: 10240

paz's avatar
paz committed
113 114 115 116
# How verbose to log on the list-level (Notifications will be sent to
# list-admins)? Error, warn, info, or debug.
log_level: warn

paz's avatar
paz committed
117 118 119 120 121
# How many logfiles to keep, including the current one.
# Logfiles are rotated daily, so 2 means: delete logfiles older than
# yesterday.  Values lower than 1 are ignored.
logfiles_to_keep: 2

paz's avatar
paz committed
122 123 124
# Which language to use for automated replies, error-messages, etc.
# Available: en, de.
language: en
paz's avatar
paz committed
125

126 127 128
# Forward a raw copy of all incoming emails to the list-admins?
# Mainly useful for debugging.
forward_all_incoming_to_admins: false
129 130 131 132 133

# Should e-mails be delivered to the original subscribed sender?
# Disabling this only works for signed e-mails; any e-mail that is unsigned
# sent to the list is treated as coming from an unknown source
deliver_selfsent: true
134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151

# Set reply-to header to original sender's reply-to? 
# Enabling this will set the reply-to-header of emails sent by schleuder
# to the original sender's reply-to-header. If the original sender
# did not supply a reply-to-header, the original from-header will be used.
# This option can enabled for improved usability since this affect
# mail client's reply-to button to reply to the original sender instead of
# the whole list.
set_reply_to_to_sender: false

# Munge from-header?
# Enabling this option will add the original sender to the from-header.
# To avoid DMARC issues, we still use the list's address as from-address.
# However the sender's address will be included as displayed name.
# For example: "sender@sender.org via list@list.org" <list@list.org>
# This option can enabled for improved usability since this affect
# mail client's displayed name.
munge_from: false