I have OpenDKIM properly set up to sign emails from my domain such that when sent through Amazon SES, Yahoo Mail shows dkim=pass
. Given I got the infrastructure working, is there any benefit to having Amazon's DKIM signature instead of my own, say for spam filtering purposes?
1 Answer
If Amazon does it for free (Well, not free, but included with their per-message billing), Why should you spend resources in signing your emails?. Think of it as a matter of costs:
SES DKIM signed email = 1 x SES Message
Self calculated DKIM signed email = 1 x SES message + DKIM signature CPU
It may sound insignificant, but think of tens of thousands of emails per month. That's a lot of CPU spent in something that SES is already doing by itself.
If CPU spends are not a problem, double signing your emails should not be an issue at all.
example.com
and then Amazon signs it also forexample.com
, but because I added CNAMES for Amazon's DKIM entries, they look like they are mine. So the question is, is the Amazon key pair that signs the message also signed and recognized by spam systems.