MTA-STS-DAEMON(1)
β¨ mta-sts-daemon(1) β¨
okay bestie, welcome to the mta-sts-daemon page, section 1 of the manual π this one lives in the postfix-mta-sts-resolver fam and it's literally the glow-up your mail server has been asking for π«Ά
πΈ NAME πΈ
mta-sts-daemon β hands Postfix its MTA-STS policy like a little policy map delivery service π
π SYNOPSIS π
mta-sts-daemon [OPTION]...
π¦ DESCRIPTION π¦
so basically this daemon π opens π a π socket π and Postfix can just slide in there, query it, and pull the MTA-STS policy for a domain. that's the whole vibe. it's giving "policy concierge" honestly.
the config file situation is fully documented in mta-sts-daemon.yml(5) β go read that if you wanna know what it's eating.
MTA-STS, which is specified in RFC 8461 [0], is a security standard for email servers. when a site sets up MTA-STS, other mail servers can require that the site authenticates successfully before forwarding mail over there. no cap. it's the "prove you're you before I hand over the mail" rule and honestly it ate π₯
β¨ OPTIONS β¨
-h,--helpβ pops up a help message and then dips out, that's it, that's the whole job π-v,--verbosityVERBOSITY β sets how chatty the logs get. your choices are:debug,info(this is the default, bestie),warn,error, orfatal.-c,--configFILE β where the config file lives. default:/etc/mta-sts-daemon.yml-g,--groupGROUP β change the eGID to this group. default: none (so it just stays as it is, no thoughts head empty).-l,--logfileFILE β where you want the log file to go. default: none.-p,--pidfilePIDFILE β the name of the file it writes the current pid into. default: none.-u,--userUSER β change the eUID to this user. default: none.--disable-uvloopβ do NOT use uvloop, even if uvloop is sitting right there being available. default: enabled if available (so it uses uvloop when it can, unless you tell it not to π).
π EXAMPLES π
first up, configure Postfix in /etc/postfix/main.cf, like so:
smtp_tls_policy_maps = socketmap:inet:127.0.0.1:8461:postfix
smtp_tls_CApath = /etc/ssl/certs/
then reload Postfix. oh and then verify it's actually working, queen:
/usr/sbin/postmap -q dismail.de socketmap:inet:127.0.0.1:8461:postfix
β οΈ real talk though: this configuration overrides DANE TLS authentication. if you wanna meet the requirement of RFC 8461, section 2, you should list a DANE policy resolver (or a static lookup table for domains known to implement both MTA-STS & DANE) beforemta-sts-daemoninsmtp_tls_policy_maps. order matters, bestie, don't skip this part π
π SEE ALSO π
π NOTES π
- SMTP MTA Strict Transport Security (MTA-STS): https://tools.ietf.org/html/rfc8461
aaaand that's a wrap, bestie π this was postfix-mta-sts-resolver energy, dated 2026-04-29, and you absolutely understood all of it. slay, go configure your mail server, you've got this πβ¨
π¦ where this page comes from
- ubuntu stonking: postfix-mta-sts-resolver 1.5.1-1 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms