As you can see in the image below, thunderbird automatically tries to use the first part of my mail as my username.
Now that is wrong, it needs to be the complete e-mail.
How can I configure mailcow to send the correct information?
Also is it possible to configure what mailcow sends as a hostname?
I would like to use “mail.example.com” instead of “smtp/imap/*.example.com”

Thank you in advance

  • post-kuh likes this.
  • I stumbled at the same problem. For me, the autoconfiguration did not work in Thunderbird, but only for email domains other than the mailserver domain. So if my mailserver domain is example.org and I have another domain second.org registered to send emails over that server, the autoconfiguration would work for mail@example.org, but not for mail@second.org.

    In order to solve your problem, you need to know how Thunderbird does the autoconfiguration. When you add a new mailbox to Thunderbird, it tries to get the server configuration via HTTPS from a webserver listening on the domain of the mailbox you want to add to Thunderbird. If you want to add mail@second.org, Thunderbird tries to get https://second.org/.well-known/autoconfig/mail/config-v1.1.xml. This file contains the parameters for protocols, ports and the mailserver Thunderbird should use. You can see all web requests from Thunderbird in the error console of it.

    If you are running the nginx-container shipped with mailcow-dockerized as webserver accessible from the internet, it should do that automatically for all registered email domains. If you are not running it or the port 443 is not allowed in your firewall, the autoconfiguration won’t work.

    If you are running an additional reverse proxy, you have to set it up according to https://docs.mailcow.email/post_installation/firststeps-rp/#nginx (this is for nginx). However, if you have multiple domains registered on your mailserver, your nginx reverse proxy e. g. needs to serve a single SSL certificate for all domains in order to prevent Thunderbird from giving you an error message regarding SSL certificate domain mismatch trying to get the autoconfiguration. You could also serve the configuration file manually and statically. Please see my own thread https://community.mailcow.email/d/2246-multiple-domains-without-one-tls-certificate-containing-all-domain-names-as-san as this could help you or others having similar problems.

    I haven’t looked it up yet, where you can directly manually edit the autoconfiguration settings in mailcow, but I hope my answer should point you in the right direction.

24 days later

I stumbled at the same problem. For me, the autoconfiguration did not work in Thunderbird, but only for email domains other than the mailserver domain. So if my mailserver domain is example.org and I have another domain second.org registered to send emails over that server, the autoconfiguration would work for mail@example.org, but not for mail@second.org.

In order to solve your problem, you need to know how Thunderbird does the autoconfiguration. When you add a new mailbox to Thunderbird, it tries to get the server configuration via HTTPS from a webserver listening on the domain of the mailbox you want to add to Thunderbird. If you want to add mail@second.org, Thunderbird tries to get https://second.org/.well-known/autoconfig/mail/config-v1.1.xml

. This file contains the parameters for protocols, ports and the mailserver Thunderbird should use. You can see all web requests from Thunderbird in the error console of it.

If you are running the nginx-container shipped with mailcow-dockerized as webserver accessible from the internet, it should do that automatically for all registered email domains. If you are not running it or the port 443 is not allowed in your firewall, the autoconfiguration won’t work.

If you are running an additional reverse proxy, you have to set it up according to https://docs.mailcow.email/post_installation/firststeps-rp/#nginx

(this is for nginx). However, if you have multiple domains registered on your mailserver, your nginx reverse proxy e. g. needs to serve a single SSL certificate for all domains in order to prevent Thunderbird from giving you an error message regarding SSL certificate domain mismatch trying to get the autoconfiguration. You could also serve the configuration file manually and statically. Please see my own thread mailcow community Icon Multiple domains without one TLS certificate containing all domain names as SAN
mailcow community Icon mailcow communityDiscussion
Multiple domains without one TLS certificate containing all domain names as SAN
Author avatar image post-kuh
I need advice configuring my mailcow instance with another mail domain, which is not the mailserver domain. I currently have a setup that is working fine, sending and receiving mails on all domains with no problems so far. The problem comes when trying to add a mailbox in Mozilla Thunderbird. The
mailcow community
9 2
as this could help you or others having similar problems.

I haven’t looked it up yet, where you can directly manually edit the autoconfiguration settings in mailcow, but I hope my answer should point you in the right direction.

Have something to say?

Join the community by quickly registering to participate in this discussion. We'd like to see you joining our great moo-community!

OH MY GOD THANK YOU!

I just tested it, it only works If you use the same domain that is used in the docker mailcow config.

I love you.

Edit:
In addition for other people that stumple across this:

  1. I indeed do not have the other domains in the mailcow.conf file under additional_server_names I did not change anything there because I use a reverse proxy.
  2. If I open the link: https://mail.*./.well-known/autoconfig/mail/config-v1.1.xml it is the same no matter which domain I enter as I reverse proxy it.

It took me days to find this out and I was pretty frustrated about it. So while doing research on this, I followed every thread regarding this topic I stumbled upon, in order to answer it once I found out. Glad it helped you! 😁

Done, definitely the best answer around here!!!!!

2 months later

Hey guys,
i’ve got the same problem, everything else is working fine so far! I’am using the Nginx Proxy Manager (nginxproxymanager.com Icon Nginx Proxy Manager

). I have only one domain, and my autoconfig “https://mail.DOMAIN.COM./.well-known/autoconfig/mail/config-v1.1.xml” is reachable and looks fine to me. As i understand, i need to change some settings on the reverse proxy manager, to solve the issue. Can you please provide more information, what i exactly need to do? I’m sorry, i’m still quite new in the mailcow/reverse proxy world.
Thank you very much in advance!

With kind regards,
Burny

No one is typing