Matt Kettler wrote:
...
>>
>>Is the whole trusted_net, dnsbl business written up somewhere? I would
>>rather not waste your time; but searching the wiki doesn't turn anything up.
>>
>>
>
>
>
> Not really, but I can go over it really fast..
>
>
> First, SA parses all the received headers, in b
Eric W. Bates wrote:
> Eric W. Bates wrote:
>> Matt Kettler wrote:
>>
>> ...
>>
>>> No, it could fire on *ANY* external IP that isn't the first hop.
> I don't think I was clear. I don't question that any IP in the chain
> might cause the difficuly. I was questioning why, if 127.0.0.1
Eric W. Bates wrote:
> Matt Kettler wrote:
>
> ...
>
>>No, it could fire on *ANY* external IP that isn't the first hop.
I don't think I was clear. I don't question that any IP in the chain
might cause the difficuly. I was questioning why, if 127.0.0.1 is the
problem, why it
Eric W. Bates wrote:
>
>
> Matt Kettler wrote:
>>> Eric W. Bates wrote:
>>>
Matt Kettler wrote:
> Eric W. Bates wrote:
>
>
>> I recently upgraded from 2.63 to 3.1 and having done so, my entries for
>> trusted_networks no longer seem to functional.
>>
>> I hav
Eric W. Bates wrote:
> Eric W. Bates wrote:
>>> Matt Kettler wrote:
>>>
Eric W. Bates wrote:
>
> ...
Maybe.. Were there any untrusted hosts in-between 68.64.105.61 and your
network
in the Received: headers?
>>>
>>> No. But even if there were, wouldn't the rule
Eric W. Bates wrote:
> Matt Kettler wrote:
>> Eric W. Bates wrote:
>>
>>> I recently upgraded from 2.63 to 3.1 and having done so, my entries for
>>> trusted_networks no longer seem to functional.
>>>
>>> I have way to many trusted network lines, but in particular I know that:
>>>
>>> trusted_netwo
Matt Kettler wrote:
> Eric W. Bates wrote:
>
>>I recently upgraded from 2.63 to 3.1 and having done so, my entries for
>>trusted_networks no longer seem to functional.
>>
>>I have way to many trusted network lines, but in particular I know that:
>>
>>trusted_networks68.64/13
>>
>>is no longer
Eric W. Bates wrote:
> I recently upgraded from 2.63 to 3.1 and having done so, my entries for
> trusted_networks no longer seem to functional.
>
> I have way to many trusted network lines, but in particular I know that:
>
> trusted_networks68.64/13
>
> is no longer working because:
>
> Con
I recently upgraded from 2.63 to 3.1 and having done so, my entries for
trusted_networks no longer seem to functional.
I have way to many trusted network lines, but in particular I know that:
trusted_networks68.64/13
is no longer working because:
Content analysis details: (5.9 points, 5.0