-
Notifications
You must be signed in to change notification settings - Fork 225
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TLS Reports from microsoft.com are not parsed #561
Comments
Running the raw json file you provided through |
Will this option suit you? --a737a3b9-5ea5-40e8-a971-a67ecbb2993e This is an aggregate TLS report from microsoft.com
Microsoft respects your privacy. Review our online Privacy Statement<=
/em> --a737a3b9-5ea5-40e8-a971-a67ecbb2993e H4sIAAAAAAAEAH2STWvDMAyG/0rwdXVwPpa1Pg123qk9dZThOU4wxFawldKs5L9PSdsxBi0ILPt9 --a737a3b9-5ea5-40e8-a971-a67ecbb2993e-- |
@seanthegeek, is the answer provided appropriate? |
Yes. The problem is a mistake in the email headers when Microsoft is generating the tlsrpt email. You can verify this by pasting the content you provided into a The mistake is here, where the Content-Type: multipart/report;
boundary="a737a3b9-5ea5-40e8-a971-a67ecbb2993e"; report-type=tlsrpt If you combine the content into one line Content-Type: multipart/report; boundary="a737a3b9-5ea5-40e8-a971-a67ecbb2993e"; report-type=tlsrpt Or indent the second line Content-Type: multipart/report;
boundary="a737a3b9-5ea5-40e8-a971-a67ecbb2993e"; report-type=tlsrpt Then the email will be successfully parsed by Thunderbird and parsedmarc. I'll see if I can find someone at Microsoft to address this. |
@makuartur Actually, looking at this again, it looks like GitHub removed all of the indents when you pasted in the sample as test, Please save the sample as a file, then drag and prop that file into the comment box to make it an attachment. |
mail.txt |
Hmm. the parsedmarc CLI parsed the email correctly, so I'm not sure why it would be moved to the invalid folder. Can you try updating to the latest release of parsedmarc, moving one of the emails from the invalid folder back to the inbox and see if the same thing happens again? |
The TLS report from microsoft.com wasn't parsed and was moved to the invalid folder
From:
tlsrpt-noreply@microsoft.com
Subject:
Report Domain: <domain_name>
Submitter: microsoft.com
Report-ID: ^[0-9]{18}+<domain_name>
Body:
_This is an aggregate TLS report from microsoft.com
Microsoft respects your privacy. Please review our online Privacy Statement.
Microsoft Corporation
One Microsoft Way
Redmond, WA, USA 98052_
Attached filename:
microsoft.com!domain_name!1725840000!1725926399!report_id.json.gz
Content of the file:
parsedmarc version: 8.14.1
The text was updated successfully, but these errors were encountered: