It's always dns.
Heute brauchte Logwatch länger als die üblichen paar Sekunden, um mir eine Auswertung aufzubereiten. Erheblich länger. Ich bin dann mal auf Recherche gegangen und siehe da: Im STRACE konnte ich sehen, dass es generell viele Versuche gab, IP-Adressen auf Hostnamen zu mappen (und wieder zurück).
Tja, und mit genügend krude konfigurierten Hostnames und IP-Kombinationen wird der Prozess halt teilweise bis zum Timeout pro Auflösung in die Länge gezogen.
It's always dns
#Logwatch sends ugly mails, this is a better approach
#adminlife #opensource
https://github.com/seraphyn/betterlogwatchhtml/tree/main
Using #Logwatch for Basic Security Monitoring on #Linux
https://linuxconfig.org/using-logwatch-for-basic-security-monitoring-on-linux
Ok, #exim can email me again. Just had to clear its retry database because it gave up sending everything. Guess it took a while for it to be able to run again even after clearing it, maybe #Mailjet or #Microsoft blocked me for a time, not sure. If you run into this, make sure you don't have #logwatch emailing you at the server's local mailbox and a remote mailbox in the cron.daily file for it at the same time, then clear the retry queue for #exim4. Then wait a few hours.
I've finally gotten emails to be sent from my server to myself via #exim4, a smarthost configuration, and #swaks. This page worked for me on #Mailjet, but Outlook is moving my emails to junk. I've said it's not junk, but it hasn't caught on yet. Did have to have logwatch's cron.daily thing run swaks since I can't seem to get #logwatch to email myself with my own email address properly. I had to think a lot on what to do, but this link should mostly help.
https://michael.franzl.name/blog/posts/2021-02-06-system-monitoring-using-e-mail
osmodia
Christian M. Grube 🐧
ricardo 
Calicosine
Stuart (moved)
Ardmore
root@eruditorum.œrg
Paula Gentle on Friendica