Date: Sat, 06 Dec 2025 07:56:48 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 243847] [NEW PORT] mail/py-parsedmarc: DMARC report analyzer and visualizer Message-ID: <bug-243847-21822-ujsxr9qggx@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-243847-21822@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243847 --- Comment #7 from ml@netfence.it --- (In reply to Mark Linimon from comment #6) It's been in my "local" ports and I've been using it for years. If I'm the only one interested, it's fine like that. Notice there's a problem with 2025Q4: I'm not sure whether this is a bug in this port or general to the port tree. I asked on the ML, but received no answer, so I "fixed" my port tree locally. See: https://lists.freebsd.org/archives/freebsd-ports/2025-October/008563.html Also this port is alredy a lot of versions behind. I once checked if it could be upgraded, but some dependencies were missing. Since it just works (for me), I didn't bother to check again. Finally, there's a bug which I'm fixing locally: https://github.com/domainaware/parsedmarc/issues/258 This fix was not solved upstream and is not in the patch above. In the end, if there is interest, I can try (not that soon) to do some work in order to bring this in a state that's not a shame to publish. So far (i.e. in the last four years) I didn't receive any feedback, though. -- You are receiving this mail because: You are on the CC list for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-243847-21822-ujsxr9qggx>