We currently had dovecote 99 running and ran into some issues with it, mainly our pop3 sessions timeout and were slow.
I upgraded to the latest version and im serving imap with pop3 using pam.
Heres my pam file:
[root@pop etc]# cat /etc/pam.d/dovecot #%PAM-1.0 auth required pam_unix.so nullok account required pam_unix.so
The problem I'm having is I can authenticate to imap, but it's very slow, however pop3 doesn't work at all. I have auth debug set and I can see the imap authentication but not pop3.
Here is my config file.
ssl_disable: yes login_dir: /usr/local/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 mail_location: maildir:/home/%1u/%u/Maildir 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 auth default: debug: yes debug_passwords: yes passdb: driver: pam args: dovecot passdb: driver: passwd userdb: driver: passwd
May 21 13:51:15 pop dovecot: imap-login: Login: user=<test>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured May 21 13:51:38 pop dovecot: auth(default): passwd(test,127.0.0.1): lookup May 21 13:51:53 pop dovecot: IMAP(ftest): Disconnected: Logged out May 21 13:51:54 pop dovecot: imap-login: Login: user=<ftest>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured May 21 13:51:54 pop dovecot: auth(default): pam(ftest,127.0.0.1): lookup service=dovecot May 21 13:51:56 pop dovecot: auth(default): client out: OK 1 user=ftest May 21 13:51:56 pop dovecot: auth(default): passwd(ftest,127.0.0.1): lookup May 21 13:51:56 pop dovecot: auth(default): master out: USER 95 ftest system_user=ftest uid=11094 g id=503 home=/home/f/ftest May 21 13:52:18 pop dovecot: auth(default): pam(ftest,127.0.0.1): lookup service=dovecot May 21 13:52:21 pop dovecot: IMAP(ftest): Time just moved backwards by 1 seconds. I'll sleep now until we're back in pre sent. May 21 13:52:21 pop dovecot: imap-login: Login: user=<ftest>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured May 21 13:52:22 pop dovecot: IMAP(ftest): Disconnected: Logged out
Using maildir's with pam authentication, I really would appreciate any help.
Paul A spake the following on 5/21/2007 10:38 AM:
We currently had dovecote 99 running and ran into some issues with it, mainly our pop3 sessions timeout and were slow.
I upgraded to the latest version and im serving imap with pop3 using pam.
Heres my pam file:
[root@pop etc]# cat /etc/pam.d/dovecot #%PAM-1.0 auth required pam_unix.so nullok account required pam_unix.so
The problem I'm having is I can authenticate to imap, but it's very slow, however pop3 doesn't work at all. I have auth debug set and I can see the imap authentication but not pop3.
<<snip>>
Did you use the new conf file, and fix the settings, or just copy over your old .99 conf file?
--
MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't!!!!
On Mon, 2007-05-21 at 13:38 -0400, Paul A wrote:
Here is my config file.
You didn't have "protocols" line there. By default Dovecot only listens for IMAP connections. If you want POP3 you'll need to add pop3 there.
passdb: driver: pam args: dovecot passdb: driver: passwd userdb: driver: passwd
You most likely don't want to have "passdb passwd" configured. pam + userdb passwd is enough.
May 21 13:51:54 pop dovecot: auth(default): pam(ftest,127.0.0.1): lookup service=dovecot May 21 13:51:56 pop dovecot: auth(default): client out: OK 1 user=ftest
It looks like your PAM lookup is taking two seconds. You could look at auth.log to see if PAM had logged something.
If nothing else helps, you could try using "passdb shadow" instead of PAM to see if it makes it faster.
May 21 13:52:21 pop dovecot: IMAP(ftest): Time just moved backwards by 1 seconds. I'll sleep now until we're back in pre sent.
Run ntpd instead of ntpdate or whatever is currently moving your time backwards. Or if you're running a virtual machine you may need to do something differently..
Timo Sirainen spake the following on 5/21/2007 3:22 PM:
On Mon, 2007-05-21 at 13:38 -0400, Paul A wrote:
Here is my config file.
You didn't have "protocols" line there. By default Dovecot only listens for IMAP connections. If you want POP3 you'll need to add pop3 there.
passdb: driver: pam args: dovecot passdb: driver: passwd userdb: driver: passwd Then there is an error in the conf file as follows; <quote> # Default values are shown for each setting, it's not required to uncomment # any of the lines. <snip> # Protocols we want to be serving: imap imaps pop3 pop3s # If you only want to use dovecot-auth, you can set this to "none". #protocols = imap imaps pop3 pop3s </quote>
So this is NOT the default, although the conf file states such?
You most likely don't want to have "passdb passwd" configured. pam + userdb passwd is enough.
May 21 13:51:54 pop dovecot: auth(default): pam(ftest,127.0.0.1): lookup service=dovecot May 21 13:51:56 pop dovecot: auth(default): client out: OK 1 user=ftest
It looks like your PAM lookup is taking two seconds. You could look at auth.log to see if PAM had logged something.
If nothing else helps, you could try using "passdb shadow" instead of PAM to see if it makes it faster.
May 21 13:52:21 pop dovecot: IMAP(ftest): Time just moved backwards by 1 seconds. I'll sleep now until we're back in pre sent.
Run ntpd instead of ntpdate or whatever is currently moving your time backwards. Or if you're running a virtual machine you may need to do something differently..
--
MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't!!!!
On Mon, 2007-05-21 at 16:09 -0700, Scott Silva wrote:
# Protocols we want to be serving: imap imaps pop3 pop3s # If you only want to use dovecot-auth, you can set this to "none". #protocols = imap imaps pop3 pop3s </quote>
So this is NOT the default, although the conf file states such?
Where did you get the config file? The default config file that comes in tarball is the same as in http://dovecot.org/doc/dovecot-example.conf and there's no pop3 in the protocols line. If some distribution changed that, it should be fixed.
Timo Sirainen spake the following on 5/22/2007 5:38 AM:
On Mon, 2007-05-21 at 16:09 -0700, Scott Silva wrote:
# Protocols we want to be serving: imap imaps pop3 pop3s # If you only want to use dovecot-auth, you can set this to "none". #protocols = imap imaps pop3 pop3s </quote>
So this is NOT the default, although the conf file states such?
Where did you get the config file? The default config file that comes in tarball is the same as in http://dovecot.org/doc/dovecot-example.conf and there's no pop3 in the protocols line. If some distribution changed that, it should be fixed.
This was from an RPM created in one of the CentOS add-on packagers. I ran a dovecot -n against this being commented and un- commented and didn't see any difference. The packager must have found a way to change the defaults.
Can that be done at compile time or could the code have been modified?
--
MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't!!!!
On Tue, 2007-05-22 at 08:39 -0700, Scott Silva wrote:
Timo Sirainen spake the following on 5/22/2007 5:38 AM:
On Mon, 2007-05-21 at 16:09 -0700, Scott Silva wrote:
# Protocols we want to be serving: imap imaps pop3 pop3s # If you only want to use dovecot-auth, you can set this to "none". #protocols = imap imaps pop3 pop3s </quote>
So this is NOT the default, although the conf file states such?
Where did you get the config file? The default config file that comes in tarball is the same as in http://dovecot.org/doc/dovecot-example.conf and there's no pop3 in the protocols line. If some distribution changed that, it should be fixed.
This was from an RPM created in one of the CentOS add-on packagers. I ran a dovecot -n against this being commented and un- commented and didn't see any difference. The packager must have found a way to change the defaults.
Can that be done at compile time or could the code have been modified?
Yes. So I guess the Centos package really changed the defaults and there's no problem.
participants (3)
-
Paul A
-
Scott Silva
-
Timo Sirainen