- dovecot - dovecot.org

[Dovecot] Dovecot accepts squirrelmail, rejects fetchmail
by M. Fioretti 01 Oct '06

01 Oct '06

Hello, this is a follow-up to the thread "Fetchmail can't talk to dovecot" http://www.dovecot.org/list/dovecot/2006-September/016477.html Increasing the log level I get this in the log filed: Sep 30 15:04:19 fm dovecot: Dovecot v1.0.rc7 starting up Sep 30 15:04:22 fm dovecot: auth(default): passwd-file /etc/dovecot_user_file: Read 1 users Sep 30 15:05:05 fm dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAPsecured +lip=::ffff:SERVER_IP_HERE rip=::ffff:CLient_IP_HERE resp=LONG_STRING_HERE VDBB Sep 30 15:05:05 fm dovecot: auth(default): passwd-file(user_name,::ffff:CLIENT_IP_HERE): unknown user Sep 30 15:05:07 fm dovecot: auth(default): client out: FAIL 1 user=user_name Sep 30 15:05:07 fm dovecot: imap-login: Aborted login: user=<user_name>, method=PLAIN, rip=::ffff:CLIENT_IP_HERE, +lip=::ffff:SERVER_IP_HERE, TLS Remember that when the same user name and password come from Squirrelmail on the same host where dovecot runs, everything works. Why does it fail with fetchmail? what does that message "unknown user" exactly mean? Thank you in advance for any help, Marco

3 3

[Dovecot] [SOLVED] quota with: postfixadmin, postfix, mysql & dovecot
by Peter Veerman 01 Oct '06

01 Oct '06

Hi, I'm quite new to dovecot but already quite satisfied. Your documentation in the wiki is great but on quota + mysql it is not very clear. Because of the previously mentioned I have got the following note to make which you will hopefully use to adjust your wiki documentation on per-user-quota + mysql. I've searched your mail archive as good as possible and found no messages on this. If already messages have been exactly on this topic I want to apologize for sending this one. The notes I want to make is about this page: http://wiki.dovecot.org/Quota I'm using postfix + postfixadmin & mysql and dovecot (previously I used courier-imap instead of dovecot). The problems I ran in to was with setting up the per-user quota, as the explanation at the wiki is quite vague. For instance, the dict plugin is used to keep the quota counters in the mysql backend but only one single line shows how to set-up a per user quota. Setting up a per user quota where the max-quota is stored in mysql should be made making use of this setting: ========== user_query = SELECT home, uid, gid, 'dirsize:storage=' || quota_bytes AS quota FROM users WHERE userid = '%u' ========== nowhere is mentioned that this should also! be set: =========== protocol imap { mail_plugins = quota imap_quota } protocol pop3 { mail_plugins = quota } =========== the second point I want to make is that the mysqlquery is incorrect as || does not do the job of joining the two strings. Secondly is dovecot making use of kilobytes instead of bytes like postfix (and postfixadmin) does. For this I have found the following solution: ========== user_query = SELECT maildir, 125 AS uid, 125 AS gid,\ CONCAT('dirsize:storage=', ROUND( mailbox.quota / 1024 ) ) AS quota \ FROM mailbox WHERE username = '%u' AND active = '1' ========== Here I select the quota field from the mailbox table. This is then divided by 1024 (1Kbyte) and ROUNDED off in order to get rid of the .00 that results from this division. Greetz, Peter Veerman pveerman NO-SPAM at NO-SPAM hackwerk DOT net

6 7

[Dovecot] fetchmail can't talk to dovecot
by M. Fioretti 30 Sep '06

30 Sep '06

