RFC 8314 § 3.3 support at Dovecot submission proxy service?

[Robert Scheck]

Hello all,

I'm currently wondering whether Dovecot submission proxy service supports
RFC 8314 § 3.3 as well, which means implicit TLS for SMTP submission.

https://github.com/dovecot/core/blob/2cbbe9b4829adb184c83dbf780316f4144559054/doc/example-config/conf.d/10-master.conf#L48
from Git master just mentions port 587 like this:

service submission-login {
  inet_listener submission {
    #port = 587
  }
}

As per RFC 8314 § 3.3, I would expect the following to work (which I did
not try), and if it already works, I even would expect this snippet part
of the future Dovecot example/default configuration:

service submission-login {
  inet_listener submission {
    #port = 587
  }
  inet_listener submissions {
    #port = 465
    #ssl = yes
  }
}

And if it isn't supported yet, I would indeed like to raise this as feature
request. Note that 465 is named "submissions" as per RFC 8314 § 7.3.


Kind regards

Robert Scheck
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
URL: <https://dovecot.org/pipermail/dovecot/attachments/20190610/a146f822/attachment.sig>