Passing those tests doesnt ensure messages wont be treated as SPAM. End users or orgs can block senders or treat them as spam depending on policy
What do the anti spam headers show?
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
We are sending emails to users using Amazon SES. Sometimes they are going into the Inbox but for Outlook, they land into the Junk Folder and sometimes the email is not received by the customer.
The emails are DKIM signed and SPF passed.
Received: from DU2P193MB2242.EURP193.PROD.OUTLOOK.COM (2603:10a6:10:2f6::12)
by AM0P193MB0514.EURP193.PROD.OUTLOOK.COM with HTTPS; Thu, 23 Dec 2021
14:53:21 +0000
Received: from SV0P279CA0067.NORP279.PROD.OUTLOOK.COM (2603:10a6:f10:14::18)
by DU2P193MB2242.EURP193.PROD.OUTLOOK.COM (2603:10a6:10:2f6::12) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4823.19; Thu, 23 Dec
2021 14:53:20 +0000
Received: from HE1EUR02FT041.eop-EUR02.prod.protection.outlook.com
(2603:10a6:f10:14:cafe::65) by SV0P279CA0067.outlook.office365.com
(2603:10a6:f10:14::18) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4823.19 via Frontend
Transport; Thu, 23 Dec 2021 14:53:20 +0000
Authentication-Results: spf=pass (sender IP is xx.xxx.x.xx)
smtp.mailfrom=eu-west-1.amazonses.com; dkim=pass (signature was verified)
header.d=;dmarc=pass action=none header.from=;compauth=pass
reason=100
Received-SPF: Pass (protection.outlook.com: domain of eu-west-1.amazonses.com
designates xx.xxx.x.xx as permitted sender) receiver=protection.outlook.com;
client-ip=xx.xxx.x.xx; helo=a7-29.smtp-out.eu-west-1.amazonses.com;
Received: from a7-29.smtp-out.eu-west-1.amazonses.com (xx.xxx.x.xx) by
HE1EUR02FT041.mail.protection.outlook.com (xx.xxx.xx.xxx) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.4823.19 via Frontend Transport; Thu, 23 Dec 2021 14:53:20 +0000
X-IncomingTopHeaderMarker:
OriginalChecksum:924A72E6C9C9EC17A1B70AF9238D19AD8257E7493432AEEA02DA9C99A61F4A7B;UpperCasedChecksum:47EC3D4F45A144B46C287ACA784126D66928B84CF1AD0278527DBCA3EDDCE2E5;SizeAsReceived:1443;Count:12
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=vpwkmuu75chdrwhepcz4dxtx4l375wpg; ; t=1640271199;
h=From:Reply-To:To:Message-ID:Subject:MIME-Version:Content-Type:Date;
bh=tFS0wtPxrpjJJmmRPqXirll5JuBKtQnfXOY7qoyOZNE=;
b=CiQl3bM2jjNPfoiBIyBxkNZ2cKuzfzrSCbq0Z7kILCZuGNka1wWcrxDtV7xWgYZE
UAcOlZLHRoZkv6dYQ19lKGv2iSYcF72ZvAKu89gV8ZDNePAWhAfZ85R5YFklGwlb3a2
ChvZHA5VoZL8W+lCSczxxm5FJipuxxLBgPoNE2Jk=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
s=uku4taia5b5tsbglxyj6zym32efj7xqv; d=amazonses.com; t=1640271199;
h=From:Reply-To:To:Message-ID:Subject:MIME-Version:Content-Type:Date:Feedback-ID;
bh=tFS0wtPxrpjJJmmRPqXirll5JuBKtQnfXOY7qoyOZNE=;
b=eAvElYSKfdB2YZjrCCJPzHFDqIBgPl2krHYoSqaKs2NKsF1CABOl5BPIqdYQ50AI
VjMLeq+xK1Sb1hhX3isD5CRdiMLfx/B1tej1rKRt9gCvwxp2vgSX/bW9evmxhGkPjpk
e55kya70mxY9YBCAkrzp6dm9VeOTKQcAT7Jbi08w=
Passing those tests doesnt ensure messages wont be treated as SPAM. End users or orgs can block senders or treat them as spam depending on policy
What do the anti spam headers show?
Some customers did not receive any mail from us at all. So we added the domain to the safe senders but that didn't fix it.
For a few customers we have added the email address as a contact in Outlook and that seems to work. The customers that didn't receive any mail now receive mail and the customers who already received mail it is not in the spam.
Now we will investigate why we need to add the email address to the contacts to get the mail working.