- dovecot - dovecot.org

[Dovecot] global and per-users sieve filters
by Nikolay Shopik 29 Dec '07

29 Dec '07

Hi Timo, I'm curious about such thing, currently if user have their own filter global filter no more take a place. Is this behavior changed in 1.1 or maybe in future? I'm unsure if this is 100 sieve related or more like Dovecot handling so fixing can be easily can done.

2 1

[Dovecot] v1.0.10 released
by Timo Sirainen 29 Dec '07

29 Dec '07

http://dovecot.org/releases/1.0/dovecot-1.0.10.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.10.tar.gz.sig v1.0.8 and v1.0.9 were a bit bad releases. Hopefully one day I've managed to have written a proper test suite which can be run before doing any releases.. * Security hole with LDAP+auth cache: If base setting contained %variables they weren't included in auth cache key, which broke caching. This could have caused different users with same passwords to log in as each other. - LDAP: Fixed potential infinite looping when connection to LDAP server was lost and there were queued requests. - mbox: More changes to fix problems caused by v1.0.8 and v1.0.9. - Maildir: Fixed a UIDLIST_IS_LOCKED() assert-crash in some conditions (caused by changes in v1.0.9) - If protocols=none, don't require imap executables to exist

3 4

[Dovecot] How to logoff a session with dovecot?
by Robin Atwood 29 Dec '07

29 Dec '07

I use dovecot to push email to my SE P1i and it works very well. :) However, I have two email accounts set up on the phone, one using my domain for GPRS and public WiFi and one using my WLAN address for use at home, the idea being I don't want to pay for GPRS data at home. The trouble is the GPRS account remains logged on and I get the mail in both inboxes. There is no option in the email client on the phone to disconnect, so is there any trick to forcing a disconnect from the mail server? TIA -Robin -- ---------------------------------------------------------------------- Robin Atwood. "Ship me somewheres east of Suez, where the best is like the worst, Where there ain't no Ten Commandments an' a man can raise a thirst" from "Mandalay" by Rudyard Kipling ----------------------------------------------------------------------

2 2

Re: [Dovecot] namespace problem / 1.1beta11
by ja nein 29 Dec '07

29 Dec '07

Hi Timo, great, that fix it! Thx. The only thing I noticed is that I've commented out the "list=yes" in namespace section of dovecot.conf, so it was automatically set to yes (according to dovecot -n): namespace private { separator = / prefix = INBOX/ inbox = yes # hidden = yes # list=yes } Regards, Sebastian ----- Ursprüngliche Mail ---- Von: Timo Sirainen <tss(a)iki.fi> An: ja nein <reg9009(a)yahoo.de> CC: Dovecot Mailing List <dovecot(a)dovecot.org> Gesendet: Samstag, den 29. Dezember 2007, 06:19:15 Uhr Betreff: Re: [Dovecot] namespace problem / 1.1beta11 On Fri, 2007-12-28 at 22:31 +0000, ja nein wrote: > > * NAMESPACE (("INBOX/" ".")) NIL NIL I don't know why I can't reproduce it, but I think this fixes it: http://hg.dovecot.org/dovecot/rev/0a0ff276bc38 __________________________________ Ihr erstes Fernweh? Wo gibt es den schönsten Strand? www.yahoo.de/clever

1 0

[Dovecot] Group inboxes
by Денис Квист 29 Dec '07

29 Dec '07

Please help, i want made "Group Inboxes" like in MDaemon "Group Inboxes: Customer service organizations often use group inboxes to receive email requests. Everyone in the customer service group has read and write access to the collective incoming mailbox. In this manner, anyone in the group can respond to each incoming email." Is it possible? Public folder is not work like i want namespace private { prefix = separator = / index = yes } namespace public { prefix = office/ separator = / location = maildir:/var/spool/mail/vhosts/testdomain.ru/Maildir/info hidden = no } dovecot --version 1.0.rc15 (Debian Etch)

2 1

[Dovecot] Fishing attempt locking up dovecot
by Patrick Milvich 29 Dec '07

29 Dec '07

