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 [https://www.trustsphere.com/images/signatures/trustsphere.gif] Roland Turner Labs Director Mobile: +65 9670 0022 3 Phillip Street, #13-03 Royal Group Building, Singapore 048693 ________________________________ [https://www.trustsphere.com/images/signatures/facebook.gif]<https://www.facebook.com/trustSphereco> [https://www.trustsphere.com/images/signatures/twitter.gif] <https://twitter.com/trustsphere> [https://www.trustsphere.com/images/signatures/linkedin.gif] <https://www.linkedin.com/company/trustsphere> [https://www.trustsphere.com/images/signatures/youtube.gif] <https://www.youtube.com/user/trustsphere> www.trustsphere.com<http://www.trustsphere.com/> ________________________________ 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:16 To: 'dmarc-discuss' Subject: [dmarc-discuss] dmarc fail for linkedin Hello all, Why is dmac failing for linkedin? following sanitised output captured from mailwatch. I thought Linkedin is active participant of DMARC. Sometimes it fails for gmail also. Received from: 108.174.6.157 Received Via: IP Address Hostname Country RBL Spam Virus All 108.174.6.157 mailb-de.linkedin.com United States 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-at007hio5vmhecl55aegbrldj55dod8ekz33kb3ea8tqs5z1y4pek73m8v82dh9r3w53jdybhoksmyfs6cs0g1gofydssh0dlrpf0p X-LinkedIn-Id: 2j1zjf-itsqh361-p8 List-Unsubscribe: <mailto:list-unsubscr...@linkedin.com?subject=unsubscribe/AQFHINMWGdBNHwAAAVeF1dCG2mwGmj1UB3Tv6UiVZOiuykyYxJ2Gg2W1-_q2uw2WyTZC3eV8QBIcs-Vn9Xk8qE0eQfg/2j1zjf-itsqh361-p8/m2-at007hio5vmhecl55aegbrldj55dod8ekz33kb3ea8tqs5z1y4pek73m8v82dh9r3w53jdybhoksmyfs6cs0g1gofydssh0dlrpf0p> Require-Recipient-Valid-Since: a...@recvdomain.com; Wed, 14 Aug 2013 00:00:00 +0000 From: s-2gvpcup5oqbkzh2ybkjw5b561o5y1w1xie7y74qzpfik7kyi2yfqr...@bounce.linkedin.com Regards Durga Prasad ________________________________ [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)
