I saw #89 and made a bash script to work them one by one. (That's slow as heck by the way as the startup takes more time than parsing one file.) But parsedmarc is unaware of the existing json files, creating invalid json. As it's unaware, it will also append already parsed files over and over.
If you added an argument for passing paths, that'd work around CLI limits and be much faster than running a gazillion times.
(Don't take this as too important/necessary, I don't even know, if I'll use parsedmarc in the future. I wanted a simple offline non-web-based tool to aggregate reports and thought I may be able to plug the json somewhere else, make something in gnuplot etc. that does not involve big fat elastic/kibana.)
Hi
I saw #89 and made a bash script to work them one by one. (That's slow as heck by the way as the startup takes more time than parsing one file.) But parsedmarc is unaware of the existing json files, creating invalid json. As it's unaware, it will also append already parsed files over and over.
If you added an argument for passing paths, that'd work around CLI limits and be much faster than running a gazillion times.
(Don't take this as too important/necessary, I don't even know, if I'll use parsedmarc in the future. I wanted a simple offline non-web-based tool to aggregate reports and thought I may be able to plug the json somewhere else, make something in gnuplot etc. that does not involve big fat elastic/kibana.)
Cheers