Re: [dmarc-discuss] DMARC oddity

2018-11-26 Thread Roland Turner via dmarc-discuss
Right. This is the envelope sender (5321.MAIL FROM). It doesn't align with linktechs.net, so won't contribute to a DMARC pass. Why does the message have an author/5322.From: address in the linktechs.net domain, but not a valid DKIM signature? This looks like a typical list-breaks-DKIM

Re: [dmarc-discuss] DMARC oddity

2018-11-26 Thread Zachary Aab via dmarc-discuss
Is the DMARC milter behind a separate gateway filter? >milter-reject: END-OF-MESSAGE from filter1.linktechs.email[127.0.0.1]: If so, the DMARC milter may be checking the email against the wrong information, DMARC milters often require some custom setup to ignore the apparent source (the gateway)

Re: [dmarc-discuss] DMARC oddity

2018-11-26 Thread Dennis Burgess via dmarc-discuss
Nov 26 11:40:44 filter1 opendmarc[21194]: 406A610E1FC: SPF(mailfrom): board-boun...@wispa.org none Dennis Burgess, Mikrotik Certified Trainer Author of "Learn RouterOS- Second Edition” Link Technologies, Inc -- Mikrotik & WISP Support Services Office: 314-735-0270 Website:

Re: [dmarc-discuss] DMARC oddity

2018-11-26 Thread Vladimir Dubrovin via dmarc-discuss
You see envelope-from (aka RFC 5321.mailfrom) address in logs, while DMARC checks policy against From: header (RFC 5322.From), envelope-from and From: may differ. 26.11.2018 22:17, Dennis Burgess via dmarc-discuss пишет: > > Got an odd one, getting e-mails from another domain rejected based on >