Missing logging from Cyrus LASL set to use sasldb

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Missing logging from Cyrus LASL set to use sasldb

Brian Wengel
Is it possible to get logging from Cyrus LASL set to use sasldb?

I don't get much using sasldb:

Jan 12 12:55:06 SRV07 postfix/smtpd[6204]: connect from localhost[127.0.0.1]
Jan 12 12:55:27 SRV07 postfix/smtpd[6204]: warning: localhost[127.0.0.1]: SASL login authentication failed: authentication failure
Jan 12 12:55:29 SRV07 postfix/smtpd[6204]: disconnect from localhost[127.0.0.1] ehlo=1 auth=0/1 quit=1 commands=2/3  


If I set Cyrus LASL to use saslauthd I do get some more logging:

Jan 12 11:24:25 SRV07 saslauthd[18450]: pam_unix(smtp:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=  user=bw
Jan 12 11:24:27 SRV07 saslauthd[18450]: DEBUG: auth_pam: pam_authenticate failed: Authentication failure
Jan 12 11:24:27 SRV07 saslauthd[18450]:                 : auth failure: [user=bw] [service=smtp] [realm=] [mech=pam] [reason=PAM auth error]


My Cyrus LASL config-file ( /etc/postfix/sasl/smtpd.conf ) 
pwcheck_method: auxprop
auxprop_plugin: sasldb
mech_list: PLAIN LOGIN
log_level: 7

I'm using Debian buster, Postfix ver. 3.4.7

Also tried to use a specific postfix logfile by settiing the following in main.cf:
maillog_file = /var/log/postfix.log

I didn't give me anymore logging.

The Cyrus LASL documentation says the followiing:
log_level (default: 1)
Specifies a numeric log level. Available log levels are:

0: Don't log anything
1: Log unusual errors
2: Log all authentication failures
3: Log non-fatal warnings
4: More verbose than 3
5: More verbose than 4
6: Traces of internal protocols
7: Traces of internal protocols, including passwords

Important
Cyrus SASL sends log messages to the application that runs it.
The application decides if it forwards such messages to the syslog service,
to which facility they are sent and which priority is given to the message.



Reply | Threaded
Open this post in threaded view
|

Re: Missing logging from Cyrus LASL set to use sasldb

Wietse Venema
Brian Wengel:
> Is it possible to get logging from Cyrus LASL set to use *sasldb*?

I'm not using that code, so it will be hard for me do test changes.

        Wietse