Problem installing chat relay [certificate for shared IPv4 address space]

Great! I just wanted to ask how to understand Copy Past to new! I’m really thankfull!

We’re getting close. The photo of the edited out version of this comment still includes the domain.

and the .txt in the initial post.:face_with_peeking_eye:

It seems your server also has incorrect MX record. It points to “mail.example.org” rather than “example.org” (itself). As a result other chatmail servers fail to deliver messages to it.

E.g. for mehl.cloud, dig MX mehl.cloud returns:

mehl.cloud.		3600	IN	MX	10 mehl.cloud.

Not

mehl.cloud.		3600	IN	MX	10 mail.mehl.cloud.

This is what I see in my MX-Record panel:

That is what strato says:

(My domain/subdomain has to be in A-Record with its own IP)

This is strange warning, maybe this is for the “STRATO Mailserver” case where they run the website and their own mailserver for you. Is it possible to ignore what the warning says and just point MX record to the domain without “mail.” prefix anyway? If they don’t prevent it, this is the right thing to do, this way incoming mails will be sent directly to your server at port 25.

Well this was no warning but part of the instructions for setting the MX-Record. So if you say it is needed to remove the “mail” prefix I will do so and see what is happening.

By the way. I created a test profile and indeed I could not finish creating a chat with a contact of my relay. Let’s see if it works after removing the prefix.

Now it works! Nice, thank you so much that you tested the mx-record! So much appreciated!

I want to donate. Are there separate channels to donate for Delta chat and donate for the relay or is it the same?

Recurring donation set for DC. Have a nice evening!

1 Like

Normally chatmail relay with a domain example.org gets a TLS certificate for example.org, mta-sts.example.org and www.example.org. If you point to your server with MX record saying mail.example.org and point mail.example.org to example.org with CNAME or directly with IP address, the other relay will connect to your server and expect mail.example.org in TLS certificate and this is why it failed before.

1 Like

My learning curve is quite steep and I love it! I will close this thread as solved if I manage to do so.

Thanks to everyone who was involved and greetings from Austria

broncheolus