amazon SES + Web API


I'm editing a campaign and send a test DKIM works:
       spf=pass ( domain of designates as permitted sender)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
    s=gdwg2y3kokkkj5a55z2ilkup5wp5hhxx;; t=1464969951;
Message-ID: <>
Date: Fri, 3 Jun 2016 16:05:51 +0000
Subject: Quer Ganhar R$ 300,00 em Compras? Participe
From: Topic <>
Reply-To: Mydomain <>
MIME-Version: 1.0
Content-Type: multipart/alternative;
X-Mw-Mailer: SwiftMailer - @SWIFT_VERSION_NUMBER@
X-SES-Outgoing: 2016.06.03-

But when I send the campaign to all the list does not work:
       spf=pass ( domain of designates as permitted sender)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
    s=gdwg2y3kokkkj5a55z2ilkup5wp5hhxx;; t=1464969602;
Message-ID: <>
Last edited:
It must be due to the inclusion of "Feedback-ID" header twice on the signature when you sent the campaign. There's already one such header present in the test email - meaning, SES adds this by default. So, it should be the responsibility of SES to strip off or handle the second header (by MW ) well to avoid a conflict. But if they don't help, you can try removing the the header from MW side, but that may need editing something by hand like this post says.
Not a bug mailwizz ? The first email functions . If I change the code affect another client ...
I'm not exactly sure about the role of "Feedback-ID" in MW. So editing this without proper understanding can affect other non-ses deliveries as you said. IMO, SES is supposed to handle this header properly, but it looks it isn't.
What do you recommend ?

Migrate to sendgrid ? Amazon does not support , it is very bad.
Let's not take any hard steps now :) . Will be good to check with someone who uses SES.

@Vpul Shah / @Ankit - You guys are using SES right ? Any hint on the above issue ?

As for the recommendation, people recommend Sparkpost now a days. You can try out their free plan to see if that works out for you. Sendgrid is of course good, but is on bit expensive side.
With Amazon SES I can get in your inbox ( not enter the SPAM) . With sendgri and spark is entering SPAM :(
@daemon : I agree, SES hit inbox while other sometimes do spam.

Use Amazon API with MW and check with test campaign.

Also include mail-tester email id to see whats wrong in that.
Setup proper DKIM, SPF and DMARC records on your sending domain name and then add it to google postmasters too. These will help to get great inbox rate.
Sparkpost is comparatively better than Amazon SES.

@VVT yes, even we had this header strip issue in old MW versions.
@Ankit so your DKIM signing works fine at AWS, right ? If so, is that the domain or custom domain ?

@daemon as a last option, you could try enabling DKIM signing for your own/custom domain at AWS to see if that works.
( Ran out of ideas :( ) Hope someone might help, think you're not the only one using SES and there should be a work around. But for the time being, you can try some other relay to keep the business going. :)
I'm currently using Sparkpost SPF+DKIM+DMARC.

The problem is that is entering SPAM. With Amazon entered the inbox.
Do this.

1. Go to your AWS SES Delivery Server Settings.
2. Add a custom header like below -
Feedback-ID : Somevalue
3. Click Save
4. Now send a "template" test email through that delivery server.
5. Post the header details here.

Now, if DKIM fails, it's SES that's creating problem. If it doesn't, will look further in to it.
Yep. 'Add Extra Header'. Put any value. Just for testing.

Feedback-ID = test
Feedback-ID = example or anything.