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
Don't check MX records for autoconfig #2265
Comments
Good point. I've seen that this is indeed quite unreliable and thus useless. I have this long-time idea of reworking the autoconfig anyway. The problem right now is that we just send the data to the server and wait for its results. Which often takes ages because it has to await lots of timeouts on configurations that don't work. |
Nice to hear that a redo is planned. Microsoft scheme: Additional the RFC 6186 SRV records can be probed. Only a few DNS lookups. [1] https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.txt |
Expected behavior
It should query the autoconfig server for the domain of the email address.
Actual behavior
The MX record of the domain is queries and then autoconfig.MX is queried which is wrong.
The MX record is only for other mail SERVERS. It has absolute no meaning for mail clients. The server for mail clients can be a total different server in a different domain. A mail client should not care at all about the MX record.
The correct address would be autoconfig.domain. See https://wiki.mozilla.org/Thunderbird:Autoconfiguration
The actual implementation might work for some bogous setups. I have here especially Cpanel administrated domians in mind. In most setups Cpanel is setting the MX record to the domain name which is wrong. According to the SMTP RFC the MX record has to be a full qualified hostname and not a domain name.
Mail app
Mail app version: 0.18.1
Mailserver or service: Own setup with postfix and dovecot spread over 4 servers and 3 domains.
Server configuration
Operating system: Ubuntu 16.04
Web server: Apache 2.4
Database: MariaDB
PHP version: 7.2
Nextcloud Version: 17.0.1
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: