You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which feature or improvement would you like to request?
The default MX patterns used by the MTA-STS get created from the available TLS certificates, but there is one problem with it:
I also need to use TLS certificates for the CNAME entries of mta-sts.example.com, autoconfig.example.com and autodiscover.example.com. So I added those to the ACME provider. Therefore by default they also appear in the mta-sts.txt as MX entries.
For now I just used the MX patterns override field and that of course works.
It might be a good idea though to automatically exclude entries starting with mta-sts., autoconfig. or autodiscover. from that default list.
Is your feature request related to a problem?
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
The TLSA records should reflect the correct port what they are used for, in this case "443". The missing TLSA records for IMAPS and SMTPs should be added to.
Which feature or improvement would you like to request?
The default MX patterns used by the MTA-STS get created from the available TLS certificates, but there is one problem with it:
I also need to use TLS certificates for the CNAME entries of
mta-sts.example.com
,autoconfig.example.com
andautodiscover.example.com
. So I added those to the ACME provider. Therefore by default they also appear in themta-sts.txt
as MX entries.For now I just used the MX patterns override field and that of course works.
It might be a good idea though to automatically exclude entries starting with
mta-sts.
,autoconfig.
orautodiscover.
from that default list.Is your feature request related to a problem?
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: