[Dovecot] troubleshooting new dovecot installation
Hello,
I'm setting up a new mail server using freebsd 6.2, postfix, dovecot with
SASL and, eventually, squirrelmail.
I've gone through
http://wiki.dovecot.org/TestPop3Installation
the program is running, plain works over telnet from local host or from a
remote machine. I can do stat and retr commands.
however, when I try to use the login method
(that is what the command
1 login username password
part is, isn't it?)
all I get is:
-ERR Unknown command.
even with auth_verbose = yes
auth_debug = yes, logs give no information.
May 7 20:41:53 server dovecot: pop3-login: Disconnected: rip=1.2.3.4,
lip=1.2.3.4
(IP's substituted)
almost all of the users will be using outlook/outlook express so I'm only enabling plain and login methods.
thanks Ray
dovecot -n gives protocols: imap pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login verbose_proctitle: yes first_valid_gid: 0 mail_extra_groups: mail mail_location: maildir:/usr/local/mail/%d/%n mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login passdb: driver: pam passdb: driver: sql args: /usr/local/etc/dovecot-sql.conf userdb: driver: passwd userdb: driver: prefetch args: /usr/local/etc/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth user: postfix group: postfix master:
I don't think it matters, but for the sake of formality: server# grep -v '^ *\(#.*\)\?$' dovecot-sql.conf driver = mysql connect = host=/tmp/mysql.sock dbname=******** user=******** password=******* password_query = SELECT md5(userpassword) AS password, home, virtual_uid AS userdb_uid, virtual_gid AS userdb_gid FROM virtual_users WHERE email = '%u' AND active = 1
sorry, forgot to add version =1.0.0 Ray
On Monday 07 May 2007 9:13 pm, Ray wrote:
Hello, I'm setting up a new mail server using freebsd 6.2, postfix, dovecot with SASL and, eventually, squirrelmail. I've gone through http://wiki.dovecot.org/TestPop3Installation the program is running, plain works over telnet from local host or from a remote machine. I can do stat and retr commands. however, when I try to use the login method (that is what the command 1 login username password part is, isn't it?) all I get is: -ERR Unknown command. even with auth_verbose = yes auth_debug = yes, logs give no information. May 7 20:41:53 server dovecot: pop3-login: Disconnected: rip=1.2.3.4, lip=1.2.3.4 (IP's substituted)
almost all of the users will be using outlook/outlook express so I'm only enabling plain and login methods.
thanks Ray
dovecot -n gives protocols: imap pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login verbose_proctitle: yes first_valid_gid: 0 mail_extra_groups: mail mail_location: maildir:/usr/local/mail/%d/%n mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login passdb: driver: pam passdb: driver: sql args: /usr/local/etc/dovecot-sql.conf userdb: driver: passwd userdb: driver: prefetch args: /usr/local/etc/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth user: postfix group: postfix master:
I don't think it matters, but for the sake of formality: server# grep -v '^ *\(#.*\)\?$' dovecot-sql.conf driver = mysql connect = host=/tmp/mysql.sock dbname=******** user=******** password=******* password_query = SELECT md5(userpassword) AS password, home, virtual_uid AS userdb_uid, virtual_gid AS userdb_gid FROM virtual_users WHERE email = '%u' AND active = 1
Hi,
El Martes, 8 de Mayo de 2007 05:13, Ray escribió:
however, when I try to use the login method (that is what the command 1 login username password part is, isn't it?)
That seems like an imap command, and I suppose that you're using a pop3 port...
Aaaaaaaaaaagur.
Joseba Torre. CIDIR Bizkaia.
On Tuesday 08 May 2007 12:33 am, Joseba Torre wrote:
Hi,
El Martes, 8 de Mayo de 2007 05:13, Ray escribió:
however, when I try to use the login method (that is what the command 1 login username password part is, isn't it?)
That seems like an imap command, and I suppose that you're using a pop3 port...
It seems like your right, as this command does work when I use port 143, but the following is a direct copy and paste from http://wiki.dovecot.org/TestPop3Installation
# telnet your.host.org 110 1 login username password
So, I guess the next question becomes how come I can use
# telnet localhost 110 user username pass password
properly from any host, but a real client reports connection refused. (kmail is the main one I've been using) Ray
Aaaaaaaaaaagur.
On Tuesday, May 8 at 08:02 AM, quoth Ray:
It seems like your right, as this command does work when I use port 143, but the following is a direct copy and paste from http://wiki.dovecot.org/TestPop3Installation
# telnet your.host.org 110 1 login username password
Ummm... maybe it's changed since you saw it, but that's not what I see on that page.
The POP3 protocol (according to RFC 1939) supports only two forms of authentication: APOP and the USER/PASS mechanism (like you have below).
# telnet localhost 110 user username pass password
So, I guess the next question becomes how come I can use
[that] properly from any host, but a real client reports connection refused. (kmail is the main one I've been using)
That's an excellent question. How do you have kmail configured? Can you use a packetsniffer to snoop on its conversation with the server?
~Kyle
I contend that we are both atheists. I just believe in one fewer god than you do. When you understand why you dismiss all the other possible gods, you will understand why I dismiss yours. -- Sir Stephen Henry Roberts
On Tuesday 08 May 2007 1:28 pm, Kyle Wheeler wrote:
On Tuesday, May 8 at 08:02 AM, quoth Ray:
It seems like your right, as this command does work when I use port 143, but the following is a direct copy and paste from http://wiki.dovecot.org/TestPop3Installation
# telnet your.host.org 110 1 login username password
Ummm... maybe it's changed since you saw it, but that's not what I see on that page.
It looks like I owe Joseba Torre an apology. I thought he was complaining about me, but it looks like he was complaining about an error in the docs which he or someone else has since fixed.
The POP3 protocol (according to RFC 1939) supports only two forms of authentication: APOP and the USER/PASS mechanism (like you have below).
# telnet localhost 110 user username pass password
So, I guess the next question becomes how come I can use
[that]
properly from any host, but a real client reports connection refused. (kmail is the main one I've been using)
That's an excellent question. How do you have kmail configured? Can you use a packetsniffer to snoop on its conversation with the server?
~Kyle
I have learned a little more since then, and it is probably a postfix error. I posted a full description to the postfix list, but I'll give a summary here, just in case. I'm not sure what has changed, but for whatever reason I can now send/receive/and relay through kmail but I can only receive, and send to a known account through outlook express. the logs seem to indicate that OE isn't even trying to authenticate. Ray
participants (3)
-
Joseba Torre
-
Kyle Wheeler
-
Ray