Hardware: VPS bought online ( Contabo )
YunoHost version: 18.104.22.168 (testing)
I have access to my server : Through SSH and browser
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no
since last night, i’ve received a storm of errors in the form of mail notifications.
always the same two, repeating over and over.
one, addressed to root states in the subject
Cron <root@mms> : YunoHost DynDNS update; sleep $((RANDOM%60)); ! ping -q -W5 -c1 ip.yunohost.org >/dev/null 2>&1 || test -e /var/run/moulinette_yunohost.lock || yunohost dyndns update >> /dev/null
while in the body you can read
Failed to resolve A for mms.nohost.me
the other email, is addressed to MAILER-DAEMON@mms.nohost.me and has this subject
Undelivered Mail Returned to Sender
and this body
This is the mail system at host mms.nohost.me.
I’m sorry to have to inform you that your message could not
be delivered to one or more recipients. It’s attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can
delete your own text from the attached returned message.
The mail system
<email@example.com> (expanded from ): user unknown
can anyone help me understand what’s going on?
do you have also get an upgrade from testing branch ?? See here Yunohost 11.1 spooky testing - #54 by xabi
I also find myself with this avalanche of emails for Dyndns and this “black hole” : /dev/null
I have to change the time variables in the file Cron Dyndns with Nano in SSH:
1/ Totally delete the sending of mail on root@XXX.nohost.XX
To prevent a particular task from sending an email, you just have to add at the end of the command a directive asking it to redirect the output to nothing (/dev/null), it is possible to do it in two ways:
by adding > /dev/null 2>&1 at the end of the command ;
or by adding &> /dev/null at the end of the command ;
2/ Change the timing of mail sending
0 7 * * 1-5 root : YunoHost DynDNS update […]
this represents one email at 7h00 from Monday to Friday
damn! it’s true! im just realised im on testing.
did you manage to go back to stable?
i changed the timing the same way you did and now i will wait to see how is it going to work.
however, this is just a fix for the notifications, but the problem/issue/error will still be there.
unless you’re saying the problem is the emailing in itaself?
You can also just add aliases with
abuse for your first user since it is like this…
We are waiting to know when a commit will fix this mistake, perhaps needs edit the
etc/apt/sources.list.d/yunohost.list to add
testing, and come back to stable after…
Better use a hook : 02-yunohost-dyndns_nomail
# A placer dans /etc/yunohost/hooks.d/conf_regen/
# on empêche le sript d'envoyer un mail
sed -i 's+>> /dev/null+> /dev/null 2>\&1+g' /etc/cron.d/yunohost-dyndns
when i try to access this file it creates a new one meaning this doesn’t exist?
Yes, it’s a new file (you can change his name if you want).
It replaces the final
>> /dev/null with
> /dev/null 2>&1 in the file
/etc/cron.d/yunohost-dyndns after you regen-conf yunohost-dyndns.