Comme j’étais en train d’effectuer une autre tâche d’administration, j’ai découvert que le serveur mail rejettait continuellement un envoi d’email local de l’utilisateur nextcloud et je ne suis pas sûr de savoir si c’est un bug du packaging de nextcloud ou une fausse manip de ma part à une époque qui a pu conduire à ça
Voici la trace qui se répète encore et encore dans les logs (tous les quarts d’heure). example.com est mon domaine principal, example_com le nom de ma machine
Nov 19 00:15:01 example_com postfix/pickup[1237463]: A69AE1F479: uid=994 from=<nextcloud>
Nov 19 00:15:01 example_com postsrsd[1238490]: srs_forward: <nextcloud@example.com> not rewritten: Domain excluded by policy
Nov 19 00:15:01 example_com postfix/cleanup[1238484]: A69AE1F479: message-id=<20231118231501.A69AE1F479@example.com>
Nov 19 00:15:01 example_com postfix/qmgr[1109091]: A69AE1F479: from=<nextcloud@example.com>, size=5142, nrcpt=1 (queue active)
Nov 19 00:15:01 example_com postfix/pipe[1238492]: A69AE1F479: to=<nextcloud@example.com>, orig_to=<nextcloud>, relay=dovecot, delay=0.04, delays=0.02/0/0/0.02, dsn=5.1.1, status=bounced (user unknown)
Nov 19 00:15:01 example_com postsrsd[1238490]: srs_forward: <""> not rewritten: No at sign in sender address
Nov 19 00:15:01 example_com postfix/cleanup[1238484]: ADD5F1F640: message-id=<20231118231501.ADD5F1F640@example.com>
Nov 19 00:15:01 example_com postfix/qmgr[1109091]: ADD5F1F640: from=<>, size=6977, nrcpt=1 (queue active)
Nov 19 00:15:01 example_com postfix/bounce[1238496]: A69AE1F479: sender non-delivery notification: ADD5F1F640
Nov 19 00:15:01 example_com postfix/qmgr[1109091]: A69AE1F479: removed
Woops, sorry. I’m using nextcloud 27.1.2 (latest) on latest yunohost version. Everything is up-to-date using stable repository. This is not a new install, I just recently discovered the problem. I’ve no idea for how long it exists, but the oldest one (back to oct. 22nd) already contains those lines.
The block is repeating every quarter of hour. Thus it does not seem to be related to the main nextcloud cron, which is configured to run every 5 minutes.
ahah, I think I found the origin of the problem: I setup the thumbnailer app by hand and configured its cron myself every quarter of hour… and forgot about it. I just saw that it was still containing a call to php8.1 when nextcloud now run with php8.2. So the cron was failing and sending an email at each run.
I’ve fixed the cron setting, thus let’s check that no more emails like this are bounced.
However, it explains the cause, but it also means that there is an issue with email deliverability when sent from the system to any app related users. What should I do here? Add an alias for nextcloud@maindomain to my own user ? Or did I miss something else?
I confirm the bounces were coming from my forgotten cron job. I’ll gently wait for the new release to come to see if it also fixes the email in case of failed cron jobs.
