For Amazon SES, they then send/forward an email to you of the spam/abuse complaint initiated by the recipient to your Bounced Email Address. Refer https://sesblog.amazon.com/blog/tag/abuse+complaint
When xF processes this spam/abuse complaint to your bounces inbox, no action is taken.
As per above blog, I believe it should be processed and mark the user state as email invalid (bounced). (Or even better, an additional user state of "email invalid (spam report)")
Here's a sample spam/abuse report email ("<redacted>" added by me) that comes to xf bounces inbox ...
Delivered-To: bounces+7893a4dc+<redacted>=yahoo.com.au@<redacted>.com.au Received: by 10.202.171.74 with SMTP id u71csp470804oie; Fri, 13 May 2016 14:40:02 -0700 (PDT) X-Received: by 10.66.152.201 with SMTP id va9mr26178294pab.73.1463175602646; Fri, 13 May 2016 14:40:02 -0700 (PDT) Return-Path: <firstname.lastname@example.org> Received: from a27-9.smtp-out.us-west-2.amazonses.com (a27-9.smtp-out.us-west-2.amazonses.com. [188.8.131.52]) by mx.google.com with ESMTPS id a3si26505755pfb.217.2016.05.13.14.40.02 for <bounces+7893a4dc+<redacted>=yahoo.com.au@<redacted>.com.au> (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 13 May 2016 14:40:02 -0700 (PDT) Received-SPF: pass (google.com: domain of email@example.com designates 184.108.40.206 as permitted sender) client-ip=220.127.116.11; Authentication-Results: mx.google.com; dkim=neutral (body hash did not verify) firstname.lastname@example.org; spf=pass (google.com: domain of email@example.com designates 18.104.22.168 as permitted sender) firstname.lastname@example.org X-Original-To: email@example.com Delivered-To: firstname.lastname@example.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=arf.mail.yahoo.com; s=arf; t=1463175600; bh=JA0DfLoWSnvhMk580J67urAR0K7gCZqQ9TKYs4ruNEA=; h=Date:From:To:Subject:From:Subject; b=YK7XkRpp5vjWWJ2wTJMNqL6FOmPrYqdyclIrBL68go84/DCB6BEURpYNnDQ+sTIH47JJtcFQYX9VO1nfqPYj6W+QjcksfxSUjnrbIBn+dZo4haV9vyuiyUHtDYGYOoS5cuAU5KFFe5xnKOFK+wp6ctW4i2EglEO8rC/u542Z1fM= X-Yahoo-Newman-Id: cfl-test MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: multipart/report; boundary="_----------=_14631756006709"; report-type="feedback-report" X-Mailer: MIME::Lite 3.028 (F2.82; A2.11; B3.13; Q3.13) Date: Fri, 13 May 2016 21:40:01 +0000 From: email@example.com To: bounces+7893a4dc+<redacted>=yahoo.com.au@<redacted>.com.au X-Yahoo-Newman-Property: cfl Message-ID: <firstname.lastname@example.org> X-SES-Outgoing: 2016.05.13-22.214.171.124 This is a multi-part message in MIME format. --_----------=_14631756006709 MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" X-Mailer: MIME::Lite 3.028 (F2.82; A2.11; B3.13; Q3.13) Date: Fri, 13 May 2016 21:40:00 +0000 This is an email abuse report for an email message received from 126.96.36.199 on Fri, 13 May 2016 16:39:32 UTC --_----------=_14631756006709 Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: message/feedback-report Feedback-Type: abuse User-Agent: Yahoo!-Mail-Feedback/1.0 Version: 0.1 Original-Mail-From: <email@example.com> Original-Rcpt-To: <redacted>@yahoo.com.au Received-Date: Fri, 13 May 2016 16:39:32 UTC Source-IP: 188.8.131.52