On Wed, 23 Mar 2016 14:36:08 -0000 Kevin Golding wrote: > On Wed, 23 Mar 2016 14:04:03 -0000, RW <rwmailli...@googlemail.com> > wrote: > > > On Wed, 23 Mar 2016 13:45:29 -0000 > > Kevin Golding wrote: > > > >> On Wed, 23 Mar 2016 12:30:43 -0000, Matus UHLAR - fantomas > >> <uh...@fantomas.sk> wrote: > >> > >> > On 23.03.16 11:56, Kevin Golding wrote: > >> >> I can't figure this one out so I'll throw it out. > >> >> > >> >> When receiving mail from the address b...@e.bbcmail.co.uk > >> >> > >> >> def_whitelist_auth *@*.bbcmail.co.uk # is not whitelisted > >> > > >> > well, it should be, but only -15 points, sice it's def_whitelist > >> > and not whitelist. check for this carefully... > >> > > >> > >> Alas, definitely not: > >> > >> Mar 23 11:17:44.805 [15610] dbg: dkim: VALID signature by > >> e.bbcmail.co.uk, author b...@e.bbcmail.co.uk, no valid matches > >> Mar 23 11:17:44.805 [15610] dbg: dkim: author b...@e.bbcmail.co.uk, > >> not in any dkim whitelist > > > > > > do you have debug where b...@e.bbcmail.co.uk both matches and fails > > on on the pattern *@*.bbcmail.co.uk on the _same_ scan? > > > > I assume you mean can I show it matching on the same message? Since > if I have both enabled on a scan it's just a case of the first to hit > will be displayed I believe, and any failures won't show at all. With > both enabled I get:
The original post had: def_whitelist_auth *@*.bbcmail.co.uk # is not whitelisted whitelist_from_dkim *@*.bbcmail.co.uk # is whitelisted which I presumed meant that both lines were present in your config and mail from b...@e.bbcmail.co.uk was hitting USER_IN_DKIM_WHITELIST, but not USER_IN_DEF_DKIM_WL. I wanted to see the debug for the case where one rule works as expected and the other doesn't - and it's important to see this on the same mail. The first two debug entries below show both def and normal whitelist hits working properly, but they are confused by a *@bbcmail.co.uk whitelisting entry which you say fixes the problem. Below that you have a def_whitelist_auth match with *@bbcmail.co.uk. All that you are illustrating here is that *@bbcmail.co.uk works as expected, not that *@*bbcmail.co.uk fails on anything. > Mar 23 15:26:55.945 [27188] dbg: dkim: VALID author domain signature > by e.bbcmail.co.uk, MATCHES whitelist_from_dkim > (?^i:^.*\@.*\.bbcmail\.co\.uk$) > Mar 23 15:26:55.945 [27188] dbg: dkim: author b...@e.bbcmail.co.uk, > WHITELISTED by whitelist_from_dkim/e.bbcmail.co.uk > > And def_whitelist_auth will match on both the full address: > > Mar 23 11:21:52.535 [15896] dbg: dkim: VALID author domain signature > by e.bbcmail.co.uk, MATCHES def_whitelist_auth > ^bbc\@e\.bbcmail\.co\.uk$ Mar 23 11:21:52.535 [15896] dbg: dkim: > author b...@e.bbcmail.co.uk, WHITELISTED by > def_whitelist_auth/e.bbcmail.co.uk > > And also if I only wildcard the user part: > > Mar 23 11:25:12.688 [16086] dbg: dkim: VALID author domain signature > by e.bbcmail.co.uk, MATCHES def_whitelist_auth > ^.*\@e\.bbcmail\.co\.uk$ Mar 23 11:25:12.688 [16086] dbg: dkim: > author b...@e.bbcmail.co.uk, WHITELISTED by > def_whitelist_auth/e.bbcmail.co.uk > > It only fails on def_whitelist_auth *@*.bbcmail.co.uk > > Same message each time, the only variation on the scans are the > whitelist settings.
