How to setup webmail.domain.tld

fiedin

I have search for this topic at the forum, but did not find any complete tutorial on how to do this

So i have been reading this https://docs.mailcow.email/manual-guides/Nginx/u_e-nginx_webmail-site/?h=webmail

IMPORTANT: This guide only applies to non SNI enabled configurations. The certificate path needs to be adjusted if SNI is enabled. Something like ssl_certificate,key /etc/ssl/mail/webmail.example.org/cert.pem,key.pem; will do. But: The certificate should be acquired first and only after the certificate exists a site config should be created. Nginx will fail to start if it cannot find the certificate and key.

Problem

there is no folder /etc/ssl/mail in the dockerized mailcow
there is only folder certs and private

Do i create it? or I am suppose looking at different folder?

The certificate should be acquired first and only after the certificate exists a site config should be created.

If later i was able to get the folder right, how do i get the cert for it?

Thanks and appreciate your help

DocFraggle

You don’t need the above, https://docs.mailcow.email/post_installation/firststeps-ssl/ is enough

Just set

ADDITIONAL_SAN=webmail.*

and restart

docker compose down
docker compose up -d

fiedin

DocFraggle

so we add in mailcow

ADDITIONAL_SERVER_NAMES=webmail.domain.tld

and then restart

docker compose down
docker compose up -d

is that it? do we need the nano data/conf/nginx/webmail.conf section?

what i was trying to do is open sogo with just webmail.domain.tld instead of host.domain.tld/sogo

DocFraggle

fiedin so we add in mailcow

ADDITIONAL_SERVER_NAMES=webmail.domain.tld

No. As I wrote above:

DocFraggle Just set

ADDITIONAL_SAN=webmail.*

and restart

fiedin

DocFraggle
so when we enter webmail.domain.tld > will it redirect to webmail.domain.tld/sogo automatically?

DocFraggle

No, but you didn’t write that in your OP…

If you want to do that, you have to set what I wrote above and edit data/conf/nginx/webmail.conf as described in the docs. As default mailcow uses only one certificate for all SANs and SNI is disabled, so you don’t have to alter the certificate path.

See https://docs.mailcow.email/post_installation/firststeps-ssl/#the-lets-encrypt-subjectaltname-limit-of-100-domains
You only enable that if you have more than 100 SANs

fiedin

DocFraggle
hey thanks a lot for the help. really appreciate it.

quick question:
just an example. if we create the SAN = mail.*
for any additional domain2.tld, can we use the MX = mail.domain2.tld once we get the certificate? instead of the master host.domain.tld

(like cpanel each domain added will have their own MX)

DocFraggle

Yes, I do it that way too.

ADDITIONAL_SAN=mail.*,webmail.*

for example

fiedin

DocFraggle
so if we set
ADDITIONAL_SAN=autoconfig.*,autodiscover.*

then we can use that in our dns record as well right? so it will be good for e.g thunderbird to discover email settings for domain2 domain3 and so on.

but the default mailcow dns will always show the master host.domain1.tld as its recommended settings for all additional domain2. domain3

is this theory right?

DocFraggle

autoconfig and autodiscover is always configured by default, you don’t have to add those.

As an example: you added DNS entries for

autoconfig.domain2.tld
autodiscover.domain2.tld
mail.domain2.tld
webmail.domain2.tld

and configured

ADDITIONAL_SAN=mail.*,webmail.*

then your certificate will contain all 4 SANs from above + the ones from domainX.tld

fiedin

DocFraggle
does that mean i can use autoconfigure.domain2 straight in dns record?

DocFraggle

Yes, see my edited example above

fiedin

DocFraggle
understood. Hope in the future users can use our conversation as reference.

Thank you very much sir