-
Notifications
You must be signed in to change notification settings - Fork 97
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
Multiple TLS for multiple domains #111
Comments
You shouldn't need that btw. TLS certs used are for your mail-server FQDN/hostname, not the mail domains managed by the MTA/MDA services. |
Unless you want to keep separate mail server FQDNs, which is what I'd also like to do. I'd like this to added as well. |
Can you elaborate why? You can have When the mail server sends mail outbound, it needs to provide a HELO greeting, this is the FQDN that identifies the mail server, sometimes an rDNS lookup is done at the receiving end to verify your connecting server is legitimately who you claim to be. Then there is other checks like SPF authorizing mail server to send mail on behalf of the sender domain. An IP address is only going to resolve to one of those FQDN though, but as long as you're not concerned about that metric (I don't think most mail servers are that strict on it, so long as the resolved FQDN resolves back to the same IP), some may use it as part of the spam score though. I'm curious what you're trying to gain from multiple domains however, since it doesn't provide any additional privacy IIRC. Services like Postfix also are generally configured to assume one hostname / FQDN aren't they? I suppose you could support multiple via |
Not sure if it's my fault, but clients like Thunderbird have a hard time auto-detecting settings when the mail-server FQDN doesn't match the e-mail domain. Not exactly a good user experience. |
Hi~
Could you support to add multiple .crt (TLS) files for multiple domains?
Thank you so much.
The text was updated successfully, but these errors were encountered: