- dovecot - dovecot.org

[Dovecot] Dovecot statistics -- I hope this is a stupid question
by Jon Callas 11 Jun '06

11 Jun '06

Is there a way for me to know the last time a user logged in? i'm running Dovecot with Postfix with the authentication bridge and completely virtual everything. It would be nice to know the last time someone logged in, so four years from now I can delete the ones that haven't been used in three years. Jon

2 1

[Dovecot] Slow caching
by John Rowe 11 Jun '06

11 Jun '06

I have just installed dovecot on a RedHat Enterprise 4 clone with exim MTA, procmail LDA and mbox format. I'm getting complaints of slow caching from a Mac user: I think there's still something very sick with [host]'s IMAP server: it just took a full five minutes to cache an attachment (350kb) in an email from [person]. In that time, I couldn't do anything else with mail; it was essentially locked. The user's inbox is in /var/spool/mail (where there are no idexes), there areindex files within his home directory: ./.imap/INBOX: total 1160 -rw------- 1 xyz users 60656 May 30 14:22 dovecot.index -rw------- 1 xyz users 891904 May 30 14:22 dovecot.index.cache -rw------- 1 xyz users 78428 May 30 14:22 dovecot.index.log -rw------- 1 xyz users 131920 May 26 11:29 dovecot.index.log.2 Everything is on local disk, there are no NFS mounts at all. Any thoughts? Thanks John

3 3

[Dovecot] Inbox in two different locations
by arilinux 11 Jun '06

11 Jun '06

Hello I'm running dovecot v1.0.beta3 on a fedora 4 machine. I'm looking for the way to tell dovecot that some users have inbox (mailbox) in /var/mail/%u and some have inbox (maildir) in /home/%u/mail. Anyway?

2 1

[Dovecot] deliver LDA status?
by Lev Serebryakov 11 Jun '06

11 Jun '06

Hello dovecot, wiki mentions `deliver', but it doesn't include into 1.0.beta8 dovecot distribution. It can be downlaoded from CVS, and even contains two tags on files, that seems to eb release tags :) But what is official status of `deliver' tool? Is it stable, or experemental, or what? Are here any plans when it will be packaged ad announced? -- Best regards, Lev mailto:lev@serebryakov.spb.ru

2 1

[Dovecot] Can't run POP3 and IMAP simultaneously from xinetd...
by Timothy Meader 11 Jun '06

11 Jun '06

Hello all, I'm hoping you can help out with an issue I'm having running dovecot-beta8 on Solaris 9 (SPARC). The reason I need to run them from xinetd is that we require the filtering ability that tcp_wrappers provide. My issue is that, when running both from xinetd, IMAP runs fine, but then, when you try to POP in to check mail on the same box, it seems that the login section is handled via pop3-login... but all subsequent commands are handled via the imap interpreter. It's as if it's getting passed off to /usr/local/libexec/dovecot/imap instead of /usr/local/libexec/dovecot/pop3 as is specified in dovecot.conf. Here's an example from running a direct telnet session to the box in question: [operator@yyyy operator]# telnet yyyy 110 Trying xxx.xxx.xxx.xxx... Connected to yyyy. Escape character is '^]'. +OK Unauthorized access prohibited USER joeblow +OK PASS joeblowspass +OK Logged in. LIST LIST BAD Error in IMAP command : Unknown command. QUIT QUIT BAD Error in IMAP command : Unknown command. 1 logout If you do a ps -ef on the box and check the processes, at no time does a pop3 process start through this process. However, if you do the ps -ef right after the "LIST" command, you can see that there's an imap process started for user 'joeblow'. Now, if I take xinetd out of the equation and instead use the daemon mode /usr/local/sbin/dovecot... everything works perfectly. I've tried using the tcp_wrappers patch that's available in the unsupported directory on dovecot.org, but I cannot get the configure script to recognize the libwrap I have on the system when I compile dovecot with "--with-libwrap" as specified. I'm using tcp_wrappers for Solaris 9 off sunfreeware, so I know it's on there. I've also created sym links to libwrap.a and tcpd.h in /usr/lib and /usr/include respectively... still no dice. Honestly, I don't care which way dovecot runs (though daemon mode WOULD actually be preferred for performance reasons IF tcp_wrappers were available for use), but I just need it running both IMAP and POP3 somehow. Here are the applicable pop3 and imap sections of my dovecot.conf: -- default_mail_env = mbox:~/mail:INBOX=/var/mail/%1u/%1.1u/%u protocol pop3 { login_executable = /usr/local/libexec/dovecot/pop3-login mail_executable = /usr/local/libexec/dovecot/pop3 pop3_no_flag_updates = no pop3_enable_last = no pop3_uidl_format = %08Xu%08Xv pop3_logout_format = top=%t/%T, retr=%r/%R, del=%d/%m, size=%s pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } protocol imap { login_executable = /usr/local/libexec/dovecot/imap-login mail_executable = /usr/local/libexec/dovecot/imap login_greeting_capability = yes } -- And the respective sections from xinetd.conf: -- service pop3 { socket_type = stream protocol = tcp wait = no user = root server = /usr/local/libexec/dovecot/pop3-login port = 110 flags = REUSE IPv4 rlimit_cpu = 150 instances = 80 cps = 110 10 disable = no } service imap { socket_type = stream protocol = tcp wait = no user = root server = /usr/local/libexec/dovecot/imap-login port = 143 flags = REUSE IPv4 rlimit_cpu = 120 disable = no } -- I hope someone can shed some light on this situation for me. Thank you in advance. --- Tim Meader CNE Internet Services NetCommerce Corporation Tim.Meader(a)gsfc.nasa.gov (301) 286-8013

