Email configuration

Yosh!!

I wanna use yunohost as my email server. I’ve simply paste the preconissed configuration found on my server in > Domain > domo.ovh / DNS

So… like this ( It’s a test VPS ):

#Basic ipv4/ipv6 records
@ 3600 IN A 54.37.68.35
* 3600 IN A 54.37.68.35

#XMPP
_xmpp-client._tcp 3600 IN SRV 0 5 5222 domo.ovh.
_xmpp-server._tcp 3600 IN SRV 0 5 5269 domo.ovh.
muc 3600 IN CNAME @
pubsub 3600 IN CNAME @
vjud 3600 IN CNAME @

#Mail
@ 3600 IN MX 10 domo.ovh.
@ 3600 IN TXT "v=spf1 a mx ip4:54.37.68.35 -all"
mail._domainkey 3600 IN TXT "v=DKIM1; k=rsa; p=something with a lot of letter :slight_smile:  "
_dmarc 3600 IN TXT "v=DMARC1; p=none"

and ovh return me :

Zone is not valid : zone domo.ovh/IN: has 0 SOA records
zone domo.ovh/IN: has no NS records

So this was in my original config :

$TTL 3600
@	IN SOA dns106.ovh.net. tech.ovh.net. (2017113000 86400 3600 3600000 300)
           IN NS     dns106.ovh.net.
           IN NS     ns106.ovh.net.
           IN MX 1   redirect.ovh.net.
           IN A      54.37.68.35
           IN TXT    "1|www.domo.ovh"
www        IN MX 1   redirect.ovh.net.
www        IN A      54.37.68.35
www        IN TXT    "l|fr"
www        IN TXT    "3|welcome"

If I understand I juste have to delete two line from the original config?

like these two?

       IN MX 1   redirect.ovh.net.

www IN MX 1 redirect.ovh.net.

And then add preconised config from yunohost?

I think you need to keep the previous IN SOA and IN NS records.

Ah Yes. It works! New config is paste. Yunohost server appear to be accessible for now.

Thanks Jimbo :slight_smile:

Is that possible to host a second mail server to the same Yunohost server?

I know we can add a second domain but… it will not create conflicts ?

Don’t know if that’s what you’re asking, but YunoHost “multi-domain-ness” also applies to mail, yes :wink:

(Technically speaking, it’s not “a second mail server on the same YunoHost instance”. You have “one mail server (postfix)” serving mail for multiple domains. :stuck_out_tongue: )

Off course :slight_smile:

My mail client (Mail on OSX) return me that let’s encrypt certificate is invalid while it is valid for the domain name (https)

Sending and receiving works.

Do I have to generate a new certificate?

Hm, is that for the same domain ?

I think I have the same behavior with Thunderbird, telling me that Let’s Encrypt certificate are not trusted. I think it might be due to Let’s Encrypt not being recognized by the default root CA’s in Thunderbird (whereas the default root CA’s in Firefox allow to recognize Lets Encrypt…)

In this case this is on my yunohost VPS with one domain : "domo.ovh"
https is ok on my browser.