Errors in log after installing dovecot

A

Auraka

Verified User
Joined
Jul 12, 2004
Messages
33
So I installed dovecot and now when I log into squirrelmail i keep seeing this message in the log:

[root@main ~]# tail /var/log/maillog
May 28 16:12:30 main dovecot[4700]: imap-login: Login: user=<[email protected]>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured
May 28 16:12:30 main dovecot[4700]: IMAP([email protected]): Disconnected: Logged out
May 28 16:12:51 main dovecot[4700]: auth(default): shadow([email protected],127.0.0.1): unknown user
May 28 16:12:51 main dovecot[4700]: auth(default): passwd([email protected],127.0.0.1): unknown user
May 28 16:12:51 main dovecot[4700]: imap-login: Login: user=<[email protected]>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured
May 28 16:12:51 main dovecot[4700]: IMAP([email protected]): Disconnected: Logged out
May 28 16:12:51 main dovecot[4700]: auth(default): shadow([email protected],127.0.0.1): unknown user
May 28 16:12:51 main dovecot[4700]: auth(default): passwd([email protected],127.0.0.1): unknown user
May 28 16:12:51 main dovecot[4700]: imap-login: Login: user=<[email protected]>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured
May 28 16:12:52 main dovecot[4700]: IMAP([email protected]): Disconnected: Logged out
[root@main ~]#

Any idea why I would be seeing this and what I can do to fix it?
 
Try:
Code: 
cd /usr/local/directadmin/customapache
./build todovecot
 
Hey,

Here's how to fix the "unknown user" messages in the logs...

In /etc/dovecot.conf look towards the bottom of the file for the following:

# More verbose logging. Useful for figuring out why authentication isn't
# working.
auth_verbose = yes
Click to expand...

and change it to this:

# More verbose logging. Useful for figuring out why authentication isn't
# working.
#auth_verbose = no
Click to expand...

Yes, it is overkill to comment it out and set it to no... But, I like being certain.

David
 
Funny, I was just looking at that in /etc/dovecot.conf but I wasn't sure if there was some underlying problem that needed to be addressed. So this is normal?

Thanks! :)
 
Hey,

Well, what's normal in this world?!...

We're running with it set to "no" without issue. My guess is that it was set that way to do some debugging and got left in... or, perhaps it was changed on purpose...

David
 
You must log in or register to reply here.
Back
Top