Hi Miles, on the whim of asking a stupid question, do you have any filtering in
place that might be stripping attachments for the inbound complaints?
Every ARF complaint we receive from Comcast has the original message attached
as well as the original headers. They do change some parts such as the Original
To address but other than that everything I need remains. The original
Message-ID header that I tagged on the message is available as well. Below is
an example ARF that I received from Comcast. For obvious reasons I did not
include the message data, which is the originally sent message, attached to the
ARF.
Return-Path: <fblboun...@senderscore.net>
Received: from mra-fbl.returnpath.net (66.45.29.178) by x id hdt58417vk41 for
<MY FBL ADDRESS>; Sat, 25 Jun 2016 23:22:42 -0400 (envelope-from
<fblboun...@senderscore.net>)
Received: from poma00.lan.returnpath.net (poma00.lan.returnpath.net
[10.2.0.104])
by mra-fbl.returnpath.net (Postfix) with ESMTP id 3272360BC6
for <MY FBL ADDRESS>; Sat, 25 Jun 2016 21:22:42 -0600 (MDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=senderscore.net;
s=081107; t=1466911362; i=@senderscore.net;
bh=mR1BKAExVVBtZNUgCX8CPc0chUgS9Eid5QmQm8KQGLQ=;
h=Date:Subject:To:From;
b=QmwvkDpVL3IyhdRucjJBG7mK/hoxQ6N/P7SxfWiKfZzIUbBU0IE6D9o6QCGrzKxHm
iW46KZWsPYIeUlYktwTHFIoD5hKFI8b9f5gypl/ihm9BbZXEjuEjW0FL1uwI4maHaI
PPhaxW+PixM9FogJMFEfy9oZEdMBsfSV33tndNuQ=
Received: by poma00.lan.returnpath.net (Postfix, from userid 106706)
id 2EED3602EC; Sat, 25 Jun 2016 21:22:42 -0600 (MDT)
Content-Transfer-Encoding: binary
Content-Type: multipart/report; boundary="_----------=_146691136226179720648";
report-type="feedback-report"
MIME-Version: 1.0
X-Mailer: MIME::Lite 3.029 (F2.84; T2.04; A2.12; B3.13; Q3.13)
Date: Sat, 25 Jun 2016 21:22:42 -0600
Subject: Comcast Abuse Report
To: MY FBL ADDRESS
From: feedbackl...@comcastfbl.senderscore.net
Message-Id: <20160626032242.2eed360...@poma00.lan.returnpath.net>
This is a multi-part message in MIME format.
--_----------=_146691136226179720648
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
This is a Comcast email abuse report for an email message received from IP
66.216.136.17 on Fri, 24 Jun 2016 14:02:31 +0000
--_----------=_146691136226179720648
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Content-Type: message/feedback-report
User-Agent: ReturnPathFBL/1.0
Abuse-Type: complaint
Arrival-Date: Fri, 24 Jun 2016 14:02:31 +0000
Feedback-Type: abuse
Version: 1
Source-IP: 66.216.136.17
Original-Rcpt-To: x...@comcast.net
Original-Mail-From: tirou3t3l8g4l8m3o66iua6igufje8f77sq6g44u...@bounce.x.x.com
Reported-Domain: comcast.net
--_----------=_146691136226179720648
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
Content-Type: message/rfc822
Return-Path:
tirou3t3l8g4l8m3o66iua6igufje8f77sq6g44u...@bounce.x.x.com
Received: from reszmta-po-02v.sys.comcast.net (LHLO
reszmta-po-02v.sys.comcast.net) (96.114.154.194) by
resmail-ch2-165v.sys.comcast.net with LMTP; Fri, 24 Jun 2016 14:02:32 +0000
(UTC)
Received: from resimta-po-06v.sys.comcast.net ([96.114.154.134]) by
reszmta-po-02v.sys.comcast.net with SMTP id GRfWbY0QwbhrAGRgmbh5UK; Fri, 24
Jun 2016 14:02:32 +0000
Received: from vmta-c-17.listrak.com ([66.216.136.17]) by
resimta-po-06v.sys.comcast.net with comcast id Ae0F1t02S0NhwvW01e2Uti; Fri,
24 Jun 2016 14:02:31 +0000
X-CAA-SPAM: 00000
X-Authority-Analysis: v=2.2 cv=M6aiE24s c=1 sm=1 tr=0 b=1
a=zTL8rsoIyQ2Fu9XpM633pw==:117 a=zTL8rsoIyQ2Fu9XpM633pw==:17
a=pD_ry4oyNxEA:10 a=g49iIO9tAAAA:8 a=Wpayg08zDLkmSyltFE4A:9
a=vupXE-yMsqEA:10 a=ssrH51q3EpgA:10 a=-CjfsyIFs30A:10 a=3g80flMcAAAA:8
a=C_IRinGWAAAA:8 a=K-soA_ZEAAAA:8 a=TeuQqM9sAAAA:8 a=1XWaLZrsAAAA:8
a=3j4BkbkPAAAA:8 a=BkpHzsgbAAAA:8 a=JqEG_dyiAAAA:8 a=SSmOFEACAAAA:8
a=Muk0_wYgoTt5b2OUatIA:9 a=oXAuiHkLLPRsq_pS:21 a=VS7aPXTO-YHmV8P7:21
a=OAFTwP2CnfMshqRt:21 a=_W_S_7VecoQA:10 a=frz4AuCg-hUA:10 a=MZpOI37Du90A:10
a=6DZHKH0kcPCj6a3tUS5D:22 a=3urWGuTZa-U-TZ_dHwj2:22
a=VOW5rJRXBamZ5z19bD7L:22 a=ldXoYgOmDgpMOQduyOTa:22
a=e177VXkoA7pnmra_KuOY:22 a=nJcEw6yWrPvoIXZ49MH8:22
a=sJh6Skxnaek_REti9G3X:22 a=f5W2ZZlouXWkMGtS5S88:22
a=U04FSIGNRx3ScUM3zguK:22 a=zjWhRoSqWz9hl55Hdlzg:22
X-Xfinity-Message-Heuristics: IPv6:N
Received: by vmta-c-17.listrak.com id hdkune1n6rc8 for
<x...@comcast.net>; Fri, 24 Jun 2016 10:00:57
-0400 (envelope-from
<tirou3t3l8g4l8m3o66iua6igufje8f77sq6g44u...@bounce.x.x.com>)
X-Mailer-Reference: TIROU3T3L8G4L8M3O66IUA6IGUFJE8F77SQ6G44U047
X-Message-Reference: 954FD7VNBTP4TEDS07OAIPEUH4
X-RPCampaign: esp5753527068558678668480528469688348557965738069857252
List-Unsubscribe:
<mailto:24lfrd2de76je7hdfmp4r0p46rini7i55g1p6jjr1...@bounce.x.x.com>
Errors-To:
tirou3t3l8g4l8m3o66iua6igufje8f77sq6g44u...@bounce.x.x.com
MIME-Version: 1.0
From: " " <x...@x.x.com>
Date: 24 Jun 2016 10:00:57 -0400
Subject: Summer Sale
Message-ID: <0.0.51.f8a.1d1ce20d50c4b48.9...@vmta-c-17.listrak.com>
Content-Type: multipart/alternative;
boundary=--boundary_373732_bf7041ae-a35f-4fc8-8a42-82db53f94251
To: x...@comcast.net
Andrew D. Wingle
Principal Delivery Strategist
717-627-4528 x318
717-625-7857 direct
awin...@listrak.com<mailto:awin...@listrak.com>
www.listrak.com<http://www.listrak.com/>
From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Miles Fidelman
Sent: Wednesday, June 29, 2016 3:43 PM
To: mailop@mailop.org
Subject: Re: [mailop] looking for contact at / info about comcast fbl -
follow-up
Well, I just received this from Return Path:
-------
Thank you for contacting us.
In order to obtain more information about the abusive user, you may implement a
tracking ID, Please see the information below
that is provided in the Comcast FAQ page:
"The ISP may redact parts of the original message to protect the privacy of
their users. In the event an ISP redacts subscriber email addresses from their
feedback loop messages, you should incorporate a tracking ID unique to the
recipient's record in your database and your messages so that you can process
the removals. You can add this ID in the body of the message or add an "X"
header in the header of the message. An example of this could be
"X-SenderName-ClientID: 543432".
--------
I find it rather disturbing that one of the major vendors of spam filtering
services does things in such a non-standards-compliant way. Everyone else
(well, AOL, Yahoo, the other "big boys") seem to return message-id along with
an FBL notice. Return Path seems to filter it out.
That's just painful.
Sigh.
Miles Fidelman
On 6/29/16 3:33 PM, Miles Fidelman wrote:
That's the thing. I DO VERP our SMTP envelopes, but Comcast's FBL reports only
include this:
User-Agent: ReturnPathFBL/1.0
Abuse-Type: complaint
Arrival-Date: Wed, 29 Jun 2016 15:23:37 +0000
Feedback-Type: abuse
Version: 1
Source-IP: 207.154.13.48
Original-Rcpt-To:
8d29aa11b1810bec67beca0de3554...@lists.fusn.org<mailto:8d29aa11b1810bec67beca0de3554...@lists.fusn.org>
Original-Mail-From: fusn-ow...@lists.fusn.org<mailto:fusn-ow...@lists.fusn.org>
Reported-Domain: lists.fusn.org
ForwardedMessage.eml
Subject:
[8d29aa11b1810bec67beca0de3554359] Free: pair of planters
From:
<redacted by me>
Date:
6/29/16, 11:23 AM
To:
8d29aa11b1810bec67beca0de3554...@lists.fusn.org<mailto:8d29aa11b1810bec67beca0de3554...@lists.fusn.org>
Note that the
Original-Rcpt-To:
8d29aa11b1810bec67beca0de3554...@lists.fusn.org<mailto:8d29aa11b1810bec67beca0de3554...@lists.fusn.org>
and
To:
8d29aa11b1810bec67beca0de3554...@lists.fusn.org<mailto:8d29aa11b1810bec67beca0de3554...@lists.fusn.org>
Addresses are not the VERPed address, or even the recipient address. They seem
to be an obfuscated version of the LIST address. Not really helpful.
As far as I can tell, there is NOTHING in the abuse report that can be
associated with either the final recipient or a message-id that would let me
locate the message in our outgoing logs (from which, given VERP, I could find
the recipient).
Based on other comments, I sent a query to Return Path - I'm half expecting
that they'll offer to sell me the info, or a slot on their whitelist.
Sigh...
Miles Fidelman
On 6/29/16 3:10 PM, Vick Khera wrote:
On Wed, Jun 29, 2016 at 12:50 PM, Miles Fidelman
<mfidel...@meetinghouse.net<mailto:mfidel...@meetinghouse.net>> wrote:
Is there anybody here from Comcast mail operations who can provide some
guidance as to how to identify the originator of an abuse report, so I can
remove them from the list(s)?
If you VERP the SMTP envelope sender address, that should help you out. It
comes back embedded in the report as "Original-Mail-From:"
_______________________________________________
mailop mailing list
mailop@mailop.org<mailto:mailop@mailop.org>
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
--
In theory, there is no difference between theory and practice.
In practice, there is. .... Yogi Berra
_______________________________________________
mailop mailing list
mailop@mailop.org<mailto:mailop@mailop.org>
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
--
In theory, there is no difference between theory and practice.
In practice, there is. .... Yogi Berra
_______________________________________________
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
