amazon SES + Web API

not work...

Code: 
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
    s=gdwg2y3kokkkj5a55z2ilkup5wp5hhxx; d=amazonses.com; t=1465821723;
    h=Message-ID:Date:Subject:From:Reply-To:To:MIME-Version:Content-Type:List-Unsubscribe:List-Id:Feedback-ID:Feedback-ID:Feedback-ID;
    bh=fPjPHuAUkwEYKpJzj2+i9qEpWTa8wfHu5TbJ8xY+mTg=;
    b=am5MJgulRqhfu19Mue81JWBxzdt6TJsM0atBWM9UFoZlUXQvhxp6SA8KW0lfe/91
    aDcevd7CB9yPBq6D98KDUK1LDh2+QTo0bLJGBgVikCxdbAyV4XkF9FgAHDz/KcWBZPp
    LW4SVifI5Wult4jAwaliMUQpQx9AHTEPkxBgOCBs=

As an alternative which is better? Sendgrid or Sparkpost ?
 
Adding header the test message does not work..

Code: 
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
    s=gdwg2y3kokkkj5a55z2ilkup5wp5hhxx; d=amazonses.com; t=1465825122;
    h=Message-ID:Date:Subject:From:Reply-To:To:MIME-Version:Content-Type:Feedback-ID:Feedback-ID;
    bh=AlaNKL6ifBn+RCeUfXndVXA8+peOqxNsCVyxy1OGBmc=;
    b=lMGSMNpdUhG/SERdx4qpGTS+SpHy9IYFllJmKuy7PVKs+wy/tJSe7KfM8XPDwHev
    d21ctLY+glc5/zSo/hmGevQ3u1cGqAOI5lt0n+c8/OISOuEUjXqPKEasvIEz3fOc52H
    tfJRi+u9unvwNSQA1tXvPKrSG34jprG8QjWl1Lm8=


Without the header works in the test, but to send the campaign the dkim is invalid.
 
@daemon ok, so this is our finding -

While doing 'template test',

1. DKIM passes without "Feedback-ID" header
2. DKIM fails with "Feedback-ID" header

Correct ?

If that's the case, obviously SES is not handling "Feedback-ID" well on their side, that's possibly conflicting with the same header added by them. You can post this on their forum and try if that can be addressed.

Meanwhile, try dedicated IP from Sparkpost. That seems to be less pricey than SendGrid.
 
daemon said:
Without looking at the prices . What is the best ? Sparkpost ?
Click to expand...
Seriously I have never used Sparkpost. But I could see people giving good feedback about them in the forum including @twisted1919 .

But I have used SendGrid in the past (dedicated IP plan) and they turned out to be really good to me - in terms of speed of delivery, inbox hit and analytics. Worked well for me especially for hotmail and gmail.
 
@VVT / @daemon - i personally used sparkpost a lot and i still am at work. But for mailwizz related things, including this forum, i am using mailgun for a while now. Sparkpost has some weird policy that they block you without any real reason, saying their spam filter decided so, which is terrible wrong having in mind they blocked even forum replies from here.
 
mail test campaing works !

