We had a stray letter in a configuration field intended to be used for port numbers which resulted in port numbers such as 587c where the letter tripped up Postfix' SMTP client which in turn caused it to exit early. Any e-mail stuck in queue to be sent upstream would remain stuck indefinitely as no connection was possible. We're opting to not implement a config test. A 'postfix check' will not find such issues and a service restart via an Ansible handler will work without issues. Postfix will only complain about such an issue when connecting its client to the upstream server for real mail delivery. Any detection or validation mechanism would require the same real-life test of sending an e-mail. At this time its appears saner to not implement a test rather than implementing an invasive test.
8 lines
1004 B
YAML
8 lines
1004 B
YAML
# SPDX-License-Identifier: MIT
|
|
somta__e_mail_default_recipient_addr_spec: '{{ lookup(''hashi_vault'', ''secret=kv/data/settings/comms/e-mail/default/recipient:addr-spec'') }}'
|
|
somta__e_mail_default_sender_addr_spec: '{{ lookup(''hashi_vault'', ''secret=kv/data/settings/comms/e-mail/default/sender:addr-spec'') }}'
|
|
somta__e_mail_default_sender_credentials_password_smtp_auth_login: '{{ lookup(''hashi_vault'', ''secret=kv/data/settings/comms/e-mail/default/sender:credentials-password-sasl-smtp-auth-login'') }}'
|
|
somta__e_mail_default_sender_credentials_username: '{{ lookup(''hashi_vault'', ''secret=kv/data/settings/comms/e-mail/default/sender:credentials-username'') }}'
|
|
somta__e_mail_default_sender_submission_server_fqdn: '{{ lookup(''hashi_vault'', ''secret=kv/data/settings/comms/e-mail/default/sender:submission-server-fqdn'') }}'
|
|
somta__e_mail_default_sender_submission_server_port: '{{ lookup(''hashi_vault'', ''secret=kv/data/settings/comms/e-mail/default/sender:submission-server-port'') }}'
|