2 1

[Dovecot] missing empty line in mbox folders with Outlook 2000 client
by Gary Funck 11 Jun '06

11 Jun '06

I recently looked into a problem that has been plaguing me since the switch to dovecot a couple of years back, documented here: http://mailman.rwth-aachen.de/pipermail/procmail/2006-May/024363.html The gist is that when I tell Outlook 2000 to write all outgoing mail into a Sent-mail folder on the IMAP server (using mbox format), I find that the mbox's don't have empty lines separating the messages, (though the Content-Length field is correct. This leads to interoperability problems with programs and scripts that expect each mbox message to be separated by an empty line. (We're running dovecot-1.0-0.beta2.7 under Fedora Core 5 on an x86_64 platform.) Has this mbox behavior been reported before? Is it considered a bug or a feature? Is there a configuration option, or Outlook tweak, that can be enabled to ensure that the mbox's produced by writing messages to them via Outlook, are well-formed (have an empty line separating messages)?

2 1

[Dovecot] Server settings for a busy server
by Pat Hastings 11 Jun '06

11 Jun '06

Hi, We are migrating from a windows server and i have very few stats as to what our current concurrent usage stats are other than about 50,000 active users and 90,000 email messages a day inbound 20,000 outbound. Anyone got some tips for tuning dovecot to handle this load? Below is my config - do the values of login_process_size etc sound correct? Also my logs seem to be written out as root which seems kind of scary do how do I / should I have these written out by the dovecot user. Any feedback greatfully accepted. Regards, Pat protocols = imap pop3 listen = * ssl_disable = no disable_plaintext_auth = no shutdown_clients = yes log_path = /var/log/dovecot/mainlog info_log_path = /var/log/dovecot/infolog log_timestamp = "%Y-%m-%d %H:%M:%S " login_dir = /var/run/dovecot/login login_chroot = yes login_user = dovecot login_process_size = 256 login_process_per_connection = no login_processes_count = 48 login_max_logging_users = 2048 login_greeting = Email server ready. login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c login_log_format = %$: %s first_valid_uid = 100 mail_extra_groups = mail valid_chroot_dirs = /var/vmail mail_debug = no default_mail_env = maildir:/var/vmail/dovecoterror/%domain/%u maildir_copy_with_hardlinks = yes protocol imap { } protocol pop3 { pop3_reuse_xuidl = no pop3_uidl_format =%u pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s pop3_client_workarounds = outlook-no-nuls, oe-ns-eoh } auth_executable = /usr/lib/dovecot/dovecot-auth auth_verbose = yes auth_debug = yes auth_debug_passwords = yes auth default { mechanisms = plain passdb pam { } passdb ldap { args = /etc/dovecot/dovecot-ldap.conf } userdb passwd { } userdb ldap { args = /etc/dovecot/dovecot-ldap.conf } user = root } --- [This E-mail has been scanned for viruses but it is your responsibility to maintain up to date anti virus software on the device that you are currently using to read this email. ]

2 1

[Dovecot] Dovecot 1.0beta8 dovecot-auth consumes 100% CPU time on Solaris 10 amd64
by Tore André Klock 11 Jun '06

11 Jun '06

Hello. I hope someone out there can help with this. It is getting pretty urgent. I am running a Solaris 10 server on Opteron (amd64) hardware and have compiled Dovecot 1.0beta8 from source. It has openssl compiled in (after much mucking around with various environment variables and modifying the Makefile), and was built with: $ ./configure --with-ldap --with-ssl-dir=/etc/ssl $ make # make install The variables: CC=/usr/sfw/bin/gcc CFLAGS='-m64 -I/usr/local/ssl/include:/usr/sfw/include:/opt/sfw/include' CPP=/usr/sfw/bin/cpp CPPFLAGS=-I/usr/local/ssl/include/openssl:/usr/sfw/include:/opt/sfw/include CXX=/usr/sfw/bin/g++ LDFLAGS='-m64 -L/usr/local/ssl/lib -R/usr/local/ssl/lib:/usr/sfw/lib:/opt/sfw/lib' LD_LIBRARY_PATH=/usr/local/ssl/lib:/usr/sfw/lib:/opt/sfw/lib It was compiled with gcc version 3.4.3 (csl-sol210-3_4-branch+sol_rpath). I modified the SSL_CFLAGS and SSL_LIBS variables in the Makefile to make it find my openssl install in /usr/local/ssl. The one that came with the OS was broken[1], so I compiled 0.9.8b from source. The configure script for some reason didn't pick this up, even when using CFLAGS, LDFLAGS, etc. At any rate, I successfully set it up to accept SSL/TLS connections and authenticate against an LDAP server. I use the auth_bind authentication method and only one LDAP host. I have confirmed that this works. In fact, dovecot runs just fine with the exception of the dovecot-auth proces, which is thrown into an endless loop. It starts off at maybe 1-2% CPU time, but after a few minutes it is back up to 100%. This is the output from truss(1) pointed at the dovecot-auth process: --cut-- pollsys(0xFFFFFD7FFFDFF6F0, 5, 0xFFFFFD7FFFDFF6D0, 0x00000000) = 0 pollsys(0xFFFFFD7FFFDFF6F0, 5, 0xFFFFFD7FFFDFF6D0, 0x00000000) = 0 pollsys(0x00467DC0, 10, 0xFFFFFD7FFFDFFB10, 0x00000000) = 1 [same sequence repeats ad nauseum] --cut-- This is a sample of top(1) output: --cut-- load averages: 1.00, 1.00, 1.00 08:51:38 60 processes: 55 sleeping, 3 running, 1 zombie, 1 on cpu CPU states: 0.0% idle, 68.3% user, 31.7% kernel, 0.0% iowait, 0.0% swap Memory: 1024M real, 680M free, 71M swap in use, 591M swap free PID USERNAME LWP PRI NICE SIZE RES STATE TIME CPU COMMAND 22875 nobody 1 0 0 0K 0K run 726:22 99.68% dovecot-auth --cut-- Here is a condensed version of my ldap-config: (comments removed, names changed to protect the innocent) --cut-- hosts = ldap.example.com auth_bind = yes auth_bind_userdn = uid=%u,ou=People,o=example.com,o=example.com ldap_version = 3 base = uid=%,ou=People,o=example.com,o=example.com --cut-- This is my condensed dovecot.conf: --cut-- base_dir = /var/run/dovecot/ protocols = imap pop3 listen = * ssl_disable = no ssl_cert_file = /etc/ssl/certs/host.cert ssl_key_file = /etc/ssl/private/host.key ssl_cipher_list = ALL:!LOW disable_plaintext_auth = no shutdown_clients = yes log_path = /var/log/dovecot log_timestamp = "%b %d %H:%M:%S " login_user = dovecot login_process_per_connection = yes verbose_proctitle = yes verbose_ssl = yes first_valid_uid = 100 last_valid_uid = 60000 mail_debug = yes default_mail_env = maildir:/var/mail/%u/Maildir mail_full_filesystem_access = no protocol imap { login_executable = /usr/local/libexec/dovecot/imap-login mail_executable = /usr/local/libexec/dovecot/imap login_greeting_capability = yes imap_client_workarounds = outlook-idle tb-extra-mailbox-sep } protocol pop3 { login_executable = /usr/local/libexec/dovecot/pop3-login mail_executable = /usr/local/libexec/dovecot/pop3 pop3_uidl_format = %08Xu%08Xv pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s mail_plugin_dir = /usr/local/lib/dovecot/pop3 pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } auth_executable = /usr/local/libexec/dovecot/dovecot-auth auth_cache_size = 0 auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ auth_verbose = yes auth_debug = no auth default { mechanisms = plain passdb ldap { args = /usr/local/etc/dovecot-ldap.conf } userdb passwd { } user = nobody } --cut-- I may have commented out more than necessary in an attempt to be explicit while I was trying to narrow this down. This is the output of ldd dovecot-auth: --cut-- libpam.so.1 => /lib/64/libpam.so.1 libldap.so.5 => /usr/lib/64/libldap.so.5 libsocket.so.1 => /lib/64/libsocket.so.1 libnsl.so.1 => /lib/64/libnsl.so.1 librt.so.1 => /lib/64/librt.so.1 libsendfile.so.1 => /lib/64/libsendfile.so.1 libc.so.1 => /lib/64/libc.so.1 libcmd.so.1 => /lib/64/libcmd.so.1 libsasl.so.1 => /usr/lib/64/libsasl.so.1 libmd5.so.1 => /lib/64/libmd5.so.1 libnspr4.so => /usr/lib/mps/64/libnspr4.so libplc4.so => /usr/lib/mps/64/libplc4.so libnss3.so => /usr/lib/mps/64/libnss3.so libssl3.so => /usr/lib/mps/64/libssl3.so libmp.so.2 => /lib/64/libmp.so.2 libscf.so.1 => /lib/64/libscf.so.1 libaio.so.1 => /lib/64/libaio.so.1 libpthread.so.1 => /lib/64/libpthread.so.1 libthread.so.1 => /lib/64/libthread.so.1 libdl.so.1 => /lib/64/libdl.so.1 libsoftokn3.so => /usr/lib/mps/amd64/libsoftokn3.so libplds4.so => /usr/lib/mps/amd64/libplds4.so libdoor.so.1 => /lib/64/libdoor.so.1 libuutil.so.1 => /lib/64/libuutil.so.1 libm.so.2 => /lib/64/libm.so.2 --cut-- Notes: - The problem *seems* to occur only when I use LDAP authentication. - Disabling SSL in the config has no effect on the CPU usage. - I am not using NFS for anything. - I use Thunderbird 1.5.0.2 and another client runs Outlook. - There is no indication of any problem in the dovecot or system logs. - I suspected this had to do with the poll method dovecot is compiled with (poll), but it happens even when I compiled it with the select method. As far as I know, none of the other methods are available on Solaris. - I noted that the poll(2) call in Solaris will return immediately given a timeout of zero (-1 is 'forever'). I tried tacking down the use of that system call, but I had to give up on that. I only mention it in case it is a dovecot bug and of any help to Timo. Any help is greatly appreciated. Thank you. - Tore [1] If you use the factory-installed version, you get messages like "Warning: imap-login: SSL_accept() failed: error:1409D08A:SSL routines:SSL3_SETUP_KEY_BLOCK:cipher or hash unavailable" in your dovecot log.

