francis picabia:
[ Charset ISO-8859-1 unsupported, converting... ]
> On Tue, Oct 2, 2012 at 9:20 PM, Wietse Venema wrote:
>
> > Nope. If you were testing this more carefully then you would have
> > found that upper or lower case does not matter in this context.
>
> I tested the exact same line w
On Tue, Oct 2, 2012 at 9:20 PM, Wietse Venema wrote:
> Nope. If you were testing this more carefully then you would have
> found that upper or lower case does not matter in this context.
I tested the exact same line with PERMIT and permit.
permit allowed the whitelist entry to work.
PERMIT gene
francis picabia:
> On Tue, Oct 2, 2012 at 4:36 PM, Wietse Venema wrote:
> > francis picabia:
> > [ Charset ISO-8859-1 unsupported, converting... ]
> >> I now notice there is a warning in the log file only when the
> >> postscreen_access
> >> file is read (and should have matched):
> >>
> >> Oct
On Tue, Oct 2, 2012 at 4:36 PM, Wietse Venema wrote:
> francis picabia:
> [ Charset ISO-8859-1 unsupported, converting... ]
>> I now notice there is a warning in the log file only when the
>> postscreen_access
>> file is read (and should have matched):
>>
>> Oct 2 15:41:05 mx10 postfix/postscree
francis picabia:
[ Charset ISO-8859-1 unsupported, converting... ]
> I now notice there is a warning in the log file only when the
> postscreen_access
> file is read (and should have matched):
>
> Oct 2 15:41:05 mx10 postfix/postscreen[11731]: warning:
> cidr:/etc/postfix/postscreen_access: unkn
I now notice there is a warning in the log file only when the postscreen_access
file is read (and should have matched):
Oct 2 15:41:05 mx10 postfix/postscreen[11731]: warning:
cidr:/etc/postfix/postscreen_access: unknown command: OK -- ignoring
the remainder of this access list
Also same warning
