I was setting up dnf-automatic on a new system today and recalled this post. I changed the reboot option and it made the systemd file as noted, which is what you report. So are you sure someone did not change your config from never to when-changed?

b4aef492-0dfb-4496-a1b4-23aaafa0299f-image.png

@JaredBusch said in Resolved - Postfix on Fedora 29 - Why Can't I Send Mail?:

@wrx7m said in Resolved - Postfix on Fedora 29 - Why Can't I Send Mail?:

It applied to the instance (multiple servers)

FFS no. That is not what anything is.

It applied to the Account. Which contains multiple instances.
Instances that could be servers or desktops or WTF ever.

My apologies. I meant to put account.

Playing around with OBS Studio: DNF Auto Update

Youtube Video

@scottalanmiller said in How Does dnf-automatic Send Emails:

@dashrender said in How Does dnf-automatic Send Emails:

@scottalanmiller said in How Does dnf-automatic Send Emails:

@dashrender said in How Does dnf-automatic Send Emails:

@scottalanmiller said in How Does dnf-automatic Send Emails:

@dashrender said in How Does dnf-automatic Send Emails:

@jaredbusch said in How Does dnf-automatic Send Emails:

@scottalanmiller said in How Does dnf-automatic Send Emails:

Starting from another thread....

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.

[email] # The address to send email messages from. email_from = [email protected] # 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.

@jaredbusch said in SaltStack State: DNF-Automatic:

@tim_g said in SaltStack State: DNF-Automatic:

@jaredbusch said in SaltStack State: DNF-Automatic:

This would be the default one that comes down with the package. So that means there is nothing to grab.

Correct. I installed it on something first to get the config files, so I know what I'm working with.

That is more work and does nothing to help you when the file is updated upstream.

I did find how to easily modify files with SaltStack: https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.file.html#salt.modules.file.replace

But I think I would still rather host my own config file(s) at least for now. If they change in future updates, I'll just modify the config files on GitLab.

Anyways, link above for future reference when I come back to this later.

@JaredBusch said in Using dnf-automatic to keep Fedora up to date:

@FATeknollogee said in Using dnf-automatic to keep Fedora up to date:

There really need to be a setting for this in the Workstation GUI.

By default Fedora Workstation + Cinnamon uses dnfdragora which is a totally separate process.

Yes, I realize that.
This setting exists in Cockpit, no reason why it can't be in WS!