On Tuesday October 9 2007 20:19:36 Loren Wilton wrote:
> > To me it looks like a misfeature.
>
> I think I would agree that it may be a misfeature in the case of this
> specific header. In general though it may not be. Consider the case of
> two separate Subject: headers, often with completely di
To me it looks like a misfeature.
I think I would agree that it may be a misfeature in the case of this
specific header. In general though it may not be. Consider the case of two
separate Subject: headers, often with completely different subjects. There
was a time that was a quite decent s
Per Jessen writes:
> Mark Martinec wrote:
>
> > Per,
> >
> >> X-Originating-IP: [17.148.16.66]
> >> X-Originating-IP: 134.32.140.207
> > ...
> >> It looks to me like the two X-Originating-IP lines are merged into
> >> one, and my regex is then applied to:
> >>
> >> X-Originating-IP: [17.148.16.6
Mark Martinec wrote:
> Per,
>
>> X-Originating-IP: [17.148.16.66]
>> X-Originating-IP: 134.32.140.207
> ...
>> It looks to me like the two X-Originating-IP lines are merged into
>> one, and my regex is then applied to:
>>
>> X-Originating-IP: [17.148.16.66]134.32.140.207
>
> True (with newline i
Per,
> X-Originating-IP: [17.148.16.66]
> X-Originating-IP: 134.32.140.207
...
> It looks to me like the two X-Originating-IP lines are merged into
> one, and my regex is then applied to:
>
> X-Originating-IP: [17.148.16.66]134.32.140.207
True (with newline inbetween).
> Is this normal/correct b
I've got a rule for spotting a dodgy X-Originating-IP:
header PJ_BOGUS_XORIGIN X-Originating-IP =~ /\.([3-9][^. ][^. ]+|2[6-9][^.
]+|25[6-9][^. ]*)\./
I was investigating an unusual hit, when I noticed the following:
It will produce a positive hit when an email contains two lines like these:
