Despite the error message showing up in a DMARC context, this sounds more like a failure in how your OOO responses are created.

For example, if LinkedIn sends you:

   MAIL
   
FROM:<44a037374908b416988bae2914f01ccc32dadbf94fb7b0cceb2b8aa7aa8b5...@bounce.linkedin.com>
   RCPT TO:<u...@example.com>
   ...
   From: LinkedIn Updates <messages-nore...@linkedin.com>
   To: User <u...@example.com>


Then a human-generated response whould look like:

   MAIL FROM:<u...@example.com>
   RCPT TO:<messages-nore...@linkedin.com>
   ...
   From: User <u...@example.com>
   To: LinkedIn Updates <messages-nore...@linkedin.com>

(this will bounce of course); while a machine-generated response should look something like:

   MAIL FROM:<>
   RCPT
   
TO:<44a037374908b416988bae2914f01ccc32dadbf94fb7b0cceb2b8aa7aa8b5...@bounce.linkedin.com>
   ...
   From: User <u...@example.com>
   To: LinkedIn Updates <messages-nore...@linkedin.com>


The empty MAIL FROM is designed specifically to stop machine-generated responses (like OOO responses) from causing the creation of more machine-generated responses. By copying the MAIL FROM address of the incoming message to the RCPT TO of the machine-generated response, LinkedIn is helped to use the VERP information (44a037374908b416988bae2914f01ccc32dadbf94fb7b0cceb2b8aa7aa8b585f in this case) to automatically work out which address is failing.

However, if you have a buggy OOO generator, you might be doing something like:

   MAIL FROM:<>
   RCPT TO:<messages-nore...@linkedin.com>
   ...
   From: User <u...@example.com>
   To: LinkedIn Updates <messages-nore...@linkedin.com>


which is correctly setting MAIL FROM to be empty - as required for machine-generated responses - but incorrectly copying RCPT TO from the message header rather (From:) than from the envelope (MAIL FROM:). Because LinkedIn uses VERP (thereby causing all bounces to go to bounce.linkedin.com), they would respond with an error about a blank MAIL FROM (because their main domain never receives bounces), which is what you're seeing.

- Roland

------------------------------------------------------------------------

On 05/06/17 11:09, Yeo via dmarc-discuss wrote:

Hi all,

We just recently enabled DMARC for our outgoing mails. We noticed our out of office (OOF) messages to internet so far ok e.g gmail.com.

But when OOF messages send to linkedin.com we will get DMARC verification failed due to Original-Mail-From is blank.

How to overcome such issue as a sender?

Thanks.

Regards,

*Yeo*



_______________________________________________
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)

Reply via email to