What type of hardware are you using: VPS bought online
What YunoHost version are you running: 13.0.3 (testing) on Trixie
How are you able to access your server: The webadmin
SSH
Are you in a special context or did you perform specific tweaking on your YunoHost instance ?: No
Describe your issue
Hello,
24 heures après avoir paramétré les reverses DNS du VPS (OVH) sur lequel est installé Yunohost le diagnostique Email renvoi toujours un problème (voir ci-dessous).
En regardant le code je crois comprendre que l’ensemble des serveurs DNS listés dans /etc/resolv.dnsmasq.conf sont interrogés mais que seule la 1ère réponse est utilisée pour déterminer si le reverse DNS est ok (extrait de la function check_fcrdns):
if len(value) > 0:
rdns_domain = value[0][:-1] if value[0].endswith(".") else value[0])
C’est bien cela ?
Si j’interroge manuellement les serveurs je constate qu’effectivement 4 des 13 serveurs de /etc/resolv.dnsmasq.conf n’ont toujours pas la bonne réponse (seulement 24 heures après) :
for ip in $(cat /etc/resolv.dnsmasq.conf | awk '{print $2}') ; do echo $ip - $(dig @$ip -x 51.178.50.232 +short) ; done
2001:1608:10:25::9249:d69b - edlm.nohost.me.
185.233.100.100 - vps-c89edce3.vps.ovh.net.
2a00:5881:8100:1000::3 - edlm.nohost.me.
194.150.168.168 - edlm.nohost.me.
2001:678:8::3 - edlm.nohost.me.
89.234.141.66 - edlm.nohost.me.
185.233.100.101 - vps-c89edce3.vps.ovh.net.
2a0c:e300::101 - vps-c89edce3.vps.ovh.net.
194.0.5.3 - edlm.nohost.me.
2a0c:e300::100 - vps-c89edce3.vps.ovh.net.
2001:1608:10:25::1c04:b12f - edlm.nohost.me.
2a0c:e300::1337 - edlm.nohost.me.
45.67.81.23 - edlm.nohost.me.
D’où ma question : est-il normal que seule la 1ère réponse (qui doit faire partie des 4 listées ci-dessus j’imagine) soit prise en compte par la fonction check_fcrdns ? Un any (ou la majorié des réponses ?) ne serait-il pas plus logique ?
Je vais attendre encore 24 heures pour voir si au bout de 48 heures l’ensemble des serveurs DNS ont bien pris en compte le reverse.
Share relevant logs or error messages
# yunohost tools regen-conf dnsmasq -f
# yunohost diagnosis run mail --force
Connection to yunohost.org (80.67.164.12) 25 port [tcp/smtp] succeeded!
Connection to yunohost.org (2001:910:1400:115::12) 25 port [tcp/smtp] succeeded!
Error: Found 3 significant issue(s) related to Email!
Warning: To see the issues found, you can go to the Diagnosis section of the webadmin, or run 'yunohost diagnosis show --issues --human-readable' from the command-line.
# yunohost diagnosis show --issues --human-readable
=================================
Email (mail)
=================================
[ERROR] Reverse DNS is not correctly configured for IPv4. Some emails may fail to get delivered or be flagged as spam.
- Current reverse DNS: vps-c89edce3.vps.ovh.net
Expected value: edlm.nohost.me
- You should first try to configure reverse DNS with edlm.nohost.me in your internet router interface or your hosting provider interface. (Some hosting providers may require you to send them a support ticket for this).
- Some providers won't let you configure your reverse DNS (or their feature might be broken…). If you are experiencing issues because of this, consider the following solutions:
- Some ISP provide the alternative of using a mail server relay though it implies that the relay will be able to spy on your email traffic.
- A privacy-friendly alternative is to use a VPN *with a dedicated public IP* to bypass this kind of limits. See https://doc.yunohost.org/vpn_advantage
- Or it's possible to switch to a different provider
[ERROR] Your IP or domain 51.178.50.232 is blocklisted on Spamhaus ZEN
- After identifying why you are listed and fixing it, feel free to ask for your IP or domain to be removed on https://www.spamhaus.org/zen/
[ERROR] Your IP or domain 2001:41d0:404:200::153a is blocklisted on Spamhaus ZEN
- The blocklist reason is: "Listed by CSS, see https://check.spamhaus.org/query/ip/2001:41d0:404:200::153a"
- After identifying why you are listed and fixing it, feel free to ask for your IP or domain to be removed on https://www.spamhaus.org/zen/