Can't autorisation dovecot imap on fresh install ISPConfig 3

Discussion in 'Installation/Configuration' started by Jolman, Nov 20, 2011.

  1. Jolman

    Jolman Member

    Can't autorisation dovecot imap on fresh install ISPConfig 3. I have followed by http://www.howtoforge.com/perfect-server-debian-squeeze-with-bind-and-dovecot-ispconfig-3-p6

    Log from mail.log:
    Nov 20 18:40:02 ns1 dovecot: imap-login: Disconnected (no auth attempts): rip=127.0.0.1, lip=127.0.0.1, secured
    Nov 20 18:40:02 ns1 postfix/smtpd[1920]: connect from localhost[127.0.0.1]
    Nov 20 18:40:02 ns1 postfix/smtpd[1920]: lost connection after CONNECT from localhost[127.0.0.1]
    Nov 20 18:40:02 ns1 postfix/smtpd[1920]: disconnect from localhost[127.0.0.1]
    Nov 20 18:45:01 ns1 dovecot: pop3-login: Disconnected (no auth attempts): rip=127.0.0.1, lip=127.0.0.1, secured
    Nov 20 18:45:01 ns1 dovecot: imap-login: Disconnected (no auth attempts): rip=127.0.0.1, lip=127.0.0.1, secured
    Nov 20 18:45:01 ns1 postfix/smtpd[2017]: connect from localhost[127.0.0.1]
    Nov 20 18:45:01 ns1 postfix/smtpd[2017]: lost connection after CONNECT from localhost[127.0.0.1]
    Nov 20 18:45:01 ns1 postfix/smtpd[2017]: disconnect from localhost[127.0.0.1]
    Nov 20 18:45:05 ns1 dovecot: imap-login: Aborted login (auth failed, 1 attempts): user=<test>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured
     
  2. Jolman

    Jolman Member

    problem is solved!

    problem is solved!
     
  3. Spheerys

    Spheerys New Member

    hummmm I have a similar problem !
    Can you explain how did you solve your problem please ?
     
  4. Jolman

    Jolman Member

    solution

    you must reinstall ISPConfig3, firstly uninstall thru uninstall.php, then remove ispconfig dirs in /root, /home, and must delete ispconfig DB in mysql
     
  5. Spheerys

    Spheerys New Member

    I did it and that's works !!
    Thanks !













    ahahah... very funny
     
    Last edited: Dec 8, 2011
  6. cbj4074

    cbj4074 Member

    I guess that's one path to a solution...

    It was probably just a password mismatch somewhere along the line. Good to see it's solved, though!
     

Share This Page