On Fri, 6 Oct 2023, Wietse Venema via Postfix-users wrote:
> Jozsef Kadlecsik via Postfix-users:
> > +sasl_username = xsasl_server_get_username(state->sasl_server);
> > +if (sasl_username != 0) {
> > + state->sasl_username = mystrdup(sasl_username)
Hello,
On Fri, 6 Oct 2023, Wietse Venema via Postfix-users wrote:
> Has this been tested:
>
> - With Cyrus SASL?
>
> - With Dovecot auth?
It was tested with Cyrus SASL only.
> - With malformed AUTH commands?
No, I tested valid AUTH commands with successful and unsuccessful
authentications
On Fri, 6 Oct 2023, Jozsef Kadlecsik via Postfix-users wrote:
> However it's a debug mode, cannot be used in production. It is clear that
> SASL protocol is not implemented and thus the messages have no meaning,
> just reported. However, it seems the data is there and available.
Hi Wietse,
On Fri, 6 Oct 2023, Wietse Venema via Postfix-users wrote:
> Jozsef Kadlecsik via Postfix-users:
> > Hi,
> >
> > Is there a way to get the SASL username logged for the failed
> > authentications together with the client IP data? Postfix can log half
Hi,
Is there a way to get the SASL username logged for the failed
authentications together with the client IP data? Postfix can log half of
the information the connecting client IP address, while Cyrus saslauthd
the second one the username. However there's no clear way (except the
timestamp) t
