My naive understanding is that when a user enables DKIM in Cpanel>Mail>Email Authentication, incoming messages that either:
a) don't have a "DKIM-Signature:" field, or
b) fail the signature comparison test
...will both be rejected outright. Is that true?
Poking around, one other possibility seems to be that failed messages get an "Authentication-Results" header attached to them, which Spam Assassin can then interpret, but there's no explanation of this in the docs.
Can someone explain how this works? I don't want to dive in and start testing on a live server. My concern is that I don't want to implement any kind of spam control that rejects messages outright. I strongly prefer that they be routed to a spam folder.
a) don't have a "DKIM-Signature:" field, or
b) fail the signature comparison test
...will both be rejected outright. Is that true?
Poking around, one other possibility seems to be that failed messages get an "Authentication-Results" header attached to them, which Spam Assassin can then interpret, but there's no explanation of this in the docs.
Can someone explain how this works? I don't want to dive in and start testing on a live server. My concern is that I don't want to implement any kind of spam control that rejects messages outright. I strongly prefer that they be routed to a spam folder.