I've mentioned this before but only heard from one other person who has experienced this, but it's becoming a pretty serious issue. The situation: A spammer sets a bot on a fishing attempt to gain email addresses, causing numerous login processes to spawn and suck up all available resources. The problem: Obviously this can act like a dos attack, but the real issue is after the spammer stops (by virtue of being added to our firewall blacklist, being caught and shut down by their isp, or otherwise), dovecot doesn't seem to relinquish the resources, causing "too many files open" errors for normal usage. The master process usually hangs around 40-50 files open at any given time, with about 10,000 logins a day (I use: lsof -p `cat /var/run/ dovecot/master.pid ` | wc -l), after the attempt is over I always see the files open shoot up to near 3,000 without it able to go down until a dovecot restart. This usually happens about once a month, though we can get unlucky and have it happen a few days apart. I have some log excerpts below. Wondering if this is happening through my own fault or at least within my ability to alleviate the issue. Is there a way to limit the number of connections from an ip address? Has anyone used login_executable to first hit their own solution to keep track of, and implement connection restrictions similar to what I'm aiming for? Thanks for any insight Patrick dovecot -n # 1.0.8: /usr/local/mail/dovecot/etc/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot protocols: imap imaps pop3 pop3s ssl_cert_file: /usr/local/mail/ssl/certs/dovecot.pem ssl_key_file: /usr/local/mail/ssl/private/dovecot.pem ssl_cipher_list: ALL:!LOW disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/local/mail/dovecot/libexec/dovecot/ imap-login login_executable(imap): /usr/local/mail/dovecot/libexec/dovecot/imap- login login_executable(pop3): /usr/local/mail/dovecot/libexec/dovecot/pop3- login first_valid_uid: 500 mail_location: maildir:/Volumes/data/mail/%Ld/%Ln mail_executable(default): /usr/local/mail/dovecot/libexec/dovecot/imap- before mail_executable(imap): /usr/local/mail/dovecot/libexec/dovecot/imap- before mail_executable(pop3): /usr/local/mail/dovecot/libexec/dovecot/pop3- before mail_plugin_dir(default): /usr/local/mail/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/mail/dovecot/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/mail/dovecot/lib/dovecot/pop3 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv auth default: mechanisms: plain digest-md5 login passdb: driver: sql args: /usr/local/mail/dovecot/etc/dovecot-sql.conf userdb: driver: static args: uid=exim gid=exim plugin: quota: maildir From the logs, first entries showing the problem: dovecot: Dec 10 16:17:02 Info: pop3-login: Disconnected: rip=207.245.39.90, lip=<lip> dovecot: Dec 10 16:17:02 Info: pop3-login: Disconnected: rip=207.245.39.90, lip=<lip> dovecot: Dec 10 16:17:03 Info: pop3-login: Disconnected: rip=207.245.39.90, lip=<lip> dovecot: Dec 10 16:17:03 Info: pop3-login: Disconnected: rip=207.245.39.90, lip=<lip> dovecot: Dec 10 16:17:03 Info: pop3-login: Disconnected: rip=207.245.39.90, lip=<lip> A little later on: dovecot: Dec 10 16:17:12 Info: pop3-login: Aborted login: user=<pwitest>, method=PLAIN, rip=207.245.39.90, lip=<lip> dovecot: Dec 10 16:17:12 Info: pop3-login: Aborted login: user=<tsinternetuser>, method=PLAIN, rip=207.245.39.90, lip=<lip> dovecot: Dec 10 16:17:12 Info: pop3-login: Aborted login: user=<bill>, method=PLAIN, rip=207.245.39.90, lip=<lip> dovecot: Dec 10 16:17:12 Info: pop3-login: Aborted login: user=<web>, method=PLAIN, rip=207.245.39.90, lip=<lip> dovecot: Dec 10 16:17:12 Info: pop3-login: Aborted login: user=<barbara>, method=PLAIN, rip=207.245.39.90, lip=<lip> dovecot: Dec 10 16:17:12 Info: pop3-login: Aborted login: user=<www>, method=PLAIN, rip=207.245.39.90, lip=<lip> dovecot: Dec 10 16:17:12 Info: pop3-login: Aborted login: user=<user>, method=PLAIN, rip=207.245.39.90, lip=<lip> dovecot: Dec 10 16:17:12 Info: pop3-login: Aborted login: user=<nathan>, method=PLAIN, rip=207.245.39.90, lip=<lip> dovecot: Dec 10 16:17:12 Info: pop3-login: Aborted login: user=<webmaster>, method=PLAIN, rip=207.245.39.90, lip=<lip> etc. etc.

