Repository navigation
Upgrade SMTP client to use the (new) settings infrastructure - #1701
Conversation
327a7cd to
754b166
Compare
|
Copied from core mr:
|
|
Copied from core mr:
|
754b166 to
2cb30bc
Compare
e616ba0 to
34e7351
Compare
34e7351 to
1b65325
Compare
These are the generic settings of lib-smtp's SMTP and LMTP client. They are used inside the submission_relay and mail_submit filters, and by the LMTP proxy.
The SMTP client settings changes move the outgoing SMTP/LMTP connection
settings into filters that hold the generic smtp_client_*/lmtp_client_*,
client_auth_* and ssl_client_* settings:
- submission_relay_* -> submission_relay { smtp_client_* / client_auth_* /
ssl_client_require_valid_cert }. submission_relay_max_idle_time never did
anything and is deprecated.
- submission_host/submission_ssl -> mail_submit { smtp_client_host /
smtp_client_port / smtp_client_ssl }, submission_timeout ->
mail_submit_timeout, and sendmail_path -> mail_submit { execute sendmail
{ } }. The host:port syntax of submission_host is gone.
- lmtp_proxy_rawlog_dir -> lmtp_client_rawlog_dir. The LMTP proxy uses the
lmtp_client_* settings directly, without a filter, so lmtp_proxy stays a
boolean.
Also list submission_relay and mail_submit as client_auth users in the
client_auth and ssl_client_require_valid_cert descriptions.
The submission relay and mail_submit SMTP clients now use the same client_auth_* settings. Add them to the client list.
…tings
submission_host and sendmail_path are now configured inside mail_submit { },
the relay settings inside submission_relay { }, and the LMTP proxy's backend
connections with the lmtp_client_* settings. Add a relay example with
authentication to the submission page.
86f55ca to
60d8e3e
Compare
DOV-9262