Certainly, for received mail I can even just look in the headers. I am using rspamd as part of the mail setup, so maybe I can do something with rspamd logging.
But the question is about reliably triggering a test where the mail server must reject. So reliably triggering so I can look at the logs to see what happens. E.g. a service that sends me a mail message but purposely from an IP that is not in the SPF record and/or a DKIM signature that is wrong and/or a DMARC situation where spf and skim do not match up. Something spammers would do. G > On 7 Jan 2020, at 19:15, Ken O'Driscoll via dmarc-discuss > <dmarc-discuss@dmarc.org> wrote: > > On Tue, 2020-01-07 at 17:04 +0100, Gerben Wierda via dmarc-discuss wrote: >> But I would like to see if a message that comes from outside and that >> should be blocked because the owner of the domain has a policy p=reject. >> So, some sort of tester that is able to make me test how I react on >> incoming mail I should reject. Does something like that exist? > > Perhaps I misunderstand, but wouldn't your inbound email server logs tell > you how DMARC is evaluated for inbound emails from domains which you do not > control? > > Ken. > > _______________________________________________ > 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)