[Feature] Configurable dkim selector - per domain/globally

[elerion64]

Describe the feature or change in detail

Hi

Currently default dkim selector in HestiaCP is "mail", which is also used by many other mailers, so it could pose a problem in case when customer wants to use both.

I'm currently suggesting opening a different subdomain for external mail servers, but it would be nice if HestiaCP DKIM selector could be configurable per domain.
Other solution could be to globally change the dkim selector to something unique, for example hestiamail instead od mail, but I'm not sure how safe it would be for existing installations (mail domains).

BR,
E.

Would you like to sponsor this feature to have it implemented?

No

[gresakg]

"mail" is currently used by Brevo, which is a problem, changing default selector to "hestia" would be fine, but making it confugurable would be great

[jaapmarcus]

If you use an external smtp provider you don't need to use it any more.

Also why not ask Bravo to change it?

By default we use the mail.domain.com for smtp / imap / pop3 server and it can't be changed so it makes sense to use mail._domainkey aswell

I don't see a reason to change it on all the servers as hell will break lose.

Feel free to submit a PR that can change it. But personally I am not going to touch it unless somebody is willing to pay for my time I need to spend on it ...

[elerion64]

Brevo can and will change it on request. But why shouldn't we be able to.

Mail in mail._domainkey has absolutely nothing to do with mail domain for smtp/imap/pop3. Mail in mail._domainkey is a selector for dkim. (If I can change it in a manually without issues, it could also be configurable in HestiaCP.)

And its a feature request, so no sweat needed. :-)

[gresakg]

@jaapmarcus I am really sorry if it sounded I demand something. I wrote it in a bit of a hurry. I highly appreciate all the hard work you guys did on Hestia. It's by far the best control panel I have used so far, and I used many (CPanel, Plesk, Virtualmin ...)

I suggested this because dkim selector is just a simple setting in exim config. I can change it myself, but not everyone can. Many people use Brevo for sending email campaings, yet still use their own SMTP for normal communication. So both Brevo and their mail server should be able to DKIM sign the messages. That is why the dkim selector exists.

Exim suggests to set it to the primary domain name like here
https://wiki.meurisse.org/wiki/Exim/DKIM
but it can actually be anything: a static string or something fancy, constructed from other variables and queries to the filesystem.

Thanks again for your time and work!