Do you have an SA rule for it?
On Fri, 31 Aug 2018, John Hardin wrote:
None of the masscheck corpora that hit __HDR_ORDER_FTSDMC also hit
ALL_TRUSTED (or at least the portion is so small it falls off the bottom of
the report) so I don't feel too worried about adding either !ALL_TRUSTED or
__ANY_EXTERNAL (or potentially
On Fri, 31 Aug 2018, John Hardin wrote:
On Fri, 31 Aug 2018, Matus UHLAR - fantomas wrote:
On Thu, 30 Aug 2018, Matus UHLAR - fantomas wrote:
That further causes hitting HDR_ORDER_FTSDMCXX_DIRECT and
HDR_ORDER_FTSDMCXX_NORDNS in cases where client uses the mail client on
local network, withou
You are correct Pedro, the curly-braces solution does work. I will
integrate the solution, I leave it to you guys to determine if a bug
should be opened and with whom.
On 2018-08-31 15:01, Pedro David Marco wrote:
It works with Perl 5.14.2 but not with 5.20.2
It seems that Perl preprocessor d
On Fri, 31 Aug 2018, Matus UHLAR - fantomas wrote:
On Thu, 30 Aug 2018, Matus UHLAR - fantomas wrote:
That further causes hitting HDR_ORDER_FTSDMCXX_DIRECT and
HDR_ORDER_FTSDMCXX_NORDNS in cases where client uses the mail client on
local network, without SMTP authentication, and without DNS (wh
It works with Perl 5.14.2 but not with 5.20.2
It seems that Perl preprocessor does something with repeated chars before the
regex engine that makes it consider it wrongly
if i change ss for s{2} like this:
body __Z_NEGATIVE_LOOKBEHIND /(?On Friday, August 31, 2018, 4:00:05 PM GMT+2, Ol
Likely best to try against svn for 3.4 and trunk where I expect it will
fail and we have to open a bug.
On Fri, Aug 31, 2018, 10:42 RW wrote:
> On Fri, 31 Aug 2018 09:59:52 -0400
> Olivier Coutu wrote:
>
> > I wrote a rule that throws a /variable length lookbehind/ error where
> > the lookbehind
On 31 Aug 2018, at 4:53, Matus UHLAR - fantomas wrote:
Long time ago I learned to configure dynamic IP addresses (dialups) as
trusted, but not as internal.
On 31.08.18 09:37, Bill Cole wrote:
They probably should be neither.
In this case, clients are internal, not dialup, but I still think
On Fri, 31 Aug 2018 09:59:52 -0400
Olivier Coutu wrote:
> I wrote a rule that throws a /variable length lookbehind/ error where
> the lookbehind is fixed length. Here is a MWE:
>
> body __Z_NEGATIVE_LOOKBEHIND /(?
> spamassassin --siteconfigpath=${HOME}/sa-rules/ --lint
> aoû 31 09:
I wrote a rule that throws a /variable length lookbehind/ error where
the lookbehind is fixed length. Here is a MWE:
body __Z_NEGATIVE_LOOKBEHIND /(?The error goes away if I remove the case insensitive, or if I put a
character between the two /s/ characters. Using /nn/ instead of /s
On 31 Aug 2018, at 4:05, Matus UHLAR - fantomas wrote:
On 08/30/2018 10:16 AM, Bill Cole wrote:
It's hard to understand this circumstance based on the generic
description.
It appears that you have a configuration where a relay is in
trusted_networks (i.e. you believe what it asserts in Recei
On 31 Aug 2018, at 4:53, Matus UHLAR - fantomas wrote:
Note that I list internal clients as trusted, not as internal.
Maybe this is the problem.
Yes, maybe...
Long time ago I learned to configure dynamic IP addresses (dialups) as
trusted, but not as internal.
They probably should be neith
I have not checked whether SA orders the Received headers in correct date/time
sequence but if not, remember that many Microsoft products change whimsically
the order of Receiveds headers (Kevin sharks are starving)...
PedroD
On Thu, 30 Aug 2018, Matus UHLAR - fantomas wrote:
That further causes hitting HDR_ORDER_FTSDMCXX_DIRECT and
HDR_ORDER_FTSDMCXX_NORDNS in cases where client uses the mail client on
local network, without SMTP authentication, and without DNS (which may be
quite common in some organizations).
On
On Thu, 30 Aug 2018 12:16:33 -0400
Bill Cole wrote:
I think the fix for all is for everyone to get their
internal_networks and trusted_networks configurations correct.
On 30.08.18 20:35, RW wrote:
Whatever is happening in this particular case (whatever that is), any
rule that works on last-ext
On 08/30/2018 10:16 AM, Bill Cole wrote:
It's hard to understand this circumstance based on the generic description.
It appears that you have a configuration where a relay is in
trusted_networks (i.e. you believe what it asserts in Received headers)
but it is NOT in internal_networks so it is i
16 matches
Mail list logo
