You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I've upgraded to 8.12.0 and had a typo on the nameserver parameter in config file, which looked like this (notice the IP address ending in 333):
This typo caused parsedmarc to not recognize any of the reports given to it.
INFO:cli.py:1023:Starting parsedmarc
DEBUG:__init__.py:1244:Parsing whatever.xml.gz
ERROR:cli.py:1200:Failed to parse whatever.xml.gz - Not a valid report
If I correct the typo, without any other change to the config file or the reports, and they get processed without any problem:
INFO:cli.py:1023:Starting parsedmarc
DEBUG:__init__.py:1244:Parsing whatever.xml.gz
WARNING:utils.py:165:get_reverse_dns(AAA.BBB.CCC.DDD) exception: The DNS query name does not exist: DDD.CCC.BBB.AAA.in-addr.arpa.
DEBUG:utils.py:422:IP address AAA.BBB.CCC.DDD reverse_dns not found
INFO:elastic.py:369:Saving aggregate report to Elasticsearch
WARNING:cli.py:100:An aggregate report ID 282692$6727846=00b96be3def2a634 from example.com about mydomain.org with a date range of 2023-11-16 23:00:03Z UTC to 2023-11-17 23:00:02Z UTC already exists in Elasticsearch
Thank you very much.
The text was updated successfully, but these errors were encountered:
spaolo
added a commit
to spaolo/parsedmarc
that referenced
this issue
Sep 18, 2024
Hello,
I've upgraded to 8.12.0 and had a typo on the nameserver parameter in config file, which looked like this (notice the IP address ending in 333):
nameserver = 10.10.10.1,10.10.10.2,10.10.10.333,10.10.10.4
This typo caused parsedmarc to not recognize any of the reports given to it.
If I correct the typo, without any other change to the config file or the reports, and they get processed without any problem:
Thank you very much.
The text was updated successfully, but these errors were encountered: