8000 how can i use imap.mydomain.com as imap server · Issue #348 · mjl-/mox · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

how can i use imap.mydomain.com as imap server #348

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
RonaldinhoL opened this issue May 8, 2025 · 4 comments
Open

how can i use imap.mydomain.com as imap server #348

RonaldinhoL opened this issue May 8, 2025 · 4 comments

Comments

@RonaldinhoL
Copy link

i dont want use mail.mydomain.com as imap server, when i use imap.mydomain.com in email client, it said connection faild, logs show

"requesting certificate" err="autotls: host not in allowlist: "imap.mydomain.com""

@RonaldinhoL
Copy link
Author

i setup cname recored for imap.mydomain.com -> mail.mydomain.com, still not work, same error

so was smtp.mydomain.com

@mjl-
Copy link
Owner
mjl- commented May 8, 2025

Mox currently assumes you want a single subdomain that's used for imap and smtp. By default, this is mail.<domain>. The setting is called ClientSettingsDomain: https://www.xmox.nl/config/#cfg-domains-conf-Domains-x-ClientSettingsDomain.

Mox will only fetch TLS certs for names it is explicitly configured for. If you configure imap.<domain> as your client settings domain, mox will fetch a TLS cert for that name (it will be in the allowlist). Unfortunately, there is no way to configure a separate "imap client settings domain" and "smtp client settings domain".

Would you could try: Add smtp.<domain> to the webserver config. That puts that name on the TLS allowlist. I think the smtp (submission) server will offer the TLS cert for that domain when requested by a client. The easiest is probably to just make it a redirect to www.<domain>.

The problem with all of the above is that autoconfiguration won't work properly. The autoconfiguration will return the ClientSettingsDomain for both imap and smtp.

I'm curious about your use-case for having separate imap and smtp domains, and not having mail.<domain>. If this is common enough, we may want to split up the ClientSettingsDomain in domains for imap and smtp.

@RonaldinhoL
Copy link
Author

Mox currently assumes you want a single subdomain that's used for imap and smtp. By default, this is mail.<domain>. The setting is called ClientSettingsDomain: https://www.xmox.nl/config/#cfg-domains-conf-Domains-x-ClientSettingsDomain.

Mox will only fetch TLS certs for names it is explicitly configured for. If you configure imap.<domain> as your client settings domain, mox will fetch a TLS cert for that name (it will be in the allowlist). Unfortunately, there is no way to configure a separate "imap client settings domain" and "smtp client settings domain".

Would you could try: Add smtp.<domain> to the webserver config. That puts that name on the TLS allowlist. I think the smtp (submission) server will offer the TLS cert for that domain when requested by a client. The easiest is probably to just make it a redirect to www.<domain>.

The problem with all of the above is that autoconfiguration won't work properly. The autoconfiguration will return the ClientSettingsDomain for both imap and smtp.

I'm curious about your use-case for having separate imap and smtp domains, and not having mail.<domain>. If this is common enough, we may want to split up the ClientSettingsDomain in domains for imap and smtp.

Because all the client tools I've seen default to using imap.domain and smtp.domain. :) Also, this makes us look more professional, like a big organization—lol.

@mjl-
Copy link
Owner
mjl- commented May 15, 2025

Can I suggest changing mail.<domain> to enterprisemail.<domain>? (;
Clients may default to showing some subdomains, but they should be using one of the many autoconfig mechanisms to find the correct host names. There's a good chance they use example hostnames just to prevent users from typing in the smtp hostname in the imap hostname input field.

We could still split up the clientsettingdomains, but it doesn't sound essential to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants
0