3 2

[Dovecot] v1.1.beta11 released
by Timo Sirainen 29 Dec '07

29 Dec '07

http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta11.tar.gz http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta11.tar.gz.sig This one should be the last beta release before the first v1.1 release candidate. I'll try to stay away from this list and Dovecot in general for the next 1,5 weeks. I've several exams coming up and I should have started studying for them days ago already.. :) The main things left in my TODO are: - Squat indexes should handle expunges - Lucene indexes are broken - See if \recent flag handling could be fixed for maildir/mbox (it works for dbox though) - Some other minor things which I'll do if I have time, but won't block v1.1.0 release. Changes since beta10: - One major performance issue found and fixed. This was the main reason why we weren't yet in release candidate stage. - configure --with-package now gives an error if it can't find the necessary libs/headers for the package. Use --with-package=auto for the old behavior. - Memory leak fixes - Convert plugin fixes. Conversion is now done to namespace with INBOX. - Changes to handling group adding/removing to processes. Hopefully didn't break anything. - Message flag/keyword searches are now faster - Fixes/optimizations to handling SORT. After building initial indexes, my 260k mail mailbox sorts in about 0.01 seconds. :) - Fixes to searching mails with unknown charsets/invalid data - deliver_log_format setting

3 8

[Dovecot] 1.1.beta10 pop3 process hangs with 100% CPU
by arvids 29 Dec '07

29 Dec '07

Hello, we have observed pop3 process which got stuck consuming all available CPU. It seems that it happened because of some kind of abnormal POP3 connection termination. Here is strace info for this process: 13:36:05.866190 writev(1, [{"508qWWH96If+uVXeH2Zxl/hkn+plVwmI"..., 3975}, {"HP1oxt+np0o4Xtz27VQBtxx0zWfGuA3r"..., 193}], 2) = -1 EPIPE (Broken pipe) 13:36:05.866250 --- SIGPIPE (Broken pipe) @ 0 (0) --- 13:36:05.866288 epoll_ctl(6, EPOLL_CTL_DEL, 1, {0, {u32=135259776, u64=135259776}}) = 0 13:36:05.866335 setsockopt(1, SOL_TCP, TCP_CORK, [1], 4) = 0 13:36:05.866372 writev(1, [{"508qWWH96If+uVXeH2Zxl/hkn+plVwmI"..., 3975}, {"HP1oxt+np0o4Xtz27VQBtxx0zWfGuA3r"..., 193}], 2) = -1 EPIPE (Broken pipe) 13:36:05.866441 --- SIGPIPE (Broken pipe) @ 0 (0) --- 13:36:05.866478 writev(1, [{"508qWWH96If+uVXeH2Zxl/hkn+plVwmI"..., 3975}, {"HP1oxt+np0o4Xtz27VQBtxx0zWfGuA3r"..., 193}], 2) = -1 EPIPE (Broken pipe) 13:36:05.866539 --- SIGPIPE (Broken pipe) @ 0 (0) --- 13:36:05.866575 epoll_ctl(6, EPOLL_CTL_ADD, 1, {EPOLLOUT|EPOLLERR|EPOLLHUP, {u32=135259776, u64=135259776}}) = 0 13:36:05.866623 setsockopt(1, SOL_TCP, TCP_CORK, [0], 4) = 0 13:36:05.866660 gettimeofday({1197372965, 866675}, NULL) = 0 13:36:05.866698 epoll_wait(6, {{EPOLLHUP, {u32=135259776, u64=135259776}}}, 4, 6986) = 1 13:36:05.866737 gettimeofday({1197372965, 866752}, {4294967176, 0}) = 0 Regards, Arvids

2 1

Re: [Dovecot] namespace problem / 1.1beta11
by ja nein 29 Dec '07

29 Dec '07

