问题描述
我一直在使用SES通过普通的 SendEmail发送电子邮件API 命令，并且DKIM签名运行正常.
I've been using SES to send emails via the normal SendEmail API command, and the DKIM signature has been working fine.
现在我想发送附件，因此我开始使用 SendRawEmail API 和DKIM签名未插入邮件标题中.这将导致GMail通过amazonses.com 显示难看的警告:
Now I want to send an attachment, so I started using SendRawEmail API and the DKIM signture is not being inserted into the mail headers. This causes GMail to display the ugly via amazonses.com warning:
>
我通过使用gmail的Show Original查看邮件源来验证了这一点.
I verified this by looking at the mail source with gmail's Show Original.
我在亚马逊的论坛上发现了同样的问题.但这实际上并不能回答问题.它确实说，一旦启用DKIM，它对SendEmail和SendRawEmail都应该起作用.
I found this same question on Amazon's forum. But it doesn't actually answer the question. It does say that once DKIM is enabled, it should work for both SendEmail and SendRawEmail.
那么AmazonSES为什么不为原始电子邮件API插入DKIM标头?
So why isn't AmazonSES inserting the DKIM header for the raw email API?
(我实际上是在使用ruby SDK，所以它是send_email和send_raw_email，但这没关系.)
(I'm actually using the ruby SDK, so it's send_email and send_raw_email, but it shouldn't matter.)
推荐答案
对我来说，我进行了DKIM设置，并在AWS SES控制台中为我的域启用了该功能.该域级DKIM在SendEmail上运行良好.
For me, I had DKIM setup and enabled in the AWS SES console for my Domains. This domain-level DKIM had worked fine for SendEmail.
但是，我必须为电子邮件地址下的每个发送电子邮件地址启用DKIM，才能在SendRawEmail上启用DKIM.
However, I had to enable DKIM for each sending email address under Email Addresses to enable DKIM on SendRawEmail.
希望这对其他人有帮助！
Hope this helps someone else!
这篇关于未随SendRawEmail插入AmazonSES DKIM签名的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！