Hello, I have dovecot q1.0-0_22.rc7 up and running on a server: I can read email from squirrelmail just fine. When I try to download email with fetchmail, however, I get the result below. Why is that happening? In dovecot.conf I have: protocols = imap imaps pop3, so why should pop3 or imap fail? Where should I look? (I'll fix the certificates problem after I've managed to get in successfully with plain imap or pop3) Thanks, Marco fetchmail: 6.3.2 querying my.server (protocol POP3) at Wed 27 Sep 2006 12:15:17 AM CEST: poll started fetchmail: POP3< +OK Dovecot ready. fetchmail: POP3> CAPA fetchmail: POP3< +OK fetchmail: POP3< CAPA fetchmail: POP3< TOP fetchmail: POP3< UIDL fetchmail: POP3< RESP-CODES fetchmail: POP3< PIPELINING fetchmail: POP3< STLS fetchmail: POP3< USER fetchmail: POP3< SASL PLAIN DIGEST-MD5 fetchmail: POP3< . fetchmail: POP3> STLS fetchmail: POP3< +OK Begin TLS negotiation now. fetchmail: Issuer Organization: SomeOrganization fetchmail: Issuer CommonName: localhost.localdomain fetchmail: Server CommonName: localhost.localdomain fetchmail: Server CommonName mismatch: localhost.localdomain != my.server fetchmail: my.server key fingerprint: ... fetchmail: Server certificate verification error: self signed certificate fetchmail: POP3> CAPA fetchmail: POP3< +OK fetchmail: POP3< CAPA fetchmail: POP3< TOP fetchmail: POP3< UIDL fetchmail: POP3< RESP-CODES fetchmail: POP3< PIPELINING fetchmail: POP3< USER fetchmail: POP3< SASL PLAIN DIGEST-MD5 fetchmail: POP3< . fetchmail: POP3> USER user_name fetchmail: POP3< +OK fetchmail: POP3> PASS * fetchmail: POP3< -ERR Authentication failed. fetchmail: Authentication failed. fetchmail: Authorization failure on user_name(a)my.server fetchmail: POP3> QUIT fetchmail: POP3< +OK Logging out fetchmail: 6.3.2 querying my.server (protocol POP3) at Wed 27 Sep 2006 12:15:21 AM CEST: poll completed fetchmail: Query status=3 (AUTHFAIL) fetchmail: Writing fetchids file. fetchmail: normal termination, status 3 fetchmail: Writing fetchids file. if I try with IMAP the part after the certificate verification error is: fetchmail: IMAP> A0003 CAPABILITY fetchmail: IMAP< * CAPABILITY IMAP4rev1 SASL-IR SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDRE N NAMESPACE LOGIN-REFERRALS AUTH=PLAIN AUTH=DIGEST-MD5 fetchmail: IMAP< A0003 OK Capability completed. fetchmail: Protocol identified as IMAP4 rev 1 fetchmail: IMAP> A0004 LOGIN "user_name" * fetchmail: IMAP< A0004 NO Authentication failed. fetchmail: IMAP> A0005 * fetchmail: Authorization failure on user_name(a)my.server fetchmail: IMAP> A0006 LOGOUT fetchmail: IMAP< A0005 BAD Error in IMAP command received by server. fetchmail: IMAP< * BYE Logging out and I don't see any error message related to this in the server log.

2 3

Re: [Dovecot] SSL errors
by Bill Boebel 29 Sep '06

29 Sep '06

