Wietse Venema:
> In summary, there are two orthogonal features that should not be
> mixed up:
>
> - routine logging, which currently does not exist for permit actions.
> This requires one-time infrastructure code for "permit" logging,
> and calls to that infrastructure from a half-dozen strategic
Noel Jones:
> No, of course not. You perform the restriction twice; the warn_if_
> is log-only, the second is live. You can do this now with
> warn_if_reject reject_rbl_client list.dnswl.org to log the hit.
>
> > I think I prefer Wietse's implementation idea.
>
> Yes, very useful general soluti
On 2/27/2012 2:15 AM, Stan Hoeppner wrote:
> On 2/27/2012 1:12 AM, Stan Hoeppner wrote:
>> On 2/26/2012 4:50 PM, /dev/rob0 wrote:
>>
>>> A "warn_if_permit" similar to "warn_if_reject" might make more sense
>>> and be more generic. I agree with your reasoning that the feature
>>> would be useful.
On 2/27/2012 1:12 AM, Stan Hoeppner wrote:
> On 2/26/2012 4:50 PM, /dev/rob0 wrote:
>
>> A "warn_if_permit" similar to "warn_if_reject" might make more sense
>> and be more generic. I agree with your reasoning that the feature
>> would be useful.
>>
>> "warn_if_reject" negates the following rest
On 2/26/2012 4:55 PM, Wietse Venema wrote:
> Stan Hoeppner:
>> On 2/26/2012 2:15 PM, Wietse Venema wrote:
>>> Stan Hoeppner:
I can't seem to find any logging of permit_dnswl_client actions. Maybe
I just don't know what to grep for. I would like to be able to track
such data.
>>>
>>
On 2/26/2012 4:50 PM, /dev/rob0 wrote:
> A "warn_if_permit" similar to "warn_if_reject" might make more sense
> and be more generic. I agree with your reasoning that the feature
> would be useful.
>
> "warn_if_reject" negates the following restriction, and likewise
> should "warn_if_permit". T
Stan Hoeppner:
> On 2/26/2012 2:15 PM, Wietse Venema wrote:
> > Stan Hoeppner:
> >> I can't seem to find any logging of permit_dnswl_client actions. Maybe
> >> I just don't know what to grep for. I would like to be able to track
> >> such data.
> >
> > Are there any "permit" features that log th
On Sun, Feb 26, 2012 at 04:08:04PM -0600, Stan Hoeppner wrote:
> Since I started using Postfix in 2005, I've come across situations
> where it would have been nice to enable logging of certain permit
> actions, sometimes just temporarily, other times more permanently;
> the former to aid trouble
On 2/26/2012 2:15 PM, Wietse Venema wrote:
> Stan Hoeppner:
>> I can't seem to find any logging of permit_dnswl_client actions. Maybe
>> I just don't know what to grep for. I would like to be able to track
>> such data.
>
> Are there any "permit" features that log their decision?
No.
> Hard-co
Stan Hoeppner:
> I can't seem to find any logging of permit_dnswl_client actions. Maybe
> I just don't know what to grep for. I would like to be able to track
> such data.
Are there any "permit" features that log their decision?
Hard-coding it "on" only for some would make little sense.
I can't seem to find any logging of permit_dnswl_client actions. Maybe
I just don't know what to grep for. I would like to be able to track
such data.
--
Stan
11 matches
Mail list logo
