Cisco Secure Email setup
Cisco Secure Email: DKIM signature is missing or fails
The DNS key, signing profile, or outbound mail policy may not match the domain and selector in the message.
The visible symptom is:
Authentication-Results: dkim=fail header.d=example.com
Fix DKIM signing
- In AsyncOS, open the DKIM signing profile used for outbound mail.
- Confirm its signing domain and selector match the intended From domain.
- Copy the public key from that profile to selector._domainkey.example.com in public DNS.
- Make sure the outbound mail flow policy uses the signing profile.
- Check the public key by domain and selector.
- Send a new message and confirm that it contains a DKIM-Signature and returns dkim=pass.
Common causes
The key is published under the wrong selector, DNS contains an old key, the profile is not attached to the outbound policy, or another system changes signed content after Cisco signs it.
What the check proves
MailFixIt can validate the public selector and key. Only a new message can prove that Cisco used the matching private key and that the signature survived delivery.
Frequently asked questions
Why is Cisco Secure Email not adding DKIM?
A signing profile is not enough by itself. It must be enabled for the outbound mail flow policy that handles the message.
Does a correct DNS record prove the gateway is using it?
No. The gateway must also enable the matching route, signing profile, or policy. Confirm the result in a new message header.
Related email diagnostics
Primary sources: Cisco Secure Email Gateway AsyncOS 16.0 user guide.