If you are used to dealing with commands like mail from the mailx package, you may be used to apps that require a local MTA in order to send emails. In the config files of dnf-automatic however, we can instantly see that there is configuration for entering a non-local server. This means that dnf-automatic is implementing the SMTP protocol (SMTP) itself and is not dropping files in a queue.
# The address to send email messages from.
email_from = email@example.com
# List of addresses to send messages to.
email_to = root
# Name of the host to connect to to send email messages.
email_host = localhost
Because of this, we know that dnf-automatic is acting as an SMTP server on its own and must be configured for how your network is going to handle email and is not just relying on the default configuration of the system MTA.
No, this is jsut droping a mail to root. not email.
Wouldn't be better to say it's an SMTP client? Akin to Thunderbird?
But in this case it's not doing that, so would be confusing. Thunderbird is an SMTP client, but doesn't do the local drop piece.
What's not doing what? dnf-automatic isn't doing a local drop piece either. It uses SMTP to drop to localhost, not whatever mailx is doing to function.
So in that regard, it should be exactly like what Thunderbird is doing, no?
I don't believe that that is true, but maybe it is.
Well we know dnf-automatic will deliver to postfix on another host assuming that host is configured to allow relay from the dnf host. Am I missing something?
Does dnf-automatic not do both, though?
I don't know if dnf-automatic is doing the local drop piece like mailx does.