Hi Kevin, On Wed, Jun 21, 2017 at 8:31 PM, John Hardin <jhar...@impsec.org> wrote: > On Wed, 21 Jun 2017, Alex wrote: >> On Wed, Jun 21, 2017 at 8:06 PM, Reindl Harald <h.rei...@thelounge.net> >> wrote: >>> Am 22.06.2017 um 01:55 schrieb Alex: >>>> >>>> >>>> Can someone else confirm this? John was unable to reproduce it on his >>>> system, but I just installed the latest svn 3.4.2 branch and it's >>>> doing it here. I'd appreciate if someone could help me figure out if >>>> this is a bug, a local misconfiguration or otherwise... >>>> >>>> https://pastebin.com/inS6qiiG >>> >>> >>> i guess you have "parse_dkim_uris" enabled as i have which is fine for >>> URIBL an so on but don't justify body_uri >> >> >> Ah, I do. It's enabled in the KAM.cf ruleset from Kevin. > > ...and I don't. Good catch. > >> Maybe Kevin or someone with knowledge of this could comment, as it >> effectively eliminates the effectiveness of the __EMPTY_BODY and >> __HAS_ANY_URI. > > It looks like there might need to be a separate URI store for that, which is > not shared with genuine body URIs.
Do you have any thoughts on this? It appears the parse_dkim_uris in your KAM.cf is effectively disabling the __EMPTY_BODY and __HAS_ANY_URI rules because they match against the DKIM header.
