On 4/14/19 10:49 AM, Alice Wonder wrote:
Yes, and they are sending them to me even when there are no errors.They are sending them to my little used mail server when they have made no attempts to deliver to that domain.
I'm surprised they are sending them to you when you say they are not delivering to your server.
I would expect that you can correlate the sending-mta-ip entries with entries in your MTA logs.
And there is no indication as to whether or not the report contains a failure, I have to open the JSON file to find out.
No. :-/
I want to RFC changed so that reports are only sent when there was a failure, like how I recall DMARC worked before I stopped using it due to the mail list false positive problem.
I personally like the reports for passes in addition to the failures. Much like backup jobs, I like to see that they are running. I configure a rule in my MUA to mark the messages as read, so they don't come to my attention as unread messages. Yet they are still there if / when I want to go look to see if the backups have been running.
Google assumes I have software receiving those messages that will decompress the archive and parse the JSON. I don't, and do not plan to. Reports should only be sent when there is an error to report. In my opinion.
I think that DMARC and MTA-STS are designed with the intent that something other than a human is going to be consuming the reports. Such is life. I don't know what I think of JSON vs XML vs something else.
I'm likely going to write something to receive the reports, extract and parse them to send me a summary. All passes will be marked as read. Any failures will be unread for me to look at.
-- Grant. . . . unix || die
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Uta mailing list Uta@ietf.org https://www.ietf.org/mailman/listinfo/uta
