On 11/18/24 9:08 AM, Michael Richardson wrote:
The message about the spam was in fact spam. But, it forged a valid From: so it got through. I'd like to fix the SPF/DKIM/spam-filter such that it more aggressively kills this kind of forgery, assuming that wireshark.org has the right policies set. This kind of thing is fraught with false-positives, but there are some reasonable howtos.
wireshark.org should have valid SPF and DKIM records. If the problem is limited to my address, I can subscribe from another one and you can just block my wireshark.org address if that's easier. _______________________________________________ tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
