Bug#1062357: systemd-cron: broken result mailing implementation
Alexandre Detiste
alexandre.detiste at gmail.com
Thu Feb 29 23:13:34 GMT 2024
control: tag +1 help
I'm running out of ideads.
Le ven. 2 févr. 2024 à 08:32, Martin-Éric Racine
<martin-eric.racine at iki.fi> a écrit :
> > > Also, can this variable be configured in a file that is dropped into
> > > some directory, to avoid editing the global /etc/crontab? e.g.
> > > /etc/crontab.d/ or something similar?
> >
> > /etc/crontab _is_ the main config file which other jobs
> > (like in /etc/cron.{d,hourly,daily,...}/ will inherit mailing settings from.
> > ("std::optional<std::string> fallback_mailto;" in code)
> >
> > /etc/sysconfig/crond & /etc/default/PACKAGE are old Redhat & Debian
> > things, mostly deprecated by systemd config drop-ins.
>
> A systemd drop-in would work too. It just needs to be documented.
> Which file? Which configuration key? Just as long as there's somewhere
> I can drop a file to configure the MAILFROM on all my hosts, I'm good
> to go.
https://people.math.wisc.edu/~emeitner/setting-a-global-mailto-environment-variable-in-cron.html
Maybe playing around with DefaultEnvironment and having MAILTO= defined
in every single process launched by systemd.
This looks a bit overkill...
https://askubuntu.com/questions/1334312/reliable-cron-errors-notifications-how-to
> > _cron-failure is a technical user, it should never leaks into e-mail envelopes.
> > I'm using nullmailer myself but I can't reproduce it.
>
> It does if delivery of the cron job report fails.
I don't know enought the email protocol & usages to fix this.
Again I carefuly monitor the cronie & Debian cron fork codebases;
but found no clue.
Greetings
More information about the Pkg-systemd-maintainers
mailing list