Should dovecot not be using different logging facility and severity levels?
Should dovecot not be using different severity levels like auth.warn? On my system everything goes to loglevel info:
lev_info:Aug 9 16:18:24 mail03 dovecot: imap-login: Aborted login (auth
failed, 1 attempts in 2 secs): user=<xxxxx>, method=PLAIN, rip=x.x.x.x,
lip=x.x.x.x, TLS, session=
This is how failed attempts are logged by vsftpd
fac_authpriv:Aug 9 16:24:42 web01 vsftpd[7255]: pam_ldap(vsftpd:auth): Authentication failure; user=xxxxx fac_authpriv:Aug 9 16:24:42 web01 vsftpd[7255]: pam_unix(vsftpd:auth): authentication failure; logname= uid=0 euid=0 tty=ftp ruser=xxxxx rhost=xxxxx user=xxxxx fac_ftp:Aug 9 16:24:44 web01 vsftpd[7255]: [xxxxx] FAIL LOGIN: Client "x.x.x.x" lev_notice:Aug 9 16:24:42 web01 vsftpd[7255]: pam_ldap(vsftpd:auth): Authentication failure; user=xxxxx lev_notice:Aug 9 16:24:42 web01 vsftpd[7255]: pam_unix(vsftpd:auth): authentication failure; logname= uid=0 euid=0 tty=ftp ruser=xxxxx rhost=xxxxx user=xxxxx lev_warn:Aug 9 16:24:44 web01 vsftpd[7255]: [xxxxx] FAIL LOGIN: Client "x.x.x.x"
Using dovecot-2.2.36-3.el7.x86_64 on CentOS7
I am looking at replacing our creaky old courier-imap server, which takes authentication and user info from an LDAP database, with dovecot imap. Any comments on the wisdom of this choice of action, or anything I should know about the setting up before starting to work on it?
On 2019-08-09, Joseph Mays via dovecot dovecot@dovecot.org wrote:
I am looking at replacing our creaky old courier-imap server, which takes authentication and user info from an LDAP database, with dovecot imap. Any comments on the wisdom of this choice of action, or anything I should know about the setting up before starting to work on it?
Plenty of people have this type of setup, if you already know what you're doing with LDAP from the existing installation you shouldn't have any problem configuring it with Dovecot.
Plenty of people have this type of setup, if you already know what you're doing with LDAP from the existing installation you shouldn't have any problem configuring it with Dovecot.
Thanks. That's what I would have thought, but I am clearly getting something wrong. I have dovecot with ldap installed, and I thought I had it configured to talk with our ldap server the same way the courier imap (which works fine) does, but all was getting was an authentication failure with timeout.
Tried running tcpdump on the ldap server to watch the exchange, but it didn't reveal much. I'm not an expert at reading tcpdump output, but it looks like when I connect to the dovecot imap server and try to log in, it opens a connection to the ldap server and then.... nothing happens. I don't see any data exchange occurring. But as I said, I am not an expert at reading tcpdump output.
nb-200# tcpdump -vv port 389
tcpdump: listening on fxp0, link-type EN10MB (Ethernet), capture size 96 bytes
15:12:53.378192 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], length: 60) nb-212.win.net.64502 > nb-200.win.net.ldap: S [tcp sum ok] 1650141152:1650141152(0) win 65535
On 9 Aug 2019, at 17.39, Marc Roos via dovecot dovecot@dovecot.org wrote:
Should dovecot not be using different severity levels like auth.warn? On my system everything goes to loglevel info:
My thinking has been:
- Panic: There's a bug that needs fixing
- Fatal: Somewhat stronger error
- Error: Something's broken or misconfigured - admin should fix something
- Warning: Something seems to be at least temporarily broken, like maybe some limit was reached because the system was overloaded. Admin may need to do something or possibly just wait. Either way, these should be looked into.
- Info: Events that admin doesn't necessarily need to look at, except while debugging or for gathering stats or something
- Debug: Only when really debugging
lev_info:Aug 9 16:18:24 mail03 dovecot: imap-login: Aborted login (auth failed, 1 attempts in 2 secs): user=<xxxxx>, method=PLAIN, rip=x.x.x.x, lip=x.x.x.x, TLS, session=
lev_info:Aug 9 16:18:29 mail03 dovecot: auth-worker(28656): pam(krinfo,188.206.104.240, ): unknown user
These are regular events that happen all the time due to brute force attacks and such. I don't know why you'd want to see them as warnings?
participants (4)
-
Joseph Mays
-
Marc Roos
-
Stuart Henderson
-
Timo Sirainen