remail/Documentation/examples/conf/lists/list1/list.yaml
Thomas Gleixner 46f6145ac5 remail: Allow optional transport based security
Add an "encryption" option 'use_transport' which does not bother with
encryption and just relies on transport security.

For admins this makes sense as none of the admin messages is really
confidential.

This is also a valid option for a subscriber and makes some sense in
scenarios where the mail provider manages the subscriber key (sic!)
and does server side decryption. Think twice before using this.

Requested-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Tested-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Reviewed-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
2020-11-01 22:19:22 +01:00

43 lines
1.2 KiB
YAML

#
# Recrypting mailing list configuration file for list1
#
# The list subscribers
subscribers:
# Format:
# email address:
# name: Real name of the subscriber
# enabled: Subscriber is enabled (if omitted defaults to False)
# use_smime: True/False (Use S/MIME for encryption. If omitted defaults to False)
# use_transport: True/False (SMTP transport layer encryption only. If omitted defaults to False.
# Conflicts with use_smime == True)
# fingerprint: GPG fingerprint (Not required when use_smime == True or use_transport == True)
# gpg_plain: Plain text inline GPG encryption (If omitted defaults to False)
# aliases: List of alias addresses which are valid for posting (moderated list)
#
# Note: Use spaces for spacing not tabs
dev1@some.domain:
name: Developer One
enabled: True
use_smime: True
dev2@some.domain:
name: Developer Two
enabled: False
dev3@other.domain:
name: Developer Three
enabled: True
fingerprint: 40_CHARACTER_PGP_FINGERPRINT
aliases:
- dev3@dev3.domain
- hckr@dev3.domain
dev4@other.domain:
name: Developer Four
enabled: True
fingerprint: 40_CHARACTER_PGP_FINGERPRINT
gpg_plain: True