Re: [dmarc-ietf] SPF/DKIM/DMARC statistics observed at UMN (past 30 days)

2023-06-16 Thread Steve Siirila
~5%. This high may just represent some level of attack this month. > Nevertheless, of the accepted mail, we have a relatively high spam mail > rate. > > Thanks > > -- > Hector Santos,https://santronics.comhttps://winserver.com > > > > On 6/16/2023 10:24 AM, Steve S

[dmarc-ietf] SPF/DKIM/DMARC statistics observed at UMN (past 30 days)

2023-06-16 Thread Steve Siirila
Below is a table of SPF/DKIM/DMARC statuses over the past 30 days on our inbound MX servers (umn.edu and several *.umn.edu domains). Note that we employ a DMARC policy of p=reject; also note that we have split our dmarc 'fail' status into three categories: *fail* indicates a DMARC failure where t

Re: [dmarc-ietf] Tree walk is screwed up

2022-01-26 Thread Steve Siirila
After reading this thread, I couldn't help but wonder about how the addition of a "PSD flag" specifically targeted to DMARC might be repurposed for other non-DMARC applications since my understanding is that the PSL is currently being used for other purposes as well. Just food for thought. ___

Re: [dmarc-ietf] Ratchets - Disallow PCT 1-99

2021-07-21 Thread Steve Siirila
At the University of Minnesota we used p=quarantine,pct=0 as a transition between p=none and p=quarantine,pct=100 as it causes header "From:" to be rewritten on DMARC-aware mailing list servers. I agree with Laura Atkins that removing pct=0 will make DMARC implementation more difficult for some or