Re: [dmarc-discuss] About that From: field
On Sat, May 10, 2014 at 9:02 PM, Dave Crocker d...@dcrocker.net wrote: My question was rather carefully formed. The intent, one assumes, of this list, is to examine and discuss operational issues that relate to DMARC. It seems as though the existence of a bug is being inferred; the archives don't reflect what recipients receive, I read. But in what way? The problem statement is going unstated, unclarified. It is, to borrow a phrase, not rather carefully formed. Here's a possible way to start: I think the web archive of this mailing list does not reflect what recipients received because it __. I think that is bad because . Do you think the web archive doesn't reflect what email subscribing recipients received? In what way, specifically? Is it material, and is it harmful? Regards, Al Iverson -- Al Iverson | Chicago, IL | (312) 725-0130 Twitter: @aliverson / www.spamresource.com ___ dmarc-discuss mailing list dmarc-discuss@dmarc.org http://www.dmarc.org/mailman/listinfo/dmarc-discuss NOTE: Participating in this list means you agree to the DMARC Note Well terms (http://www.dmarc.org/note_well.html)
Re: [dmarc-discuss] About that From: field
On 5/11/2014 2:22 PM, Al Iverson via dmarc-discuss wrote: The intent, one assumes, of this list, is to examine and discuss operational issues that relate to DMARC. It seems as though the existence of a bug is being inferred; the archives don't reflect what recipients receive, I read. But in what way? The problem statement is going unstated, unclarified. It is, to borrow a phrase, not rather carefully formed. Nice job, Al. http://en.wikipedia.org/wiki/Question_dodging Bullet's 8 and 9 diligently applied. Although it does prompt the question of why you are working so hard to avoid responding to the substance of the question I asked. And no, I'm not expecting a useful response. d/ -- Dave Crocker Brandenburg InternetWorking bbiw.net ___ dmarc-discuss mailing list dmarc-discuss@dmarc.org http://www.dmarc.org/mailman/listinfo/dmarc-discuss NOTE: Participating in this list means you agree to the DMARC Note Well terms (http://www.dmarc.org/note_well.html)
Re: [dmarc-discuss] About that From: field
On Sun, May 11, 2014 at 4:43 PM, Dave Crocker d...@dcrocker.net wrote: Although it does prompt the question of why you are working so hard to avoid responding to the substance of the question I asked. And no, I'm not expecting a useful response. Dave, I apologize for frustrating you. Neither you nor I have any particular standing relating to the list's administration, and thus, little recourse when an attempt to steer a conversation in a certain direction is rebuffed. What you call carefully formed, I look at and go, interesting questions, but very cart before the horse, and I'm not a student in attendance at a lecture you're presenting, so, no, you don't get to call on me and demand that I answer you. I find the tactic distasteful and declined to respond to it as you desired. Back to the point, which is: I'd like to understand the operational issue before I'm willing to jump to the existential crisis of what I should or shouldn't want from a list archive. That doesn't mean I'm not willing to answer your questions -- I'm very much willing to do so. But you've jumped ahead in the discussion. I still don't understand what changed and why it is considered bad. I saw John say, the mail going into the archive isn't the same as the mail going out to the list. In what way? I look at the archive and I see several ways. I see different headers. Obfuscation of email addresses to prevent spambot harvesting. Web markup and navigational links inserted, to account for the very different protocols used to interact with a web page versus an email message. And, of course, the fact that the archive is showing you a representation of the submitter's address, even though the emailed copy may have had a rewritten from address to deal with DMARC policy. A web archived copy of a message posted to the list doesn't look like the email copy I received, in a bunch of different ways. Regards, Al Iverson ___ dmarc-discuss mailing list dmarc-discuss@dmarc.org http://www.dmarc.org/mailman/listinfo/dmarc-discuss NOTE: Participating in this list means you agree to the DMARC Note Well terms (http://www.dmarc.org/note_well.html)
[dmarc-discuss] DMARC Successful Mail Delivery Reports
Over the last few days I've gotten a number of bounces like this, all from AOL: Return-Path: Received: from imb-d04.mx.aol.com (imb-d04.mx.aol.com [205.188.128.65]) by qs3710.pair.com (Postfix) with ESMTPS id 51A76125427 for i...@kitterman.com; Sun, 11 May 2014 13:05:39 -0400 (EDT) Received: from mtaig-mca02.mx.aol.com (mtaig-mca02.mx.aol.com [172.26.221.66]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by imb-d04.mx.aol.com (AOL Mail Bouncer) with ESMTPS id 12B0E38000AA for i...@kitterman.com; Sun, 11 May 2014 13:05:39 -0400 (EDT) Received: by mtaig-mca02.mx.aol.com (Internet Inbound) id 040077087; Sun, 11 May 2014 13:05:39 -0400 (EDT) Date: Sun, 11 May 2014 13:05:39 -0400 (EDT) From: mailer-dae...@aol.com (Mail Delivery System) Subject: Successful Mail Delivery Report To: i...@kitterman.com Auto-Submitted: auto-replied MIME-Version: 1.0 Content-Type: multipart/report; report-type=delivery-status; boundary=8C3437094.1399827939/mtaig-mca02.mx.aol.com Message-Id: 20140511170539.040077...@mtaig-mca02.mx.aol.com This is a MIME-encapsulated message. --8C3437094.1399827939/mtaig-mca02.mx.aol.com Content-Description: Notification Content-Type: text/plain; charset=us-ascii Your message was successfully delivered to the destination(s) listed below. If the message was delivered to mailbox you will receive no further notifications. Otherwise you may still receive notifications of mail delivery errors from other systems. Please direct further questions regarding this message to your e-mail administrator. --AOL Postmaster erica.bbr...@aim.com: alias expanded --8C3437094.1399827939/mtaig-mca02.mx.aol.com Content-Description: Delivery report Content-Type: message/delivery-status Reporting-MTA: dns; mtaig-mca02.mx.aol.com X-Internet-Inbound-Queue-ID: 8C3437094 X-Internet-Inbound-Sender: rfc822; i...@kitterman.com Arrival-Date: Sun, 11 May 2014 13:05:38 -0400 (EDT) Final-Recipient: rfc822; erica.bbr...@aim.com Original-Recipient: rfc822;erica.bbr...@aim.com Action: expanded Status: 2.0.0 Diagnostic-Code: X-Internet-Inbound; alias expanded --8C3437094.1399827939/mtaig-mca02.mx.aol.com Content-Description: Message Headers Content-Type: text/rfc822-headers Return-Path: i...@kitterman.com Received: from are-financed-errors.oilbrooklyn.com (safety-good- sparkprovo.oilbrooklyn.com [199.175.55.32]) by mtaig-mca02.mx.aol.com (Internet Inbound) with ESMTP id 8C3437094 for erica.bbr...@aim.com; Sun, 11 May 2014 13:05:38 -0400 (EDT) Date: Sun, 11 May 2014 06:30:50 CDT Mime-Version: 1.0 X-MSGID:1 Content-Type: text/html From: Loan Department. i...@kitterman.com To: erica.bbr...@aim.com Subject: RE:Congratulations erica.bbrown $9500 Available For You! x-aol-global-disposition: S X-AOL-SCOLL-DMARC: mtaig-mca02.mx.aol.com ; domain : kitterman.com ; policy : none ; result : F Authentication-Results: mx.aol.com; spf=fail (aol.com: the domain kitterman.com reports that 199.175.55.32 is explicitly not authorized to send mail using it's domain name.) smtp.mailfrom=kitterman.com; dmarc=fail (aol.com: the domain kitterman.com reports that Neither SPF nor DKIM align.) header.from=kitterman.com; X-AOL-REROUTE: YES x-aol-sid: 3039ac1add42536fade22f5e X-AOL-IP: 199.175.55.32 X-AOL-SPF: domain : kitterman.com SPF : fail --8C3437094.1399827939/mtaig-mca02.mx.aol.com-- Dear AOL: please stop. This is brain dead. In case anyone is wondering, no one from i...@kitterman.com sent erica.bbrown any mail telling here we had $9500 available for her. I don't know for sure if this is related to DMARC or not, but the timing seems to be roughly in line with their rollout of DMARC p=reject. I have more if anyone wants to see them. Scott K ___ dmarc-discuss mailing list dmarc-discuss@dmarc.org http://www.dmarc.org/mailman/listinfo/dmarc-discuss NOTE: Participating in this list means you agree to the DMARC Note Well terms (http://www.dmarc.org/note_well.html)
Re: [dmarc-discuss] DMARC Successful Mail Delivery Reports
Besides the backscatter AOL is creating and should stop, seems you should move your domain to p=reject to avoid that these spoofed emails get delivered to aol users and others... Printed on recycled paper! On May 11, 2014, at 19:34, Scott Kitterman via dmarc-discuss dmarc-discuss@dmarc.org wrote: Over the last few days I've gotten a number of bounces like this, all from AOL: Return-Path: Received: from imb-d04.mx.aol.com (imb-d04.mx.aol.com [205.188.128.65]) by qs3710.pair.com (Postfix) with ESMTPS id 51A76125427 for i...@kitterman.com; Sun, 11 May 2014 13:05:39 -0400 (EDT) Received: from mtaig-mca02.mx.aol.com (mtaig-mca02.mx.aol.com [172.26.221.66]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by imb-d04.mx.aol.com (AOL Mail Bouncer) with ESMTPS id 12B0E38000AA for i...@kitterman.com; Sun, 11 May 2014 13:05:39 -0400 (EDT) Received: by mtaig-mca02.mx.aol.com (Internet Inbound) id 040077087; Sun, 11 May 2014 13:05:39 -0400 (EDT) Date: Sun, 11 May 2014 13:05:39 -0400 (EDT) From: mailer-dae...@aol.com (Mail Delivery System) Subject: Successful Mail Delivery Report To: i...@kitterman.com Auto-Submitted: auto-replied MIME-Version: 1.0 Content-Type: multipart/report; report-type=delivery-status; boundary=8C3437094.1399827939/mtaig-mca02.mx.aol.com Message-Id: 20140511170539.040077...@mtaig-mca02.mx.aol.com This is a MIME-encapsulated message. --8C3437094.1399827939/mtaig-mca02.mx.aol.com Content-Description: Notification Content-Type: text/plain; charset=us-ascii Your message was successfully delivered to the destination(s) listed below. If the message was delivered to mailbox you will receive no further notifications. Otherwise you may still receive notifications of mail delivery errors from other systems. Please direct further questions regarding this message to your e-mail administrator. --AOL Postmaster erica.bbr...@aim.com: alias expanded --8C3437094.1399827939/mtaig-mca02.mx.aol.com Content-Description: Delivery report Content-Type: message/delivery-status Reporting-MTA: dns; mtaig-mca02.mx.aol.com X-Internet-Inbound-Queue-ID: 8C3437094 X-Internet-Inbound-Sender: rfc822; i...@kitterman.com Arrival-Date: Sun, 11 May 2014 13:05:38 -0400 (EDT) Final-Recipient: rfc822; erica.bbr...@aim.com Original-Recipient: rfc822;erica.bbr...@aim.com Action: expanded Status: 2.0.0 Diagnostic-Code: X-Internet-Inbound; alias expanded --8C3437094.1399827939/mtaig-mca02.mx.aol.com Content-Description: Message Headers Content-Type: text/rfc822-headers Return-Path: i...@kitterman.com Received: from are-financed-errors.oilbrooklyn.com (safety-good- sparkprovo.oilbrooklyn.com [199.175.55.32]) by mtaig-mca02.mx.aol.com (Internet Inbound) with ESMTP id 8C3437094 for erica.bbr...@aim.com; Sun, 11 May 2014 13:05:38 -0400 (EDT) Date: Sun, 11 May 2014 06:30:50 CDT Mime-Version: 1.0 X-MSGID:1 Content-Type: text/html From: Loan Department. i...@kitterman.com To: erica.bbr...@aim.com Subject: RE:Congratulations erica.bbrown $9500 Available For You! x-aol-global-disposition: S X-AOL-SCOLL-DMARC: mtaig-mca02.mx.aol.com ; domain : kitterman.com ; policy : none ; result : F Authentication-Results: mx.aol.com; spf=fail (aol.com: the domain kitterman.com reports that 199.175.55.32 is explicitly not authorized to send mail using it's domain name.) smtp.mailfrom=kitterman.com; dmarc=fail (aol.com: the domain kitterman.com reports that Neither SPF nor DKIM align.) header.from=kitterman.com; X-AOL-REROUTE: YES x-aol-sid: 3039ac1add42536fade22f5e X-AOL-IP: 199.175.55.32 X-AOL-SPF: domain : kitterman.com SPF : fail --8C3437094.1399827939/mtaig-mca02.mx.aol.com-- Dear AOL: please stop. This is brain dead. In case anyone is wondering, no one from i...@kitterman.com sent erica.bbrown any mail telling here we had $9500 available for her. I don't know for sure if this is related to DMARC or not, but the timing seems to be roughly in line with their rollout of DMARC p=reject. I have more if anyone wants to see them. Scott K ___ dmarc-discuss mailing list dmarc-discuss@dmarc.org http://www.dmarc.org/mailman/listinfo/dmarc-discuss NOTE: Participating in this list means you agree to the DMARC Note Well terms (http://www.dmarc.org/note_well.html) ___ dmarc-discuss mailing list dmarc-discuss@dmarc.org http://www.dmarc.org/mailman/listinfo/dmarc-discuss NOTE: Participating in this list means you agree to the DMARC Note Well terms (http://www.dmarc.org/note_well.html)
Re: [dmarc-discuss] DMARC Successful Mail Delivery Reports
You have p=none and ruf= turned on, AOL's doing exactly what you've requested. - Roland On 05/12/2014 10:25 AM, Scott Kitterman via dmarc-discuss wrote: Over the last few days I've gotten a number of bounces like this, all from AOL: Return-Path: Received: from imb-d04.mx.aol.com (imb-d04.mx.aol.com [205.188.128.65]) by qs3710.pair.com (Postfix) with ESMTPS id 51A76125427 for i...@kitterman.com; Sun, 11 May 2014 13:05:39 -0400 (EDT) Received: from mtaig-mca02.mx.aol.com (mtaig-mca02.mx.aol.com [172.26.221.66]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by imb-d04.mx.aol.com (AOL Mail Bouncer) with ESMTPS id 12B0E38000AA for i...@kitterman.com; Sun, 11 May 2014 13:05:39 -0400 (EDT) Received: by mtaig-mca02.mx.aol.com (Internet Inbound) id 040077087; Sun, 11 May 2014 13:05:39 -0400 (EDT) Date: Sun, 11 May 2014 13:05:39 -0400 (EDT) From: mailer-dae...@aol.com (Mail Delivery System) Subject: Successful Mail Delivery Report To: i...@kitterman.com Auto-Submitted: auto-replied MIME-Version: 1.0 Content-Type: multipart/report; report-type=delivery-status; boundary=8C3437094.1399827939/mtaig-mca02.mx.aol.com Message-Id: 20140511170539.040077...@mtaig-mca02.mx.aol.com This is a MIME-encapsulated message. --8C3437094.1399827939/mtaig-mca02.mx.aol.com Content-Description: Notification Content-Type: text/plain; charset=us-ascii Your message was successfully delivered to the destination(s) listed below. If the message was delivered to mailbox you will receive no further notifications. Otherwise you may still receive notifications of mail delivery errors from other systems. Please direct further questions regarding this message to your e-mail administrator. --AOL Postmaster erica.bbr...@aim.com: alias expanded --8C3437094.1399827939/mtaig-mca02.mx.aol.com Content-Description: Delivery report Content-Type: message/delivery-status Reporting-MTA: dns; mtaig-mca02.mx.aol.com X-Internet-Inbound-Queue-ID: 8C3437094 X-Internet-Inbound-Sender: rfc822; i...@kitterman.com Arrival-Date: Sun, 11 May 2014 13:05:38 -0400 (EDT) Final-Recipient: rfc822; erica.bbr...@aim.com Original-Recipient: rfc822;erica.bbr...@aim.com Action: expanded Status: 2.0.0 Diagnostic-Code: X-Internet-Inbound; alias expanded --8C3437094.1399827939/mtaig-mca02.mx.aol.com Content-Description: Message Headers Content-Type: text/rfc822-headers Return-Path: i...@kitterman.com Received: from are-financed-errors.oilbrooklyn.com (safety-good- sparkprovo.oilbrooklyn.com [199.175.55.32]) by mtaig-mca02.mx.aol.com (Internet Inbound) with ESMTP id 8C3437094 for erica.bbr...@aim.com; Sun, 11 May 2014 13:05:38 -0400 (EDT) Date: Sun, 11 May 2014 06:30:50 CDT Mime-Version: 1.0 X-MSGID:1 Content-Type: text/html From: Loan Department. i...@kitterman.com To: erica.bbr...@aim.com Subject: RE:Congratulations erica.bbrown $9500 Available For You! x-aol-global-disposition: S X-AOL-SCOLL-DMARC: mtaig-mca02.mx.aol.com ; domain : kitterman.com ; policy : none ; result : F Authentication-Results: mx.aol.com; spf=fail (aol.com: the domain kitterman.com reports that 199.175.55.32 is explicitly not authorized to send mail using it's domain name.) smtp.mailfrom=kitterman.com; dmarc=fail (aol.com: the domain kitterman.com reports that Neither SPF nor DKIM align.) header.from=kitterman.com; X-AOL-REROUTE: YES x-aol-sid: 3039ac1add42536fade22f5e X-AOL-IP: 199.175.55.32 X-AOL-SPF: domain : kitterman.com SPF : fail --8C3437094.1399827939/mtaig-mca02.mx.aol.com-- Dear AOL: please stop. This is brain dead. In case anyone is wondering, no one from i...@kitterman.com sent erica.bbrown any mail telling here we had $9500 available for her. I don't know for sure if this is related to DMARC or not, but the timing seems to be roughly in line with their rollout of DMARC p=reject. I have more if anyone wants to see them. Scott K ___ dmarc-discuss mailing list dmarc-discuss@dmarc.org http://www.dmarc.org/mailman/listinfo/dmarc-discuss NOTE: Participating in this list means you agree to the DMARC Note Well terms (http://www.dmarc.org/note_well.html) -- Roland Turner | Director, Labs TrustSphere Pte Ltd | 3 Phillip Street #13-03, Singapore 048693 Mobile: +65 96700022 | Skype: roland.turner roland.tur...@trustsphere.com | http://www.trustsphere.com/ ___ dmarc-discuss mailing list dmarc-discuss@dmarc.org http://www.dmarc.org/mailman/listinfo/dmarc-discuss NOTE: Participating in this list means you agree to the DMARC Note Well terms (http://www.dmarc.org/note_well.html)
Re: [dmarc-discuss] DMARC Successful Mail Delivery Reports
No. I care too much about actual mailing list traffic for that to be feasible. If this is happening due to DMARC, a better solution for my use case would be to remove my DMARC record. Scott K On Monday, May 12, 2014 03:01:00 Franck Martin wrote: Besides the backscatter AOL is creating and should stop, seems you should move your domain to p=reject to avoid that these spoofed emails get delivered to aol users and others... Printed on recycled paper! On May 11, 2014, at 19:34, Scott Kitterman via dmarc-discuss dmarc-discuss@dmarc.org wrote: Over the last few days I've gotten a number of bounces like this, all from AOL: Return-Path: Received: from imb-d04.mx.aol.com (imb-d04.mx.aol.com [205.188.128.65]) by qs3710.pair.com (Postfix) with ESMTPS id 51A76125427 for i...@kitterman.com; Sun, 11 May 2014 13:05:39 -0400 (EDT) Received: from mtaig-mca02.mx.aol.com (mtaig-mca02.mx.aol.com [172.26.221.66]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by imb-d04.mx.aol.com (AOL Mail Bouncer) with ESMTPS id 12B0E38000AA for i...@kitterman.com; Sun, 11 May 2014 13:05:39 -0400 (EDT) Received: by mtaig-mca02.mx.aol.com (Internet Inbound) id 040077087; Sun, 11 May 2014 13:05:39 -0400 (EDT) Date: Sun, 11 May 2014 13:05:39 -0400 (EDT) From: mailer-dae...@aol.com (Mail Delivery System) Subject: Successful Mail Delivery Report To: i...@kitterman.com Auto-Submitted: auto-replied MIME-Version: 1.0 Content-Type: multipart/report; report-type=delivery-status; boundary=8C3437094.1399827939/mtaig-mca02.mx.aol.com Message-Id: 20140511170539.040077...@mtaig-mca02.mx.aol.com This is a MIME-encapsulated message. --8C3437094.1399827939/mtaig-mca02.mx.aol.com Content-Description: Notification Content-Type: text/plain; charset=us-ascii Your message was successfully delivered to the destination(s) listed below. If the message was delivered to mailbox you will receive no further notifications. Otherwise you may still receive notifications of mail delivery errors from other systems. Please direct further questions regarding this message to your e-mail administrator. --AOL Postmaster erica.bbr...@aim.com: alias expanded --8C3437094.1399827939/mtaig-mca02.mx.aol.com Content-Description: Delivery report Content-Type: message/delivery-status Reporting-MTA: dns; mtaig-mca02.mx.aol.com X-Internet-Inbound-Queue-ID: 8C3437094 X-Internet-Inbound-Sender: rfc822; i...@kitterman.com Arrival-Date: Sun, 11 May 2014 13:05:38 -0400 (EDT) Final-Recipient: rfc822; erica.bbr...@aim.com Original-Recipient: rfc822;erica.bbr...@aim.com Action: expanded Status: 2.0.0 Diagnostic-Code: X-Internet-Inbound; alias expanded --8C3437094.1399827939/mtaig-mca02.mx.aol.com Content-Description: Message Headers Content-Type: text/rfc822-headers Return-Path: i...@kitterman.com Received: from are-financed-errors.oilbrooklyn.com (safety-good- sparkprovo.oilbrooklyn.com [199.175.55.32]) by mtaig-mca02.mx.aol.com (Internet Inbound) with ESMTP id 8C3437094 for erica.bbr...@aim.com; Sun, 11 May 2014 13:05:38 -0400 (EDT) Date: Sun, 11 May 2014 06:30:50 CDT Mime-Version: 1.0 X-MSGID:1 Content-Type: text/html From: Loan Department. i...@kitterman.com To: erica.bbr...@aim.com Subject: RE:Congratulations erica.bbrown $9500 Available For You! x-aol-global-disposition: S X-AOL-SCOLL-DMARC: mtaig-mca02.mx.aol.com ; domain : kitterman.com ; policy : none ; result : F Authentication-Results: mx.aol.com; spf=fail (aol.com: the domain kitterman.com reports that 199.175.55.32 is explicitly not authorized to send mail using it's domain name.) smtp.mailfrom=kitterman.com; dmarc=fail (aol.com: the domain kitterman.com reports that Neither SPF nor DKIM align.) header.from=kitterman.com; X-AOL-REROUTE: YES x-aol-sid: 3039ac1add42536fade22f5e X-AOL-IP: 199.175.55.32 X-AOL-SPF: domain : kitterman.com SPF : fail --8C3437094.1399827939/mtaig-mca02.mx.aol.com-- Dear AOL: please stop. This is brain dead. In case anyone is wondering, no one from i...@kitterman.com sent erica.bbrown any mail telling here we had $9500 available for her. I don't know for sure if this is related to DMARC or not, but the timing seems to be roughly in line with their rollout of DMARC p=reject. I have more if anyone wants to see them. Scott K ___ dmarc-discuss mailing list dmarc-discuss@dmarc.org http://www.dmarc.org/mailman/listinfo/dmarc-discuss NOTE: Participating in this list means you agree to the DMARC Note Well terms (http://www.dmarc.org/note_well.html) ___ dmarc-discuss mailing list dmarc-discuss@dmarc.org
Re: [dmarc-discuss] DMARC Successful Mail Delivery Reports
Look at the ruf= address and where it was sent. No. Not what I requested. Scott K On Monday, May 12, 2014 11:07:59 you wrote: You have p=none and ruf= turned on, AOL's doing exactly what you've requested. - Roland On 05/12/2014 10:25 AM, Scott Kitterman via dmarc-discuss wrote: Over the last few days I've gotten a number of bounces like this, all from AOL: Return-Path: Received: from imb-d04.mx.aol.com (imb-d04.mx.aol.com [205.188.128.65]) by qs3710.pair.com (Postfix) with ESMTPS id 51A76125427 for i...@kitterman.com; Sun, 11 May 2014 13:05:39 -0400 (EDT) Received: from mtaig-mca02.mx.aol.com (mtaig-mca02.mx.aol.com [172.26.221.66]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by imb-d04.mx.aol.com (AOL Mail Bouncer) with ESMTPS id 12B0E38000AA for i...@kitterman.com; Sun, 11 May 2014 13:05:39 -0400 (EDT) Received: by mtaig-mca02.mx.aol.com (Internet Inbound) id 040077087; Sun, 11 May 2014 13:05:39 -0400 (EDT) Date: Sun, 11 May 2014 13:05:39 -0400 (EDT) From: mailer-dae...@aol.com (Mail Delivery System) Subject: Successful Mail Delivery Report To: i...@kitterman.com Auto-Submitted: auto-replied MIME-Version: 1.0 Content-Type: multipart/report; report-type=delivery-status; boundary=8C3437094.1399827939/mtaig-mca02.mx.aol.com Message-Id: 20140511170539.040077...@mtaig-mca02.mx.aol.com This is a MIME-encapsulated message. --8C3437094.1399827939/mtaig-mca02.mx.aol.com Content-Description: Notification Content-Type: text/plain; charset=us-ascii Your message was successfully delivered to the destination(s) listed below. If the message was delivered to mailbox you will receive no further notifications. Otherwise you may still receive notifications of mail delivery errors from other systems. Please direct further questions regarding this message to your e-mail administrator. --AOL Postmaster erica.bbr...@aim.com: alias expanded --8C3437094.1399827939/mtaig-mca02.mx.aol.com Content-Description: Delivery report Content-Type: message/delivery-status Reporting-MTA: dns; mtaig-mca02.mx.aol.com X-Internet-Inbound-Queue-ID: 8C3437094 X-Internet-Inbound-Sender: rfc822; i...@kitterman.com Arrival-Date: Sun, 11 May 2014 13:05:38 -0400 (EDT) Final-Recipient: rfc822; erica.bbr...@aim.com Original-Recipient: rfc822;erica.bbr...@aim.com Action: expanded Status: 2.0.0 Diagnostic-Code: X-Internet-Inbound; alias expanded --8C3437094.1399827939/mtaig-mca02.mx.aol.com Content-Description: Message Headers Content-Type: text/rfc822-headers Return-Path: i...@kitterman.com Received: from are-financed-errors.oilbrooklyn.com (safety-good- sparkprovo.oilbrooklyn.com [199.175.55.32]) by mtaig-mca02.mx.aol.com (Internet Inbound) with ESMTP id 8C3437094 for erica.bbr...@aim.com; Sun, 11 May 2014 13:05:38 -0400 (EDT) Date: Sun, 11 May 2014 06:30:50 CDT Mime-Version: 1.0 X-MSGID:1 Content-Type: text/html From: Loan Department. i...@kitterman.com To: erica.bbr...@aim.com Subject: RE:Congratulations erica.bbrown $9500 Available For You! x-aol-global-disposition: S X-AOL-SCOLL-DMARC: mtaig-mca02.mx.aol.com ; domain : kitterman.com ; policy : none ; result : F Authentication-Results: mx.aol.com; spf=fail (aol.com: the domain kitterman.com reports that 199.175.55.32 is explicitly not authorized to send mail using it's domain name.) smtp.mailfrom=kitterman.com; dmarc=fail (aol.com: the domain kitterman.com reports that Neither SPF nor DKIM align.) header.from=kitterman.com; X-AOL-REROUTE: YES x-aol-sid: 3039ac1add42536fade22f5e X-AOL-IP: 199.175.55.32 X-AOL-SPF: domain : kitterman.com SPF : fail --8C3437094.1399827939/mtaig-mca02.mx.aol.com-- Dear AOL: please stop. This is brain dead. In case anyone is wondering, no one from i...@kitterman.com sent erica.bbrown any mail telling here we had $9500 available for her. I don't know for sure if this is related to DMARC or not, but the timing seems to be roughly in line with their rollout of DMARC p=reject. I have more if anyone wants to see them. Scott K ___ dmarc-discuss mailing list dmarc-discuss@dmarc.org http://www.dmarc.org/mailman/listinfo/dmarc-discuss NOTE: Participating in this list means you agree to the DMARC Note Well terms (http://www.dmarc.org/note_well.html) ___ dmarc-discuss mailing list dmarc-discuss@dmarc.org http://www.dmarc.org/mailman/listinfo/dmarc-discuss NOTE: Participating in this list means you agree to the DMARC Note Well terms (http://www.dmarc.org/note_well.html)
Re: [dmarc-discuss] DMARC Successful Mail Delivery Reports
Not exactly, the failure reports are not supposed to go back to the (fake) sender but to the email specific by the ruf. This seems a delivery notification, so besides a bug at AOL, I would think that the fake email contains a delivery receipt header... Which AOL would honor... I did not see such read receipt header in the original email, but it could have been removed as part of the notification. Printed on recycled paper! On May 11, 2014, at 20:15, Roland Turner via dmarc-discuss dmarc-discuss@dmarc.org wrote: You have p=none and ruf= turned on, AOL's doing exactly what you've requested. - Roland On 05/12/2014 10:25 AM, Scott Kitterman via dmarc-discuss wrote: Over the last few days I've gotten a number of bounces like this, all from AOL: Return-Path: Received: from imb-d04.mx.aol.com (imb-d04.mx.aol.com [205.188.128.65]) by qs3710.pair.com (Postfix) with ESMTPS id 51A76125427 for i...@kitterman.com; Sun, 11 May 2014 13:05:39 -0400 (EDT) Received: from mtaig-mca02.mx.aol.com (mtaig-mca02.mx.aol.com [172.26.221.66]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by imb-d04.mx.aol.com (AOL Mail Bouncer) with ESMTPS id 12B0E38000AA for i...@kitterman.com; Sun, 11 May 2014 13:05:39 -0400 (EDT) Received: by mtaig-mca02.mx.aol.com (Internet Inbound) id 040077087; Sun, 11 May 2014 13:05:39 -0400 (EDT) Date: Sun, 11 May 2014 13:05:39 -0400 (EDT) From: mailer-dae...@aol.com (Mail Delivery System) Subject: Successful Mail Delivery Report To: i...@kitterman.com Auto-Submitted: auto-replied MIME-Version: 1.0 Content-Type: multipart/report; report-type=delivery-status; boundary=8C3437094.1399827939/mtaig-mca02.mx.aol.com Message-Id: 20140511170539.040077...@mtaig-mca02.mx.aol.com This is a MIME-encapsulated message. --8C3437094.1399827939/mtaig-mca02.mx.aol.com Content-Description: Notification Content-Type: text/plain; charset=us-ascii Your message was successfully delivered to the destination(s) listed below. If the message was delivered to mailbox you will receive no further notifications. Otherwise you may still receive notifications of mail delivery errors from other systems. Please direct further questions regarding this message to your e-mail administrator. --AOL Postmaster erica.bbr...@aim.com: alias expanded --8C3437094.1399827939/mtaig-mca02.mx.aol.com Content-Description: Delivery report Content-Type: message/delivery-status Reporting-MTA: dns; mtaig-mca02.mx.aol.com X-Internet-Inbound-Queue-ID: 8C3437094 X-Internet-Inbound-Sender: rfc822; i...@kitterman.com Arrival-Date: Sun, 11 May 2014 13:05:38 -0400 (EDT) Final-Recipient: rfc822; erica.bbr...@aim.com Original-Recipient: rfc822;erica.bbr...@aim.com Action: expanded Status: 2.0.0 Diagnostic-Code: X-Internet-Inbound; alias expanded --8C3437094.1399827939/mtaig-mca02.mx.aol.com Content-Description: Message Headers Content-Type: text/rfc822-headers Return-Path: i...@kitterman.com Received: from are-financed-errors.oilbrooklyn.com (safety-good- sparkprovo.oilbrooklyn.com [199.175.55.32]) by mtaig-mca02.mx.aol.com (Internet Inbound) with ESMTP id 8C3437094 for erica.bbr...@aim.com; Sun, 11 May 2014 13:05:38 -0400 (EDT) Date: Sun, 11 May 2014 06:30:50 CDT Mime-Version: 1.0 X-MSGID:1 Content-Type: text/html From: Loan Department. i...@kitterman.com To: erica.bbr...@aim.com Subject: RE:Congratulations erica.bbrown $9500 Available For You! x-aol-global-disposition: S X-AOL-SCOLL-DMARC: mtaig-mca02.mx.aol.com ; domain : kitterman.com ; policy : none ; result : F Authentication-Results: mx.aol.com; spf=fail (aol.com: the domain kitterman.com reports that 199.175.55.32 is explicitly not authorized to send mail using it's domain name.) smtp.mailfrom=kitterman.com; dmarc=fail (aol.com: the domain kitterman.com reports that Neither SPF nor DKIM align.) header.from=kitterman.com; X-AOL-REROUTE: YES x-aol-sid: 3039ac1add42536fade22f5e X-AOL-IP: 199.175.55.32 X-AOL-SPF: domain : kitterman.com SPF : fail --8C3437094.1399827939/mtaig-mca02.mx.aol.com-- Dear AOL: please stop. This is brain dead. In case anyone is wondering, no one from i...@kitterman.com sent erica.bbrown any mail telling here we had $9500 available for her. I don't know for sure if this is related to DMARC or not, but the timing seems to be roughly in line with their rollout of DMARC p=reject. I have more if anyone wants to see them. Scott K ___ dmarc-discuss mailing list dmarc-discuss@dmarc.org http://www.dmarc.org/mailman/listinfo/dmarc-discuss NOTE: Participating in this list means you agree to the DMARC Note Well terms (http://www.dmarc.org/note_well.html) -- Roland Turner | Director, Labs TrustSphere Pte Ltd | 3 Phillip Street #13-03, Singapore 048693 Mobile: +65 96700022 | Skype:
