On Sat, 2011-04-23 at 18:49 +0100, Niamh Holding wrote:
> KB> Besides, X-Spam-Relays-* are pseudo-headers, not part of the
> KB> email unless you specifically add_header them.
>
> I guess I must have done that to get them into every email :)
Oh, you really got that from the mail's headers? Yeah,
On Sat, 2011-04-23 at 18:49 +0100, Niamh Holding wrote:
> Hello Karsten,
>
> Saturday, April 23, 2011, 6:23:51 PM, you wrote:
>
> KB> Besides, X-Spam-Relays-* are pseudo-headers, not part of the
> KB> email unless you specifically add_header them.
>
> I guess I must have done that to get them in
Hello Karsten,
Saturday, April 23, 2011, 6:23:51 PM, you wrote:
KB> Besides, X-Spam-Relays-* are pseudo-headers, not part of the
KB> email unless you specifically add_header them.
I guess I must have done that to get them into every email :)
--
Best regards,
Niamh
On Sat, 2011-04-23 at 17:49 +0100, Niamh Holding wrote:
> KB> Other than the tool being broken, it is of course entirely possible you
> KB> simply typo'ed either the RE or the Relay pseudo-header -- a newline
> KB> easily would have done that.
>
> Cut'n'paste from locals.cf and the relevant header
Hello Karsten,
Saturday, April 23, 2011, 5:30:58 PM, you wrote:
KB> Other than the tool being broken, it is of course entirely possible you
KB> simply typo'ed either the RE or the Relay pseudo-header -- a newline
KB> easily would have done that.
Cut'n'paste from locals.cf and the relevant heade
On Sat, 2011-04-23 at 11:05 +0100, Niamh Holding wrote:
> KB> The regex tester is broken.
To be honest, it is not necessarily broken. I don't even know which tool
you used.
That comment should be understood as an emphasis of my previous detailed
explanation of the RE and the issues with it. Point
Hello Karsten,
Friday, April 22, 2011, 4:31:25 PM, you wrote:
KB> The regex tester is broken.
Anyone care to suggest a good tester that runs locally under XP
--
Best regards,
Niamhmailto:ni...@fullbore.co.uk
pgpvKD5l1UlCk.pgp
Description: PGP signature
Hello Karsten,
Friday, April 22, 2011, 7:09:06 PM, you wrote:
KB> Not permitting square brackets will indeed prevent a relay border
KB> between the rdns= key and the matched value, but since spaces are
KB> allowed, it happily matches e.g. helo= or by= values.
That did click eventually:)
--
On Fri, 2011-04-22 at 18:55 +0100, Niamh Holding wrote:
> KB> What you want instead is to match anything BUT a space /[^ ]+/. That
> KB> will prevent this part from matching beyond borders. More specifically,
> KB> it prevents matching any other data point and ensures the right hand
> KB> part actu
Hello Karsten,
Friday, April 22, 2011, 6:53:28 PM, you wrote:
KB> /^[^\]]+ rdns=[^ ]+\.no\.space\.there /
Ah I see what you meant now, and that wouldn't match where the
dip.tdialin.net was in the helo and not the rdns.
Thanks.
--
Best regards,
Niamhmailto:ni...@f
Hello Karsten,
Friday, April 22, 2011, 4:31:25 PM, you wrote:
KB> What you want instead is to match anything BUT a space /[^ ]+/. That
KB> will prevent this part from matching beyond borders. More specifically,
KB> it prevents matching any other data point and ensures the right hand
KB> part act
On Fri, 2011-04-22 at 17:51 +0100, Niamh Holding wrote:
> KB> What you want instead is to match anything BUT a space /[^ ]+/. That
> KB> will prevent this part from matching beyond borders. More specifically,
> KB> it prevents matching any other data point and ensures the right hand
> KB> part actu
Hello Michael,
Friday, April 22, 2011, 5:55:49 PM, you wrote:
MS> how about 'msa=0 \] \[ ip=.*rdns=.*dip\.t-dialin\.net/i'
But that'll definitely match into the second block, what I need is to
end the matching at the end of the first block ie the first ]
--
Best regards,
Niamh
On 4/22/11 12:51 PM, Niamh Holding wrote:
Hello Karsten,
Friday, April 22, 2011, 4:31:25 PM, you wrote:
KB> What you want instead is to match anything BUT a space /[^ ]+/. That
KB> will prevent this part from matching beyond borders. More specifically,
KB> it prevents matching any other data
Hello Karsten,
Friday, April 22, 2011, 4:31:25 PM, you wrote:
KB> What you want instead is to match anything BUT a space /[^ ]+/. That
KB> will prevent this part from matching beyond borders. More specifically,
KB> it prevents matching any other data point and ensures the right hand
KB> part act
On Fri, 2011-04-22 at 16:07 +0100, Niamh Holding wrote:
> I have a custom rule-
>
> header NH_TDIALIN X-Spam-Relays-Untrusted =~ /^[^\]]+
> rdns=.*dip\.t-dialin\.net/i
^^
The rdns= part correctly is in the first block. The above mar
On 4/22/11 11:07 AM, Niamh Holding wrote:
Hello
I have a custom rule-
header NH_TDIALIN X-Spam-Relays-Untrusted =~ /^[^\]]+
rdns=.*dip\.t-dialin\.net/i
scoreNH_TDIALIN 1.61
describe NH_TDIALIN Received directly from dynamic t-dialin.net address
postfix? #1, just reject at mta.!
if not,
Hello
I have a custom rule-
header NH_TDIALIN X-Spam-Relays-Untrusted =~ /^[^\]]+
rdns=.*dip\.t-dialin\.net/i
scoreNH_TDIALIN 1.61
describe NH_TDIALIN Received directly from dynamic t-dialin.net address
Now the regex should only match on anything in the first [...] block
of the X-Spam-Re
18 matches
Mail list logo
