As Elizabeth said. I suspect your implementation of openDMARC cannot see the SPF result in the email.
You may want to read https://sourceforge.net/p/opendmarc/tickets/100/ they suggest a few fixes... Notably, do you have a recent public suffix list in your openDMARC config? On Mon, Oct 3, 2016 at 12:20 PM, Elizabeth Zwicky via dmarc-discuss < dmarc-discuss@dmarc.org> wrote: > Those headers cannot all be true. If the SPF pass is right, then the DMARC > fail is wrong. Look at fixing the DMARC calculation, not your calculations. > > Elizabeth > > On Monday, October 3, 2016, 4:59:53 AM PDT, DurgaPrasad - DatasoftComnet > via dmarc-discuss <dmarc-discuss@dmarc.org> wrote: > > Actually I’m parsing the headers and based on the dmarc=fail and further > checking whether it’s from a mailing list - assigning a score in > spamassassin. If I need to use the fail in conjunction with the spf=pass - > then that premise is shot right? > > > > Regards > > DP > > > > *From:* Franck Martin [mailto:fmar...@linkedin.com] > *Sent:* 03 October 2016 23:56 > *To:* Roland Turner; DurgaPrasad - DatasoftComnet > *Cc:* DMARC Discussion List > *Subject:* Re: [dmarc-discuss] dmarc fail for linkedin > > > > Happy to help, but as Roland said the problem seems to be on the receiver > side. SPF is pass and aligned, that alone should do a DMARC pass. > > > > On Sun, Oct 2, 2016 at 9:03 PM, Roland Turner via dmarc-discuss < > dmarc-discuss@dmarc.org> wrote: > > This looks like a receiver-side bug. An SPF pass for bounces.linkedin.com > implies a DMARC pass for linkedin.com so long as the linked.com policy > specifies or defaults to relaxed alignment (it does). > > > > - Roland > > > > > > *Roland Turner* > Labs Director > *Mobile:* +65 9670 0022 > 3 Phillip Street, #13-03 Royal Group Building, Singapore 048693 > ------------------------------ > > <https://www.facebook.com/trustSphereco> > > <https://www.facebook.com/trustSphereco> > > <https://www.facebook.com/trustSphereco> > > <https://www.facebook.com/trustSphereco> > > *www.trustsphere.com* <https://www.facebook.com/trustSphereco> > > <https://www.facebook.com/trustSphereco> > > <https://www.facebook.com/trustSphereco> > > <https://www.facebook.com/trustSphereco> > ------------------------------ > <https://www.facebook.com/trustSphereco> > > > > > *From: dmarc-discuss <dmarc-discuss-boun...@dmarc.org> on behalf of > DurgaPrasad - DatasoftComnet via dmarc-discuss > <dmarc-discuss@dmarc.org>Sent: Sunday, 2 October 2016 23:16To: > 'dmarc-discuss'Subject: [dmarc-discuss] dmarc fail for linkedin > <https://www.facebook.com/trustSphereco>* > > <https://www.facebook.com/trustSphereco> > > Hello all, <https://www.facebook.com/trustSphereco> > > Why is dmac failing for linkedin? <https://www.facebook.com/trustSphereco> > > following sanitised output captured from mailwatch. I thought Linkedin is > active participant of DMARC. <https://www.facebook.com/trustSphereco> > > Sometimes it fails for gmail also. > <https://www.facebook.com/trustSphereco> > > <https://www.facebook.com/trustSphereco> > > <https://www.facebook.com/trustSphereco> > > Received from: <https://www.facebook.com/trustSphereco> > > 108.174.6.157 <https://www.facebook.com/trustSphereco> > > Received Via: <https://www.facebook.com/trustSphereco> > > *IP Address <https://www.facebook.com/trustSphereco>* > > *Hostname <https://www.facebook.com/trustSphereco>* > > *Country <https://www.facebook.com/trustSphereco>* > > *RBL <https://www.facebook.com/trustSphereco>* > > *Spam <https://www.facebook.com/trustSphereco>* > > *Virus <https://www.facebook.com/trustSphereco>* > > *All <https://www.facebook.com/trustSphereco>* > > 108.174.6.157 <https://www.facebook.com/trustSphereco> > > *mailb-de.linkedin.com* <https://www.facebook.com/trustSphereco> > > United States <https://www.facebook.com/trustSphereco> > > <https://www.facebook.com/trustSphereco> > > <https://www.facebook.com/trustSphereco> > > <https://www.facebook.com/trustSphereco> > > <https://www.facebook.com/trustSphereco> > > <https://www.facebook.com/trustSphereco> > > X-Greylist: delayed 62 seconds by postgrey-1.34 at *sync.recvdomain.com*; > Sun, 02 Oct 2016 20:10:32 IST > DMARC-Filter: OpenDMARC Filter v1.3.1 *sync.recvdomain.com* 3561F1A4C04 > Authentication-Results: *sync.recvdomain.com*; dmarc=fail header.from= > *linkedin.com* > Authentication-Results: *sync.recvdomain.com*; spf=pass smtp.mailfrom= > *s-2gvpcup5oqbkzh2ybkjw5b561o5y1w1xie7y74qzpfik7kyi2yfqr...@bounce.linkedin.com* > Received: from *mailb-de.linkedin.com* (*mailb-de.linkedin.com* > [108.174.6.157]) > by *sync.recvdomain.com* (Postfix) with ESMTP id 3561F1A4C04 > for <*a...@recvdomain.com*>; Sun, 2 Oct 2016 20:10:31 +0530 (IST) > DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=*linkedin.com*; > s=proddkim1024; t=1475419164; > bh=0BGcec8gfa2UUrhh3rWJw+dpo9wKPor0X6Nmr4swfos=; > h=From:Subject:MIME-Version:Content-Type:To:Date:X-LinkedIn-Class: > X-LinkedIn-Template:X-LinkedIn-fbl; > b=o/PNleMe51U0pZDfW/LAVdNKiv2C4ovHt5yvMj1yrIhPfRBMKGtcGYSk67Vfl7CKx > sHutanfc5qs/eUEKnE3kMH5d2ErQ6PrVf89XBoQJtdLTOkMAAi7xEMFeE3FG0kY7Dw > otmGefhsAJezAVhhv0enUvM5Lho7jEcJ3xFcksls= > From: John Kennedy <*invitati...@linkedin.com*> > Message-ID: < > *401079548.70154.1475419164807.javamail....@lva1-app2439.prod.linkedin.com* > > > Subject: Abc, please add me to your LinkedIn network > MIME-Version: 1.0 > Content-Type: multipart/alternative; > boundary="----=_Part_70152_1116365500.1475419164803" > To: Abc Ganta <*a...@recvdomain.com*> > Date: Sun, 2 Oct 2016 14:39:24 +0000 (UTC) > X-LinkedIn-Class: INVITE-MBR > X-LinkedIn-Template: email_m2m_invite_single_01 > X-LinkedIn-fbl: m2-at007hio5vmhecl55aegbrldj55dod > 8ekz33kb3ea8tqs5z1y4pek73m8v82dh9r3w53jdybhoksmyfs6cs0g1gofydssh0dlrpf0p > X-LinkedIn-Id: 2j1zjf-itsqh361-p8 > List-Unsubscribe: <mailto:*list-unsubscr...@linkedin.com*?subject= > unsubscribe/AQFHINMWGdBNHwAAAVeF1dCG2mwGmj1UB3Tv6UiVZOiuykyYxJ2Gg2W1-_ > q2uw2WyTZC3eV8QBIcs-Vn9Xk8qE0eQfg/2j1zjf-itsqh361-p8/m2- > at007hio5vmhecl55aegbrldj55dod8ekz33kb3ea8tqs5z1y4pek73m8v82 > dh9r3w53jdybhoksmyfs6cs0g1gofydssh0dlrpf0p> > Require-Recipient-Valid-Since: *a...@recvdomain.com*; Wed, 14 Aug 2013 > 00:00:00 +0000 <https://www.facebook.com/trustSphereco> > > From: <https://www.facebook.com/trustSphereco> > > > *s-2gvpcup5oqbkzh2ybkjw5b561o5y1w1xie7y74qzpfik7kyi2yfqr...@bounce.linkedin.com* > <https://www.facebook.com/trustSphereco> > > <https://www.facebook.com/trustSphereco> > > <https://www.facebook.com/trustSphereco> > > Regards <https://www.facebook.com/trustSphereco> > > Durga Prasad <https://www.facebook.com/trustSphereco> > > <https://www.facebook.com/trustSphereco> > > <https://www.facebook.com/trustSphereco> > ------------------------------ > <https://www.facebook.com/trustSphereco> > > <https://www.facebook.com/trustSphereco> > > This email has been checked for viruses by Avast antivirus software. > *www.avast.com* <https://www.facebook.com/trustSphereco> > > <https://www.facebook.com/trustSphereco> > > > _______________________________________________ > 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*) > <https://www.facebook.com/trustSphereco> > > <https://www.facebook.com/trustSphereco> > > > ------------------------------ > [image: Avast logo] > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > > This email has been checked for viruses by Avast antivirus software. > www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> > > _______________________________________________ > 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) >
_______________________________________________ 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)
