From c417fc5d2aaa371112551087d6652b7f097e8010 Mon Sep 17 00:00:00 2001 From: Sean Whalen Date: Mon, 5 Feb 2018 23:11:53 -0500 Subject: [PATCH] 1.0.3 --- _modules/index.html | 8 ++++---- _modules/parsedmarc.html | 10 +++++----- _sources/index.rst.txt | 1 + genindex.html | 8 ++++---- index.html | 34 ++++++++++++++++++---------------- objects.inv | 2 +- py-modindex.html | 8 ++++---- search.html | 8 ++++---- 8 files changed, 41 insertions(+), 38 deletions(-) diff --git a/_modules/index.html b/_modules/index.html index fa44567..b490e19 100644 --- a/_modules/index.html +++ b/_modules/index.html @@ -8,7 +8,7 @@ - Overview: module code — parsedmarc 1.0.2 documentation + Overview: module code — parsedmarc 1.0.3 documentation @@ -35,7 +35,7 @@ - + @@ -64,7 +64,7 @@
- 1.0.2 + 1.0.3
@@ -187,7 +187,7 @@ @@ -65,7 +65,7 @@
- 1.0.2 + 1.0.3
@@ -218,7 +218,7 @@ @@ -64,7 +64,7 @@
- 1.0.2 + 1.0.3
@@ -90,7 +90,7 @@
@@ -170,9 +172,8 @@

Welcome to parsedmarc’s documentation!

Build Status

pasedmarc is a Python module and CLI utility for parsing aggregate DMARC reports.

-
-

Features

+

Features

-

CLI help

+

CLI help

usage: parsedmarc.py [-h] [-f FORMAT] [-o OUTPUT]
                      [-n NAMESERVER [NAMESERVER ...]] [-t TIMEOUT] [-v]
                      file_path [file_path ...]
@@ -210,7 +211,7 @@
-

Sample output

+

Sample output

Here are the results from parsing the example report from the dmarc.org wiki. It’s actually an older draft of the the 1.0 report schema standardized in @@ -218,7 +219,7 @@ report schema standardized in This draft schema is still in wide use.

parsedmarc produces consistent, normalized output, regardless of the report schema.

-

JSON

+

JSON

{
   "xml_schema": "draft",
   "report_metadata": {
@@ -282,7 +283,7 @@ This draft schema is still in wide use.
-

CSV

+

CSV

xml_schema,org_name,org_email,org_extra_contact_info,report_id,begin_date,end_date,errors,domain,adkim,aspf,p,sp,pct,fo,source_ip_address,source_country,source_reverse_dns,source_base_domain,count,disposition,dkim_alignment,spf_alignment,policy_override_reasons,policy_override_comments,envelope_from,header_from,envelope_to,dkim_domains,dkim_selectors,dkim_results,spf_domains,spf_scopes,spf_results
 draft,acme.com,noreply-dmarc-support@acme.com,http://acme.com/dmarc/support,9391651994964116463,2012-04-27 20:00:00,2012-04-28 19:59:59,[],example.com,r,r,none,none,100,0,72.150.241.94,US,adsl-72-150-241-94.shv.bellsouth.net,bellsouth.net,2,none,fail,pass,,,example.com,example.com,,example.com,none,fail,example.com,mfrom,pass
@@ -290,7 +291,7 @@ This draft schema is still in wide use.

-

What about forensic DMARC reports?

+

What about forensic DMARC reports?

Forensic DMARC reports are emails with an attached email sample that failed a DMARC check. You can parse them with any email message parser, such as mail-parser.

@@ -299,12 +300,12 @@ provide only the message headers, and not the message’s content, for privacy reasons.

-

Bug reports

+

Bug reports

Please report bugs on the GitHub issue tracker

https://github.com/domainaware/parsedmarc/issues

-

Installation

+

Installation

parsedmarc works with Python 2 or 3, but Python 3 is preferred.

On Debian or Ubuntu systems, run:

$ sudo apt-get install python3-pip
@@ -326,7 +327,7 @@ substitute pip as
-

API

+

API

A Python module and CLI for parsing aggregate DMARC reports

@@ -408,12 +409,13 @@ headers

-

Indices and tables

+

Indices and tables

+
@@ -451,7 +453,7 @@ headers

@@ -64,7 +64,7 @@
- 1.0.2 + 1.0.3
@@ -195,7 +195,7 @@