For example the following transaction will not show any errors in SYSLOG:
In: AUTH LOGIN
Out: 503 5.5.1 Error: authentication not enabled
In: QUIT
Out: 221 2.0.0 Bye
You can use the existing notify_classes based mechamism and pipe
that into syslog.
notify_classes = protocol, ...
Kevin N.:
> > Kevin N.:
> >> For example the following transaction will not show any errors in SYSLOG:
> >>
> >> In: AUTH LOGIN
> >> Out: 503 5.5.1 Error: authentication not enabled
> >> In: QUIT
> >> Out: 221 2.0.0 Bye
> >
> > You can use the existing notify_classes based mechamism and pipe
> >
For example the following transaction will not show any errors in
SYSLOG:
In: AUTH LOGIN
Out: 503 5.5.1 Error: authentication not enabled
In: QUIT
Out: 221 2.0.0 Bye
You can use the existing notify_classes based mechamism and pipe
that into syslog.
notify_classes = protocol, ...
e
Kevin N.:
For example the following transaction will not show any errors in SYSLOG:
In: AUTH LOGIN
Out: 503 5.5.1 Error: authentication not enabled
In: QUIT
Out: 221 2.0.0 Bye
You can use the existing notify_classes based mechamism and pipe
that into syslog.
notify_classes = protocol,
Kevin N.:
> For example the following transaction will not show any errors in SYSLOG:
>
> In: AUTH LOGIN
> Out: 503 5.5.1 Error: authentication not enabled
> In: QUIT
> Out: 221 2.0.0 Bye
You can use the existing notify_classes based mechamism and pipe
that into syslog.
notify_classes = pr
It would be nice to have an option to enable logging to SYSLOG the SMTP
protocol errors that occur during a SMTP session, along with the SMTP
commands that caused them.
As far as I know, currently these errors can be logged to SYSLOG only by
one of the following methods:
1. By making the SMT