2 7

[Dovecot] Can't read dovecot.conf
by E P 11 Jun '06

11 Jun '06

Hello all, I'm attempting to run dovecot on an HP-UX 11.11 system ... the built went fine, and I've got the program installed. I copied dovecot-example.conf to dovecot.conf and made a few changes to it, then went to sbin and ran the dovecot binary to see what would happen. What happened was this: colin:/usr/local/dovecot/sbin# ./dovecot Error: Error in configuration file /usr/local/dovecot/etc/dovecot.conf line 1: Unknown setting: _cert_file ... which is odd; line 1 of dovecot.conf was actually this: ## Dovecot configuration file ... and the first line that wasn't commented out was this: protocols = imaps So just for fun I changed the first non-commented line to this: protocols=imaps ... and then ran the dovecot binary again. This time the error was subtly different: colin:/usr/local/dovecot/sbin# ./dovecot Error: Error in configuration file /usr/local/dovecot/etc/dovecot.conf line 1: Unknown setting: ert_file ... "aha" says I, "it's having some issue with comments." So I took out every line in dovecot.conf that wasn't a comment, leaving me with just 23 lines: protocols=imaps listen=<IP address> ssl_cert_file=/opt/openssl/certs/imapd.pem ssl_key_file=/opt/openssl/certs/imapd.pem disable_plaintext_auth=yes protocol imap { login_executable=/usr/local/dovecot/libexec/dovecot/imap-login mail_executable=/usr/local/dovecot/libexec/dovecot/imap mail_plugin_dir=/usr/local/dovecot/lib/dovecot } protocol pop3 { } auth_executable=/usr/local/dovecot/libexec/dovecot/dovecot-auth auth default { mechanisms=plain passdb pam { } userdb passwd { } user=root } plugin { } This time, when I ran the binary, I got a new error: colin:/usr/local/dovecot/sbin# ./dovecot Error: Can't use SSL certificate /opt/openssl/certs/dovecot.pem: No such file or directory ... this is odd, because the config file clearly states that it should look for the certificate elsewhere. But just for fun, I made dovecot.pem symlinks in /opt/openssl/certs and /opt/openssl/private. Then I try running again: colin:/usr/local/dovecot/sbin# ./dovecot Error: Missing auth section for server default At this point, it's becoming clear to me that my current tactic isn't doing much, so I read some READMEs, checked the wiki, googled around a bit, and now I'm here. Anyone have hints on this? Thanks -- Elliott

2 1

[Dovecot] Dovecot wont start.
by Cesar Diaz 11 Jun '06

11 Jun '06

I installed Dovecot along with Postfix on a FreeBSD server using the port. When I try to start dovecot I get the following error: Fatal: Can't resolve address : hostname nor servname provided, or not known I have the hostname define on the server and can ping it by FQDN and by just hostname with out problems. Any suggestions are greatly appreciated.

2 1