Dovecot problem

Discussion in 'Installation/Configuration' started by Ryanmt, Jan 19, 2011.

  1. Ryanmt

    Ryanmt New Member

    Fresh install of ispconfig 3 on centos 5.5, i followed the 64bit perfect server, but the machine is actually 32 bit.

    I installed ispconfig, but dovecot was screwed up cause it didnt install properly.

    I have since removed the old dovecot and added...

    rpm -ivh
    rpm -ivh

    and restarted dovecot

    [[email protected] tmp]# telnet localhost 143
    Connected to (
    Escape character is '^]'.
    a login [email protected] password
    a NO [AUTHENTICATIONFAILED] Authentication failed.

    Jan 18 23:37:59 server32 dovecot: auth(default): client in: AUTH 2 PLAIN service=imap secured lip= rip= lport=143 rport=38938 resp=AHRlc3RAa2....
    Jan 18 23:37:59 server32 dovecot: auth-worker(default): pam([email protected], lookup service=dovecot
    Jan 18 23:37:59 server32 dovecot: auth-worker(default): pam([email protected], #1/1 style=1 msg=Password:
    Jan 18 23:38:01 server32 dovecot: auth-worker(default): pam([email protected], unknown user
    Jan 18 23:38:03 server32 dovecot: auth(default): client out: FAIL 2 [email protected]

    dovecot seems to have an OK mysql connection in dovecot-sql.conf using the details i can login, and going into the database and select * from mail_user shows me the test user and encrypted password for the user. Also their maildir exists ok and seems to have a few autogenerated files in.

    Run out of ideas to debug now, can anybody help?
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    It might be that the main dovecot.conf file was overwritten as you reinstalled dovecot. To fix that, download the ispconfig 3 tar.gz again, unpack it and run the update.php script which is in the install folder. Choose to reconfigure services during update.
  3. Ryanmt

    Ryanmt New Member

    Hi Till,

    Thanks for the reply. I uninstalled ispconfig, installed ipsconfig 3 (old version oops!) then upgraded whist resetting the configs as suggested.

    That seemed to fix the error and its now working well.
    Last edited: Jan 19, 2011

Share This Page