On Fri, September 29, 2006 11:47 am, Charles Marcus <CMarcus(a)Media-Brokers.com> said: > Bill Boebel wrote: >> I have a Dovecot server set up as a proxy and getting a ton of these >> errors, but I'm not sure where to begin troubleshooting it. I'm >> hearing frequently that Outlook users who use IMAP with SSL are >> getting disconnected often as a result. Any suggestions?... > > Need more details... Dovecot version? Platform? > Sorry... Red Hat ES4 (2.6.9-42.0.2.EL), latest dovecot CVS 20060926. login_process_per_connection = no login_processes_count = 3 login_max_processes_count = 10 login_max_connections = 4000 login_process_size = 64 Also added this to the dovecot init script to allocate more file descriptors to dovecot: start() { echo -n $"Starting $prog: " + ulimit -n 16384 daemon /usr/sbin/dovecot Also, seeing this error occasionally... Sep 29 11:34:15 director4 dovecot: imap-login: SSL_write() syscall failed: Bad file descriptor [166.137.221.91] Maybe nothing to worry about now that I have increased "login_process_size". Checking with customers to see if the Outlook IMAP SSL disconnects are still frequently occurring. Thanks, Bill

1 0

[Dovecot] SSL errors
by Bill Boebel 29 Sep '06

29 Sep '06

I have a Dovecot server set up as a proxy and getting a ton of these errors, but I'm not sure where to begin troubleshooting it. I'm hearing frequently that Outlook users who use IMAP with SSL are getting disconnected often as a result. Any suggestions?... Sep 29 11:12:07 director4 dovecot: imap-login: SSL_accept() failed: error:1409C041:SSL routines:SSL3_SETUP_BUFFERS:malloc failure [64.81.197.28] Sep 29 11:12:07 director4 dovecot: imap-login: SSL_accept() syscall failed: EOF [24.236.204.154] Bill

2 1

Re: [Dovecot] SSL errors
by Bill Boebel 29 Sep '06

29 Sep '06

On Fri, September 29, 2006 11:23 am, Bill Boebel <bill(a)webmail.us> said: > I have a Dovecot server set up as a proxy and getting a ton of these errors, but > I'm not sure where to begin troubleshooting it. I'm hearing frequently that > Outlook users who use IMAP with SSL are getting disconnected often as a result. > Any suggestions?... > > Sep 29 11:12:07 director4 dovecot: imap-login: SSL_accept() failed: > error:1409C041:SSL routines:SSL3_SETUP_BUFFERS:malloc failure [64.81.197.28] > > Sep 29 11:12:07 director4 dovecot: imap-login: SSL_accept() syscall failed: EOF > [24.236.204.154] > Actually, I found in the archives that I should increase login_process_size if I'm not running with login_process_per_connection. I have done this and that seems to have taken care of the malloc failure. However I am still getting a ton of these every few seconds: Sep 29 11:30:06 director4 dovecot: imap-login: SSL_read() syscall failed: EOF [70.171.61.190] Sep 29 11:30:06 director4 dovecot: imap-login: SSL_read() syscall failed: EOF [24.236.204.154] Sep 29 11:30:06 director4 dovecot: imap-login: SSL_read() syscall failed: EOF [70.171.61.190] Sep 29 11:30:08 director4 dovecot: imap-login: SSL_read() syscall failed: EOF [65.242.19.3]

2 1

[Dovecot] Passdb passwd on FreeBSD
by Jim Flowers 29 Sep '06

29 Sep '06

I am trying to use dovecot for both virtual and local pop3 mailboxes. When I try to access a local account, I get an "unknown user" reject from 'passdb sql', as expected. However, I also get a reject from 'passdb pam' with the message: dovecot: auth(default_with_listener): pam(username(a)domain.tld,###.###.###.###): pam_authenticate() failed: authentication error. Is this because it is trying to authenticate username(a)domain.tld instead of just username? What can I do about it? Although I have a block for 'passdb passwd' following the 'passdb pam' block, there is nothing in the log. Why is this, I wonder? Any help to point me in the right direction will be appreciated. Thanks. -- Jim Flowers <jflowers(a)ezo.net> -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

1 0

[Dovecot] Quota plugin rewrite
by Timo Sirainen 28 Sep '06

28 Sep '06

Backported from CVS HEAD to branch_1_0. You can get it as a patch from http://dovecot.org/patches/1.0/quota-rewrite.diff New features include support for multiple quota roots, so you could have eg. per-user quota and a larger domain quota (although no backend actually supports this yet..). The more important feature is that you can configure specific mailboxes to have a bit more space available for them, such as Trash or Spam. The configuration has also changed. Normally you'd use something like this: quota = maildir # 1GB quota in general quota_rule = *:storage=1048576 # Trash mailbox gets 100MB more (so max. 1,1GB) quota_rule2 = Trash:storage=102400 # Spam mailbox gets also +100MB (still maxes at 1,1GB, not 1,2GB) quota_rule3 = Spam:storage=102400 You can place all the above into plugin { .. } section in dovecot.conf. In userdb if users have different quotas you'd then need to override only quota_rule (not quota, quota_rule2 and quota_rule3). I tested quickly that this seemed to work as described above. Please test and report. :)

2 6

[Dovecot] [BUG(let)] Dovecot does not recognize threaded/reentrant mysql libs
by OpenMacNews 28 Sep '06

28 Sep '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, i build mysql (currently v5.0.22) on OSX 10.4.7 w/ threading enabled. i.e., i build the reentrant libs: libmysqlclient_r.dylib rather than the 'usual': libmysqlclient.dylib currently, to make Dovecot 'play nice' and recognize the reentrant libs, I: perl -pi -e 's/AC_CHECK_LIB\(mysqlclient,/AC_CHECK_LIB\(mysqlclient_r,/g' configure.in perl -pi -e 's/mysql_lib=\"\-lmysqlclient \-lz \-lm"/mysql_lib=\"\-lmysqlclient_r \-lz \-lm\"/g' configure.in then: autoreconf -i -f before configure, etc. subsquent build/exec/function all seem OK with this mod, and the linked, reentrant mysql lib: ls -al /usr/local/dovecot/libexec/dovecot/dovecot-auth -rwxr-xr-x 1 root wheel 950616 Sep 28 09:59 /usr/local/dovecot/libexec/dovecot/dovecot-auth otool -L /usr/local/dovecot/libexec/dovecot/dovecot-auth /usr/local/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0) /usr/lib/libpam.1.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/local/mysql/lib/mysql/libmysqlclient_r.15.dylib (compatibility version 16.0.0, current version 16.0.0) /usr/local/lib/libreadline.5.1.dylib (compatibility version 5.0.0, current version 5.1.0) /usr/local/ncurses/lib/libncurses.5.5.dylib (compatibility version 5.5.0, current version 5.5.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.1.6) /usr/local/ssl/lib/libssl.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8) /usr/local/ssl/lib/libcrypto.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8) /usr/local/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.3) /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0) once verified that these changes are sufficient (anybody else got eyeballs on this?), a conditional in configure should do ... richard - -- /"\ \ / ASCII Ribbon Campaign X against HTML email, vCards / \ & micro$oft attachments [GPG] OpenMacNews at gmail dot com fingerprint: 50C9 1C46 2F8F DE42 2EDB D460 95F7 DDBD 3671 08C6 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iEYEARECAAYFAkUcAcUACgkQlffdvTZxCMYQXACgustNRKkqu97hWI88CTQwxZG7 q10AniSAcnhYesxf68x4y5Z7pg6uf/2f =py2/ -----END PGP SIGNATURE-----

1 0

[Dovecot] LDA and chroot
by Uldis Pakuls 28 Sep '06

28 Sep '06

Hi, I'd like to ask: is it possible to use Dovecot's LDA with mail_chroot variable set, e.g. "mail_chroot = /serv/storage19/vmail"? Without "mail_chroot" set all works fine. If mail_chroot is set and user database contains relative paths to home directory (without chroot part like "domain.net/user") deliver ignores this and tries to work at real root, while imap and pop3 processes founds home directory correctly. If users database contains full paths deliver works correctly, but imap/pop3 processes tries to access chroot directory + full path (and fails). Home directory in form "/chroot/path/./domain.net/user" solves the problem..., but as I understand, it is jut form to override default. Thus I can't find a way to correctly set default chroot path. Any suggestions? Tnx, Uldis

1 0

[Dovecot] LDA directly to Maildir/cur
by Scott Murman 28 Sep '06

28 Sep '06

i'm tired of dealing with buggy clients so i'm moving more processing into the server-side. i configured procmail as LDA with maildir-style mailboxes. i would like to simulate an automatic "mark as read" feature during procmail processing. simplest way looks to be forcing delivery directly to Maildir/cur instead of Maildir/new, but i suspect this may screw up dovecot. will this work? is there another (better) method? -SM-

3 3

[Dovecot] dovecot checkpassword passdb and vmailmgr
by Mij 28 Sep '06

28 Sep '06

hello some times ago I posted some patches to workaround vmailmgr not fitting into dovecot's passdb-checkpassword authentication module. Yesterday I spent some spare time for carrying out a cleaner solution for this problem. Check out these patches. If you're not interested in merging them, I will make them available at the same page I used for the former solution [ http://mij.oltrelinux.com/net/dovecot-qmail-vmailmgr ]; there were some 20 people/month that checked it out. This is a brief explanation of the patches: The root of all evil is that the checkpassword interface [ http://cr.yp.to/checkpwd/interface.html ] leaves room to interpretation when the scope is not system login. Vmailmgr and vpopmail, for example, collapse many mail users on the same system account. So, what "home" is here is not specified. In the case of vmailmgr, it's "checkvpw" sets HOME to the system user's home, and returns the path of the actual mail user differently. The solution I applied for this problem is to generalize the process that fetches authentication data (what currently is "checkpassword- reply"). I was set up for a specific passdb-vmailmgr module, but this would have seen a lot of code replication. Similarly (but I did not inspect further), I guess vpopmail can fit in this solution as well. So 1) provide a module "vmailmgr-reply", with the same behavior as checkpassword-reply, that's aware of the way checkvpw returns accounting information and pass this back to dovecot transparently so, this patch ships vmailmgr-reply along with checkpassword-reply (name them "fetcher"s for brevity) The idea is that every checkpassword-compatible module may have its own fetcher for passing correct info back to dovecot. Now with this generalization, the user must be able to specify if its checkpassword module needs a custom fetcher, and if it does, what's its path. So 2) modify auth/passdb-checkpassword.c and pump "args =". By default it takes the path of the checkpassword module (e.g. "checkvpw"), now it can be appended another field, that is the path of the custom fetcher. If this optional is omitted, the default checkpassword-reply will be used, and the cp module is supposed to behave like dovecot expects from it. Otherwise, a comma appear after the first path. e.g. passdb checkpassword { args = /xyz/checkvpw,/libexec/vmailmgr-reply } if one needs to specify paths with commas in the first one, commas can be escaped with \ (eg args=first\,path,second_path) Last but not least, the patch addresses again the problem with colons in paths. Currently, dovecot dictates no colons can exist in mailbox path names. In UNIX, no such constraint exist. Moreover, paths with colons are common when working specifically with qmail (see dot-qmail). When dovecot encounters ':', it truncates the path. This way, for example, if the authentication module returned home "/ path/name:surname", dovecot will truncante it to "/path/name". If name exist, name:surname will browse his mail without effort. All this comes from dovecot parsing params on MAIL environment (INDEX, INBOX, CONTROL), but it also happens if none of them was actually specified. So 3) modify lib-storage/index/maildir/maildir-storage.c for fixing the parsing problem with the mail environment. [ I did not provide the same fix for the remaining storages, but this can easily be done by copy/paste if convenient ]. For simplification and without loss of generality, this fix mandates ":INBOX=", ":INDEX=" and ":CONTROL=" params to follow in this order, if they appear. [ a minor patch agains auth/Makefile.am is provided for including vmailmgr-reply when building the rest of the auth stuff ] Any comment on this is welcome for discussion. bye

1 0

[Dovecot] Big sites using Dovecot
by Jonathan 28 Sep '06

28 Sep '06

Hi, Are there any big Dovecot sites (say 50,000-100,000) users on this list? What sort of hardware do you use. What sort of problems do you see? Many thanks, Jonathan.

14 22

Re: [Dovecot] syslog messages
by Rich West 27 Sep '06

27 Sep '06

After commenting out the "passdb pam" section and uncommenting "passdb ldap", with the "args = /etc/dovecot-ldap.conf", the syslog messages went completely away, and everything continued to work. I just thought I would mention it in the event that anyone else was seeing similar problems in the future. :) -Rich > > (I sent this last night, but to the wrong address.. argh) > > After an upgrade to FC5, and a rebuild and install of dovecot 1.0RC7, > > I've been getting a LOT of syslog messages like the following: > > Sep 26 21:47:55 myhost dovecot-auth: nss_ldap: reconnected to LDAP > > server ldap://ldap.mydomain.com after 1 attempt > > > > Now, everything is working fine as far as I can tell (it's only been a > > rocky day since the upgrade.. and that was littered with other LDAP > > related problems), but I was wondering why it was even using > > nss_ldap... I have dovecot configured to connect to LDAP directly. > > > > My dovecot.conf contains: > > auth default { > > # Space separated list of wanted authentication mechanisms: > > # plain login digest-md5 cram-md5 ntlm rpa apop anonymous gssapi > > mechanisms = plain > > ... > > passdb pam { > > } > > ... > > # LDAP database > > #passdb ldap { > > # Path for LDAP configuration file, see doc/dovecot-ldap.conf for > > example > > #args = > > #} > > ... > > # LDAP database > > userdb ldap { > > # Path for LDAP configuration file, see doc/dovecot-ldap.conf for > > example > > args = /etc/dovecot-ldap.conf > > } > > > > And I am wondering if I missed something obvious here... > > > > I'm going to try commenting out the "passdb pam" section, uncommenting > > the "passdb ldap" section and see if that allows for everything to go > > directly to LDAP (and not rely on nss_ldap or pam_ldap). > > > > -Rich > > >

1 0

Re: [Dovecot] support for UW-style mbox
by Rich West 27 Sep '06

27 Sep '06

> UW-IMAP will automatically append the contents of /var/spool/mail/user to > ~user/mbox (and then clear /var/spool/mail/user) if ~user/mbox exists. > I'd like to mimic that action with Dovecot. (I'm probably going to be unlucky, > as an earlier respondent pointed out). > > Sorry to show my ignorance, but I thought delivery was a function > of the MTA (Exim in my case), which would require a change to my exim > config file, and would probably not then be a per-user thing. > (i.e. with UW-IMAP, if ~user/mbox doesnt exist, mail gets left in > /var/spool/mail/user). > I need to read about dovecot.conf No, you are correct. Delivery is handled by the MTA. Dovecot just needs to know where to access it. By default, for example, with Sendmail, it will place the email in /var/spool/mail (unless you change some back-end code somewhere along the line), and then you can use procmail (with a global procmailrc file in /etc) to place the mail where you want it to go.. I haven't used UW-IMAP in a while now (well over a year and a half). I stopped using it at all of my supported sites because, even though it was simple to manage, it was just way too slow. From what I remember, the UW implementation is such that UW-IMAP will read from the user's mbox file if it exists, and if it doesn't, it will read from <spooldir>/<username> (in this case, /var/spool/mail/user). UW-IMAP (or any IMAP) wouldn't actually do the delivery, so writing to the spool directory temporarily and then moving it to the home directory shouldn't actually happen. However, I don't truly remember how it worked under the hood, but that just doesn't seem right to me (too much chance for conflict). I do remember (back in the day) the headaches we would get when trying to debug a "lost mail" problems (with a centralized /var/spool/mail directory) and it turned out the user in question had created an mbox file which had next to nothing in it. :) -Rich

2 2

[Dovecot] syslog messages
by Rich West 27 Sep '06

27 Sep '06

(I sent this last night, but to the wrong address.. argh) After an upgrade to FC5, and a rebuild and install of dovecot 1.0RC7, I've been getting a LOT of syslog messages like the following: Sep 26 21:47:55 myhost dovecot-auth: nss_ldap: reconnected to LDAP server ldap://ldap.mydomain.com after 1 attempt Now, everything is working fine as far as I can tell (it's only been a rocky day since the upgrade.. and that was littered with other LDAP related problems), but I was wondering why it was even using nss_ldap... I have dovecot configured to connect to LDAP directly. My dovecot.conf contains: auth default { # Space separated list of wanted authentication mechanisms: # plain login digest-md5 cram-md5 ntlm rpa apop anonymous gssapi mechanisms = plain ... passdb pam { } ... # LDAP database #passdb ldap { # Path for LDAP configuration file, see doc/dovecot-ldap.conf for example #args = #} ... # LDAP database userdb ldap { # Path for LDAP configuration file, see doc/dovecot-ldap.conf for example args = /etc/dovecot-ldap.conf } And I am wondering if I missed something obvious here... I'm going to try commenting out the "passdb pam" section, uncommenting the "passdb ldap" section and see if that allows for everything to go directly to LDAP (and not rely on nss_ldap or pam_ldap). -Rich

1 0

Re: [Dovecot] Big sites using Dovecot
by Bill Boebel 27 Sep '06

27 Sep '06

On Thu, September 21, 2006 1:14 pm, Jonathan <dovecot(a)redigloo.org> said: > Are there any big Dovecot sites (say 50,000-100,000) users on this > list? Yes, Webmail.us. Many multiples of that number :) > What sort of hardware do you use. 80 backend IMAP servers. 5 front-end IMAP-proxy servers. All running Dovecot. The boxes are single AMD CPU, 1GB RAM, and 4 SATA drives. DRBD used to replicate data between servers. > What sort of problems do you see? Dovecot doesn't need much CPU, but it needs a lot of disk. So give it lots of spindles, either in one big box or many small boxes like we do. Right now the only problem we have is the Dovecot proxy software sometimes disconnects imap sessions that it should not disconnect. Since Timo is very busy, we are working on a patch for this. http://www.dovecot.org/list/dovecot/2006-August/015401.html Bill

3 2

[Dovecot] SSL_accept failed
by Timothy Martin 26 Sep '06

26 Sep '06

Hello, I'm new to dovecot. I just installed it a few days ago on FreeBSD via the ports and got it up and running without too much trouble. Although yesterday I turned on the SSL/TLS features and tried to get secure connections to work. I don't get any error messages when launching dovecot, I saw it successfully create the SSL parameters after first enabling the feature yet I can't seem to get a successful connection. Normal non- ssl connections work fine. What happens: 1) my client claims to be attempting the connection. 2) things go on for some time with nothing happening 3) finally the dovecot log pops up with these messages dovecot: Sep 09 02:25:23 Warning: imap-login: SSL_accept() syscall failed: EOF [x.x.x.x] dovecot: Sep 09 02:25:23 Info: imap-login: Disconnected: rip=x.x.x.x, lip=x.x.x.x, TLS handshake dovecot: Sep 09 02:26:23 Info: imap-login: Disconnected: Inactivity: rip=x.x.x.x, lip=x.x.x.x, TLS handshake FYI: I've regenerated a fresh cert and key, just for dovecot and I'm using Mac OS X's Mail client. Any clues? .tim

6 17

[Dovecot] log tools with html for dovecot
by Robert Schetterer 26 Sep '06

26 Sep '06

Hi @ll, are there any recommandations for logging tools with html display for dovecot thx -- Diese Nachricht wurde auf Viren und andere gefährliche Inhalte untersucht und ist - aktuelle Virenscanner vorausgesetzt - sauber.

2 2

[Dovecot] Error: pipe() failed: Too many open files
by Dirk Essl 26 Sep '06

26 Sep '06

Hi, I am currently migrating a big bunch of mail accounts to a dovecot server running 1.0rc2 on Solaris 10 suddenly all imap processes died and I see this in my dovecot.log: dovecot: Sep 26 14:54:31 Error: pipe() failed: Too many open files dovecot: Sep 26 14:54:31 Fatal: dup2(stderr) failed: Bad file number dovecot: Sep 26 14:54:31 Error: child 29376 (imap) returned error 89 dovecot: Sep 26 15:15:48 Error: pipe() failed: Too many open files dovecot: Sep 26 15:15:48 Fatal: dup2(stderr) failed: Bad file number dovecot: Sep 26 15:15:49 Error: child 1563 (imap) returned error 89 dovecot: Sep 26 15:15:55 Error: pipe() failed: Too many open files dovecot: Sep 26 15:15:55 Fatal: dup2(stderr) failed: Bad file number dovecot: Sep 26 15:15:55 Error: child 1572 (imap) returned error 89 dovecot: Sep 26 15:15:58 Error: pipe() failed: Too many open files dovecot: Sep 26 15:15:58 Fatal: dup2(stderr) failed: Bad file number dovecot: Sep 26 15:15:58 Error: child 1577 (imap) returned error 89 dovecot: Sep 26 15:18:25 Error: pipe() failed: Too many open files dovecot: Sep 26 15:18:25 Fatal: dup2(stderr) failed: Bad file number dovecot: Sep 26 15:18:25 Error: child 1659 (imap) returned error 89 dovecot: Sep 26 15:18:27 Error: pipe() failed: Too many open files dovecot: Sep 26 15:18:27 Fatal: dup2(stderr) failed: Bad file number dovecot: Sep 26 15:18:27 Error: child 1662 (imap) returned error 89 dovecot: Sep 26 15:18:32 Error: socketpair() failed: Too many open files dovecot: Sep 26 15:18:32 Error: Temporary failure in creating login processes, slowing down for now dovecot: Sep 26 15:18:32 Error: pipe() failed: Too many open files what could cause the error? is this from Solaris or from dovecot? TIA dirk

2 1

[Dovecot] Not getting new mail notification
by Robert Creager 26 Sep '06

26 Sep '06

Hey all, I'm having no luck getting new mail notification except in two mail folders (using maildir w/procmail delivery). I'm using three different clients (sylpheed-claws 1.9.14, Thunderbird 1.5.0.5 and a newer version of Horde). None of them are getting new mail in any except these two folders (inbox and 1 other). If I browse to the folders, still nothing. If I browse to the folders with Horde, I see the new mail, but not always in the other clients. It's hit or miss if the other clients get notified of the mail, but the mail is moved from the new folder. I'm subscribed to the folders and have them to be checked for new messages (in Thunderbird). I tried using dnotify, and things got worse (no folders updated). I've over 350 e-mails sitting in new folders right now: [robert@thunder Maildir]$ ls .*/new | wc 397 332 12925 One interesting item I noticed is that if I touch a file in a new directory (or vi it), I immediately get notification of the mail (and it gets moved from new to cur). I'm running dovecot 1.0 RC7 configured as ./configure --sysconfdir=/etc/dovecot --with-pgsql --with-pam --localstatedir=/var with the following changes to the config: base_dir = /var/lib/dovecot/ protocols = imaps ssl_cert_file = /etc/ssl/dovecot/certs/dovecot.pem ssl_key_file = /etc/ssl/dovecot/private/dovecot.pem default_mail_env = maildir:%h/Maildir verbose_proctitle = yes protocol imap { imap_client_workarounds = tb-extra-mailbox-sep } I'm running dovecot through xinetd: service imaps { disable = no socket_type = stream protocol = tcp wait = no user = root server = /usr/local/libexec/dovecot/imap-login flags = IPv4 server_args = --ssl } Linux thunder.logicalchaos.org 2.6.12-12-3 #5 SMP Wed Feb 1 23:59:03 MST 2006 i686 AMD Athlon(tm) MP 2600+ unknown GNU/Linux Help? Thanks, Rob

9 31

[Dovecot] Preforming an action/trigger after a user successfully authenticates
by Dan Trainor 26 Sep '06

26 Sep '06

Hi - I have searched the docs for v1.0 RC7, but cannot find what I'm looking for. What I'm ultimately wanting to do is have Dovecot preform some action, or a trigger, when the user is successfully authenticated. Even more specifically, I'd like to run another SQL query to record a date/time for last authenticated login. Short from running a script during logrotate, or constantly tailing the log, is there any mechanism in Dovecot that would allow me to do this? Again, all I'm looking to do is to record the last date/time that someone successfully logged in, into a MySQL database. Thanks! -dant

3 7

[Dovecot] Dovecot Usage Poll
by Jackie Hunt 25 Sep '06

25 Sep '06

Hi all, I'm trying to get a feel for how many sites are using Dovecot and the size of the installation. Jonathan's query about big sites spurred my curiousity. I'd like to take an informal poll and will post results to the list. I'm interested in hearing from those of you who are using dovecot in a real-life/production type environment (not just testing). Please email me directly [jackie.hunt(a)colostate.edu] and send the following info: (1) Type of organization: commercial/government/educational/etc. (2) Number of users supported with Dovecot (3) Approx. length of time you've used Dovecot in "production" (4) Whether or not you are using the Dovecot LDA Thanks much, Jackie --- Jackie Hunt ACNS Voice: (970) 663-3789 Colorado State University FAX: (970) 491-1958 Fort Collins, CO 80523 Email: jackie.hunt(a)colostate.edu

7 7

[Dovecot] DSpam mysql-plugin (was DSpam plugin)
by Michael Blinn 25 Sep '06

25 Sep '06

After wrestling with Johannes's original plugin, I had a go at the mysql plugin that Tim wrote, as described here: http://members.plug.org.au/~linuxalien/dokuwiki/projects:dovecot-mysql-dspa… I kept getting "Error: imap dump-capability process killed with signal 11" when attempting to start dovecot with this plugin. I traced the error to line 656 of master-settings.c in the dovecot source, in the 'get_imap_capability' function. In this function, it notes: "Reloading configuration. Don't try to execute the imap process again. Too risky and the wait() call below will break it anyway. Just use the previous capability list we already had generated." I changed the source so that the function always ran " set->imap_generated_capability = p_strdup(settings_pool, generated_capability); return TRUE;" instead of going through the function where it had on the wait described in the comments. Now, voila. Dovecot starts without complaint, the plugin works, the delivery and moving of email works. I'm assuming I've screwed something up by skipping the rest of this get_imap_capability function. My C skills are a few years rusty. What are the ramifications of skipping the remainder of this function? Thanks, Michael

7 8

[Dovecot] Moving to dovecot
by Ian C. Quorn 25 Sep '06

25 Sep '06

We're in the process of moving to Dovecot. We're currently running UW-IMAP live with Dovecot 1.0rc7 on alternate ports for testing. We're set to switch to Dovecot tomorrow morning, and I'm sure I'll have lots of stupid questions once that happens. So I guess you can consider this message an introduction as well as a preemptive apology. Our setup: our mailserver is a SunFire 880 running solaris 8. Inboxes are stored in /var/mail, home directories are in /home. Mailboxes are mbox. Both /home and /var/mail are NFS-mounted from a NetApp filer. Indexes are stored in /dovecot (this is a partition on local disk). We have about 500 users accesing their mail on this server. Supported clients are Outlook, Mac Mail, and Thunderbird (both PC and Mac). Many people access their mail via webmail (IMP Horde) instead of or in addition to using a normal client. We also have a few people who use Pine. Authentication is against the local shadow file. Given this setup, do the following config lines seem sane? login_process_per_connection = no login_max_connections = 256 default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u:INDEX=/dovecot/%u namespace private { separator = / prefix = inbox = yes } # for backwards compatibility: namespace private { separator = / prefix = mail/ hidden = yes } namespace private { separator = / prefix = ~/mail/ hidden = yes } namespace private { separator = / prefix = ~%u/mail/ hidden = yes } mail_read_mmaped = no mmap_disable = no mmap_no_write = no lock_method = fcntl mbox_read_locks = dotlock mbox_write_locks = dotlock imap_client_workarounds = outlook-idle tb-extra-mailbox-sep pop3_uidl_format = %08Xv%08Xu pop3_client_workarounds = outlook-no-nuls oe-ns-eoh The namespace stuff came from http://wiki.dovecot.org/Namespaces - it was listed as a way to allow backwards-compatability with UW-IMAP. So, anything there look like a bad idea? Any other config parameters I might want to tweak, tune, or otherwise take a look at? So far dovecot's been pretty much trouble-free in our testing. But I have noticed some error messages in the logs. Anyone know what these mean? Are they anything I should panic over? dovecot: Sep 25 09:34:19 Error: IMAP(cliftoja): UIDVALIDITY changed (1034876030 -> 1159201281) in mbox file /home/wcts/cliftoja/mail/Common installation codes dovecot: Sep 25 09:50:24 Error: IMAP(cliftoja): UIDVALIDITY changed (1156881790 -> 1159202005) in mbox file /home/wcts/cliftoja/mail/Junk dovecot: Sep 25 10:04:01 Error: imap-login: Master sent reply with unknown tag 180 dovecot: Sep 25 10:04:01 Error: child 1078 (login) returned error 89 dovecot: Sep 25 10:18:58 Error: login: tried to change state 0 -> 44 (if you can't login at all, see src/lib/fdpass.c) Thanks in advance, and here's to (hopefully) a trouble-free Dovecot migration (hey, it can't be worse than UW-IMAP). Ian Quorn System Administrator Whitman College Technology Services

1 0