Mehmet Avcioglu:
> On Tue, Dec 20, 2022 at 9:57 PM Wietse Venema wrote:
>
> > However, Postfix does make information from multiple layers available
> > for policy decisions:
>
> Thank you. Yes I am using milter extensively, however I am trying to
> influence and log transport and sender dependen
On Tue, Dec 20, 2022 at 10:20 PM Mehmet Avcioglu wrote:
> Also I know syslog_name has a max length, but couldn't find the
> documentation on it.
>
Sorry, what I am referring to is probably a syslog limitation, not
postfix.
On Tue, Dec 20, 2022 at 9:57 PM Wietse Venema wrote:
> However, Postfix does make information from multiple layers available
> for policy decisions:
>
Thank you. Yes I am using milter extensively, however I am trying to
influence and log transport and sender dependent transport decisions based
o
Mehmet Avcioglu:
> On Sun, Dec 11, 2022 at 3:27 PM Mehmet Avcioglu wrote:
>
> > Is it possible to log the result of a table lookup? Perhaps similar to the
> > header_checks INFO option.
>
> I guess it is not.
>
> I can write a daemon that acts like a tcp map and log the results, but I
> wouldn'
On Sun, Dec 11, 2022 at 3:27 PM Mehmet Avcioglu wrote:
> Is it possible to log the result of a table lookup? Perhaps similar to the
> header_checks INFO option.
>
I guess it is not.
I can write a daemon that acts like a tcp map and log the results, but I
wouldn't be able to match those log line
On Sun, Dec 11, 2022 at 03:27:43PM +0300, Mehmet Avcioglu wrote:
> Is it possible to log the result of a table lookup? Perhaps similar to the
> header_checks INFO option.
No. There is presently no syntax for tables that log lookup keys and
results.
If you want to log table lookups on a temporar
Is it possible to log the result of a table lookup? Perhaps similar to the
header_checks INFO option.
Thanks
--
Mehmet
