DKIM support for custom selector

Estel Technologies shared this idea 3 years ago
Open Discussion

Hi,

As per the basic Exim configurations provided by cPanel,

only DKIM with the default selector will be recognized, however lots of domains are using a custom selector.

In order to accept the custom selector, we would need

to modify the Exim configurations and we wish to open a feature request.

Please do the needful to help us on priority.

Thanks and regards

Charan

Comments (7)

photo
1

Would love this, as Dkim requires a different selector than "default" for some sites.

I had problems with godaddy always telling me to "tell the selector" when using default.

I made a exim4 configuration tweak to use the domain name instead of default and it works.

photo
1

I think I am using your tweak "dkim_selector = ${dkim_domain} " have you found a way to make it permanent so when exim gets updated it doesn't change it back to "default"?

photo
photo
1

I would very much like to see this happen as I run an Autoresponder Service and Yahoo wants to know the selector being used and they do not accept "default" as the selector hense mail doesn't go through.

photo
1

I agree. This becomes a real issue rather than a minor annoyance in the event of trying to send mail for the same domain from two different cpanel servers.

If one has root access, then they can edit the keys to match, but this is not "according to Hoyle" and while it would be technically feasible as a work-around, it does present some issues.

And if the case of operating in a shared hosting environment, this would not be possible at all, since to change the default selector would change it for everyone on the server.

photo
1

Would like to add my voice to this. I use G Suite for Business and would like to use its DKIM key for to cover any outgoing messages from my web site running on the cPanel server. Without being able to tell cPanel that I'm already using a DKIM selector and key, this makes it rather difficult to ensure that everything I send is compliant.

photo
2

Maybe I misunderstand your comment, because as I understand what you are wanting to do, you wouldn't need this feature to accomplish that. You set the public key for DKIM in your DNS settings, using the one provided by Google. All email sent through Google's servers would validate using the Google DKIM settings. You would only need the cpanel DKIM if you send some email from your server (i.e., scripts that send mail through sendmail). For that, you would add the cpanel DKIM which uses a different selector. You wouldn't be able to use the Google DKIM to validate mail sent from your own server, no matter what features cpanel might add, because you will not have access to the Google private key.

photo
1

Gah - yes, you're right Kevin. I had no idea why or how I'd forget about the private key in all of this.

photo