Amazon automated bounce email handling no user detected

I've set up Amazon SES/SNS and performed a test by setting an email of a user to an invalid one as such:
1590133119492.png

After sending a test mail through XF Admin CP; I do receive the bounced email from Amazon to my bounce@mydomain.com but XenForo automatic bounce handler doesn't seem to be able to find which user the bounced mail belongs to? This is what it looks like:
1590133039210.png

Upon clicking 'View', the following is shown:
Code:
Return-Path: <010201723079c3-ffe2fcd1-0779-413b-a00e-0e32cbf96-000000@eu-west-1.amazonses.com>
Delivered-To: bounce@mydomain.com
Received: from host.xxx.io ([xxx.xxx.xxx.xx])
    by gcp-europe-west4-a-mail.xxx.io with LMTP
    id dHHGBJx+x149CwAA/189bQ
    (envelope-from <010201724079c3-ffe2fcd1-0779-413b-a00e-023b2cbf96-000000@eu-west-1.amazonses.com>)
    for <bounce@mydomain.com>; Fri, 22 May 2020 07:26:20 +0000
Received: from nl-srv-mailscanner3.xxxx.io (unknown [IPv6:22:470:8:6::c])
    by nl-srv-smtpin1.xxxx.io ([Mail System]) with SMTP id 00DDF367BCF
    for <bounce@mydomain.com>; Fri, 22 May 2020 07:26:19 +0000 (UTC)
X-Fuglu-Spamstatus: NO
X-Fuglu-Suspect: 2098752274945a19c8112793a2ee196
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
    nl-srv-mailscanner3.xxxxx.io
X-Spam-Level:
X-Spam-Status: No, score=0.5 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED,
    HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,
    SPF_HELO_NONE,SPF_PASS,TVD_RCVD_SPACE_BRACKET,URIBL_BLOCKED
    autolearn=disabled version=3.4.0
X-Fuglu-Incomingport: 10025
Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=5.20.2.119; helo=a2-149.smtp-out.eu-west-1.amazonses.com; envelope-from=0101723b79c3-ffe2d1-0779-413b-ae-023be32cbf96-000000@eu-west-1.amazonses.com; receiver=bounce@mydomain.com
Authentication-Results: nl-srv-smtpin2.xxxx.io;
    dkim=pass (1024-bit key) header.d=sns.amazonaws.com header.i=@sns.amazonaws.com header.b="Y4OLv0L";
    dkim=pass (1024-bit key) header.d=amazonses.com header.i=@amazonses.com header.b="mwEIlsO"
Received: from a2-119.smtp-out.eu-west-1.amazonses.com (a2-119.smtp-out.eu-west-1.amazonses.com [5.20.2.119])
    by nl-srv-smtpin2.xxxx.io ([Mail System]) with ESMTPS id 8C922A56A
    for <bounce@mydomain.com>; Fri, 22 May 2020 07:26:19 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
    s=7is6oizc6t7vbfvwu5kg6gzh27hoe; d=sns.amazonaws.com;
    t=1590131980;
    h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding;
    bh=tRueX1H6qgoF2v47B6eW52CZBYTt4zIFqIgBGnzjRg=;
    b=Y4OZLv0LtbHwioeD7wdPyfpO8FkoJ9rEyeRlcdMXGhxPfob8A5xeqdJ2UNn2qLm
    2rrvt58HDppDiWFxi8TuKom6jG5wl6JS17WNw7/Ul7A347NtpBYp61vlxmBPV3w/t
    CAODShnRHIxyyMoezup/qyJeNS3jIwE+DZmge1U=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
    s=shh3fegw5fppqsuzpvschd53n6ihuv; d=amazonses.com; t=1590131980;
    h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID;
    bh=tRueX1H6qgoF2v4B6eW52kCZYTt4zIFqIgBGnzjRg=;
    b=mwEIRlsOkN5Zjp1yrYU5giI11+iszl39GcgU6nKwuSvwchU+xdjLlecINikC82
    vymswd6NPr1rfyOZ+Ga1Iw1twxNPWtqxyCJ5qaJ1eDEZ6H2gem8D7q+qH0iJDF9of
    4wOZUKliUy9hgbeQLpwOeGLit6xGo7NM9lFNY=
Date: Fri, 22 May 2020 07:19:40 +0000
From: AWS Notifications <no-reply@sns.amazonaws.com>
To: bounce@mydomain.com
Message-ID: <010201723b4079c-ffe2fc1-0779-43b-a00e-23e32cbf96-00000@eu-west-1.amazonses.com>
Subject: AWS Notification Message
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
x-amz-sns-message-id: f72dbed-c34e-54ccb940-e9cbc0253ea
x-amz-sns-subscription-arn: arn:aws:sns:eu-central-1:59703271:Wave_Bounce:c395e578-059c-4388088-399cb2d91b
X-SES-Outgoing: 2020.05.22-54.240.2.119
Feedback-ID: 1.eu-west-1.7KHVHObBFqnkHZu/Gxo5uNNbgCZmsrTqzEgI=:AmazonSES

{"notificationType":"Bounce","bounce":{"bounceType":"Permanent","bounceSubType":"OnAccountSuppressionList","bouncedRecipients":[{"emailAddress":"1d442eab44a9704a91f7095b5cf58da133dd813@yahoo.com","action":"failed","status":"5.1.1","diagnosticCode":"Amazon SES did not send the message to this address because it is on the suppression list for your account. For more information about removing addresses from the suppression list, see the Amazon SES Developer Guide at https://docs.aws.amazon.com/ses/latest/DeveloperGuide/sending-email-suppression-list.html"}],"timestamp":"2020-05-22T07:19:40.666Z","feedbackId":"010701723b407934-cbb918-e02d-4a4d117-5a2c7b3476-000000","reportingMTA":"dns; amazonses.com"},"mail":{"timestamp":"2020-05-22T07:19:39.000Z","source":"bounce+8facd5e1+1d442eab44a9704a91f7095b5cf58da133dd813=yahoo.com@mydomain.com","sourceArn":"arn:aws:ses:eu-central-1:599070316271:identity/bounce@mydomain.com","sourceIp":"185.237.146.118","sendingAccountId":"599070316271
 ","messageId":"01070172307881-cf3a4e-c228-42fd-8a40-260a35dd36-000000","destination":["1d442eab44a9704a91f7095b5cf58da133dd813@yahoo.com"]}}

My amazon domain notifcation settings has Email Feedback Forwarding: Enabled and Bounce has been set also for SNS Topic Configuration.
My amazon bounce@mydomain.com and support@mydomain.com (email used to send emails) also has the same configuration as above.

Am I missing something here?
 

motowebmaster

Active member
I use Amazon SES on my XF site.

The problem with SES is that it receives/processes the bounce within the AWS platform, XF doesn't ever receive it.

I was confused on this as well, until realizing that this is normal operation for SES. The downside is that I have to manually change a user profile when a bounce notification comes in, but few bounces happen these days.

Hope this helps,
 

Alpha1

Well-known member
This thread may help you on your way:
 
Top