5 ms·
I deployed this a few days ago using postfix-mta-sts-resolver in docker, spun up an nginx server to handle the txt file, and added the dns txt record. Fairly st
by amaccuish 8y ago
I deployed this a few days ago using postfix-mta-sts-resolver in docker, spun up an nginx server to handle the txt file, and added the dns txt record. Fairly straightforward. I'll keep an eye on my logs and see if it changes anything.
I also note that google is in the starttls-policy [1] list in testing mode (they're also on testing, not enforced, for mta-sts on gmail.com [2])
[0] https://github.com/Snawoot/postfix-mta-sts-resolver https://github.com/Snawoot/postfix-mta-sts-resolver (this is more up-to-date than the PyPI package)
[1] https://starttls-everywhere.org/policy-list/ https://starttls-everywhere.org/policy-list/
[2] https://mta-sts.gmail.com/.well-known/mta-sts.txt https://mta-sts.gmail.com/.well-known/mta-sts.txt
- Snawoot 8y agoIf you are concerned, for both MTA-STS and STARTTLS-Everywhere you may use enforcing policy even against domains in testing mode at the cost of small possibility of delivery failure. postfix-mta-sts-resolver has config option strict_testing: true starttls-policy-cli has Early Adopter mode of config generator (-e, --early-adopter).