Unable to receive email on additional domain

Discuss Advanced use case
, ,
1
  • VPS Online
  • SSH/Webadmin access
  • No special circumstances/configs
  • YunoHost 12.1.17.1 (stable)

I have yunohost working with domain A.tld. And have now added B.tld. The problem is that email is not working as expected. I can send email from B.tld but am not able to receive any email on B.tld from outside the server.

  • all the relevant switches in the webadmin. are set correctly
  • the dns settings are according to the yunohost suggestions
  • there is an app installed on B.tld that all users have access to
  • tail -f /var/log/mail.log does not show anything when sending an email to B.tld from outside the server
  • mail.log gives a warning that ***domain*** postfix/postfix-script[1811]: warning: /var/spool/postfix/etc/ssl/certs/GTS_Root_R1.pem and /etc/ssl/certs/GTS_Root_R1.pem differ There are a total of 4 of these warnings (R1-R4)

I don’t know if the last point (about the warnings) has anything to do with this but thought to mention it anyway.

Is there anything I can do to solve this and start receiving mail on B.tld?
Or is it just not possible to use email with an additional tld ?

Any help/answers/pointers would be appreciated.

2

The diagnosis can help us understand.
What’s the output of yunohost tools regen-conf --dry-run --with-diff ?

3

Could be a problem with the MX records for B.tld?

4

When looking at Domains/DNS in the Admin Web interface the recommended config is:

; Mail
@ 3600 IN MX 10 b.tld.
@ 3600 IN TXT "v=spf1 a mx -all"
mail._domainkey 3600 IN TXT "v=DKIM1; h=sha256; k=rsa; p=***key***"
_dmarc 3600 IN TXT "v=DMARC1; p=none"

This is the same as the DNS config at my domain provider. (I double checked with the help of an editor diff/comparison)

Basic ipv4/ipv6 records are pointing to the IP addresses of the server. (Same as for A.tld.)

5

See the below file for the output.

regen-conf_diff.pdf (153.5 KB)

(B.tld is not on it, I didn’t change anything to that domain.)

6

You need to check the resource records with dig or nslookup.

This is also a good starting point.:

This means that your server does not know anything about the MX records of the B.tld domain.

7

We’ll begin with yunohost tools regen-conf --force
Then rerun the diagnosis to check if everything is OK.
Go to the webadmin >domains >your subdomain and check the recommended dns configuration. If your registrar supports autodns, that will help you a lot

9

I did the yunohost tools regen-conf --force and run the diagnosis → everything is OK.

Checking with the DNS provider and mxtoolbox.com gives correct results for MX records and also for A and AAAA records. I assume they are correct because they are the same for both domains and one domain is working.

The dig MX and dig ANY results are here : dig_A_B.pdf (67.6 KB)

10

Are they correct here too?

dig @one.one.one.one B.tld MX

11

Yes, I think so. dig1111.pdf (59.3 KB)

12

Then the sending server should have it in the log file

13

I searched for the log files with my email provider. But couldn’t find them.
However they have the possibility to review an email’s delivery route. Tracing the route shows that the server redirects to local host.

This provider is hosting email for all my other domains and used to also host for B.tld. I had already asked them to stop hosting B.tld But apparently not all settings have been reset properly (something they should have done).

Sending an email to B.tld from a different server not hosted by my former provider results in receiving the email with yunohost !

Since I don’t have other email providers I was not able to test that earlier. And I had already contacted that provider a second time to verify that everything was reset properly at their end. (They told me I was good to go.)

I am very sorry to have bothered you for something that was not due to yunohost. But you have helped me greatly, by the process of elimination, to find the cause of error.

You have made me very happy, thank you so much !

1 Like