With phishing at an all time high during this pandemic, we have started to flag emails failing DMARC... and it just so happens that some notifications from the Meraki Community system are failing the DMARC policy.
The reason for the failure is that the From and Return-Path headers are not aligned from the same domain.
This looks correct to me.
noreply.meraki.com has no DMARC record, so the parent's domain policy will apply. The DMARC policy for meraki.com is:
The policy is "none" (p=none), so anyone processing DMARC should do nothing.
A quick Google search of Khorus and Lithium suggests it doesn't support any kind of DMARC configuration.