Code: 
Authentication-Results: mx.google.com;
       dkim=pass header.i=@mydomain;
       dkim=pass header.i=@amazonses.com;
       spf=pass (google.com: domain of 010001567565ccb6-6f53f9d8-5a95-4d9f-922f-5bce09ef560c-000000@amazonses.com designates 54.240.8.82 as permitted sender) smtp.mailfrom=010001567565ccb6-6f53f9d8-5a95-4d9f-922f-5bce09ef560c-000000@amazonses.com
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
    s=6kzodaeozq5njf23tfu7eedwaospvk4t; d=mydomain;
    t=1470848421;
    h=Message-ID:Date:Subject:From:Reply-To:To:MIME-Version:Content-Type;
    bh=NRUjqC4gCtMf17cA0anAmjzHGYkWVpuyHS1KIg2qFJ4=;
    b=iZqEjPLuV5y3lVJnjddqMbLDLy3Znx41JElQLhwvcs7Ycb2t4sGe9rWX40KE6U14
    SMPHOqEOlbRgffOh5y+CgvC4Vm/PDnDNDJUFVRJt0qD6+PqVrmcsUE7RDGv108x9F6Q
    bWZkNoXvk73GlG46Fd2p8yATls/+fMtSZI4px+0U=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
    s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1470848421;
    h=Message-ID:Date:Subject:From:Reply-To:To:MIME-Version:Content-Type:Feedback-ID;
    bh=NRUjqC4gCtMf17cA0anAmjzHGYkWVpuyHS1KIg2qFJ4=;
    b=vLBNMyV6wST4holPyG3aJPmEBQr7ycymSg4WaWiAUE2CRMMi902Imr/HJNHqEFF0
    YDiFPt8oTp0qN6h3ycqcv80yz+JNUpTin1C/HdszIQ53w8n6XhRPu4p9xYSk+n5b8gW
    frpY6lySkd7NJdfgJymJCUp+YERH/8uw7L7FB0ac=
Message-ID: <010001567565ccb6-6f53f9d8-5a95-4d9f-922f-5bce09ef560c-000000@email.amazonses.com>

But when sending the campaign to all users looks like this:

Code: 
       dkim=pass header.i=@mydomain;
       dkim=fail header.i=@amazonses.com;
       spf=pass (google.com: domain of 010001567560f168-4ad2288f-7223-4d1e-b650-e1c3b8cfee53-000000@amazonses.com designates 54.240.8.98 as permitted sender) smtp.mailfrom=010001567560f168-4ad2288f-7223-4d1e-b650-e1c3b8cfee53-000000@amazonses.com
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
    s=6kzodaeozq5njf23tfu7eedwaospvk4t; d=mydomain;
    t=1470848102;
    h=Message-ID:Date:Subject:From:Reply-To:To:MIME-Version:Content-Type:List-Unsubscribe:List-Id;
    bh=lYG1l6E+tpfX8sa0jpiBlyo6mVKQ1hs4C6FCtPvNv1Q=;
    b=mYePZT2Z8qCE/GHcYd8o2l2Pv1R9ojUwfdmLsorrDWN7Q63Z9zQIzmoighGer+Y8
    8kK+uS9V/+u5cQk0+kKDykkhleknEoyao6I7JrPVO232WGDQadNWpxcKsEOZn/+g0YA
    ukbnLVYVpgovsg5Lhm5qwcvzT/qqMBInEa0tcyNA=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
    s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1470848102;
    h=Message-ID:Date:Subject:From:Reply-To:To:MIME-Version:Content-Type:List-Unsubscribe:List-Id:Feedback-ID:Feedback-ID;
    bh=lYG1l6E+tpfX8sa0jpiBlyo6mVKQ1hs4C6FCtPvNv1Q=;
    b=0TnXazfwbRoiiIJ7WSLHZ+q4p+s40E19FPgsDnAEQ2Ny7srRShmLexNRe7g10uLJ
    kcxbZ9Y+PNIF9qwOHG5rM5xvGpZp0SpEnvhZIAOPfcr8VTT0msXC8hoZFgs4pGGh6bv
    05brEUP+Qzl0H9XULt0dMRmQxNk8AUcjPHIAQN7s=
Message-ID: <010001567560f168-4ad2288f-7223-4d1e-b650-e1c3b8cfee53-000000@email.amazonses.com>


In short when you create the campaign e-mail test works, but when you send to all users error happens.
 
In both your signatures, the selector s=6kzodaeozq5njf23tfu7eedwaospvk4t, respectively s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw.
Mailwizz selector is s=mailer so i have no idea how that ends up there.
 
I've tried disabling the DKIM on amazon panel.
But always when you send up the header of the amazon (DKIM).

The funny thing is that this happens only when sending the campaign .. When I'm in TEST (Sending a test) goes right.
So I think it's something in mailwizz.
 
You must log in or register to reply here.
Back
Top