Duplicate report_id methodology
Closed this issue · 0 comments
Deleted user commented
There's a problem in the parser as it checks for duplicate report ID's and skips them when found. This leads to incorrect results as there are multiple DMARC Aggregators that use the same nomenclature for reports so it is very possible that you receive multiple reports with the same ID for a single domain.
These reports cannot be skipped, but have to be parsed as unique reports.
As there are foreign constraints on the report_id key, the only workaround currently is to add a random prefix before the report_id and pass this on to the INSERT query.
code part : lines 79-92