Backup MX servers

dos622 · February 28, 2025, 8:10am

What type of hardware are you using: Virtual machine
What YunoHost version are you running: 12.0.11 (stable)
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

I am using yunohost as primary mail server, but I have two other mail backup servers, so my DNS MX configuration is:
10 domain.xx
20 backup1.server.xx
30 backup2.server.xx
When I check the DNS configuration from Yuno it complain that the DNS configuration for mail is incorrect … seems the it would like to receive only “10 domain.xx” as answer and it do not check that this record is correctly present inside the full list of MX records.

It is possible to fix this simple problem? I know that I can ignore it but … if in the future I will made a mistake with my domain DNS … I will not be notified.

Regards

Share relevant logs or error messages

None

ChriChri · February 28, 2025, 10:47am

You could look into the python about comparing the expected and the found MX record to add something to ignore additional MX:

github.com

YunoHost/yunohost/blob/434eea3793b0d5532d73a41c5a503d55131858cf/src/diagnosers/12-dnsrecords.py#L193


      
          
              if success != "ok":
                  return None
              else:
                  if type_ == "TXT" and isinstance(answers, list):
                      for part in answers:
                          if part.startswith('"v=spf1'):
                              return part
                  return answers[0] if len(answers) == 1 else answers
          
          def current_record_match_expected(self, r):
              if r["value"] is not None and r["current"] is None:
                  return False
              if r["value"] is None and r["current"] is not None:
                  return False
              elif isinstance(r["current"], list):
                  return False
          
              if r["type"] == "TXT":
                  # Split expected/current
                  #  from  "v=DKIM1; k=rsa; p=hugekey;"

In my setup I have the same problem, but just disabled the warning.

system · March 30, 2025, 10:47am

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.