I found I was enabling the options you requested in the wrong place. After fixing it I get:
Mar 26 16:21:03 booklion dovecot: Dovecot v1.2.9 starting up (core dumps disabled) Mar 26 16:21:04 booklion dovecot: auth(default): Fatal: APOP mechanism can't be supported with given passdbs Mar 26 16:21:04 booklion dovecot: dovecot: Fatal: Auth process died too early - shutting down Mar 26 16:22:31 booklion dovecot: Dovecot v1.2.9 starting up (core dumps disabled) Mar 26 16:22:31 booklion dovecot: auth(default): Fatal: DIGEST-MD5 mechanism can't be supported with given passdbs Mar 26 16:22:31 booklion dovecot: dovecot: Fatal: Auth process died too early - shutting down Mar 26 16:23:21 booklion dovecot: Dovecot v1.2.9 starting up (core dumps disabled) Mar 26 16:23:21 booklion dovecot: auth(default): Fatal: CRAM-MD5 mechanism can't be supported with given passdbs Mar 26 16:23:21 booklion dovecot: dovecot: Fatal: Auth process died too early - shutting down
On Wed, Mar 26, 2014 at 4:02 PM, Blake McBride <blake1024@gmail.com> wrote:
Thanks for the help!!
I added the auth_mech.. line and reset dovecot but got the same error message.
dovecot -n # 1.2.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-57-server x86_64 Ubuntu 10.04.4 LTS log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap pop3 imaps pop3s managesieve ssl_cert_file: /etc/ssl/certs/ssl-mail.pem ssl_key_file: /etc/ssl/private/ssl-mail.key ssl_cipher_list: ALL:!LOW:!SSLv2:ALL:!aNULL:!ADH:!eNULL:!EXP:RC4+RSA:+HIGH:+MEDIUM login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login mail_privileged_group: mail mail_location: maildir:~/Maildir mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve imap_client_workarounds(default): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail imap_client_workarounds(pop3): imap_client_workarounds(managesieve): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh pop3_client_workarounds(managesieve): lda: postmaster_address: postmaster mail_plugins: sieve quota_full_tempfail: yes deliver_log_format: msgid=%m: %$ rejection_reason: Your message to <%t> was automatically rejected:%n%r auth default: mechanisms: plain login debug: yes debug_passwords: yes passdb: driver: shadow userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/dovecot-auth mode: 432 user: postfix group: postfix plugin: sieve: ~/.dovecot.sieve sieve_dir: ~/sieve
On Wed, Mar 26, 2014 at 3:52 PM, Reindl Harald <h.reindl@thelounge.net>wrote:
Am 26.03.2014 21:47, schrieb Blake McBride:
Mar 26 15:04:51 booklion dovecot: imap-login: Aborted login (no auth attempts): rip=74.179.230.177, lip=192.168.168.53 Mar 26 15:04:51 booklion dovecot: last message repeated 2 times Mar 26 15:04:51 booklion dovecot: pop3-login: Aborted login (no auth attempts): rip=74.179.230.177, lip=192.168.168.53 Mar 26 15:04:51 booklion dovecot: last message repeated 3 times Mar 26 15:04:51 booklion dovecot: imap-login: Aborted login (no auth attempts): rip=74.179.230.177, lip=192.168.168.53
what auth-mechs have you configured and how is TB configured? "no auth attempts" in most cases indicates the client don't agree with the auth-mechs offered by the server (PLAUN, LOGIN, CRAM-MD5, LMTP)
in doubt try that in dovecot.conf auth_mechanisms = CRAM-MD5 DIGEST-MD5 APOP LOGIN PLAIN