Ability to separate SPF and DKIM functionality into their own features
Needs Feedback
Maybe we only want users to be able to set SPF records, but not mess with DKIM. We for example use mailchannels, which is not compatible with DKIM at this time, but we still want users to be able to edit their SPF records.
I like this idea 
cPanel, WebHost Manager and WHM are registered trademarks of cPanel, L.L.C. for providing its computer software that facilitates the management and configuration of Internet web servers.
I'm going through some of our historical requests, and I wanted to clarify something here: do you mean that you would like them separated in the cPanel interface? They currently are managed individually in the cPanel and WHM interfaces, but in cPanel they are on a single page. Is that what you're referencing? Or do you mean in the feature manager?
I'm going through some of our historical requests, and I wanted to clarify something here: do you mean that you would like them separated in the cPanel interface? They currently are managed individually in the cPanel and WHM interfaces, but in cPanel they are on a single page. Is that what you're referencing? Or do you mean in the feature manager?
@benny,
While I can't speak for the OP, I'll throw out my $0.02 and say that on the cPanel interface, it WOULD be nice to have the DKIM contained within maybe a tab and SPF contained within it's own tab.
I recently published a request for greatly enhancing the DKIM portion of the Email authentication (awating modration ATM) and if this request gets implemented, it will kind of overwhem the page by having both DKIM and SPF contained on one page.
That said, if the OP was talking about separating them out as "features" within WHM, I can see where this might be beneficial, despite being in agreement of the current route that the feature either enables all email authentication settings or hides them.
"If" the feature was split out into DKIM and SPF on WHM, then two separate pages, thus links from cPanel would allow access specifically to SPF or specifically to DKIM. Obviously if both features were enabled on WHM, the user has access to both interfaces.
It's a thought. I have no input one way or the other on the matter, however since SPF and DKIM do kind of go hand in hand, it makes more sense to have them both enabled as one feature at the WHM level, then simply separated on the cPanel interface as two separate pages to "reduce the clutter", but all still housed within Email Authentication.
If the point of the OP was the WHM features route, I think their goal was to reduce the clutter on the cPanel interface page. If that is the case, containing each on their own respective page would accomplish this. I think.
@benny,
While I can't speak for the OP, I'll throw out my $0.02 and say that on the cPanel interface, it WOULD be nice to have the DKIM contained within maybe a tab and SPF contained within it's own tab.
I recently published a request for greatly enhancing the DKIM portion of the Email authentication (awating modration ATM) and if this request gets implemented, it will kind of overwhem the page by having both DKIM and SPF contained on one page.
That said, if the OP was talking about separating them out as "features" within WHM, I can see where this might be beneficial, despite being in agreement of the current route that the feature either enables all email authentication settings or hides them.
"If" the feature was split out into DKIM and SPF on WHM, then two separate pages, thus links from cPanel would allow access specifically to SPF or specifically to DKIM. Obviously if both features were enabled on WHM, the user has access to both interfaces.
It's a thought. I have no input one way or the other on the matter, however since SPF and DKIM do kind of go hand in hand, it makes more sense to have them both enabled as one feature at the WHM level, then simply separated on the cPanel interface as two separate pages to "reduce the clutter", but all still housed within Email Authentication.
If the point of the OP was the WHM features route, I think their goal was to reduce the clutter on the cPanel interface page. If that is the case, containing each on their own respective page would accomplish this. I think.
Replies have been locked on this page!