Hi Timo, well, I don't know how I managed it, either :) Here's the output of the log file with mail_debug=yes. Interestingly it prints out the correct namespace in the log file (I did a synchronization of some folders in this period): Dec 28 23:24:33 51 dovecot: IMAP(merk(a)smcc.net): Loading modules from directory: /opt/dovecot-1.1-beta12/lib/dovecot/imap Dec 28 23:24:33 51 dovecot: IMAP(merk(a)smcc.net): Module loaded: /opt/dovecot-1.1-beta12/lib/dovecot/imap/lib20_fts_plugin.so Dec 28 23:24:33 51 dovecot: IMAP(merk(a)smcc.net): Module loaded: /opt/dovecot-1.1-beta12/lib/dovecot/imap/lib21_fts_squat_plugin.so Dec 28 23:24:33 51 dovecot: IMAP(merk(a)smcc.net): Effective uid=40000, gid=40000, home=/home/dovecot/mail/smcc.net/merk@smcc.net Dec 28 23:24:33 51 dovecot: IMAP(merk(a)smcc.net): Namespace: type=private, prefix=INBOX/, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes Dec 28 23:24:33 51 dovecot: IMAP(merk(a)smcc.net): maildir: data=/home/dovecot/mail/smcc.net/merk@smcc.net:INDEX=/home/dovecot/index/sm… Dec 28 23:24:33 51 dovecot: IMAP(merk(a)smcc.net): maildir++: root=/home/dovecot/mail/smcc.net/merk@smcc.net, index=/home/dovecot/index/smcc.net/merk@smcc.net, control=, inbox=/home/dovecot/mail/smcc.net/merk@smcc.net Dec 28 23:24:33 51 dovecot: imap-login: Login: user=<merk(a)smcc.net>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Dec 28 23:24:52 51 dovecot: IMAP(merk(a)smcc.net): Disconnected: Logged out bytes=17572/71038 It seems that the output to the client doesn't correspond to the settings dovecot uses internally?! Regards, Sebastian ----- Ursprüngliche Mail ---- Von: Timo Sirainen <tss(a)iki.fi> An: ja nein <reg9009(a)yahoo.de> CC: Dovecot Mailing List <dovecot(a)dovecot.org> Gesendet: Freitag, den 28. Dezember 2007, 18:45:56 Uhr Betreff: Re: [Dovecot] namespace problem / 1.1beta11 On Sat, 2007-12-22 at 13:48 +0000, ja nein wrote: > I think I've hit a separator bug: > > This is namespace query of dovecot and source server: > > * NAMESPACE (("INBOX/" ".")) NIL NIL Yes, that does look like a bug, but I've no idea how you managed to cause it. I just tested your namespace configuration and it works fine with me. Also there shouldn't even be any way to cause this configuration for a list=yes namespace: imap(tss)(pid=31754): namespace configuration error: list=yes requires prefix=INBOX/ to end with separator What do logs show with mail_debug=yes? __________________________________ Ihr erstes Baby? Holen Sie sich Tipps von anderen Eltern. www.yahoo.de/clever

2 1

[Dovecot] auth-ldap not resetting connection state after failed bind
by Brendan Braybrook 29 Dec '07

29 Dec '07

timo, i think i found a small problem with the ldap implementation: when using auth_bind (this might be in all conditions, not just that one - i haven't tested further), if the server lost connection to the ldap server (ie, the ldap server died) dovecot-auth would never reconnect to the ldap server and all subsequent auth attempts would fail. after a little more digging, i discovered that if the ldap server went down and came back up before the next dovecot request then everything would be fine. however, if a request came in while the ldap server was down then dovecot-auth would "cache" that the server was unavailable and never recheck it. i believe i tracked it down to a couple lines in db_ldap_bind and fixed it - dovecot-auth is reconnecting to ldap in the condition where it was not previously: --- dovecot-1.0.3/src/auth/db-ldap.c 2007-10-15 18:26:55.983349000 +0000 +++ dovecot-1.0.3/src/auth/db-ldap.c.new 2007-10-15 18:28:03.124136000 +0000 @@ -446,7 +446,10 @@ msgid = ldap_bind(conn->ld, conn->set.dn, conn->set.dnpass, LDAP_AUTH_SIMPLE); if (msgid == -1) { - db_ldap_connect_finish(conn, ldap_get_errno(conn)); + if (db_ldap_connect_finish(conn, ldap_get_errno(conn)) < 0) { + /* lost connection, close it */ + ldap_conn_close(conn, TRUE); + } i_free(ldap_request); return -1; }

3 3