- 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

[Dovecot] sieve variables
by Pavel Volkovitskiy 29 Dec '07

29 Dec '07

Hello! I wonder if that possible to add support for sieve variables extension in upcoming dovecot 1.1? ( ftp://ftp.rfc-editor.org/in-notes/internet-drafts/draft-ietf-sieve-variable… ) -- Pavel

3 2

[Dovecot] dovecot: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server
by Rolf E. Sonneveld 28 Dec '07

28 Dec '07

Hi, I'm new to the list; excuse me if this has been asked recently/before. running: # dovecot --version 1.0.8 Output of dovecot -n: base_dir: /var/run/dovecot protocols: none ssl_disable: yes login_dir: /var/run/dovecot/login login_executable: /usr/local/dovecot/libexec/dovecot/imap-login auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: ldap args: /usr/local/dovecot/etc/dovecot-ldap.conf userdb: driver: ldap args: /usr/local/dovecot/etc/dovecot-ldap.conf socket: type: listen client: path: /usr/local/postfix/spool/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot-auth-master mode: 438 Using dovecot only for the purpose of providing SMTP AUTH service for Postfix, using Active Directory (AD) as authentication source. As you can see from the config, connectivity between Dovecot and AD is implemented using LDAP. Contents of /usr/local/dovecot/etc/dovecot-ldap.conf (some site-specific info masqueraded): auth_bind = yes pass_filter = (sAMAccountName=%u) hosts = AD1.domain.com:3268 AD2.domain.com:3268 dn = CN=Service Account Postfix,OU=Services,DC=domain,DC=com dnpass = secret ldap_version = 3 base = DC=domain,DC=com scope = subtree Now, this works fine and authentication via SMTP AUTH + Dovecot works perfect. Yet, every 15 minutes I get the following warning in the syslog logfile: Dec 24 07:20:00 hostname dovecot: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server Dec 24 07:35:01 hostname dovecot: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server Dec 24 07:50:01 hostname dovecot: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server Dec 24 08:05:02 hostname dovecot: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server Dec 24 08:20:02 hostname dovecot: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server Dec 24 08:35:03 hostname dovecot: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server I've looked through the archives and it seems that this problem is caused by the fact that Dovecot (using the OpenLDAP client libraries?) keeps the LDAP connection open; after (in our case) 15 minutes Active Directory closes the connection and Dovecot signals this in the syslog (and presumably automatically will create a new connection to AD). I'm pretty sure that the OpenLDAP client libraries provide options to use a client-side timeout for LDAP connections. My questions are: * is there a reason that Dovecot wants to keep the LDAP connection open? * Will the new V1.1 version have a config parameter to set the LDAP client timeout or a default timeout value to close the connection? * If there's no 'fix' foreseen for V1.1, I'd like to file a request to add such a parameter. How can I file such a request? The warning is annoying; the sysadmin will create a filter, to filter the warning out from the syslog, but I'm afraid that if there's a real problem with authentication, that will be filtered too and the real problem is not noticed, before users start to complain. /rolf

2 3

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

28 Dec '07

Hi Timo, I think I've hit a separator bug: This is namespace query of dovecot and source server: ---snip--- * OK Dovecot ready. 1 login ... 1 OK Logged in. 2 NAMESPACE * NAMESPACE (("INBOX/" ".")) NIL NIL 2 OK Namespace completed. 3 logout * BYE Logging out 3 OK Logout completed. Connection closed by foreign host. Escape character is '^]'. * OK [CAPABILITY IMAP4 IMAP4rev1 LITERAL+ ID STARTTLS AUTH=CRAM-MD5 AUTH=DIGEST-MD5 AUTH=NTLM AUTH=SRP AUTH=OTP AUTH=PASSDSS-3DES-1 SASL-IR] Cyrus IMAP4 v2.3.8 server ready 1 login ... 1 OK [CAPABILITY IMAP4 IMAP4rev1 LITERAL+ ID LOGINDISABLED ACL RIGHTS=kxte QUOTA MAILBOX-REFERRALS NAMESPACE UIDPLUS NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND BINARY SORT SORT=MODSEQ THREAD=ORDEREDSUBJECT THREAD=REFERENCES ANNOTATEMORE CATENATE CONDSTORE IDLE LISTEXT LIST-SUBSCRIBED X-NETSCAPE URLAUTH] User logged in 2 NAMESPACE * NAMESPACE (("INBOX/" "/")) (("user/" "/")) (("" "/")) 2 OK Completed 3 logout * BYE LOGOUT received ---snip--- So Dovecot is stating Namespace separator is ".". But my dovecot -n namespace section shows: namespace: type: private separator: / prefix: INBOX/ inbox: yes list: yes subscriptions: yes According to this I've set separator to "/". And this is the problem. I think problem arised somewhere between beta9 and beta11, as it worked before... The separator in imapsync was for both "/" (--sep1 /, --sep2 /), I just played with all possibilities... Well, never mind if v1.2 or v2.0, as long as LMTP makes it in ;) Anyway, we can provide some good stress testing in such an environment... Regards and for all Merry Christmas and a happy new year! Sebastian ----- Ursprüngliche Mail ---- Von: Timo Sirainen <tss(a)iki.fi> An: ja nein <reg9009(a)yahoo.de> CC: dovecot(a)dovecot.org Gesendet: Freitag, den 21. Dezember 2007, 18:19:31 Uhr Betreff: Re: [Dovecot] namespace problem / 1.1beta11 On Wed, 2007-12-12 at 07:16 +0000, ja nein wrote: > From Folder [INBOX/Trash] .. > /home/imapsync/imapsync --host1 ip.of.host.1 --user1 user1 --password1 password --host2 127.0.0.1 --user2 user2 --password2 password --authmech2 LOGIN --regextrans2 s/\./_/g --delete2 --sep1 . --sep2 . --justfolders Shouldn't those be -sep1 / -sep2 /. Or at least the one that's on Dovecot's side. > Btw., as we work in a load balanced environment, LMTP delivery would be a great feature for upcoming releases, as it would enable people to use multiple frontends of SMTP servers without the need of connecting them to a somewhat shared file system. Forwarding all mail to a SMTP server on the machine running dovecot and doing delivery there isn't the favoured option (at least for us). Yes, LMTP would be nice, but it pretty much requires v2.0 framework. I'm still not sure if the next version will be v1.2 or v2.0.. Jetzt Mails schnell in einem Vorschaufenster überfliegen. Dies und viel mehr bietet das neue Yahoo! Mail - www.yahoo.de/mail

3 2

[Dovecot] assertion on deliver (1.1.beta10)
by Nuno Lopes 28 Dec '07

28 Dec '07

Hi, I'm testing version 1.1.beta10 and getting these assertions on deliver: file index-transaction.c: line 54 (index_transaction_finish_rollback): assertion failed: (t->mail_ref_count == 0) This was after an upgrade from a 1.0 release candidate. If you need I can try and reproduce this in a more controled environment to pinpoint the problem. Thanks, -- Nuno Lopes

2 4

[Dovecot] Dovecot + Cygwin the 2nd
by Ronny 28 Dec '07

28 Dec '07

Hi, i still try to get dovecot to run under cygwin. After a post on the cygwin list i am able tu run dovecot. Under Cygwin you have to run dovecot by inetd. Starting the binary "dovecot.exe" does not work. Well the server is running but answers with a fatal error. Account: 'localhost', Server: 'localhost', Protokoll: POP3, Serveranswer: 'Fatal: EOF while reading environment from master', Port: 110, Secure (SSL): No, error on server: 0x800CCC90, Fehlernummer: 0x800CCC90 This error is from Outlook, Thunderbird just says there is an error without any error message. So maybe you can help me to bring my story to a hapy end ;-) Cheers Ronny

3 11

[Dovecot] cache files corruption
by Dmitry Pryadko 28 Dec '07

28 Dec '07

Here what one of my users sometimes gets in logs when using IMAP: dovecot: IMAP(skribtsov(a)pawlin.mass.hc.ru): Disconnected in IDLE dovecot: IMAP(skribtsov(a)pawlin.mass.hc.ru): Maildir /usr/local/mail/pawlin.mass.hc.ru/skribtsov/Maildir sync: UID inserted in the middle of mailbox (59 > 16, file = 1198267793.H747026P68033.mail5.hc.ru:2,RS) dovecot: IMAP(skribtsov(a)pawlin.mass.hc.ru): Disconnected: Mailbox is in inconsistent state, please relogin. dovecot: IMAP(skribtsov(a)pawlin.mass.hc.ru): Maildir /usr/local/mail/pawlin.mass.hc.ru/skribtsov/Maildir sync: UID inserted in the middle of mailbox (59 > 16, file = 1198267793.H747026P68033.mail5.hc.ru:2,RS) dovecot: IMAP(skribtsov(a)pawlin.mass.hc.ru): Disconnected: Mailbox is in inconsistent state, please relogin. dovecot: IMAP(skribtsov(a)pawlin.mass.hc.ru): Corrupted transaction log file /usr/local/mail/pawlin.mass.hc.ru/skribtsov/Maildir/dovecot.index.log.2: invalid indexid (1198254020 != 1198498301) dovecot: IMAP(skribtsov(a)pawlin.mass.hc.ru): Corrupted index cache file /usr/local/mail/pawlin.mass.hc.ru/skribtsov/Maildir/dovecot.index.cache: indexid changed After that, some messages could "disappear" from messages list. And then maybe "appear" again. When I delete dovecot.* files, all goes ok. I use NFS storage. BTW, it seems like this problem exists only when working with M$ Outlook :) # 1.0.5: /usr/local/etc/dovecot.conf syslog_facility: local7 protocols: imap pop3 imaps pop3s ssl_cert_file: /etc/ssl/mail5.hc.ru.pem ssl_key_file: /etc/ssl/mail5.hc.ru.pem 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 login_greeting: Mail server ready. login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no login_max_processes_count: 256 max_mail_processes: 2048 verbose_proctitle: yes first_valid_uid: 90 last_valid_uid: 65000 first_valid_gid: 90 last_valid_gid: 90 mail_extra_groups: mail mail_location: maildir:~/Maildir mmap_disable: yes lock_method: dotlock 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_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota 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 cram-md5 verbose: yes debug: yes debug_passwords: yes worker_max_count: 150 passdb: driver: sql args: /usr/local/etc/dovecot-sql.conf userdb: driver: prefetch userdb: driver: sql args: /usr/local/etc/dovecot-sql.conf socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: vexim plugin: quota: maildir -- Dmitry Pryadko http://www.hc.ru

2 5

[Dovecot] per user quota
by Massimo Maioli 28 Dec '07

28 Dec '07

Hi, i've tryed to setup per user quota with postfix/dovecot, but without luck. My configuration is: postfix 2.3.8 with virtualdomain on mysql (http://workaround.org tutorial) dovecot 1.0.9 IMAP/PO3 OK on dovecot config, i've made the changes for the quota plugin, i've setup the gereral quota at 20MB, with this configuration: quota = maildir:storage=20480:messages=1000 it works very well, from telnet connection and squirrelmail, i see the right % of quota used. My problem is the per user quota, if i want give some user, more or minus space, i'm not able to do this. I've added a quota field to the mysql that read dovecot, but i don't know ho to read this in dovecot-mysql.conf. Someone can help me? Thanks

2 1

[Dovecot] Audit log?
by Bjørn T Johansen 26 Dec '07

26 Dec '07

Where can I found the log that dovecot writes if a user fails to log in? I am authenticating agains an sql db, but I can't find where dovecot logs this, if it does? Regards, BTJ -- ----------------------------------------------------------------------------------------------- Bjørn T Johansen btj(a)havleik.no ----------------------------------------------------------------------------------------------- Someone wrote: "I understand that if you play a Windows CD backwards you hear strange Satanic messages" To which someone replied: "It's even worse than that; play it forwards and it installs Windows" -----------------------------------------------------------------------------------------------

5 9

[Dovecot] v1.1.beta12 released
by Timo Sirainen 25 Dec '07

25 Dec '07

http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta12.tar.gz http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta12.tar.gz.sig Still not a release candidate, maybe the next one.. This release fixes a lot of bugs and adds some new sanity checks. Fixes quite a lot of mbox problems. v1.1.beta11 (no other versions) had a potential security hole where memory was free()d multiple times. \Recent flags should work perfectly now with mbox. Still somewhat broken with maildir.

2 1

[Dovecot] Dovecot Log control=
by Evaggelos Balaskas 24 Dec '07

24 Dec '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, i use dovecot-1.0.9 + sieve plugin 1.0.2 pop3 - imap, virtual users from file with MD5-CRYPT some with maildir some with mbox, spamassasin + sieve filter per user, etc - etc and everything are simple perfect. The only real question i have is this: in the logs when the dovect LDA deliver a mail to a maildir account is something control= What exactly is this ? deliver(ebalaskas): Dec 14 23:32:35 Info: maildir: root=/var/mail/folders/ebalaskas, index=/var/mail/index/ebalaskas, control=, inbox= -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHYvb0WIK+Pe9twhoRAnyVAKCKHsvi7DJ01uYnAQvbeLNh85HBoQCgxtSp Sm9WetpSQMJsiyp0wAkReOQ= =k0f0 -----END PGP SIGNATURE-----

2 2

[Dovecot] Brute Force Blocking?
by Ben Cadieux 24 Dec '07

24 Dec '07

Hi Everyone, Before I begin, I'd just like to mention: I love dovecot. Thank you :) Anyway, today I had 8000 login attempts to my dovecot server in an hour before blocking the IP with my firewall. After googling, I didn't see very much discussion on the topic. There was some mention of blocksshd which was supposed to support dovecot in the next release (but doesn't appear to) and also fail2ban. While a script that parses logfiles will work, I'm not sure that this is the best way to go about handling repeated authentication failure. Would it not be best built into dovecot? Are there any plans for this? Best Regards, Ben Cadieux

8 8

[Dovecot] Compact all maildirs with dovecot-1.0.9?
by Jeff Kowalczyk 23 Dec '07

23 Dec '07

I'm running dovecot-1.0.9 on Gentoo Linux. I recently observed a large increase in disk usage on this dedicated mailserver. I attribute it to high spam traffic and/or large attachments for legit email retained on the server. How can I run a command equivalent to an IMAP client's 'Compact Folder' on the entire tree of maildirs under each /home/(user)? Thanks.

2 1

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

22 Dec '07

yep, originally I want Dovecot to behave exactly the same like our Cyrus environment regarding namespaces, in preparation of a migration :) The first login shows Dovecot output, second show Cyrus, for comparison... Regards, Sebastian ----- Ursprüngliche Mail ---- Von: Charles Marcus <CMarcus(a)Media-Brokers.com> An: Dovecot Mailing List <dovecot(a)dovecot.org> Gesendet: Samstag, den 22. Dezember 2007, 16:24:00 Uhr Betreff: Re: [Dovecot] namespace problem / 1.1beta11 On 12/22/2007, ja nein (reg9009(a)yahoo.de) wrote: > AUTH=DIGEST-MD5 AUTH=NTLM AUTH=SRP AUTH=OTP AUTH=PASSDSS-3DES-1 > SASL-IR] Cyrus IMAP4 v2.3.8 server ready Cyrus?? -- Best regards, Charles __________________________________ Ihr erstes Baby? Holen Sie sich Tipps von anderen Eltern. www.yahoo.de/clever

2 1

Re: [Dovecot] v1.1.beta12 deliver crashes (arvids) Ditto!
by Jerry Yeager 22 Dec '07

22 Dec '07

On Dec 22, 2007, at 5:00 AM, dovecot-request(a)dovecot.org wrote: (stuff cut out) > Message: 10 > Date: Sat, 22 Dec 2007 11:12:30 +0200 > From: arvids <arvids(a)mpe.lv> > Subject: [Dovecot] v1.1.beta12 deliver crashes > To: Dovecot Mailing List <dovecot(a)dovecot.org> > Message-ID: <200712221112.30760.arvids(a)mpe.lv> > Content-Type: text/plain; charset="us-ascii" > > Hello, > > v1.1.beta12 deliver crashes: > > Dec 22 11:05:29 iserver deliver(tests2): file index-mail.c: line > 1042 (index_mail_close): assertion failed: (!mail- > >data.destroying_stream) > Dec 22 11:05:29 iserver deliver(tests2): Raw backtrace: /usr/local/ > dovecot/libexec/dovecot/deliver(i_syslog_fatal_handler+0x2c) > [0x80baa8c] -> /usr/local/do > vecot/libexec/dovecot/deliver [0x80ba88b] -> /usr/local/dovecot/ > libexec/dovecot/deliver [0x80852e1] -> /usr/local/dovecot/libexec/ > dovecot/deliver(index_mail > _free+0xe) [0x8085f5e] -> /usr/local/dovecot/libexec/dovecot/ > deliver(mail_free+0x10) [0x80a9b70] -> /usr/local/dovecot/libexec/ > dovecot/deliver(main+0xfce) [ > 0x805a9be] -> /lib/libc.so.6(__libc_start_main+0xd8) [0xb7e69df8] - > > /usr/local/dovecot/libexec/dovecot/deliver [0x8058a51] > more stuff cut out > > Regards, Arvids > > > ------------------------------ > I am getting essentially the same type of error, except that the message actually is delivered along with a receipt to the sender that it was not able to be delivered. Dec 22 11:33:57 mac-g5 deliver(jerry(a)scene-naturally.dyndns.org) [28416]: msgid=<B865E78F-83BB-4B46-864C-44EEC1BC01AF(a)scene-naturally.dyndns.org >: saved mail to INBOX Dec 22 11:33:57 mac-g5 deliver(jerry(a)scene-naturally.dyndns.org) [28416]: file index-mail.c: line 1042 (index_mail_close): assertion failed: (!mail->data.destroying_stream) Dec 22 11:33:57 mac-g5 deliver(testuser(a)scene-naturally.dyndns.org) [28417]: auth input: testuser(a)scene-naturally.dyndns.org Dec 22 11:33:57 mac-g5 deliver(jerry(a)scene-naturally.dyndns.org) [28416]: Raw backtrace: 2 deliver 0x00000000000c8ae4 i_syslog_fatal_handler + 124 -> 3 deliver 0x00000000000c8598 i_fatal + 0 -> 4 deliver 0x0000000000057f5c index_mail_close + 264 -> 5 deliver 0x0000000000058958 index_mail_free + 68 -> 6 deliver 0x00000000000a406c mail_free + 68 - > 7 deliver 0x00000000000055d8 main + 4344 -> 8 deliver 0x00000000000010d0 start + 68 Dec 22 11:33:58 mac-g5 postfix/pipe[28415]: 251EE4D094C: to=<jerry(a)scene-naturally.dyndns.org >, relay=dovecot, delay=0.38, delays=0.02/0.04/0/0.32, dsn=5.3.0, status=bounced (Command died with signal 6: "/usr/local/libexec/ dovecot/deliver") Dec 22 11:33:58 jerry-yeagers-power-mac-g5 postfix/qmgr[67]: 251EE4D094C: removed Switching to using the Postfix deliver works and it seems everything else in the new beta 12, so far, is fine. Running on OS X 10.5.1 Jerry

1 0

[Dovecot] v1.1.beta12 deliver crashes
by arvids 22 Dec '07

22 Dec '07

Hello, v1.1.beta12 deliver crashes: Dec 22 11:05:29 iserver deliver(tests2): file index-mail.c: line 1042 (index_mail_close): assertion failed: (!mail->data.destroying_stream) Dec 22 11:05:29 iserver deliver(tests2): Raw backtrace: /usr/local/dovecot/libexec/dovecot/deliver(i_syslog_fatal_handler+0x2c) [0x80baa8c] -> /usr/local/do vecot/libexec/dovecot/deliver [0x80ba88b] -> /usr/local/dovecot/libexec/dovecot/deliver [0x80852e1] -> /usr/local/dovecot/libexec/dovecot/deliver(index_mail _free+0xe) [0x8085f5e] -> /usr/local/dovecot/libexec/dovecot/deliver(mail_free+0x10) [0x80a9b70] -> /usr/local/dovecot/libexec/dovecot/deliver(main+0xfce) [ 0x805a9be] -> /lib/libc.so.6(__libc_start_main+0xd8) [0xb7e69df8] -> /usr/local/dovecot/libexec/dovecot/deliver [0x8058a51] My dovecot -n: # 1.1.beta12: /usr/local/dovecot/etc/dovecot.conf base_dir: /var/run/dovecot/ syslog_facility: local0 protocols: pop3 imap ssl_cert_file: /etc/postfix/mail-cert.pem ssl_key_file: /etc/postfix/mail-key.pem disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable(default): /usr/local/dovecot/libexec/dovecot/imap-login login_executable(imap): /usr/local/dovecot/libexec/dovecot/imap-login login_executable(pop3): /usr/local/dovecot/libexec/dovecot/pop3-login login_greeting: Server. login_process_per_connection: no login_processes_count: 5 login_max_processes_count: 32 verbose_proctitle: yes first_valid_uid: 95 first_valid_gid: 95 mail_uid: 95 mail_gid: 95 mail_location: maildir:~/Maildir mail_debug: yes fsync_disable: yes mail_executable(default): /usr/local/dovecot/libexec/dovecot/rawlog /usr/local/dovecot/libexec/dovecot/imap mail_executable(imap): /usr/local/dovecot/libexec/dovecot/rawlog /usr/local/dovecot/libexec/dovecot/imap mail_executable(pop3): /usr/local/dovecot/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/dovecot/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail imap_client_workarounds(imap): delay-newmail imap_client_workarounds(pop3): pop3_enable_last(default): no pop3_enable_last(imap): no pop3_enable_last(pop3): yes pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh namespace: type: private separator: . inbox: yes list: yes subscriptions: yes auth default: mechanisms: plain login digest-md5 cram-md5 apop cache_size: 1024 cache_ttl: 600 cache_negative_ttl: 60 user: doveauth verbose: yes passdb: driver: sql args: /usr/local/dovecot/etc/dovecot-sql.conf userdb: driver: prefetch userdb: driver: sql args: /usr/local/dovecot/etc/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail plugin: quota: dict:::proxy:/var/run/dovecot/dict-server:quotadict dict: quotadict: mysql:/usr/local/dovecot/etc/dovecot-sql-dict-quota.conf Regards, Arvids

2 1

[Dovecot] How to restore old mailbox
by Simon Gao 22 Dec '07

22 Dec '07

Hi, I have issue with one user mailbox in /var/spool/mail. I have to restore older version of the same mailbox file over the newer one. What's the best way to do this? Simon

2 1

[Dovecot] Squirrelmail + Dovecot + Maildir
by Vicki Stanfield 21 Dec '07

21 Dec '07

I have been struggling with getting my Fedora 7 box set up to use dovecot with Squirrelmail and Maildir. It works correctly with the exception of writing outgoing mail to the right folder (.Sent) or drafts (.Drafts). If I send a mail with Mutt, it writes the mail to the right place, so it has to be squirrelmail config or dovecot config. I want to use .Sent for sent-mail (~user/Maildir/.Sent) and .Drafts for drafts (~user/Maildir/.Drafts). Here is what I see in /etc/squirrelmail/config.php $optional_delimiter = '.'; [snip] $default_folder_prefix = ''; $trash_folder = 'Trash'; $sent_folder = 'Sent'; $draft_folder = 'Drafts'; $default_move_to_trash = true; $default_move_to_sent = true; $default_save_as_draft = true; The error in the browser is: * ERROR : Bad or malformed request.* Server responded: {830} BAD Error in IMAP command : Unknown command. and in the logs I see this: Dec 18 09:41:56 opus postfix/smtpd[12747]: connect from localhost[127.0.0.1] Dec 18 09:41:56 opus postfix/smtpd[12747]: 4CB7329B00B2: client=localhost[127.0.0.1] Dec 18 09:41:56 opus postfix/cleanup[12750]: 4CB7329B00B2: message-id=<51150.127.0.1.1.1197988916.squirrel(a)127.0.1.1> Dec 18 09:41:56 opus postfix/qmgr[2650]: 4CB7329B00B2: from=<vic(a)thepenguin.net>, size=1015, nrcpt=1 (queue active) Dec 18 09:41:56 opus postfix/smtpd[12747]: disconnect from localhost[127.0.0.1] Dec 18 09:41:56 opus dovecot: imap-login: Login: user=<vic>, method=PLAIN, rip=::ffff:127.0.1.1, lip=::ffff:127.0.1.1, secured Dec 18 09:41:56 opus dovecot: IMAP(vic): Disconnected: Too many invalid IMAP commands. Dec 18 09:41:59 opus postfix/smtp[12751]: 4CB7329B00B2: to=<vstanfield(a)other.com>, relay=platinum.fusionalliance.com[168.215.73.114]:25, delay=3.6, delays=0.08/0.01/2.6/0.89, dsn=2.0.0, status=sent (250 Requested mail action okay, completed) Dec 18 09:41:59 opus postfix/qmgr[2650]: 4CB7329B00B2: removed As you can surmise from the logs, the mail does get sent. Anybody see my mistake? CaptainVic

5 5

[Dovecot] 1.1.beta11 crashes
by Brian Taber 21 Dec '07

21 Dec '07

I am running 1.1.beta11 because I was having locking and coruption issues with indexes and mailbox on the latest release version. Some of my previous corrupted indexes caused an issue with 1.1.beta11: Dec 20 21:25:40 ra dovecot: IMAP(bodil(a)mydomain.com): Raw backtrace: imap [0x47ef81] -> imap [0x47eca6] -> imap [0x42c3bc] -> imap [0x42f201] -> imap [0x42f324] -> imap [0x41d585] -> imap(imap_fetch+0x147) [0x41cb17] -> imap(cmd_fetch+0x1bc) [0x41686c] -> imap(cmd_uid+0x52) [0x419c42] -> imap [0x41a508] -> imap [0x41a5aa] -> imap(client_input+0x72) [0x41ab72] -> imap(io_loop_handler_run+0x106) [0x485746] -> imap(io_loop_run+0x1d) [0x484dbd] -> imap(main+0x401) [0x421f51] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x30af61d8a4] -> imap [0x414fa9] Dec 20 21:25:40 ra dovecot: child 4353 (imap) killed with signal 6 Dec 20 21:28:24 ra dovecot: IMAP(bodil(a)mydomain.com): file maildir-uidlist.c: line 840 (maildir_uidlist_set_ext_real): assertion failed: (rec != NULL) Dec 20 21:28:24 ra dovecot: IMAP(bodil(a)mydomain.com): Raw backtrace: imap [0x47ef81] -> imap [0x47eca6] -> imap [0x42c3bc] -> imap [0x42f201] -> imap [0x42f324] -> imap [0x41d585] -> imap(imap_fetch+0x147) [0x41cb17] -> imap(cmd_fetch+0x1bc) [0x41686c] -> imap(cmd_uid+0x52) [0x419c42] -> imap [0x41a508] -> imap [0x41a5aa] -> imap(client_input+0x72) [0x41ab72] -> imap(io_loop_handler_run+0x106) [0x485746] -> imap(io_loop_run+0x1d) [0x484dbd] -> imap(main+0x401) [0x421f51] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x30af61d8a4] -> imap [0x414fa9] Dec 20 21:28:24 ra dovecot: child 4385 (imap) killed with signal 6 Dec 20 21:30:08 ra dovecot: IMAP(bodil(a)mydomain.com): file maildir-uidlist.c: line 840 (maildir_uidlist_set_ext_real): assertion failed: (rec != NULL) Dec 20 21:30:08 ra dovecot: IMAP(bodil(a)mydomain.com): Raw backtrace: imap [0x47ef81] -> imap [0x47eca6] -> imap [0x42c3bc] -> imap [0x42f201] -> imap [0x42f324] -> imap [0x41d585] -> imap(imap_fetch+0x147) [0x41cb17] -> imap(cmd_fetch+0x1bc) [0x41686c] -> imap(cmd_uid+0x52) [0x419c42] -> imap [0x41a508] -> imap [0x41a5aa] -> imap(client_input+0x72) [0x41ab72] -> imap(io_loop_handler_run+0x106) [0x485746] -> imap(io_loop_run+0x1d) [0x484dbd] -> imap(main+0x401) [0x421f51] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x30af61d8a4] -> imap [0x414fa9] Dec 20 21:30:08 ra dovecot: child 4397 (imap) killed with signal 6 I removed the index files for that mainbox and that error went away, but it caused another error: Dec 20 21:45:29 ra dovecot: IMAP(bodil(a)mydomain.com): file_dotlock_open() failed with file /mailindex/mydomain.com/bodil/.INBOX/dovecot.index.log: No such file or directory I had to recreate the .INBOX folder manually and all was great. The funny thing is it had already created all the other folders in the mailbox....

2 1

[Dovecot] Recent message flag unavailable ?
by Nicolas KOWALSKI 21 Dec '07

21 Dec '07

Hello, When a message is copied or newly-delivered to a folder, it does not have the "recent" flag set. Is there something in the configuration to activate it ? Thanks. # dovecot -n # 1.0.9: /usr/local/etc/dovecot.conf protocols: imap login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login mail_location: mbox:~/mail:INBOX=~/mail/INBOX:INDEX=/var/cache/dovecot mbox_write_locks: fcntl auth default: passdb: driver: pam userdb: driver: passwd The MUA which shows it is Alpine 0.999999. -- Nicolas

2 2

[Dovecot] namespace problem / 1.1beta11
by ja nein 21 Dec '07

21 Dec '07

Hi all, actually I got a problem with the namespaces in dovecot 1.1 beta11. It occured after purging index files and resynch via imapsync. Dovecot complains about "Unknown namespace", though it worked with versions before. I cannot comfirm for 1.1beta10, but I surely know 1.1beta9 worked with these settings. Example: From Folder [INBOX/Trash] To Folder [___________] To Folder ___________ does not exist Creating folder [___________] Couldn't create [___________]266 NO Unknown namespace. Used imapsync command: /home/imapsync/imapsync --host1 ip.of.host.1 --user1 user1 --password1 password --host2 127.0.0.1 --user2 user2 --password2 password --authmech2 LOGIN --regextrans2 s/\./_/g --delete2 --sep1 . --sep2 . --justfolders Another run with different namespace settings shows up the folders in Thunderbird as INBOX^2002, INBOX^Trash ans so on... My goal is to keep all client settings when migrating a bigger installation of cyrus to dovecot. For know all folders in Cyrus appear as subfolders of INBOX, which I had achieved with dovecot < 1.1beta11. Any ideas? Btw., as we work in a load balanced environment, LMTP delivery would be a great feature for upcoming releases, as it would enable people to use multiple frontends of SMTP servers without the need of connecting them to a somewhat shared file system. Forwarding all mail to a SMTP server on the machine running dovecot and doing delivery there isn't the favoured option (at least for us). And a huge thx to Timo on working that hard on such a great working product! Regrads, Sebastian Dovecot conf putput: # 1.1.beta11: /etc/dovecot/dovecot.conf base_dir: /home/dovecot/ syslog_facility: local3 protocols: imap pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /home/dovecot/var/run/login login_executable(default): /opt/dovecot-1.1-beta11/libexec/dovecot/imap-login login_executable(imap): /opt/dovecot-1.1-beta11/libexec/dovecot/imap-login login_executable(pop3): /opt/dovecot-1.1-beta11/libexec/dovecot/pop3-login verbose_proctitle: yes mail_location: maildir:/home/dovecot/mail/%d/%u:INDEX=/home/dovecot/index/%d/%u mail_executable(default): /opt/dovecot-1.1-beta11/libexec/dovecot/imap mail_executable(imap): /opt/dovecot-1.1-beta11/libexec/dovecot/imap mail_executable(pop3): /opt/dovecot-1.1-beta11/libexec/dovecot/pop3 mail_plugins(default): fts fts_squat mail_plugins(imap): fts fts_squat mail_plugins(pop3): mail_plugin_dir(default): /opt/dovecot-1.1-beta11/lib/dovecot/imap mail_plugin_dir(imap): /opt/dovecot-1.1-beta11/lib/dovecot/imap mail_plugin_dir(pop3): /opt/dovecot-1.1-beta11/lib/dovecot/pop3 namespace: type: private separator: / prefix: INBOX/ inbox: yes list: yes subscriptions: yes auth default: mechanisms: plain login digest-md5 cram-md5 verbose: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /home/dovecot/var/run/dovecot/auth-client master: path: /home/dovecot/var/run/dovecot/auth-master user: vuser plugin: fts: squat __________________________________ Ihr erstes Baby? Holen Sie sich Tipps von anderen Eltern. www.yahoo.de/clever

2 1

[Dovecot] Dovecot truncating messages and/or attachments
by fp＠kraptastic.com 21 Dec '07

21 Dec '07

Hello, I am having problems with Dovecot not sending clients emails bigger then 8-12k (it varies) or attachments bigger then 8-12k. I am also getting 'Corrupted transaction log file' errors ' unexpected end of file while reading header' I have deleted the dovecot.index.log, dovecot.index.cache, and dovecot.index several dozen times. I started off using Centos 5, with their package of dovecot 1.05, after seeing that there were problems in the package in the http://wiki.dovecot.org/WhyDoesItNotWork, I went with a source install of dovecot 1.09. Here is my cfg info: # dovecot -n # 1.0.9: /etc/dovecot.conf protocols: pop3 pop3s imap imaps ssl_cert_file: /etc/dovecert.pem ssl_key_file: /etc/dovekey.pem disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_process_size: 128 first_valid_uid: 106 last_valid_uid: 106 mail_extra_groups: mail mail_location: maildir:/var/spool/postfix/virtual/%d/%u mail_debug: yes maildir_copy_with_hardlinks: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib64/dovecot/imap mail_plugin_dir(imap): /usr/lib64/dovecot/imap mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3 imap_client_workarounds(default): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail imap_client_workarounds(pop3): outlook-idle pop3_uidl_format: %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 user: vmail passdb: driver: sql args: /etc/dovecot-mysql.conf userdb: driver: sql args: /etc/dovecot-mysql.conf userdb: driver: prefetch socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: vmail master: path: /var/run/dovecot/auth-master mode: 432 user: vmail group: vmail (the login process is 128 because i was experimenting with various numbers (32,64,80,etc) The /var/log/maillog has hundreds of these: Dec 11 16:27:42 le1 dovecot: POP3(xxx@xxx): Corrupted transaction log file /var/spool/postfix/virtual/xxx.com/xxx(a)xxx/dovecot.index.log: unexpected end of file while reading header I turned made it so the mail stays on the server, so i can see that the mail stored there by postfix is the correct size. When email clients download mail through pop3 or pop3s it only downloads 4,8, or 12 k worth of the email (whether it has attachments or not). Here is an example transaction: Dec 11 17:18:31 le1 dovecot: auth(default): client in: AUTH 1 PLAIN service=POP3 lip=142.179.211.193 rip=24.71.237.54 resp= Dec 11 17:18:31 le1 dovecot: auth(default): client out: CONT 1 Dec 11 17:18:31 le1 dovecot: auth(default): client in: CONT 1 AHNoYXduQGxhbmdmb3JkZWxlY3RyaWMuY2EAdW5mdW5m Dec 11 17:18:31 le1 dovecot: auth(default): cache(shawn(a)xxx.com,24.71.237.54): hit Dec 11 17:18:31 le1 dovecot: auth(default): client out: OK 1 user=shawn(a)xxx.com Dec 11 17:18:31 le1 dovecot: auth(default): master in: REQUEST 92 8447 1 Dec 11 17:18:31 le1 dovecot: pop3-login: Login: user=<shawn(a)xxx.com>, method=PLAIN, rip=24.71.237.54, lip=142.179.211.193 Dec 11 17:18:31 le1 dovecot: auth(default): master out: USER 92 shawn(a)xxx.com maildir=xxx.com/shawn@xxx.com/ uid=106 gid=106 Dec 11 17:18:31 le1 dovecot: POP3(shawn(a)xxx.com): Effective uid=106, gid=106 Dec 11 17:18:31 le1 dovecot: POP3(shawn(a)xxx.com): maildir: data=/var/spool/postfix/virtual/xxx.com/shawn@xxx.com Dec 11 17:18:31 le1 dovecot: POP3(shawn(a)xxx.com): maildir: root=/var/spool/postfix/virtual/xxx.com/shawn@xxx.com, index=/var/spool/postfix/virtual/xxx.com/shawn@xxx.com, control=, inbox= Dec 11 17:18:31 le1 dovecot: auth(default): new auth connection: pid=8487 Dec 11 17:18:31 le1 dovecot: POP3(shawn(a)xxx.com): Disconnected: Logged out top=0/0, retr=1/4215, del=0/1, size=70206 To be clear, if i telnet to 110, and manually do a retr on the message it only sends 4,8,or 12k worth of the message. So it does not appear to be a permission problem, it is reading and writing to the directory properly. The system is x86_64 centos 5, not using the standard dovecot nor postfix rpms that come with the distro. postfix from what I can tell, is working fine, but dovecot isn't. I'm going to try installing cyrus to make sure it's not postfix, but I'd really like to avoid cyrus if possible. Thanks in advance for any help.

2 1

[Dovecot] about quota_warning behavior
by naoki 21 Dec '07

21 Dec '07

Hi, We've been using v1.0.5 +quota_warning patch, however quota_warning does't seem to be working properly. For example, in order to enable 80% over for quota warning, and we configured like following: ----------------------------------------------------------------------- plugin { quota_warning = storage=80%% /usr/local/path/to/plugin } ----------------------------------------------------------------------- But it does not work. However we set quota_warning value to 20%, it seems to be working. ----------------------------------------------------------------------- plugin { quota_warning =storage=20%% /usr/local/path/to/plugin } ----------------------------------------------------------------------- If this is the case, do we always have to set quota value to what we have after subtracting the required quota warning value from 100. for example, if we want quota warning value to be 70%, we actually have to write 30% in configuration?? Will there be another patch to fix this? Thanks -- Naoki Takazawa Marino Ltd., Yokohama, JAPAN

2 1

Re: [Dovecot] 1.1.Beta9 deliver problem: Unknown mail storage driver raw
by ja nein 21 Dec '07

21 Dec '07

Hi Velko, I recently hit the same problem. You have to add raw storage driver to your compile options, meaning "--with-storages=maildir,mbox,dbox,raw,cydir", that will do the trick. Maybe it would be good to update the description of available storage drivers in configure script. Regards, Sebastian ----- Ursprüngliche Mail ---- Von: Velko Ivanov <dachev(a)nove.bg> An: dovecot(a)dovecot.org Gesendet: Samstag, den 1. Dezember 2007, 14:19:18 Uhr Betreff: [Dovecot] 1.1.Beta9 deliver problem: Unknown mail storage driver raw Hello, I'm new to dovecot, trying to configure a Postfix/Dovecot system. Got everything in place - smtp with dovecot SASL and imap working fine, maildir is created, thunderbird logs in successfuly .. but the Dovecot LDA gives me this error on delivery: "Couldn't create internal raw storage: Unknown mail storage driver raw". I tried searching the configuration manual, reference, google and this list's archives, but found no clue. Checked the source, but it will take me some time to figure out what is a storage driver and where is the "raw" one hiding, so if somebody could help, please .. I did it with userdb static initially - uid=dovecot_mail, gid=dovecot_mail, home=/usr/local/storage/mail/%d/%n but after reading, that some passdbs don't work with deliver&static, I moved everything to the db (found out that prefetch isn't working with deliver btw - moans about userdb_ entries not present, while the imap finds them and works happily). It didn't help. # 1.1.beta9: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot listen: mail.srv.ivanov-nest.com ssl_cert_file: /usr/local/etc/dovecot.crt ssl_key_file: /usr/local/etc/dovecot.key login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login mail_location: dbox:~/Maildir dotlock_use_excl: yes maildir_copy_preserve_filename: yes namespace: type: private inbox: yes hidden: yes list: yes subscriptions: yes auth default: mechanisms: plain login user: dovecot_db passdb: driver: sql args: /usr/local/etc/dovecot-sql.conf userdb: driver: sql args: /usr/local/etc/dovecot-sql.conf socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: dovecot_mail group: wheel Heute schon einen Blick in die Zukunft von E-Mails wagen? www.yahoo.de/mail

5 7

[Dovecot] 1.1 beta 11 - no quota warnings
by adam_jh＠hotmail.com 21 Dec '07

21 Dec '07

Having tried and failed to get 1.0.8 with quota-rewrite to send warnings, I removed the 1.0.8 and installed the latest 1.1 - however I still can't get the warnings! Can someone advise what might be wrong - it must be my configuration?? To compile 1.1 I used ./configure --with-deliver --with-mysql. I've chopped and changed my conf till I'm blue in the face. My dovecot-mysql.conf file does not override the quota, I've enabled the debug and verbose = yes - but they don't mention any quota warnings, just normal delivered logs. What else can I do? The process I use is to add up the maildirsize totals, set a storage figure in the conf which makes the maildirsize just less than 95%, then restart dovecot, send an email - and nothing - no warning is triggered! Any help appreciated - I've spent so long on this now. adam # 1.1.beta11: /usr/local/etc/dovecot.conf protocols: imap imaps pop3 pop3s 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 mail_extra_groups: mail mail_location: maildir:/var/vmail/%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_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota 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): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: user: nobody verbose: yes debug: yes passdb: driver: sql args: /usr/local/etc/dovecot-mysql.conf userdb: driver: sql args: /usr/local/etc/dovecot-mysql.conf socket: type: listen client: path: /var/spool/postfix/private/auth user: postfix group: mail master: path: /var/run/dovecot/auth-master user: vmail group: mail plugin: quota: maildir quota_rule: *:storage=220000b quota_warning: storage=95%% /usr/local/bin/quota-warning 90

3 4

[Dovecot] imap+unix users and pop3+virtual users
by Wendell Turner 21 Dec '07

21 Dec '07

This should be simple, but I'm missing something. My virtual users cannot access their mail. I would like Unix users to get their mail via imap which is deposited in /var/spool/mail/username. (This works.) I would like virtual users to get their mail via pop3 which is deposited in /var/spool/mail/vhosts/example.com/auser/mail/inbox (postfix does in fact put the mail there). Those users can get authenticated via file /var/dovecot/passwd, but cannot retrieve their mail. The log message is shown below. The file/directory is there, but doesn't dovecot see it? Thanks, Wendell -------------------- Info: POP3(auser(a)example.com): mbox: data=/var/spool/mail/vhosts/example.com/auser/mail/:INBOX=/var/mail/auser@e… Info: POP3(auser(a)example.com): mbox: root=/var/spool/mail/vhosts/example.com/auser/mail, index=/var/spool/mail/vhosts/example.com/auser/mail, inbox=/var/mail/auser(a)example.com Info: POP3(auser(a)example.com): Mailbox init failed top=0/0, retr=0/0, del=0/0, size=0 -------------------- /usr/sbin/dovecot -n # 1.0.7: /etc/dovecot.conf log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot-info.log protocols: pop3 imap imaps pop3s ssl_cert_file: /etc/CA/cert.pem ssl_key_file: /etc/CA/key.pem login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login mail_location: mbox:~/mail/:INBOX=/var/mail/%u mail_debug: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: pam passdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: passwd userdb: driver: static args: uid=vmail gid=vmail home=/var/spool/mail/vhosts/%d/%n

4 9

[Dovecot] upgrade to 1.1 and mail location
by lenny＠edpausa.com 21 Dec '07

21 Dec '07

I recently upgraded from 1.0.8 to 1.1-11 the only thing that was changed in the config file was the new syntax for mail location. default_mail_env = mbox:~/:INBOX=~/mbox to mail_location = mbox:~/:INBOX=~/mbox now some imap clients, like squirrellmail and pine have difficulties writting to Sent, Draft and sent-mail folders. In all cases the folders are visible and are present in .subsriptions file( although not seen as subscribed in squirrelmail), but the clients complain that folders already exist when trying to write to them after sending. has anyone run into this ? any suggestions ? thanks a lot.

2 1

[Dovecot] v1.1.beta11 quota plugin and dict server
by arvids 21 Dec '07

21 Dec '07

Hello, when dovecot is started, it prints the following error to the console: ILoading modules from directory: /usr/local/dovecot/lib/dovecot/imap IModule loaded: /usr/local/dovecot/lib/dovecot/imap/lib10_quota_plugin.so IEffective uid=65534, gid=65534, home= Idict quota: user = dump-capability, uri = proxy:/var/run/dovecot/dict-server:quotadict Enet_connect_unix(/var/run/dovecot/dict-server) failed: Connection refused It seems that problem is that dict server is not started yet. Later everything seems to be OK, so it is more cosmetic issue. My dovecot -n: # 1.1.beta11: /usr/local/dovecot/etc/dovecot.conf base_dir: /var/run/dovecot/ syslog_facility: local0 protocols: pop3 imap ssl_cert_file: /etc/postfix/mail-cert.pem ssl_key_file: /etc/postfix/mail-key.pem disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable(default): /usr/local/dovecot/libexec/dovecot/imap-login login_executable(imap): /usr/local/dovecot/libexec/dovecot/imap-login login_executable(pop3): /usr/local/dovecot/libexec/dovecot/pop3-login login_greeting: Server. login_process_per_connection: no verbose_proctitle: yes mail_uid: 95 mail_gid: 95 mail_location: maildir:~/Maildir mail_debug: yes fsync_disable: yes mail_executable(default): /usr/local/dovecot/libexec/dovecot/imap mail_executable(imap): /usr/local/dovecot/libexec/dovecot/imap mail_executable(pop3): /usr/local/dovecot/libexec/dovecot/pop3 mail_plugins: quota mail_plugin_dir(default): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/dovecot/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail imap_client_workarounds(imap): delay-newmail imap_client_workarounds(pop3): pop3_enable_last(default): no pop3_enable_last(imap): no pop3_enable_last(pop3): yes pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login digest-md5 cram-md5 apop user: doveauth verbose: yes passdb: driver: sql args: /usr/local/dovecot/etc/dovecot-sql.conf userdb: driver: prefetch userdb: driver: sql args: /usr/local/dovecot/etc/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth user: postfix group: postfix master: path: /var/run/dovecot/auth-master user: vmail group: vmail plugin: quota: dict:::proxy:/var/run/dovecot/dict-server:quotadict dict: quotadict: mysql:/usr/local/dovecot/etc/dovecot-sql-dict-quota.conf Regards, Arvids

3 5

[Dovecot] minor issue - dovecot -n output with 1.1.beta11
by arvids 21 Dec '07

21 Dec '07

Hello, when running diff for 'dovecot -n' outputs from beta10 and beta11(for the same config file), I noticed that 'dovecot -n' beta11 output does not show anymore the following parameters, which are set to non-default values(and which 'dovecot -a' shows): login_processes_count login_max_processes_count first_valid_uid first_valid_gid cache_size cache_ttl cache_negative_ttl mode(from auth default section) And by the way, parameters from lda section are not showed both with -a and -n. But it is so already for a long time, so I assume that it is OK :) Regards, Arvids

2 1

[Dovecot] Permission for /var/run/dovecot
by Dr. Ashok N. Ullal 21 Dec '07

21 Dec '07

I have just installed my mail server on a Ubuntu Linux V.7.10 box with sendmail and dovecot imap from the Ubuntu packages. Each time the machines boots, I get the following messages: Starting mail server: dovecotWarning: Fixing permissions of /var/run/dovecot to be world readable Warning: Corrected permissions for login directory /var/run/dovecot/login After the boot the permissions visible are: drwxr-xr-x root root /var/run/dovecot drwxr-x--- root dovecot /var/run/dovecot/login What permissions do I need to set so that the warnings do not appear?

3 2

[Dovecot] Dirsize quotas with 1.1beta9
by Dean Brooks 21 Dec '07

21 Dec '07

Hi, Anyone able to get 'dirsize' quotas to work properly under 1.1beta9? I can get them to reflect the size of the INBOX properly, but it never seems to be adding up the size of the files in the folder directory itself. I'll keep hammering away at it if others are able to use dirsize with no problems, but wanted to check first. -- Dean Brooks dean(a)iglou.com

2 1

[Dovecot] V1.1beta11 compile problem
by Stewart Dean 21 Dec '07

21 Dec '07

Using IBM's C for AIX V9 with Ralf Becker's AIX adaption, I see this: + exec /usr/vac/bin/xlc -DHAVE_CONFIG_H -I. -I. -I../.. -I/opt/freeware/include/ openssl -g -c close-keep-errno.c -M source='compat.c' object='compat.o' libtool=no DEPDIR=.deps depmode=aix /bin/sh ../../depcomp /usr/local/dovecot/dovecot-cc -DHAVE_CONFIG_H -I. -I. -I ../.. -I/opt/freeware/include/openssl -g -c compat.c + exec /usr/vac/bin/xlc -DHAVE_CONFIG_H -I. -I. -I../.. -I/opt/freeware/include/ openssl -g -c compat.c -M "compat.c", line 64.71: 1506-275 (S) Unexpected text ';' encountered. "compat.c", line 64.23: 1506-238 (S) Function argument cannot be type void. make: 1254-004 The error code from the last command is 1. Is this enough or do you need more....? -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

2 3

[Dovecot] dovecot 1.1beta11 auth problems
by Moritz Mertinkat 21 Dec '07

21 Dec '07

Hi everybody, I've problems running Dovecot 1.1beta11 using vpopmail userdb/passdb (Dovecot 1.08 however works just fine). It looks like as if the auth process gets killed somehow... Any ideas what might be wrong? Dec 12 20:02:32 vs247165 dovecot: Dovecot v1.1.beta11 starting up Dec 12 20:02:32 vs247165 dovecot: Generating Diffie-Hellman parameters for the first time. This may take a while.. Dec 12 20:03:06 vs247165 dovecot: imap-login: Waiting for SSL parameter file ssl-parameters.dat Dec 12 20:03:46 vs247165 dovecot: ssl-build-param: SSL parameters regeneration completed Dec 12 20:03:47 vs247165 dovecot: imap-login: Disconnected: rip=a.a.a.a, lip=b.b.b.b, TLS handshaking Dec 12 20:04:03 vs247165 dovecot: child 32051 (auth) killed with signal 11 Dec 12 20:04:03 vs247165 dovecot: imap-login: Internal login failure: user=<postmaster(a)mydomain.de>, method=PLAIN, rip=a.a.a.a, lip=b.b.b.b, TLS Dec 12 20:04:04 vs247165 dovecot: imap-login: Internal login failure: user=<postmaster(a)mydomain.de>, method=PLAIN, rip=a.a.a.a, lip=b.b.b.b, TLS Dec 12 20:04:04 vs247165 dovecot: child 1503 (auth) killed with signal 11 # /usr/local/dovecot-1.1/sbin/dovecot -n protocols: imap login_dir: /usr/local/dovecot-1.1/var/run/dovecot/login login_executable: /usr/local/dovecot-1.1/libexec/dovecot/imap-login mail_location: maildir:/var/lib/vpopmail/domains/%d/%n/Maildir auth default: passdb: driver: vpopmail userdb: driver: vpopmail Regards, Moritz

2 2

[Dovecot] Security hole #4: Specific LDAP + auth cache configuration may mix up user logins
by Timo Sirainen 21 Dec '07

21 Dec '07

Somehow I doubt there are any Dovecot setups left that unknowingly have this problem, but it still counts as a security hole. The possibility to cause this problem exists in Dovecot v1.0.rc11 and later. If you use: 1. passdb ldap with settings: - auth_bind = yes - auth_bind_userdn = no - base containing %variables required for unique user identification, e.g. base = dc=%d,dc=org - pass_filter not containing all %variables required for unique user identification - pass_attrs returning user-specific settings, such as user's home directory 2. userdb prefetch 3. auth_cache_size non-zero (0 is default) If two users with the same password and same pass_filter variables log in within auth_cache_ttl seconds (1h by default), the second user may get logged in with the first user's cached pass_attrs. For example if pass_attrs contained the user's home/mail directory, this would mean that the second user will be accessing the first user's mails. You most likely would have noticed this already by wondering why logins keep failing, unless pass_filter used also some %variables that most of the time uniquely identifies the user. For example %r (remote IP address) or %n (username without domain). You can fix this by upgrading to v1.0.10 (to be released soon), or using this patch: http://hg.dovecot.org/dovecot-1.0/raw-rev/2cedab21cd6d

2 2

[Dovecot] dovecot-auth: returning incorrect maildir for user (user seeing another user's mail)
by Brendan 20 Dec '07

20 Dec '07

timo, here is an bizarre bug for you: i had (foolishly, it turns out) configured dovecot-auth to do ldap authentication binding with a prefect userdb (configs at end of message). everything worked fine, although with huge numbers of pop logins per second we started to see some pileup in the pop3-login processes as they were all waiting for ldap responses on the single ldap connection. the auth caching was never getting hit (some interaction with the prefetch, i assume), but everything worked fine. or so i thought. we had complaints from a user saying they would occasionally pop another user's mail. after much digging, it turned out that if two or more users: - were logged/logging in at the same time - had the same password - got "lucky" then one of the users would occasionally end up with the other users' homedir/maildir. it didn't happen often (maybe once every 500-1000 login attempts), but it did happen. (i ended up writing a script that would pound the pop3 server with logins and look for the wrong number of messages in the inbox. it was not easy to trigger). i'd already realized that having the auth bind do a search and return that to prefetch was a bad idea (since it used a single ldap connection) and had already built a new config that used auth binding and userdb ldap - when we switched over to that config we were unable to replicate the problem again. so, it's not an issue for us right now. i've confirmed that the ldap server never returns the wrong homedir, so it must have been getting mixed up somehow in dovecot-auth. but it did seem like something you might want to dig into a bit, as it might indicate that something could be amiss somewhere in the auth code. that the problem only occured when the users had the same password seemed truly bizarre.. sorry i can't provide more details, it was very difficult to reproduce (and i was reproducing in a production environment and couldn't turn debug up). the auth section from the poorly behaving dovecot.conf: auth default { mechanisms = plain login passdb ldap { args = /opt/dovecot-1.0.3/etc/dovecot-ldap.conf } userdb prefetch { } user = mail } the poorly behaving dovecot-ldap.conf: hosts = ldap ldap_version = 3 auth_bind = yes base = uid=%u,o=imap user_global_uid = 8 user_global_gid = 8 dn = uid=imap@dovecot,o=imap dnpass = ****** pass_filter = (&(proto=%s)(remoteip=%r)(localip=%l)(mech=%m)(pid=%p)) pass_attrs = home=userdb_home,quota=userdb_quota,nologin=nologin,reason=reason,user=user note: the ldap server does some custom processing based on the filter - the filter was the easiest way to get them passed to it. (in case that looks a little wierd :)

2 1

[Dovecot] Wiki license
by Timo Sirainen 20 Dec '07

20 Dec '07

Any suggestions as to what license to use for wiki.dovecot.org? I should have specified this a long time ago, but luckily(?) most of the content is written by me, so I don't think there are going to be problems. The main choices are: a) GNU Free Documentation License b) Creative Commons (Attribution-Share Alike?) It could also be dual-licensed to both to maximize the distribution possibilities.

4 4

[Dovecot] How to change dovecot's bounce message
by Markus Reymann 20 Dec '07

20 Dec '07

Hi, I am using the quota plugin of dovecot. Dovecot is running as LDA for postfix. When the system is running into the quota limit, the bounce message reads as follows: > Your message was automatically rejected by Dovecot Mail Delivery Agent. > The following reason was given: > Quota exceeded Can I somehow change this message, to make it more userfriendly? Postfix has a possibilty to change the bounce_template_file. Best regards, Markus

2 1

[Dovecot] Massive Dovecot auth errors too strange for me
by Rudi K. 20 Dec '07

20 Dec '07

Hello out there, im running Dovecot on "ubuntu Dapper" serving pop3 only in maildir-style, but the dove-auth-process refuses "answers" to the deliver or login-process from time to time, (several times a day), and I have no glue whats going on and why ... Debbugging password-Auth surprised me, as the transmitted password IS correct and allows an successfull authenification lots of hundreds times a day.... but suddenly runs into trouble .. here the logs ... (please take care..., I´m a newbie ;-) Dec 18 10:25:05 server dovecot: pop3-login: Disconnected: Inactivity: method=PLAIN, rip=91.9.201.219, lip=83.154.61.77 Dec 18 10:25:07 server deliver(user.yxz(a)somedom.de): User request from dovecot-auth timed out Dec 18 10:25:07 server postfix/pipe[22156]: 63861180062A7: to=<user.yxz(a)somedom.de>, relay=dovecot, delay=60, status=deferred (temporary failure) Dec 18 10:33:09 server dovecot: auth(default): ssha_verify(info(a)mydom.de): invalid SSHA base64 decode Dec 18 10:33:09 server dovecot: auth(default): cache(info(a)mydom.de,84.166.106.150): Password mismatch Dec 18 10:33:09 server dovecot: auth(default): cache(info(a)mydom.de,84.166.106.150): SSHA(1234) != '1234' Dec 18 10:33:11 server dovecot: auth(default): client out: FAIL^I56^Iuser=info(a)mydom.de Dec 18 10:33:11 server dovecot: auth(default): client out: FAIL^I57^Iuser=info(a)mydom.de root@server:~# dovecot --version 1.0.rc17 root@server:~# dovecot --build-options Build options: ioloop=poll notify=dnotify ipv6 openssl SQL drivers: mysql postgresql sqlite Passdb: checkpassword ldap pam passwd passwd-file shadow sql Userdb: checkpassword ldap passwd prefetch passwd-file sql static root@server:/etc/dovecot# grep -v '^ *$#.*$\?$' dovecot-ldap.conf hosts = localhost dn = cn=admin,dc=jdbit,dc=de dnpass = auth_bind = yes ldap_version = 3 base = ou=mailsystem,dc=jdbit,dc=de scope = subtree user_attrs = uid=user,userPassword=password user_filter = (&(objectClass=ekitsMailAccount)(|(uid=%u)(userAlias=%u))) pass_attrs = uid=user,userPassword=password pass_filter = (&(objectClass=ekitsMailAccount)(|(uid=%u)(userAlias=%u))) default_pass_scheme = SSHA user_global_uid = vmail user_global_gid = vmail root@server:~# dovecot -n # /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S protocols: pop3 listen: mail.mydom.de disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/pop3-login login_greeting: mail.mydom.de POP3-Server ready login_process_size: 64 login_processes_count: 64 first_valid_uid: 5000 last_valid_uid: 5000 first_valid_gid: 5000 last_valid_gid: 5000 mail_extra_groups: mail mail_location: maildir:/var/spool/dovecot/mail/%Ld/%Ln mail_executable: /usr/lib/dovecot/pop3 mail_process_size: 384 mail_plugin_dir: /usr/lib/dovecot/modules/pop3 pop3_uidl_format: %08Xu%08Xv pop3_client_workarounds: outlook-no-nuls oe-ns-eoh auth default: cache_ttl: 0 user: nobody worker_max_count: 60 passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf userdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf socket: type: listen client: master: path: /var/run/dovecot/dovecot-auth-master mode: 384 user: vmail

2 1

[Dovecot] Question with versions and problem with IMAP
by Drew Weaver 20 Dec '07

20 Dec '07

General question I have is this. Recently my personal server which I receive e-mail for a domain which is just for playing with rebooted on its own and I had both an RPM version and a source version of dovecot installed on the same machine. The RPM version started first even though I had been running under the source built version up until this point (I originally found that for some reason the version centos built was missing something, maybe plugins, I don't remember now) Anyhow, the question I have is why did it insist that all of my mail was new mail? I quickly realized what the problem is, and I noticed that once I switched it back and forth between the old and new versions it properly updated the 'read vs unread' mail in IMAP, and even though dovecot was using the same configuration file with both binaries (/etc/dovecot.conf) it made such a huge difference. The reason I am asking is because I want to update my source version from 1.0.rc2 to 1.0.9 but I would really like to retain my read vs. unread mail. The RPM version in question is: 0.99.11 The problem I am facing is, today a large mailbox approx. 570M suddenly stopped working via IMAP in outlook express. (again on version 1.0.rc2) no changes have been made to the configuration for over a year. There are no errors in maillog here is the output however: Dec 18 09:49:53 mail dovecot: imap-login: Login: user=<user>, method=PLAIN, rip=client, lip=server Dec 18 09:49:53 mail dovecot: IMAP(user): Effective uid=552, gid=100 Dec 18 09:49:53 mail dovecot: IMAP(user): Loading modules from directory: /usr/local/lib/dovecot/imap Dec 18 09:49:53 mail dovecot: IMAP(user): Module loaded: /usr/local/lib/dovecot/imap/lib01_quota_plugin.so Dec 18 09:49:53 mail dovecot: IMAP(user): Module loaded: /usr/local/lib/dovecot/imap/lib02_imap_quota_plugin.so Dec 18 09:49:53 mail dovecot: IMAP(user): maildir: data=/home/user/Maildir:INDEX=/mailaux/user:CONTROL=/mailaux/user Dec 18 09:49:53 mail dovecot: IMAP(user): maildir: root=/home/user/Maildir, index=/mailaux/user, control=/mailaux/user, inbox= Dec 18 09:49:53 mail dovecot: IMAP(user): fs quota add storage dir = /home/user/Maildir Dec 18 09:49:53 mail dovecot: IMAP(user): fs quota block device = /dev/sda1 Dec 18 09:49:53 mail dovecot: IMAP(user): fs quota mount point = /home Dec 18 09:49:55 mail dovecot: IMAP(user): Disconnected: Logged out Outlook express gives its usually helpful error message: Header download for the 'Inbox' folder did not complete. Account: 'server', Server: 'server', Protocol: IMAP, Server Response: '', Port: 143, Secure(SSL): No, Error Number: 0x800C0148 Any advice on either of these issues would just be great. Happy holidays to those who are celebrating this time of year! -Drew

2 1

[Dovecot] Upgrading from 1.0.rc2-1ubuntu2.2 on edgy
by Daragh Mc Grath 20 Dec '07

20 Dec '07

Hi Guys, Can anyone shed some light as to how I upgrade away from 1.0.rc2-1ubuntu2.2 on edgy? The usual aptitude upgrades aren't doing anything for me, and, downloading the package from another Ubuntu release, and trying a dpkg -i is causing lots of dependency errors. Daragh

2 1

Re: [Dovecot] Dovecot + SASL + allow_nets
by Andrew Garner 20 Dec '07

20 Dec '07

> Timo Sirainen schreef: > > On Mon, 2007-12-03 at 14:36 +0100, Marc Cuypers wrote: > >> When using dovecot for authentication of an SASL (postfix) request, i > >> cannot use the allow_nets parameter. The IP-address of the requester is > >> not known in dovecot. > >> > >> I would like to allow sasl for certain users, others are not allowed to > >> access via SASL. > >> Some users can have access to imap and pop3 from certain IP-addresses. > >> > >> How could i combine this in then dovecot configuration? > > > > Since Postfix doesn't send the IP to Dovecot, there isn't anything on > > Dovecot's side you can do. You could try asking about this in Postfix > > list.. Someone at least had a patch which allowed sending local IP to > > Dovecot (http://marc.info/?t=119306971600010&r=1&w=2) Maybe it sends > > remote IP as well. I wrote that patch. It passes both endpoints (remote & local) through to dovecot . This lets you restrict smtp-auth just like pop3 or imap using the remote IP. In my case, I had played around with a quick hack for doing per-ip realming (using the local IP) w/ dovecot-sql.

3 4

[Dovecot] child (login) killed with signal 9
by Matt LaPlante 19 Dec '07

19 Dec '07

Hi, I'm running dovecot on an Ubuntu server (1:1.0.5-1ubuntu2). Dovecot provides pop3, imap, and sasl to postfix. The setup works quite nicely, however I do have one error that shows up repeatedly in my dovecot.log. <snip> dovecot: 2007-12-12 09:29:06 Error: child 32765 (login) killed with signal 9 dovecot: 2007-12-12 09:29:06 Error: child 18039 (login) killed with signal 9 dovecot: 2007-12-12 10:05:07 Error: child 26088 (login) killed with signal 9 dovecot: 2007-12-12 10:05:07 Error: child 5271 (login) killed with signal 9 dovecot: 2007-12-12 10:05:07 Error: child 5273 (login) killed with signal 9 <snip> I'm not aware that this is actually causing problems, but since it shows up several hundred times a day on a couple-user setup, I'm rather curious about what's causing it. Thanks, Matt

3 6

[Dovecot] maildirsize quota counting locking account?
by Daniel Watts 19 Dec '07

19 Dec '07

Hi, I've just straced a dovecot imap process and found one thread sitting there doing hundreds and hundreds of maildirsize updates as follows: > > open("/home/virtual/mydomain.com/home/admin/Maildir/maildirsize", O_RDWR|O_APPEND) = 7 > read(7, "10485760000S\n1562717408 107547\n-"..., 5120) = 2446 > read(7, "", 2674) = 0 > write(1, "* 1810 FETCH (UID 1815 RFC822.SI"..., 2031) = 2031 > setsockopt(1, SOL_TCP, TCP_CORK, [0], 4) = 0 > epoll_wait(4, {{EPOLLIN, {u32=101056896, u64=2370923004288}}}, 5, 2584) = 1 > read(0, "2838 UID fetch 1816 (UID RFC822."..., 2974) = 51 > setsockopt(1, SOL_TCP, TCP_CORK, [1], 4) = 0 > close(7) = 0 > open("/home/virtual/mydomain.com/home/admin/Maildir/maildirsize", O_RDWR|O_APPEND) = 7 > read(7, "10485760000S\n1562717408 107547\n-"..., 5120) = 2446 > read(7, "", 2674) = 0 > open("/home/virtual/mydomain.com/home/admin/Maildir/.Folders.ALERTS.Payments/cur/1195331425.M52296P11937V0000000000000807I000000001015A5EB_0.tg3,S=2079:2,Sa", O_RDONLY) = 10 > fstat(10, {st_mode=S_IFREG|0600, st_size=2079, ...}) = 0 > pread(10, "Return-Path: <apache(a)tg7.alumina"..., 4096, 0) = 2079 > pread(10, "", 2017, 2079) = 0 > pread(10, "Return-Path: <apache(a)tg7.alumina"..., 4096, 0) = 2079 > write(1, "* 1811 FETCH (UID 1816 RFC822.SI"..., 2180) = 2180 > close(10) = 0 > stat("/home/virtual/mydomain.com/home/admin/Maildir/.Folders.ALERTS.Payments/new", {st_mode=S_IFDIR|0700, st_size=6, ...}) = 0 > stat("/home/virtual/mydomain.com/home/admin/Maildir/.Folders.ALERTS.Payments/cur", {st_mode=S_IFDIR|0700, st_size=618496, ...}) = 0 > close(7) = 0 > open("/home/virtual/mydomain.com/home/admin/Maildir/maildirsize", O_RDWR|O_APPEND) = 7 > read(7, "10485760000S\n1562717408 107547\n-"..., 5120) = 2446 > read(7, "", 2674) = 0 > write(1, "2838 OK Fetch completed.\r\n", 26) = 26 > setsockopt(1, SOL_TCP, TCP_CORK, [0], 4) = 0 > epoll_wait(4, {}, 5, 800) = 0 > epoll_wait(4, {{EPOLLIN, {u32=101056896, u64=2370923004288}}}, 5, 5000) = 1 > read(0, "2839 UID fetch 1817 (UID RFC822."..., 2923) = 51 > setsockopt(1, SOL_TCP, TCP_CORK, [1], 4) = 0 > close(7) = 0 > open("/home/virtual/mydomain.com/home/admin/Maildir/maildirsize", O_RDWR|O_APPEND) = 7 During this time (at least 5-10 minutes) , I could not check the account via my email client Thunderbird. Clicking on an email would just sit there as if it is loading but nothing would happen - the read pane just remains blank. Is Dovecot going through every email (of many 10,000's) and counting up the sizes? Could this be made more efficient so it doesn't lock the account? This could I guess be a Thunderbird issue - it is a disappointingly imperfect client. Dan

4 5

[Dovecot] Start using Dovecot
by Isaak 19 Dec '07

19 Dec '07

Hey,I have recently set up Dovecot on my server but I have trouble with using it. I'm using Dovecot 1.0.rc15, SQL password and user database with the SQL config files provided on the home page. I'm using Thunderbird to connect to Dovecot. When trying to connect it gives me an internal server error: User not found Is there anything else I need to do before I can use Dovecot? Here's my configuration, any help would be appreciated. # /etc/dovecot.conf log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot.info.log protocols: imap pop3 imaps pop3s listen(default): *:143 listen(imap): *:143 listen(pop3): *:110 ssl_cert_file: /var/www/ssl/just-click.pem ssl_key_file: /var/www/ssl/just-click.pem login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login max_mail_processes: 100 first_valid_uid: 1000 last_valid_uid: 1500 mail_extra_groups: mail mail_location: mbox:~/mail/:INBOX=/var/mail/%u mail_debug: yes mbox_read_locks: dotlock fcntl mbox_write_locks: dotlock fcntl mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /etc/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot-sql.conf socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 432 user: dovecot group: mail _________________________________________________________________ Neem je vrienden overal mee dankzij Messenger op je gsm. http://messenger.live.com

3 2

[Dovecot] sieve & vacation question
by Ralf Hildebrandt 19 Dec '07

19 Dec '07

We have a setup where a Postfix gateway does virtual_alias rewriting of the envelope sender: ralf.hildebrandt(a)charite.de get rewritten to hildeb(a)postamt.charite.de The mail is then sent on to postamt.charite.de, the Mailbox server. There we use deliver & doecot. The sieve vacation recipient says it won't answer if: "The envelope recipient is not found in the message To:, Cc: or Bcc: fields." But this is never the case, since the envelope is being rewritten. How can I solve this conundrum? -- Ralf Hildebrandt (Ralf.Hildebrandt(a)charite.de) plonk(a)charite.de Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de The ashtray in my office proudly displays "Designed for Windows98/NT"

2 1

[Dovecot] Bug track list
by Antonis Faragitakis 17 Dec '07

17 Dec '07

Hello everyone, I'm looking for a bugs track list for postfix. Is there one ?

2 2

[Dovecot] Help please: Migrating Courier imap - Dovecot (Postfix virtual mailbox domains)
by Mark Piekos 17 Dec '07

17 Dec '07

I'm trying to migrate from qmail to postfix. The original server is combo of qmail and Courier imap (no pop mailboxes) I have a working Postfix config and had imap working with Courier imap on the new server. I thought I would experiment with Dovecot as it has some good press. I have moved the contents of my original maildir's to the new server and ste permissions and group membership appropriatley. I can read the 'Inbox' via Dovecot but non of the subfolders that I had configured. I have tried the 'manual' migration method as described in the faq without success (I can see the subfolders but no contents)and have tried running courier-dovecot-migrate.pl witt he same result. I'd be grateful for any advice. Kind regards, Mark. Dovecote version: 1.0.rc15 /etc/dovecot.conf log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot-info.log ssl_disable: yes login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login mail_location: maildir:/home/vmail/%d/%n maildir_copy_with_hardlinks: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 namespace: type: private prefix: INBOX. inbox: yes auth default: verbose: yes passdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: static args: uid=vmail gid=vmail home=/home/vmail/%u

4 9

[Dovecot] v1.1.beta11 deliver crashes when quota exceeded
by arvids 15 Dec '07

15 Dec '07

Hello, v1.1.beta11 deliver crashes when quota exceeded. This also reveals another problem in v1.1.beta11 - imap process does not follow quota settings - this user copied(with imap client) to his imap folder large volume of emails and these emails significantly exceeded quota settings for this user, but imap process did not complain about it. Here is full backtrace of deliver crash: (gdb) bt full #0 0xb7e5dc87 in raise () from /lib/libc.so.6 No symbol table info available. #1 0xb7e5f4f8 in abort () from /lib/libc.so.6 No symbol table info available. #2 0x080ba998 in i_syslog_fatal_handler (type=LOG_TYPE_PANIC, status=0, fmt=0x80ce1c8 "file %s: line %d (%s): assertion failed: (%s)", args=0xbf9e0674 "4W\r\b6") at failures.c:303 backtrace = 0x80e7d20 "/usr/local/dovecot/libexec/dovecot/deliver(i_syslog_fatal_handler+0x2c) [0x80ba98c] -> /usr/local/dovecot/libexec/dovecot/deliver [0x80ba78b] -> /usr/local/dovecot/libexec/dovecot/deliver [0x808c914] "... #3 0x080ba78b in i_panic (format=0x80ce1c8 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:196 args = 0xbf9e0674 "4W\r\b6" #4 0x0808c914 in index_transaction_finish_rollback (t=0x810e210) at index-transaction.c:54 __PRETTY_FUNCTION__ = "index_transaction_finish_rollback" #5 0x0808c758 in index_transaction_rollback (_t=0x810e210) at index-transaction.c:114 itrans = (struct mail_index_transaction *) 0x0 #6 0xb7e2fcf4 in quota_mailbox_transaction_rollback (ctx=0x810e210) at quota-storage.c:113 qt = (struct quota_transaction_context *) 0x810e8c0 #7 0x0805990b in deliver_save (namespaces=0x80f2280, storage_r=0xbf9e0828, mailbox=0x80d8a58 "INBOX", mail=0x80f9c38, flags=0, keywords=0x0) at deliver.c:216 box = (struct mailbox *) 0x80fe048 t = (struct mailbox_transaction_context *) 0x0 kw = (struct mail_keywords *) 0x0 error = 134759821 mailbox_name = 0x80e7af0 "INBOX" ret = <value optimized out> #8 0x0805ac0d in main (argc=Cannot access memory at address 0x58ac ) at deliver.c:954 error_string = <value optimized out> error = <value optimized out> ret = <value optimized out> config_path = 0x80cdb08 "/usr/local/dovecot/etc/dovecot.conf" envelope_sender = 0x80e7030 "arvids(a)mpe.lv" mailbox = 0x80d8a58 "INBOX" auth_socket = <value optimized out> home = <value optimized out> destaddr = 0xbf9e1869 "tests1" user = 0xbf9e1869 "tests1" error = <value optimized out> extra_fields = {arr = {buffer = 0x80e7070, element_size = 4}, v = 0x80e7070, v_modifiable = 0x80e7070} ns = (struct mail_namespace *) 0x80f2280 raw_ns = (struct mail_namespace *) 0x80f22a8 storage = (struct mail_storage *) 0x80f2688 box = (struct mailbox *) 0x80f4a98 input = (struct istream *) 0x80f49b8 t = (struct mailbox_transaction_context *) 0x80f8fc8 headers_ctx = (struct mailbox_header_lookup_ctx *) 0x80f88b8 mail = (struct mail *) 0x80f9c38 process_euid = 95 namespace_pool = <value optimized out> stderr_rejection = false keep_environment = false user_auth = true i = 63 ret = <value optimized out> (gdb) Regards, Arvids

1 0

[Dovecot] Just verifying upgrade procedure?
by Bjørn T Johansen 14 Dec '07

14 Dec '07

When upgrading from source, it's ok to just run make install and every files will be overwritten with the new version? Nothing else one should do? Regards, BTJ -- ----------------------------------------------------------------------------------------------- Bjørn T Johansen btj(a)havleik.no ----------------------------------------------------------------------------------------------- Someone wrote: "I understand that if you play a Windows CD backwards you hear strange Satanic messages" To which someone replied: "It's even worse than that; play it forwards and it installs Windows" -----------------------------------------------------------------------------------------------

3 3

[Dovecot] Xen + NFS
by Eric 14 Dec '07

14 Dec '07

Thanks for Dovecot! I am currently testing several scenarios to help determine how to best implement dovecot for our environment. One scenario of particular interest is Maildir + NFS, load balanced between several servers running dovecot. I am not sure anyone would ever want to implement what I am about to describe here, but none-the-less, I thought I would mention it to the list to see if anyone has had the same experience, or could possibly help. What I am using to _test_ is a single server running RedHat Server 5 + Xen. Dom0 is acting as my NFS server, and a RedHat Server 5 guest running on the same machine is acting as my NFS client and dovecot server. I have a single directory exported from the NFS server which contains several home folders with inboxes stored in Maildir format. The problem I am having is when I open a POP3 connection from a separate machine, I see the following messages on the virtual server in /var/log/maillog and I am unable to retrieve mail: file maildir-uidlist.c: line 139 (maildir_uidlist_unlock): assertion failed: (uidlist->lock_count > 0) and more often: Mailbox init failed top=0/0, retr=0/0, del=0/0, size=0 It appears to be an issue with the login not having the proper permissions to create the dovecot.uidlist file, however, when I log in locally to the dovecot server with the POP3 account, I can read+write in the directory without problems. I suspect that I am missing something simple, but cannot seem to figure it out. dovecot-1.0-1.2.rc15.el5 RedHat Server 5 kernel: 2.6.18-8.1.14.el5xen dovecot -n: shutdown_clients: no login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_greeting: Server ready. mail_location: maildir:~/.maildir:INDEX=/var/spool/dovecot/%u maildir_copy_with_hardlinks: yes mbox_write_locks: dotlock fcntl mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 pop3_reuse_xuidl(default): no pop3_reuse_xuidl(imap): no pop3_reuse_xuidl(pop3): yes pop3_lock_session(default): no pop3_lock_session(imap): no pop3_lock_session(pop3): yes auth default: passdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: ldap args: /etc/dovecot-ldap.conf nfs mount options: rw,rsize=32768,wsize=32768,hard,fg,lock,nfsvers=3,tcp,retrans=0,noac --------------------------------- Looking for last minute shopping deals? Find them fast with Yahoo! Search.

2 1

[Dovecot] 1.08 + quota-rewrite has no trash plugin
by adam_jh＠hotmail.com 14 Dec '07

14 Dec '07

I think I'm just going to move to 1.1 - however, I'm not keen on installing all the dev tools necessary on a production box. Does anyone have any pointers to web pages or keywords I can check to see what kind of safeguards are needed. The problem I have is building the the srpm to include the quota-rewrite with the trash plugin. I think it has been removed and I wanted to check if anyone knows any good reason not just simply re-enable it (though without the skills I'm not sure I'd do it). -SUBDIRS = acl convert quota imap-quota lazy-expunge mail-log trash $(ZLIB) +SUBDIRS = acl convert quota imap-quota lazy-expunge mail-log $(ZLIB) [root@test ~]# /etc/rc.d/init.d/dovecot start Starting Dovecot Imap: Warning: Corrected permissions for login directory /var/run/dovecot-login FPlugin trash not found from directory /usr/lib/dovecot/imap Error: imap dump-capability process returned 89 Fatal: Invalid configuration in /etc/dovecot.conf [FAILED] A year ago the same question was asked, but I'm not sure of any changes since then. >>> >From tss at iki.fi Sun Oct 15 22:44:38 2006 From: tss at iki.fi (Timo Sirainen) Date: Mon, 16 Oct 2006 00:44:38 +0300 Subject: [Dovecot] Apple Mail quota display In-Reply-To: <C49A984C-F2BF-4A40-84A4-7ED1F7264866(a)mac.com> References: <E94C8EAF-E17E-4E68-B43F-E990A632C4F9(a)mac.com> <1160339709.5137.125.camel@hurina> <C49A984C-F2BF-4A40-84A4-7ED1F7264866(a)mac.com> Message-ID: <1160948678.5448.85.camel@hurina> On Sat, 2006-10-14 at 01:13 -0700, Timothy Martin wrote: > I'm no wiz at applying diffs and compiling my own (i'm a BSD ports > kinda guy) but when i tried that diff i couldn't compile because > there looked to be a couple of lines that should have been removed > and the Trash plugin doesn't appear to be updated to work with the > quota rewrite. Yea, trash plugin won't compile. Just ignore that. Unless you need it.. <<< Thanks Adam

1 0

[Dovecot] dovecot.index only gets updated in Root maildir Folder
by Florian Franzeck 13 Dec '07

13 Dec '07

Debian uses dnotify by default.

3 5

Re: [Dovecot] antispam integration (dovecot antispam plugin): chroot & no way to pass `--user=' to dspam?
by Johannes Berg 13 Dec '07

13 Dec '07

> I want have dspam statistics to be per-user, not global. And I like > idea to learn filter by moving messages from/to SPAM folder, it seems to > be natural and much better, than Web UI (I don't want to use dspam Web > UI at all). > > Is here any way to resolve two problems: > > (1) Run dspam in chrooted environment > (2) pass `--user=${USER}' parameter to dspam. No idea. Passing --user is easy, there's an example in the readme file for the antispam plugin. The former I have no idea about, I guess all it needs is access to the mysql db. > Oh, and even more: I think, that it will be useful to have `socket' > backend for spam-plugin, which allows to send messages to two different > configured sockets (TCP or UNIX domain) -- one for `learn as spam' and > other for `learn as ham'. It allows to run in chrooted environment > easily, and solve problem with exec-dspam-on-every-message. Dunno. Why are you running it chrooted anyway? If you write such a backend I can add it to my tree :) johannes

1 0

[Dovecot] SYN flooding / pipe() failed: Too many open files
by Frank Elsner 13 Dec '07

13 Dec '07

Hello *, I've the following problem with dovecot 1.0.7: /var/log/messages shows | Dec 13 13:48:27 mailbox kernel: possible SYN flooding on port 143. Sending cookies. and /var/log/maillog shows (Please note: nearly the same time): | Dec 13 13:48:28 mailbox dovecot: pipe() failed: Too many open files This leads to an unresponsive mail service and requires a dovecot restart. What can be done to prevent this? BTW, this is my dovecot -n: # 1.0.7: /usr/local/dovecot/etc/dovecot.conf base_dir: /var/run/dovecot/ protocols: imap imaps pop3 pop3s ssl_cert_file: /usr/local/dovecot/etc/mailbox.pem ssl_key_file: /usr/local/dovecot/etc/mailbox.key disable_plaintext_auth: no login_dir: /var/run/dovecot//login login_executable(default): /usr/local/dovecot/libexec/dovecot/imap-login login_executable(imap): /usr/local/dovecot/libexec/dovecot/imap-login login_executable(pop3): /usr/local/dovecot/libexec/dovecot/pop3-login login_greeting: TU-Berlin.DE POP3-/IMAP Service ready login_log_format_elements: %u %r %c login_processes_count: 24 login_max_processes_count: 512 verbose_proctitle: yes mail_location: maildir:/var/Mail/Boxes/%1u/%u mailbox_idle_check_interval: 15 maildir_copy_with_hardlinks: yes maildir_copy_preserve_filename: yes mail_executable(default): /usr/local/dovecot/libexec/dovecot/imap mail_executable(imap): /usr/local/dovecot/libexec/dovecot/imap mail_executable(pop3): /usr/local/dovecot/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/dovecot/lib/dovecot/pop3 mail_log_prefix: %Ls(%u): 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 anonymous count: 32 passdb: driver: ldap args: /usr/local/dovecot/etc/dovecot-ldap.conf userdb: driver: static args: uid=777 gid=12 plugin: quota: maildir:ignore=Trash Kind regards ______________________________________________________________ Frank Elsner / c/o Technische Universitaet Berlin | ____________/ tubIT [BD], Sekr. E-N 50 | | Einsteinufer 17 | | Phone: +49 30 314 23897 D-10587 Berlin | | eMail: Frank.Elsner(a)TU-Berlin.DE Germany __________________| |_________________________________________________________| in dubio pro exim

3 2

[Dovecot] How to copy Spammail for learning out of Postfix and Dovecot (vmail)
by Sven Schmidt 13 Dec '07

13 Dec '07

Hi! I am using Postfix 2.3.8 and Dovecot 1.0.rc15. Virtual Domains and Mailboxes are configured. I tried to copy spammy Mail with Procmail, but Procmail only sees local mails. How to configure it to get a copy of spammy mails in a mbox or mail-dir?

3 4

[Dovecot] Dovecot Antispam Problem (Using mail sending backend)
by Justin Refice 13 Dec '07

13 Dec '07

I'm trying to setup DSPAM training using the mail-sending backend of the Antispam filter, unfortunately, things don't appear to be working. I've compiled it against the debian etch dovecot libraries, and the plugin itself builds, and doesn't report any errors when running. As a matter of fact, it doesn't report ANYTHING when running, except for the initialization code (DEBUG=syslog): imap: antispam: plugin initialising imap: antispam: "trash" is trash folder imap: antispam: "Trash" is trash folder imap: antispam: "Deleted Items" is trash folder imap: antispam: "spam" is spam folder imap: antispam: "Spam" is spam folder imap: antispam: "SPAM" is spam folder imap: antispam: "junk" is spam folder imap: antispam: "Junk" is spam folder imap: antispam: "Junk Mail" is spam folder imap: antispam: no unsure folders imap: antispam: mail backend spam address dspam-add(a)xxx.yyy imap: antispam: mail backend not-spam address dspam-fp(a)xxx.yyy imap: antispam: mail backend sendmail /usr/sbin/sendmail imap: antispam: mail backend tmpdir /tmp .... And that's it. I never hear from the plugin again, regardless of how many times I create/delete the SPAM folder, or how many times I move/copy into/out of the folder. The plugin is basically silent. I don't see the mails being sent/recieved, so I'm assuming that's it isn't doing anything at all. I can manually use the training addresses, so I know they're working. Any help would be appreciated. -Justin R.

5 9

[Dovecot] got too little data ??
by Benoit Branciard 12 Dec '07

12 Dec '07

I just switched in a hurry one of our mailbox servers from UW-imapd to Dovecot in an attempt to address performance and stability problems. This server hosts ~5500 accounts, ~2000 are daily used, ~600 simultaneous IMAP connexions in rush hours, and lots of POP ones. Some accounts may be accessed simultaneously with IMAP and POP. The system is : - Debian Sarge (x86 with amd64 kernel) - MBOX files mailboxes - indexes migrated out of filesystem quotas - Sendmail MTA - Procmail local delivery agent (not easily replaceable due to extensive use of procmailrc filters) - Both Procmail and Dovecot use [dotlock, fcntl] as mailbox locking scheme - No other processes have access to mailboxes in normal use - Dovecot 1.0.8 hand-compiled from tarball The good new is that it seems to perform better than UW-imapd. The bad new is that we get lots or errors like this in log: IMAP(username): FETCH for mailbox INBOX UID 23862 got too little data: 3186 vs 3206 Such "accidents" happen about 4-5 times a day, and does not correct themselves, even with a mailbox expunge or reopen. However manual deletion of the faulty mailbox index seems to clear the problem, until another one occurs. On such errors some mail clients (Thunderbird) retry operation in infinite loop, so log gets really cluttered. In imap-fetch-body.c it is stated : "We shouldn't really ever get here. One reason is if mail was deleted from NFS server while we were reading it. Another is some temporary disk error." Both reasons do not seem to apply in our case: mail partition is not NFS-mounted, and disks (a RAID5 array) seem healthy. Furthermore, affected accounts are not over quota. So may we have found a bug ? Or may we have a locking problem ? Or an index handling one ? I tried to disable mbox_lazy_writes without success. I will try to disable disk indexes totally, which should help since problems seem index-related; but performance may suffer. Any clues appreciated... Dovecot -n says : # 1.0.8: /usr/local/etc/dovecot.conf protocols: imap imaps pop3 pop3s listen: [::] ssl_cert_file: /usr/local/etc/ssl/private/our-certificate.pem ssl_key_file: /usr/local/etc/ssl/private/our-certificate.pem 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 first_valid_uid: 200 first_valid_gid: 200 mail_location: mbox:~/mail:INBOX=~/mail/INBOX:INDEX=/espace/dovecot/indexes/%u fsync_disable: yes mbox_lazy_writes: no 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_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota 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): outlook-idle tb-extra-mailbox-sep delay-newmail imap_client_workarounds(imap): outlook-idle tb-extra-mailbox-sep delay-newmail imap_client_workarounds(pop3): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xv%08Xu pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: passdb: driver: pam args: * userdb: driver: passwd plugin: quota: fs -- Ce message a ete verifie par MailScanner pour des virus ou des polluriels et rien de suspect n'a ete trouve.

4 6

[Dovecot] Dovecot 1.08 seems very slow
by Marc Perkel 12 Dec '07

12 Dec '07

I know I'm late reporting this but 1.08 seems really slow. It seems like it is as slow as some of the early RCs were. Wish I had more info. Using Maildir format.

2 1

[Dovecot] 1.0.8 with quota 1.0.8 patch - undefined symbol: quota_set
by adam_jh＠hotmail.com 12 Dec '07

12 Dec '07

I get the following error after patching the 1.0.8 src.rpm with the quota-rewrite-1.0.8.diff [root@test dovecot]# /etc/rc.d/init.d/dovecot start Starting Dovecot Imap: Edlopen(/usr/lib/dovecot/imap/lib02_imap_quota_plugin.so) failed: /usr/lib/dovecot/imap/lib02_imap_quota_plugin.so: undefined symbol: quota_set FCouldn't load required plugins Error: imap dump-capability process returned 89 Fatal: Invalid configuration in /etc/dovecot.conf [FAILED] I have checked the new quota config changes. The src rpm is taken from http://atrpms.net/dist/el4/dovecot/. Using the same process without the patch, the rpm that's built and installed works (or at least starts). A process of elimination revealed it doesn't understand the imap_quota aspect of the quota imap_quota configuration line. Removing that it works, but I kind of need it! Can anyone help? Thanks, adam To patch it I did: Patch103: dovecot-1.0.beta2-mkcert-permissions.patch Patch105: dovecot-1.0.rc7-mkcert-paths.patch # quota patch Patch106: quota-rewrite-1.0.8.diff and %patch103 -p1 -b .mkcert-permissions %patch105 -p1 -b .mkcert-paths %patch106 -p1 -b .quota Since I'm using centos to match RHEL 4 [rpmbuild@test SPECS]$ cat /etc/redhat-release Red Hat Enterprise Linux WS release 4 (Nahant) I also added to my .rpmmacros for the rpmbuild user I have %bcond_with() %{expand:%%{?_with_%{1}:%%global with_%{1} 1}} %bcond_without() %{expand:%%{!?_without_%{1}:%%global without_%{1} 1}} %with() %{expand:%%{?with_%{1}:1}%%{!?with_%{1}:0}} %without() %{expand:%%{?without_%{1}:0}%%{!?without_%{1}:1}} then rpm -e dovecot su rpmbuild ... rpmbuild -ba postfix.spec rpm -Uvh ...dovecot.rpm [root@test dovecot]# /usr/sbin/postfix -n # 1.0.8: /etc/dovecot.conf login_dir: /var/run/dovecot-login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_processes_count: 1 first_valid_uid: 505 last_valid_uid: 505 mail_extra_groups: mail mail_location: maildir:/var/vmail/%d/%n maildir_copy_with_hardlinks: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 imap_client_workarounds(default): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail imap_client_workarounds(pop3): outlook-idle pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: user: nobody passdb: driver: sql args: /etc/dovecot-mysql.conf userdb: driver: sql args: /etc/dovecot-mysql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: mail master: path: /var/run/dovecot/auth-master mode: 432 user: vmail group: mail plugin: quota: maildir

2 3

[Dovecot] Fishing attempt locking up dovecot
by Jerry Yeager 12 Dec '07

12 Dec '07

On Dec 11, 2007, at 5:58 PM, dovecot-request(a)dovecot.org wrote: > > > Message: 10 > Date: Tue, 11 Dec 2007 15:58:16 -0700 > From: Patrick Milvich <patrick(a)milvich.com> > Subject: [Dovecot] Fishing attempt locking up dovecot > To: dovecot(a)dovecot.org > Message-ID: <8C5CE5FE-BD2F-40C4-8A36-A4CD8BD533DB(a)milvich.com> > Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes > > 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. > > stuff cut out > > End of dovecot Digest, Vol 56, Issue 33 > *************************************** Will the following be of any help to you? (it is a patch for Postfix 2.4.nn) It would seem that the type of fishing expedition you mention would fall into the bit described below (lots of errors). While it will not directly solve the "out of resources" Dovecot problem, it may limit the up-front damage, followed with a CRON script running every twenty minutes or so that scans the last line of the mail log for the 'too many files open' error and upon finding it runs a version of the killall imap-login processes. ftp://postfix.mirrors.pair.com/index.html Postfix 2.4 patch (PGP signature ) to add stress-adaptive behavior to the SMTP server. When some mail flood keeps all server ports busy, this feature can be used to quickly drop connections from clients that make errors, and to reduce the time that Postfix waits for a client command. This may delay some legitimate deliveries, but it will allow you to still keep some mail flowing. After the mail flood ends, Postfix reverts to its normal behavior.

1 0

[Dovecot] dovecot deliver errors
by Andrew Garner 12 Dec '07

12 Dec '07

I think someone else mentioned this problem earlier on the list, and I've recently started seeing the following error show up: file index-transaction.c: line 54 (index_transaction_finish_rollback): assertion failed: (t->mail_ref_count == 0) Raw backtrace: /usr/lib/dovecot/deliver(i_syslog_fatal_handler+0x2b) [0x80bff0b] -> /usr/lib/dovecot/deliver [0x80bfd1a] -> /usr/lib/dovecot/deliver [0x808f783] -> /usr/lib/dovecot/deliver(index_transaction_rollback+0x1a) [0x808f5aa] -> /usr/lib/dovecot/modules/lda//lib10_quota_plugin.so [0xb7e6d013] -> /usr/lib/dovecot/deliver(deliver_save+0x202) [0x8059812] -> /usr/lib/dovecot/modules/lda//lib90_cmusieve_plugin.so [0xb7e4bb1d] -> /usr/lib/dovecot/modules/lda//lib90_cmusieve_plugin.so [0xb7e5bdbc] -> /usr/lib/dovecot/modules/lda//lib90_cmusieve_plugin.so(sieve_execute_bytecode+0x1c4) [0xb7e5c7d4] -> /usr/lib/dovecot/modules/lda//lib90_cmusieve_plugin.so(cmu_sieve_run+0x30c) [0xb7e4c7bc] -> /usr/lib/dovecot/modules/lda//lib90_cmusieve_plugin.so [0xb7e4a81f] -> /usr/lib/dovecot/deliver(main+0x10c0) [0x805a990] -> /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xc8) [0xb7e86ea8] -> /usr/lib/dovecot/deliver [0x80588e1] With beta11 I started running into this problem (using postfix's smtp-source messages): postfix/pipe[19560]: 85372294: to=<example(a)example.com>, relay=dovecot, delay=20385, delays=20384/0.01/0/0.19, dsn=5.3.0, status=bounced (Command died with signal 11: "/usr/ lib/dovecot/deliver") Program received signal SIGSEGV, Segmentation fault. 0x080d017a in str_sanitize_append (dest=0x80ee2f8, src=0x0, max_len=80) at str-sanitize.c:11 11 str-sanitize.c: No such file or directory. in str-sanitize.c (gdb) #0 0x080d017a in str_sanitize_append (dest=0x80ee2f8, src=0x0, max_len=80) at str-sanitize.c:11 p = <value optimized out> #1 0x080d02ce in str_sanitize (src=0x0, max_len=80) at str-sanitize.c:35 str = (string_t *) 0x80ee2f8 #2 0x080594f4 in deliver_log (mail=0x8107a48, fmt=0x80d349b "saved mail to %s") at deliver.c:120 args = 0xbfb087d8 "\200<DA>\016\b" str = (string_t *) 0x80ee120 #3 0x0805979f in deliver_save (namespaces=0x80f7a90, storage_r=0xbfb088e8, mailbox=0x80ded98 "INBOX", mail=0x8107a48, flags=0, keywords=0x0) at deliver.c:222 box = (struct mailbox *) 0x810be58 t = (struct mailbox_transaction_context *) 0x0 kw = (struct mail_keywords *) 0x0 error = MAIL_ERROR_NONE mailbox_name = 0x80eda80 "INBOX" ret = 0 #4 0x0805ac15 in main (argc=5, argv=Cannot access memory at address 0x4 ) at deliver.c:954 error_string = <value optimized out> error = <value optimized out> ret = <value optimized out> config_path = 0x80d34ba "/etc/dovecot/dovecot.conf" envelope_sender = 0x80ed030 "example(a)foo.net" mailbox = 0x80ded98 "INBOX" auth_socket = <value optimized out> home = <value optimized out> destaddr = 0xbfb09f9c "example(a)example.com" user = 0xbfb09f9c "example(a)example.com" error = <value optimized out> extra_fields = {arr = {buffer = 0x80ed080, element_size = 4}, v = 0x80ed080, v_modifiable = 0x80ed080} ns = (struct mail_namespace *) 0x80f7a90 raw_ns = (struct mail_namespace *) 0x80f7ab8 storage = (struct mail_storage *) 0x80f7e98 box = (struct mailbox *) 0x8102768 input = (struct istream *) 0x80f8670 t = (struct mailbox_transaction_context *) 0x8106be8 headers_ctx = (struct mailbox_header_lookup_ctx *) 0x8106508 mail = (struct mail *) 0x8107a48 process_euid = 89 namespace_pool = <value optimized out> stderr_rejection = false keep_environment = false user_auth = true i = 63 ret = <value optimized out> # dovecot -n # 1.1.beta11: /etc/dovecot/dovecot.conf base_dir: /var/run/dovecot/ protocols: imap imaps pop3 pop3s login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login verbose_proctitle: yes mail_uid: 89 mail_gid: 89 mail_location: maildir:~/Maildir mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: yes mail_executable(default): /usr/lib/dovecot/rawlog /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/rawlog /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugins(default): fts fts_squat mail_plugins(imap): fts fts_squat mail_plugins(pop3): quota mail_plugin_dir(default): /usr/lib/dovecot/modules/imap/ mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap/ mail_plugin_dir(pop3): /usr/lib/dovecot/modules/ imap_client_workarounds(default): delay-newmail imap_client_workarounds(imap): delay-newmail imap_client_workarounds(pop3): pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): %f pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: login plain cram-md5 digest-md5 username_format: %Lu verbose: yes debug: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth user: postfix group: postfix master: path: /var/run/dovecot/auth-master user: vmail group: vmail plugin: quota: maildir quota_rule: *:storage=102400:messages=30000 fts: squat

2 1

[Dovecot] dovecot.index only gets updated in Root maildir Folder
by Florian Franzeck 11 Dec '07

11 Dec '07

version 1.0.rc15 (Newest Version available in Debian 4.0, newer version in testing tree requires new version libc...) I got a procmail rule that moves mail from some senders to another folder, e.g. .archive.facebook/ . This works fine, the message appear in .archive.facebook/new if i "ls" that directory by shell. But dovecot.index files don't get updated, hence IDLE doesn't tell the client new mail arrived. this only happens if i click on the folder in thunderbird. like this, not even clicking on Thunderbird "Check mail" button shows me new Mail arrived. Is this a common error in this version? would there any benefit if i self compiled a newer version regarding this issue? Thanx Config: log_timestamp: %Y-%m-%d %H:%M:%S ssl_listen: * login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_extra_groups: mail mail_location: maildir:~/Maildir auth default: mechanisms: plain login passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master:

1 0

[Dovecot] v1.0.9 released
by Timo Sirainen 11 Dec '07

11 Dec '07

http://dovecot.org/releases/1.0/dovecot-1.0.9.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.9.tar.gz.sig + Maildir: Don't wait on dovecot-uidlist.lock when we just want to find out a new filename for the message. - mbox: v1.0.8 changes sometimes caused FETCH to fail with "got too little data", disconnecting the client. - Fixed a memory leak when FETCHing message header/body multiple times within a command (e.g. BODY[1] BODY[2]) - IMAP: Partial body fetching was still slow with mboxes

1 0

[Dovecot] Using global und per-user sieve scripts at the same time
by Matthias Kellermann 11 Dec '07

11 Dec '07

Hi list, I'm trying to get a global sieve mailfilter with per-user sieve scripts to work. At the "lda"-section in the dovecot.conf file I have: global_script_path = /usr/local/etc/sieve/spam /usr/local/etc/sieve/spam: require "fileinto"; if header :contains ["Subject"] ["***Spam***"] { fileinto "Spam"; stop; } which will work fine delivering Spam Mails in a Spam dir for every user. If a user creates his own .dovecot.sieve file the global script will not work anymore. How can I enable global and local per-user sieve scripts at once? Is this possible? Do you know any workaround so all users will have the same (Spam-)sieve filters beside there own (global templates or so)? Matthias

5 11

[Dovecot] squat also not working in beta11
by Joe Wong 10 Dec '07

10 Dec '07

Hi Timo, Just tried squat in beta11. I also get the same error in the log: dovecot: Dec 10 14:21:17 Error: IMAP(joewong99:joew.outblaze.com): Corrupted squat uidlist file /mailfs/4/22/3/joewon g99:joew.outblaze.com@joew_outblaze_com/Maildir/dovecot.index.search.uids: Broken uidlists There is not change in my configuration file. # 1.1.beta11: /usr/local/etc/dovecot.conf log_path: /var/log/dovecot-1.1.log info_log_path: /var/log/dovecot-1.1.log protocols: imap ssl_disable: yes login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_user: nobody verbose_proctitle: yes mail_location: maildir:~/Maildir mail_debug: yes mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: yes mail_drop_priv_before_exec: yes mail_plugins: fts fts_squat auth default: user: mdrop username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@: username_translation: @: verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /usr/local/etc/dovecot-sql.conf userdb: driver: sql args: /usr/local/etc/dovecot-sql.conf plugin: fts: squat --

2 5

Re: [Dovecot] New Mailbox Format Plugin Help
by Sacha Bernstein 10 Dec '07

10 Dec '07

On 12/8/07, Timo Sirainen <tss(a)iki.fi> wrote: > On Sat, 2007-12-08 at 10:11 -0500, Sacha Bernstein wrote: > > I would like to develop a new mailbox format for a very specialized > > application. Can anyone point me in the appropriate direction to get > > started writing a plugin? > > > > More detail for anyone interested: > > I need to store mail in a format that's quickly accessible and > > modifiable to an external process. This is for a very low-volume mail > > system (averaging less than 50 messages stored at any one time) that > > needs very good indexing. I need to create new mailboxes on the fly > > and perform fast searches across all the mailboxes. I intend to store > > all the messages in an SQL database. Any help getting started > > interfacing with dovecot (other than reading through _all_ the source > > code) would be greatly appreciated. > > v1.1 makes this a lot easier, so start with it instead of v1.0. You can > probably get started with my existing SQL backend code: > http://dovecot.org/list/dovecot/2007-November/026632.html > > The main idea is to implement APIs in lib-storage/mail-storage-private.h > and lib-storage/mailbox-list-private.h. Most of these calls can be > implemented by calling generic index_*() functions in > lib-storage/index/. Thanks, I'll get started with this. I'm sure I'll have more questions once I get further into it. If anyone's interested (especially any amateur radio operators that may be on this list), you can see what my plans are for the SQL storage backend for dovecot at w2sjb.org. Basically, the short version is a linux gateway to a radio-based email system for use in emergencies. Of course it has many other uses, but that's what I'm going to be using it for :-) Thanks, Sacha

1 0

Re: [Dovecot] Automatic Index Generation
by Maciej Poszywak 10 Dec '07

10 Dec '07

>> Timo Sirainen wrote: >> >>> I guess you mean logging in with POP3? There the slowdown comes from >>> getting all messages' virtual sizes. So your preindexer could probably >>> do this by running pop3 for all users. If you use only a single UID for >>> users, you could do something like: >>> >>> for user in `cat users`; do >>> export MAIL=maildir:/home/$user/Maildir >>> echo "quit" | /usr/local/libexec/dovecot/pop3 >>> done >>> >>> >>> >> vmu1@test:~$ env | grep MAIL >> MAIL=maildir:/var/mail/testuser >> vmu1@test:~$ echo "quit" | /usr/lib/dovecot/pop3 >> pop3(vmu1): Fatal: pop3_uidl_format setting is missing from config file >> >> I have pop3_uidl_format correctly defined in the config file. I've also >> tried to strace pop3, to find where it does look for it, but with no >> success. >> > > It gets it from environment: > > POP3_UIDL_FORMAT=... pop3 > > In general all settings are passed in environment using uppercased > names. > > Are you sure that all variables can be read from environment ? vmu1@mail:~$ env | grep -E "(MMAP|LOCK)" MMAP_DISABLED=yes MAIL_READ_MMAPED=no LOCK_METHOD=dotlock POP3_LOCK_SESSION=yes vmu1@mail:~$ echo "quit" | /usr/lib/dovecot/pop3 pop3(vmu1): Fatal: lock_method=dotlock and mmap_disable=no combination isn't supported. You don't _really_ want it anyway. vmu1@mail:~$ /usr/sbin/dovecot --version 1.0.rc15 -- Maciej Poszywak

2 1

[Dovecot] v1.1.beta11 released (Problems)
by Jerry Yeager 10 Dec '07

10 Dec '07

On Dec 9, 2007, at 1:48 PM, dovecot-request(a)dovecot.org wrote: > > > Message: 7 > Date: Sun, 09 Dec 2007 20:29:49 +0200 > From: Timo Sirainen <tss(a)iki.fi> > Subject: [Dovecot] v1.1.beta11 released > To: dovecot(a)dovecot.org > Message-ID: <1197224989.922.405.camel@hurina> > Content-Type: text/plain; charset="us-ascii" > > 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.. :) > stuff cut out > End of dovecot Digest, Vol 56, Issue 26 > *************************************** I ran into a problem moving from v 1.1 beta 10 to v 1.1 beta 11, the logs show: Dec 9 16:03:49 ns1 dovecot[331]: Dovecot v1.1.beta11 starting up Dec 9 16:03:50 ns1 dovecot[331]: imap-login: We couldn't drop root group privileges (wanted=150, gid=150, egid=0) Dec 9 16:03:50 ns1 dovecot[331]: Temporary failure in creating login processes, slowing down for now The last two messages then begin repeating until Dovecot is shut down. obviously, no one can log in. I tried changing the following # System user and group used to access mails. If you use multiple, userdb # can override these by returning uid or gid fields. You can use either numbers # or names. <doc/wiki/UserIds> #mail_uid = #mail_gid = to explicitly specifying # System user and group used to access mails. If you use multiple, userdb # can override these by returning uid or gid fields. You can use either numbers # or names. <doc/wiki/UserIds> mail_uid = Dovecot mail_gid = Dovecot As well as setting the setuid bit in login_executable = /usr/local/libexec/dovecot/imap-login to no avail. Dropping back to v 1.1 beta 10 fixed things for the moment. I did a quick scan of the example conf file and the wiki docs but could not find anything relevant. dovecot -n shows (essentially the same for both versions) # 1.1.beta11: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ protocols: imaps ssl_listen: *:993 ssl_cipher_list: ALL:!LOW:!SSLv2 verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_user: Dovecot login_greeting: Hello, Dovecot is ready. valid_chroot_dirs: /var/mail/vmail/ mail_extra_groups: mail mail_location: maildir:/var/spool/vmail/%d/%n:INDEX=/var/spool/vmail/ %d/%n:INBOX=/var/spool/vmail/%d/%n mail_debug: yes lock_method: flock auth default: mechanisms: plain login passdb: driver: passwd-file args: scheme=plain-md5 username_format=%u /etc/dovecot/passwd userdb: driver: static args: uid=virtual gid=virtual home=/var/spool/vmail/%d/%n socket: type: listen client: path: /var/spool/postfix/private/auth user: postfix group: postfix master: path: /usr/local/var/run/dovecot/auth-master user: virtual group: virtual This is running on OS X 10.5.1 ??? Jerry

2 2

[Dovecot] Dovceot 1.0.8 compile error after rewrite patch
by Lars Johansen 10 Dec '07

10 Dec '07

Added the rewrite patch for 1.0.8 without any problems, but when I tried building with: configure --prefix=/usr/local/dovecot, make gives this output: gcc -shared .libs/mail-log-plugin.o -Wl,-soname -Wl,lib20_mail_log_plugin.so -o .libs/lib20_mail_log_plugin.so ar cru .libs/lib20_mail_log_plugin.a mail-log-plugin.o ranlib .libs/lib20_mail_log_plugin.a creating lib20_mail_log_plugin.la (cd .libs && rm -f lib20_mail_log_plugin.la && ln -s ../lib20_mail_log_plugin.la lib20_mail_log_plugin.la) make[4]: Leaving directory `/usr/local/src/dovecot-1.0.8/src/plugins/mail-log' Making all in trash make[4]: Entering directory `/usr/local/src/dovecot-1.0.8/src/plugins/trash' if /bin/sh ../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../../src/lib -I../../../src/lib-mail -I../../../src/lib-storage -I../../../src/plugins/quota -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -MT trash-plugin.lo -MD -MP -MF ".deps/trash-plugin.Tpo" -c -o trash-plugin.lo trash-plugin.c; \ then mv -f ".deps/trash-plugin.Tpo" ".deps/trash-plugin.Plo"; else rm -f ".deps/trash-plugin.Tpo"; exit 1; fi mkdir .libs gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../../src/lib -I../../../src/lib-mail -I../../../src/lib-storage -I../../../src/plugins/quota -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -MT trash-plugin.lo -MD -MP -MF .deps/trash-plugin.Tpo -c trash-plugin.c -fPIC -DPIC -o .libs/trash-plugin.o trash-plugin.c:110: warning: 'struct quota_root_transaction_context' declared inside parameter list trash-plugin.c:110: warning: its scope is only this definition or declaration, which is probably not what you want trash-plugin.c: In function 'trash_try_clean_mails': trash-plugin.c:134: error: dereferencing pointer to incomplete type trash-plugin.c:205: error: dereferencing pointer to incomplete type trash-plugin.c:205: error: dereferencing pointer to incomplete type trash-plugin.c:206: error: dereferencing pointer to incomplete type trash-plugin.c:207: error: dereferencing pointer to incomplete type trash-plugin.c:207: error: dereferencing pointer to incomplete type trash-plugin.c:208: error: dereferencing pointer to incomplete type trash-plugin.c: At top level: trash-plugin.c:214: warning: 'struct quota_root_transaction_context' declared inside parameter list trash-plugin.c: In function 'trash_quota_root_try_alloc': trash-plugin.c:216: error: dereferencing pointer to incomplete type trash-plugin.c:220: error: 'struct quota_backend_vfuncs' has no member named 'try_alloc' trash-plugin.c:238: warning: passing argument 1 of 'trash_try_clean_mails' from incompatible pointer type trash-plugin.c: At top level: trash-plugin.c:248: warning: 'struct quota_root_transaction_context' declared inside parameter list trash-plugin.c: In function 'trash_quota_root_try_alloc_bytes': trash-plugin.c:250: error: dereferencing pointer to incomplete type trash-plugin.c:254: error: 'struct quota_backend_vfuncs' has no member named 'try_alloc_bytes' trash-plugin.c:262: warning: passing argument 1 of 'trash_try_clean_mails' from incompatible pointer type trash-plugin.c: At top level: trash-plugin.c:272: warning: 'struct quota_root_transaction_context' declared inside parameter list trash-plugin.c: In function 'trash_quota_root_test_alloc_bytes': trash-plugin.c:274: error: dereferencing pointer to incomplete type trash-plugin.c:278: error: 'struct quota_backend_vfuncs' has no member named 'test_alloc_bytes' trash-plugin.c:286: warning: passing argument 1 of 'trash_try_clean_mails' from incompatible pointer type trash-plugin.c: In function 'trash_quota_root_created': trash-plugin.c:313: error: 'struct quota_root' has no member named 'v' trash-plugin.c:314: error: 'struct quota_root' has no member named 'v' trash-plugin.c:315: error: 'struct quota_root' has no member named 'v' trash-plugin.c:316: error: 'struct quota_root' has no member named 'v' trash-plugin.c:317: error: 'struct quota_root' has no member named 'v' make[4]: *** [trash-plugin.lo] Error 1 make[4]: Leaving directory `/usr/local/src/dovecot-1.0.8/src/plugins/trash' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/usr/local/src/dovecot-1.0.8/src/plugins' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/local/src/dovecot-1.0.8/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/dovecot-1.0.8' make: *** [all] Error 2

2 1

[Dovecot] Automatic Index Generation
by Maciej Poszywak 10 Dec '07

10 Dec '07

Hello, I'm looking for an application/script/etc. which will allow me to recreate dovecot indexes by hand from shell. I'm preparing myself for migration to dovecot 1.0.rc15 (debian stable) and would like to create indexes before users start to login into new server to ease the load. My other option is to write a script which will log as each user and create indexes, however this seems a bit of painful way to do it. Anybody can point me in right direction? -- Maciej Poszywak

5 10

[Dovecot] dict: Leaked a t_pop() call in I/O handler
by Sergio Lopez 10 Dec '07

10 Dec '07

Hello, I've just installed another postfix+dovecot based mail service (I love dovecot! :-), and I found this message "dict: Leaked a t_pop() call in I/O handler (nil)" being logged each time I authenticate against it via POP3 or IMAP. Searching through the code, I've found this (this is Dovecot v1.0.8): ---- src/dict/dict-cache.c ---- void dict_cache_unref(struct dict_cache *cache, const char *uri, const char *username) { struct dict_entry *entry; t_push(); entry = hash_lookup(cache->dicts, t_strdup_printf("%s\t%s", username, uri)); i_assert(entry != NULL && entry->refcount > 0); if (--entry->refcount == 0) { hash_remove(cache->dicts, entry->user_uri); dict_deinit(&entry->dict); i_free(entry->user_uri); i_free(entry); } } ---- src/dict/dict-cache.c ---- Notice the "t_push()" call there. So calling t_pop() somewhere before the end of the function, makes dovecot work like a charm (again). P.D: I'm really surprised that nobody noticed this before. Am I the only man in the world who uses Dovecot storing quota information into a SQL Database? ;-) -- Sergio López - <sergio.lopez(a)nologin.es> Nologin Consulting S.L. - http://nologin.es

2 1

[Dovecot] Internal Error - Cannot select inbox
by Eric Beda 10 Dec '07

10 Dec '07

Hi, I am new to this list although i have been using dovecot for some time now, i've come accross this error when a user tries to log in * OK Dovecot ready. 1 login username password 1 OK Logged in. 1 select inbox 1 NO Internal error occurred. Refer to server log for more information. [2007-12-07 12:51:56] there are no errors reported in the log files related to that issue for both dovecot.log and maillog what i do receive in the log files is dovecot: Dec 07 12:55:46 Info: imap-login: Login: user=<username@domain>, method=PLAIN, rip=::ffff:127.0.0.1, lip=::ffff:127.0.0.1, secured dovecot: Dec 07 12:55:46 Info: IMAP(username@domain): Effective uid=500, gid=500 dovecot: Dec 07 12:55:46 Info: IMAP(aadu(a)uccmail.co.tz): mbox: data=/var/spool/mail/vmail/domain/username:INBOX=/var/spool/mail/vmail/domain/username/Inbox:INDEX=/var/spool/mail/vmail/domain/username:home=/var/spool/mail/vmail/domain/username/.imap/.imap dovecot: Dec 07 12:55:46 Info: IMAP(aadu(a)uccmail.co.tz): mbox: root=/var/spool/mail/vmail/domain/username, index=/var/spool/mail/vmail/domain/username, inbox=/var/spool/mail/vmail/domain/username/Inbox dovecot: Dec 07 12:55:46 Info: IMAP(username@domain): Disconnected i can't seem to pinpoint what is going wrong, some things to note i have existing users who can read email succesfully, its when i create a new user via postfixadmin, one should note that all directories are created and owned by vmail whose gid and uid is 500 and for the new users the directories and mboxes are created succesfully, but even if i copy over a working inbox of previous user to new user i still get an error so i don't think it is an mbox formatting issue another thing is that i can successfully check mail using mutt facility, even sending using mail clients (outlook express) is possible other configurations that might be helpful # dovecot --version 1.0.rc15 #cat /etc/group |grep vmail dovecot:x:97:vmail vmail:x:500:dovecot # /etc/dovecot.conf log_path: /var/log/dovecot.log protocols: pop3 pop3s imap imaps ssl_disable: yes login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login mail_location: mbox:/var/spool/mail/vmail/%d/%n:INBOX=/var/spool/mail/vmail/%d/%n/Inbox:INDEX=/var/spool/mail/vmail/%d/%n:home=/var/spool/mail/vmail/%d/%n/.imap/.imap mail_debug: yes maildir_copy_with_hardlinks: yes mbox_min_index_size: 200 mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 auth default: mechanisms: plain login passdb: driver: pam passdb: driver: sql args: /etc/dovecot/dovecot-mysql.conf userdb: driver: sql args: /etc/dovecot/dovecot-mysql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master:

3 5

[Dovecot] Roadmap to future
by Timo Sirainen 10 Dec '07

10 Dec '07

v1.1.0 is finally getting closer, so it's time to start planning what happens after it. Below is a list of some of the larger features I'm planning on implementing. I'm not yet sure in which order, so I think it's time to ask again what features companies would be willing to pay for? Sponsoring Dovecot development gets you: - listed in Credits in www.dovecot.org - listed in AUTHORS file - you can tell me how you want to use the feature and I'll make sure that it's possible (within reasonable limits) - allows you to change the order in which features are implemented (more or less) As you can see below, some features are easier to implement when other features are implemented first. Several of them depend on v2.0 master rewrite, so I'm thinking that maybe it's time to finally finish that first. I know several companies have requested replication support, but since it kind of depends on several other features, it might be better to leave that for v2.1. But of course sponsoring development of those features that replication depends on gets you the replication support faster. :) I'm still trying to go to school (and this year I started taking CS classes as well as biotech classes..), so it might take a while for some features to get implemented. I'm anyway hoping for a v1.2 or v2.0 release before next summer. So, the list.. -------------- Implemented, but slightly buggy so not included in v1.1 (yet): - Mailbox list indexes - THREAD REFERENCES indexes - THREAD X-REFERENCES2 algorithm where threads are sorted by their latest message instead of the thread root message Could be implemented for v1.2: - Shared mailboxes and ACLs http://www.dovecot.org/list/dovecot/2007-April/021624.html - Virtual mailboxes: http://www.dovecot.org/list/dovecot/2007-May/022828.html - Depends on mailbox list indexes dbox plans, could be implemented for v1.2: - Support for single instance attachment storage - Global dbox storage so copying messages from mailbox to another involves only small metadata updates - Support some kind of hashed directories for storing message files, instead of storing everything in a single directory. - Finish support for storing multiple messages in a file v2.0 master/config rewrite -------------------------- It's mostly working already. One of the larger problems left is how to handle plugin settings. Currently Dovecot just passes everything in plugin {} section to mail processes without doing any checks. I think plugin settings should be checked just as well as the main settings. Also plugins should be able to create new sections instead of having to use plain key=value settings for everything. v2.0 currently runs a perl script on Dovecot's source tree to find settiongs from different places then then creates a single all-settings.c for config process. This obviously doesn't work for out-of-tree plugins, so there needs to be some other way for them to pass the allowed settings. There are two possibilities: a) Read them from separate files. This is a bit annoying, because it's not anymore possible to distribute simple plugin.c files and have them compiled into plugin.so files. b) Read them from the plugin itself. This would work by loading the plugin and then reading the variable containing the configuration. I'm a bit worried about security implications though, because the plugins could execute some code while they're loaded. But I guess a new unprivileged process could be created for doing this. Of course normally admins won't run any user-requested plugins anyway so this might not be a real issue anyway. :) Index file optimizations ------------------------ - Since these are not backwards compatible changes, the major version number should be increased whenever these get implemented. So I think these should be combined with v2.0 master/config rewrite. I'd rather not release v3.0 soon after v2.0 just for these.. - dovecot.index.log: Make it take less space! Get rid of the current "extension introduction" records that are large and written over and over again. Compress UID ranges using similar methods than Squat uses now. Try all kinds of other methods to reduce space usage. Write transaction boundaries, so the reader can process entire transactions at a time. This will make some things easier, such as avoiding NFS data cache flushes, replication support and also allows lockless writes using O_APPEND. - dovecot.index: Instead of keeping a single message record array, split it into two: A compressed list of message UIDs and array containing the rest of the data. This makes the file smaller and keeping UIDs separate allows better CPU cache (and maybe disk I/O) utilization for UID -> sequence lookups. At least this is the theory, I should benchmark this before committing to this design. :) There could also be a separate expunged UIDs list. UIDs existing in there would be removed from existing UIDs list, but it wouldn't affect calculating offsets to record data in the file. So while currently updating dovecot.index file after expunges requires recreating the whole file, with this method it would be possible to just write 4 bytes to the expunged UIDs list. The space reserved for expunged UIDs list would be pretty small though, so when it gets full the file would be recreated. - dovecot.index.cache: Better disk I/O and CPU cache utilization by keeping data close together in the file when it's commonly accessed toghether. For example message sizes and dates for all messages could be close to each others to optimize SORTing by message size/date. If clients use conflicting access patterns, the data could be either duplicated to optimize both patterns or just let it be slower for the other pattern. Deliver / LMTP server --------------------- Currently deliver parses dovecot.conf using its own parser. This has caused all kinds of problems. v2.0's master rewrite helps with this, because deliver can then just ask the configuration from config process the same way as other processes are. Another problem is that people who use multiple user IDs have had to make deliver setuid-root. I really hate this, but currently there's no better way. Better fix for this would be to use LMTP server instead. There could be either a separate LMTP client or deliver could support LMTP protocol as well. I'm not sure which one is better. How would LMTP server then get around the multiple user IDs issue? There are two possibilities: a) Run as root and temporarily set effective UID to the user whose mails we are currently delivering. This has the problem that if users have direct access to their mailboxes and index files, the mailbox handling code has to be bulletproof to avoid regular users gaining root privileges by doing special modifications to index files -- possibly at the same time as the mail is being delivered to exploit some race condition with mmaped index files.. b) Create a child process for each different UID and drop its privileges completely. If all users have different UIDs, this usually means forking a new process for each mail delivery, making the performance much worse than with a) method. It would anyway be possible to delay destroying the child processes in case a new message comes in for the same UID. This would probably mostly help only when UIDs are shared by multiple users, such as each domain having their own UID. I think I'll implement both and let admin choose which method to use. This same problem exists for several other things besides deliver/LMTP server. For example a) method is already implemented for expire plugin's expire-tool in v1.1. So this code needs to be somewhat generic so it won't have to be duplicated in multiple places. All of this pretty much requires the new v2.0 master rewrite. Adding these to v1.x would be ugly. Proxying -------- - These could be implemented to v1.2. - Log in normally (no proxying) if destination IP is the server itself. - Support for per-namespace proxying: namespace public { prefix = Public/ location = proxy:public.example.org } There are two choices for this: Dummy IMAP proxying or handling it with a mail storage backend. Dummy IMAP proxying would just let the remote server whose mailbox is currently selected handle most of the commands and their replies. I'm just afraid that this will become problematic in future. For example if the proxying server wants to send the client an event, such as "new message was added to this other mailbox", it would have to be sure that the remote server isn't currently in the middle of sending something. And the only way to be sure would be to parse its input, which in turn would make the proxying more complex. Then there would be problems if the servers support different IMAP extensions. And maybe some extensions will require knowing the state of multiple mailboxes, which will make handling them even more complex if the mailboxes are on different servers. Implementing this as a mail storage backend would mean that the proxying server parses all the IMAP commands internally and uses Dovecot's mail storage API to process them. The backend would then request data from the remote server when needed and cache it internally to avoid asking the same data over and over again. Besides caching, this would mean that there are no problems with extensions, since Dovecot handles the the exact same way as for other backends, requiring no additional code. To get better performance the storage backend would have to be smarter than most other Dovecot backends. For example while the current backends handle searches by reading through all the messages, the proxy backend should just send the search request to the remote server. The same for SORT. And for THREAD, which the current storage API doesn't handle.. And how would proxying server and remote server then communicate? Again two possibilities: Either a standard IMAP protocol, with possibly some optional Dovecot-extensions to improve performance, or a bandwidth-efficient protocol. The main advantage with IMAP protocol is that it could be used for proxying to other servers. Bandwidth-efficient protocol could be based on dovecot.index.log format, making it faster/easier to parse and generate. Once we're that far with proxying, we're close to having..: Replication ----------- The plans haven't changed much from: http://www.dovecot.org/list/dovecot/2007-May/022792.html The roadmap to complete replication support would be basically: 1. Implement proxying with mail storage API. 2. Implement asynchronous replication: - Replication master process collecting changes from other Dovecot processes via UNIX sockets. It would forward these changes to slaves. Note that this requires that only Dovecot is modifying mailboxes, mails must be delivered with Dovecot's deliver! - If some slaves are down, save the changes to files in case they come back up. In case they don't and we reach some specific max. log file size, keep also track of mailboxes that have changed and once the slaves do come back, make sure those mailboxes are synced. - If replication master is down and there have been changes to mailboxes.. Well, I haven't really thought about this. Maybe refuse to do any changes to mailboxes? Maybe have mail processes write to some "mailboxes changed" log file directly? Probably not that big of a deal since replication master just shouldn't be down. :) - Support for manual resync of all mailboxes, in case something was done outside Dovecot. - Replication slave processes would be reading incoming changes. I think this process should just make sure that the changes are read as fast as possible, so with sudden bursts of activity the slave would start saving the changes to a log instead of the master. - Replication mailbox writer processes would receive changes from the main slave process via UNIX sockets. They'd be responsible for actually saving the data to mailboxes. If multiple user IDs are used, this has the same problems as LMTP server. - Conflict resolution. If mailbox writer process notices that the UID already exists in the mailbox, both the old and the new message must be given new UIDs. This involves telling the replication master about the problem, so both servers can figure out together the new UIDs. I haven't thought this through yet. - Conflict resolution for message flags/keywords. The protocol would normally send flag changes incrementally, such as "add flag1, remove flag2". Besides that there could be a 8bit checksom of all the resulting flags/keywords. If the checksum doesn't match, request all the current flags. It would be of course possible to send the current flags always instead of incremental updates, but this would waste space when there are lots of keywords, and multi-master replication will work better when the updates are incremental. 3. Synchronous replication: - When saving messages, don't report success until at least one replication slave has acknowledged that it has also saved the message. Requires adding bidirectional communication with the replication master process. The message could sent to slaves in smaller parts, so if the message is large the wait at the end would basically consist of sending "finished saving UID 1234, please ack". - Synchronous expunges also? Maybe optional. The main reason for this is that it wouldn't be nice to break IMAP state by having expunged messages come back. 4. Multi-master replication: - Almost everything is already in place. The main problem here is IMAP UID allocation. They must be allocated incrementally, so each mailbox must have a globally increasing UID counter. The usage goes like: 1. Send the entire message body using a global unique ID to all servers. No need to wait for their acknowledgement. 2. Increase the global IMAP UID counter for this mailbox. 3. Send global UID => IMAP UID message to all servers. 4. Wait for one of them to reply with "OK". Because messages sent by different servers can end up being visible in different times, the servers must wait that they've seen all the previous UIDs before notifying client of a new UID. If the sending server crashed between steps 2 and 3, this never happens. So the replication processes must be able to handle that, and also handle requesting missing UIDs in case they had lost connections to other servers. - I just had the idea of global UID counters instead of global locks, so I haven't yet thought how the counters would be best implemented. It should be easier to implement than global locks though. - Non-incremental changes are somewhat problematic and could actually require global locks. The base IMAP protocol supports replacing flags, so if there is no locking and conflicting flag replacement commands are sent to two servers, which one of those commands should be effective? Timestamps would probably be enough for flag changes, but it may not be enough for some IMAP extensions (like CONDSTORE?). - If global locks are required, they would work by passing the lock from one server to another when requested. So as long as only a single server is modifying the mailbox, it would hold the global lock and there would be no need to keep requesting it for each operation. 5. Automation: - Automatically move/replicate users between servers when needed. This will probably be implemented separately long after 4. The replication processes would be ugly to implement for v1.x master, so this pretty much depends on v2.0 master rewrite.

4 6

[Dovecot] disconnect after too many errors?
by Peter Hessler 09 Dec '07

09 Dec '07

There are a couple of jerks that are tying to dictionary attack my email server, and one of the vectors is pop3/imap logins. Something I would like to do in dovecot, but can't seem to find, is the ability to disconnect after a certain number of errors. The vast majority of my users (i.e. me) don't hand-type POP3 or IMAP transactions, but when we do, we know how to spell things properly. Does dovecot have this? A simiple look shows no. -- I wouldn't mind dying -- it's that business of having to stay dead that scares the shit out of me. -- R. Geis

4 6

[Dovecot] MANAGESIEVE patch v7 for dovecot 1.0.3 and TLS
by Andreas Schneider 09 Dec '07

09 Dec '07

Hi, I allow only TLS/SSL connection to dovecot. The managesieve doesn't work with TLS but it works without it. gladiac@magrathea:~> gnutls-cli -p 2000 -s --insecure -V milliways.cynapses.org Resolving 'milliways.cynapses.org'... Connecting to '213.239.217.124:2000'... - Simple Client Mode: - Received[194]: "IMPLEMENTATION" "dovecot" "SASL" "PLAIN" "SIEVE" "fileinto reject envelope vacation imapflags notify subaddress relational comparator-i;ascii-numeric regex" "STARTTLS" OK "Dovecot ready." STARTTLS - Sent: 9 bytes - Received[33]: OK "Begin TLS negotiation now." Let me know if you need more information. Thanks, -- andreas -- http://www.cynapses.org/ - cybernetic synapses

3 4

[Dovecot] Compiling with SQL support
by Mark Smith 09 Dec '07

09 Dec '07

Hello all, I am currently having a slight problem (ok well more likely me just not doing it right), with compiling Dovecot with MySQL support. The version is 1.0.8. I have tried running configure with --with-sql and --with-sql-drivers, but this however still does not compile MySQL support, I do no wish to install MySQL on this server, as I am using a network SQL server, but I do have the compiled source available on this server. I have tried running: gcc -shared -fPIC -DHAVE_CONFIG_H -DBUILD_MYSQL \ -I../.. -I../lib -I../lib-settings -I/data/mysql/include/mysql \ driver-mysql.c -o driver_mysql.so -lmysqlclient inside the /src/lib-sql, but this just returns an error that mysqlclient cannot be found. I have tried running dovecot --build-options, but MySQL is not listed here, the operating system is FreeBSD 6.2. The documentation does not seem to be giving any hints as to why this is not working, nor do How Tos. Anyrhing remotely helpful would be appreciated. Mark Smith

2 1

[Dovecot] Is dovecot the right choice for this problem?
by Darren McLaughlin 09 Dec '07

09 Dec '07

Is dovecot the right choice for this problem? I have a shared server with verio. I have one particular client that sends and receives numerous large emails, and those emails were causing me to run out of processes on my verio server, and basically slow things down a great deal due to the shared mail queue. Verio suggested Dovecot to reduce server load and allow this one client to have less problems with sending and receiving email. Does this sound logical to anyone in the know? Thanks! Darren

3 6

[Dovecot] Are these events normal?
by Jost Krieger 08 Dec '07

08 Dec '07

We have dropped dovecot in place of UW-IMAP for about 40000 users and have solved our immediate problem: disk I/O overload, mainly from people doing POP3 and "leave mail on server". Thank you! Now i got loads of dovecot error messages in the logs and don't know if there is any significance. Here are a few examples: The most common event is: 2007-12-06 16:00:17.837654500 dovecot: Error: IMAP(xxxxxxxx): FETCH for mailbox UCE-TMP UID 1547 got too little data: 5176 vs 5184 2007-12-06 16:00:18.575403500 dovecot: Error: IMAP(xxxxxxxx): FETCH for mailbox UCE-TMP UID 1548 got too little data: 4749 vs 4757 2007-12-06 16:00:19.276147500 dovecot: Error: IMAP(xxxxxxxx): FETCH for mailbox UCE-TMP UID 1548 got too little data: 4749 vs 4757 2007-12-06 16:00:20.371238500 dovecot: Error: IMAP(xxxxxxxx): FETCH for mailbox UCE-TMP UID 1540 got too little data: 5162 vs 5170 2007-12-06 16:00:20.996483500 dovecot: Error: IMAP(xxxxxxxx): FETCH for mailbox UCE-TMP UID 1540 got too little data: 5162 vs 5170 2007-12-06 16:00:21.650218500 dovecot: Error: IMAP(xxxxxxxx): FETCH for mailbox UCE-TMP UID 1541 got too little data: 4086 vs 4094 2007-12-06 16:00:22.273782500 dovecot: Error: IMAP(xxxxxxxx): FETCH for mailbox UCE-TMP UID 1541 got too little data: 4086 vs 4094 2007-12-06 16:00:22.920507500 dovecot: Error: IMAP(xxxxxxxx): FETCH for mailbox UCE-TMP UID 1542 got too little data: 3556 vs 3562 2007-12-06 16:00:23.490787500 dovecot: Error: IMAP(xxxxxxxx): FETCH for mailbox UCE-TMP UID 1542 got too little data: 3556 vs 3562 2007-12-06 16:00:24.052849500 dovecot: Error: IMAP(xxxxxxxx): FETCH for mailbox UCE-TMP UID 1543 got too little data: 4098 vs 4106 2007-12-06 16:00:24.741072500 dovecot: Error: IMAP(xxxxxxxx): FETCH for mailbox UCE-TMP UID 1543 got too little data: 4098 vs 4106 2007-12-06 16:00:25.448977500 dovecot: Error: IMAP(xxxxxxxx): FETCH for mailbox UCE-TMP UID 1544 got too little data: 4627 vs 4635 2007-12-06 16:00:26.130131500 dovecot: Error: IMAP(xxxxxxxx): FETCH for mailbox UCE-TMP UID 1544 got too little data: 4627 vs 4635 2007-12-06 16:00:26.819376500 dovecot: Error: IMAP(xxxxxxxx): FETCH for mailbox UCE-TMP UID 1545 got too little data: 7582 vs 7590 2007-12-06 16:00:27.445497500 dovecot: Error: IMAP(xxxxxxxx): FETCH for mailbox UCE-TMP UID 1545 got too little data: 7582 vs 7590 Somewhat rarer are events like 2007-12-06 19:36:44.114294500 dovecot: Info: POP3(yyyyyyyy): Disconnected: Storage error during logout. top=1/1723, retr=1/4665462, del=27/61, size=17280696 and rarely we got 2007-11-24 12:10:01.086620500 dovecot: Error: IMAP(zzzzzzzz): file istream-header-filter.c: line 194 (read_header): assertion failed: (hdr == NULL) 2007-11-24 12:10:01.086718500 dovecot: Error: IMAP(zzzzzzzz): Raw backtrace: 2007-11-24 12:10:01.089552500 dovecot: Error: child 13083 (imap) killed with signal 6 2007-11-24 12:10:01.655875500 dovecot: Error: IMAP(zzzzzzzz): file istream-header-filter.c: line 194 (read_header): assertion failed: (hdr == NULL) 2007-11-24 12:10:01.656106500 dovecot: Error: IMAP(zzzzzzzz): Raw backtrace: 2007-11-24 12:10:01.659853500 dovecot: Error: child 13098 (imap) killed with signal 6 2007-11-24 12:10:02.022553500 dovecot: Error: IMAP(zzzzzzzz): file istream-header-filter.c: line 194 (read_header): assertion failed: (hdr == NULL) 2007-11-24 12:10:02.022761500 dovecot: Error: IMAP(zzzzzzzz): Raw backtrace: 2007-11-24 12:10:02.025866500 dovecot: Error: child 13121 (imap) killed with signal 6 Our dovecot is # 1.0.5: /usr/local/dovecot/etc/dovecot.conf log_path: /dev/stderr log_timestamp: protocols: pop3 imap listen(default): 134.147.64.16:143 listen(imap): 134.147.64.16:143 listen(pop3): 134.147.64.16:110 ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/local/dovecot/libexec/dovecot/imap-login login_executable(imap): /usr/local/dovecot/libexec/dovecot/imap-login login_executable(pop3): /usr/local/dovecot/libexec/dovecot/pop3-login login_process_per_connection: no valid_chroot_dirs: /net/sunu007/disc3/home:/net/sunu007/disc4/home max_mail_processes: 4096 first_valid_uid: 50 mail_location: mbox:~/Mail:INBOX=~/Mailbox:INDEX=~/ mail_executable(default): /usr/local/dovecot/libexec/dovecot/imap mail_executable(imap): /usr/local/dovecot/libexec/dovecot/imap mail_executable(pop3): /usr/local/dovecot/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/dovecot/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/dovecot/lib/dovecot/pop3 mail_log_max_lines_per_sec: 0 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv auth default: passdb: driver: shadow args: blocking=yes userdb: driver: passwd Is there anything we should do? The crashes have stopped in the meantime, it seems. Jost -- | Helft Spam ausrotten! HTML in Mail ist unhöflich. | | Postmaster, JAPH, manchmal Wahrsager am RZ der RUB | | Wahre Worte sind nicht gefällig, gefällige Worte sind nicht wahr.| | Lao Tse, Tao Te King 81 |

3 3

[Dovecot] New Mailbox Format Plugin Help
by Sacha Bernstein 08 Dec '07

08 Dec '07

I would like to develop a new mailbox format for a very specialized application. Can anyone point me in the appropriate direction to get started writing a plugin? More detail for anyone interested: I need to store mail in a format that's quickly accessible and modifiable to an external process. This is for a very low-volume mail system (averaging less than 50 messages stored at any one time) that needs very good indexing. I need to create new mailboxes on the fly and perform fast searches across all the mailboxes. I intend to store all the messages in an SQL database. Any help getting started interfacing with dovecot (other than reading through _all_ the source code) would be greatly appreciated. Thanks, Sacha

2 1

[Dovecot] Questions about deliver log files
by frank.kintrup＠fkware.de 08 Dec '07

08 Dec '07

Hi, I upgraded from Courier to dovecot, and now I try to rebuild some of the features I used to have. One was a monthly per user log of maildrop's work. I used this code in maildroprc: DATE=`date +%m` logfile "$MAILDIR/maildrop-$DATE.log" This created a monthly log in the each user's Maildir. I find it easier to have a log per user than having to filter the log entries from a large log file for all users. I tried to recreate it with deliver by using the variables %h and %d/%n, but they are not interpreted when the log file is accessed ("Can't open log file /var/vmail/%d/%n/deliver.log: No such file or directory"). And there seems to be no way to include a date in the file name (but maybe I could use logrotate for that). Another problem: Currently deliver only logs the message id. A user would never ask for this (especially if he asks where certain mails were stored/discarded), he would ask for the sender's name/email or subject. Is the contents of the log file configurable? Frank

2 2

[Dovecot] Stale NFS file handle and duplicated messages
by Adrian Barker 08 Dec '07

08 Dec '07

We recently moved all our users from the Washington IMAP server to Dovecot. There has been a substantial improvement in performance, but some users are reporting duplicate messages, and we see 'Stale NFS file handle' errors in the syslog. Does anyone know what would cause this ? The errors relate to the index file, eg. Nov 29 00:49:47 imap-e.ucl.ac.uk dovecot: [ID 107833 mail.error] IMAP(ccaazzz): close() failed with index file /home/ccaazzz/imap-mail/.imap/mbox/dovecot.index: Stale NFS file handle Our IMAP servers (5 of them) are a mixture of Sparc Solaris 8 and Solaris 10 machines, using NFS to a central mailspool running on AIX. We are using a mixture of Dovecot 1.0.3 and 1.0.5. dovecot -n gives: # 1.0.3: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ listen: *:143 ssl_listen: *:993 ssl_ca_file: /usr/local/ssl/certs/sureserveredu.pem ssl_cert_file: /usr/local/ssl/certs/imap-server_ucl_ac_uk.crt ssl_key_file: /usr/local/ssl/certs/imap.key ssl_cipher_list: MEDIUM:!LOW disable_plaintext_auth: no login_dir: /var/run/dovecot//login login_executable: /usr/local/libexec/dovecot/imap-login login_user: pp login_process_per_connection: no login_processes_count: 30 max_mail_processes: 1500 first_valid_uid: 200 mail_location: mbox:%h/imap-mail:INBOX=/nfs/rcs/mail-spool/mail/%u mmap_disable: yes mbox_lock_timeout: 55 mbox_dotlock_change_timeout: 50 mail_drop_priv_before_exec: yes mail_executable: /usr/local/sbin/dovecot-login.csh mail_plugins: mbox_snarf mail_plugin_dir: /usr/local/lib/dovecot namespace: type: private separator: / inbox: yes auth default: passdb: driver: pam passdb: driver: passwd userdb: driver: passwd plugin: mbox_snarf: ~/imap-mail/mbox -- Adrian Barker, Internet Technology Section Information Systems University College London, Gower Street, London WC1E 6BT External phone: +44 20 7679 5140, Fax (+44) 20 7388 5406 Internal phone: x 25140 Email: A.Barker(a)ucl.ac.uk

2 3

[Dovecot] Sponsorship of Dovecot
by Ed W 08 Dec '07

08 Dec '07

Timo Sirainen wrote: > v1.1.0 is finally getting closer, so it's time to start planning what > happens after it. Below is a list of some of the larger features I'm > planning on implementing. I'm not yet sure in which order, so I think > it's time to ask again what features companies would be willing to pay > for? > OK, I would like to sponsor Dovecot for three months for $1,000/month I am just a small business and this is basically coming straight out of my own paycheck, but we use the product internally and I like it and would like to see it continue to develop at the rate it has done. Although this is just a small token of my appreciation, I hope that other businesses who are using dovecot will step up and at least match this contribution. It's less than the price of a small Exchange Server setup and has oh so much more potential I have some minimal requests for what I would like to be developed during that period, but largely the pledge is without strings and you can develop as you wish. I will add a note on the Roadmap thread with my thoughts Thanks for writing Dovecot. Please contact me offlist and let me know how you want the sponsorship delivered (Paypal is fine but sometimes expensive for the receiver). I hope others will step up and increase this substantially Regards Ed W http://www.mailasail.com

1 0

Re: [Dovecot] imap crash with fts squat enabled.
by Joe Wong 08 Dec '07

08 Dec '07

Hi Timo, Dovecot was running on FC7 while the file server is running on FC4. - Joe May the force be with you..

1 0

[Dovecot] "pipe" plugin - is anyone interested (or using it)?
by Nicolas Boullis 08 Dec '07

08 Dec '07

Hi, A few months ago, I sent a message to this list asking if people would be interested by a "pipe" plugin (see http://dovecot.org/pipermail/dovecot/2007-May/023005.html ). I received a few answers of people who told they were intersted. A few months later, I sent a new message announcing the availability of my work (see http://dovecot.org/pipermail/dovecot/2007-August/024805.html ). Since then, I have received no feedback... So, is anyone using this plugin? Is anyone using it? Timo, on my first message, you seemed to be interested to merge such a feature (see http://dovecot.org/pipermail/dovecot/2007-May/023055.html ). Are you still interested? All comments are welcome. I think the feature (or a more generic one) would be a worthy addition for dovecot, be it for ham/spam learning, to implement an "outbox" or anything else I can't think about. All comments about my work are welcome. (Please note that I have not (yet) tried to port it to dovecot 1.1...) Cheers, Nicolas Boullis Ecole Centrale Paris

7 13

[Dovecot] Corrupted Transaction Log File: v1.0.7
by Daniel Watts 07 Dec '07

07 Dec '07

Following errors have happened quite a bit: Dec 7 14:19:26 locallog@tg3/tg3 dovecot: IMAP(peter.day(a)mydomain.com): Transaction log file /home/virtual/mydomain.com/home/peter.day/Maildir/.Trash/dovecot.index.log: marked corrupted Dec 7 14:19:26 locallog@tg3/tg3 dovecot: IMAP(peter.day(a)mydomain.com): Transaction log file /home/virtual/mydomain.com/home/peter.day/Maildir/.Trash/dovecot.index.log.2: marked corrupted Dec 7 14:19:26 locallog@tg3/tg3 dovecot: IMAP(peter.day(a)mydomain.com): Corrupted transaction log file /home/virtual/mydomain.com/home/peter.day/Maildir/.Trash/dovecot.index.log: Append with UID 50, but next_uid = 15870 Causing Peter Day not to be able to delete emails. Seems mostly to happen in the Trash I think. Shouldn't Dovecot be able to recover from this? And then have some rule that if it cannot recover, delete the index file and rebuild? When I manually remove the file it works fine. Thanks, Daniel

3 4

[Dovecot] open files
by Steve Heaven 07 Dec '07

07 Dec '07

This morning dovecot stopped allowing pop3 logins. In the logs I found the messages below Is there a config value for the max open files ? Dec 7 10:00:22 frigga dovecot: execv(/usr/local/libexec/dovecot/pop3) failed: Too many open files Dec 7 10:01:14 frigga dovecot: pipe() failed: Too many open files Dec 7 10:03:40 frigga dovecot: pipe() failed: Too many open files Dec 7 10:03:40 frigga dovecot: pipe() failed: Too many open files Dec 7 10:03:40 frigga dovecot: pipe() failed: Too many open files Dec 7 10:03:40 frigga dovecot: pipe() failed: Too many open files Dec 7 10:03:43 frigga dovecot: pipe() failed: Too many open files Dec 7 10:03:45 frigga dovecot: pipe() failed: Too many open files Dec 7 10:04:39 frigga dovecot: pipe() failed: Too many open files Dec 7 10:04:41 frigga dovecot: pipe() failed: Too many open files Dec 7 10:04:50 frigga dovecot: pipe() failed: Too many open files Dec 7 10:05:00 frigga dovecot: pipe() failed: Too many open files Dec 7 10:05:02 frigga dovecot: pipe() failed: Too many open files Dec 7 10:06:05 frigga dovecot: pipe() failed: Too many open files Dec 7 10:06:05 frigga dovecot: pipe() failed: Too many open files Dec 7 10:06:05 frigga dovecot: pipe() failed: Too many open files Dec 7 10:06:06 frigga dovecot: pipe() failed: Too many open files Dec 7 10:07:48 frigga dovecot: pipe() failed: Too many open files Dec 7 10:08:05 frigga dovecot: pipe() failed: Too many open files

3 5

[Dovecot] imap crash with fts squat enabled.
by Joe Wong 07 Dec '07

07 Dec '07

Hi Timo, Here is the backtrace for your reference. I have already applied dovecot-97702c9c4111 changes to my 1.1 beta10 code base. I am running dovecot on FC7, gcc 4.1.2, mailbox is on NFS. Whenever I did UID SEARCH body "xxxx" imap crashes. Program terminated with signal 6, Aborted. #0 0x00110402 in __kernel_vsyscall () (gdb) bt full #0 0x00110402 in __kernel_vsyscall () No symbol table info available. #1 0x00790fa0 in raise () from /lib/libc.so.6 No symbol table info available. #2 0x007928b1 in abort () from /lib/libc.so.6 No symbol table info available. #3 0x080ca029 in i_internal_fatal_handler (type=LOG_TYPE_PANIC, status=0, fmt=0x80ebb5c "Leaked a t_pop() call in timeout handler %p", args=0xbf8538b4 "\005\b\226\225~") at failures.c:424 backtrace = 0xa0e1168 "imap [0x80ca020] -> imap [0x80c9f2c] -> imap(io_loop_handle_timeouts+0x1b7) [0x80d0bc7] -> imap(io_loop_handler_run+0x69) [0x80d1309] -> imap(io_loop_run+0x28) [0x80d09f8] -> imap(main+0x4ac) [0x8066c"... #4 0x080c9f2c in i_panic (format=0x80ebb5c "Leaked a t_pop() call in timeout handler %p") at failures.c:197 args = 0xbf8538b4 "\005\b\226\225~" #5 0x080d0bc7 in io_loop_handle_timeouts (ioloop=0xa0e99b0, update_run_now=true) at ioloop.c:268 diff = <value optimized out> called_timeouts = (struct timeout *) 0x0 tv = {tv_sec = 8579595, tv_usec = 323093} t_id = 2 #6 0x080d1309 in io_loop_handler_run (ioloop=0xa0e99b0) at ioloop-poll.c:159 ctx = (struct ioloop_handler_context *) 0xa0e99f0 pollfd = <value optimized out> tv = {tv_sec = 0, tv_usec = 0} io = <value optimized out> t_id = <value optimized out> msecs = <value optimized out> ret = 0 call = <value optimized out> #7 0x080d09f8 in io_loop_run (ioloop=0xa0e99b0) at ioloop.c:305 No locals. #8 0x08066c2c in main (argc=Cannot access memory at address 0x5dd2 ) at main.c:293 -- And dovecot.conf: # 1.1.beta10: /usr/local/etc/dovecot.conf log_path: /var/log/dovecot-1.1.log info_log_path: /var/log/dovecot-1.1.log protocols: imap ssl_disable: yes login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_user: nobody verbose_proctitle: yes mail_location: maildir:~/Maildir mail_debug: yes mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: yes mail_drop_priv_before_exec: yes mail_plugins: fts fts_squat mail_log_max_lines_per_sec: 100 auth default: user: mdrop username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@: username_translation: @: verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /usr/local/etc/dovecot-sql.conf userdb: driver: sql args: /usr/local/etc/dovecot-sql.conf plugin: fts: squat

2 4

[Dovecot] Mails "get lost" - RHEL 5.1 - dovecot-1.0-1.2.rc15.el5
by Götz Reinicke 07 Dec '07

07 Dec '07

Hi, we do have a Voiceboxserver which forward recorded avi messages to the mailserver account of users. I'v tested it for my account 10 minutes ago and everything works. Some users don't get the messages shown up in there mailclient while the logs show a delivery of that mail. May be some mail caches are messed up? We use Thunderbird 2 and the users concerned use imap. Where may I look or what may I check? Thanks for your help! Regards Götz -- Götz Reinicke IT Koordinator Tel. +49 7141 969 420 Fax +49 7141 969 55 420 E-Mail goetz.reinicke(a)filmakademie.de Filmakademie Baden-Württemberg GmbH Mathildenstr. 20 71638 Ludwigsburg www.filmakademie.de Eintragung Amtsgericht Stuttgart HRB 205016 Vorsitzender des Aufsichtsrats: Dr. Christoph Palmer, MdL, Minister a.D. Geschäftsführer: Prof. Thomas Schadt

2 2

[Dovecot] Sieve MySQL integration
by Steven Murphy 07 Dec '07

07 Dec '07

I have dovecot running with sieve performing vacation autoreply. Can sieve do sql lookups for vacation messages instead of having to do flat files in the users home directory? Thank you in advance. Steve

4 3

[Dovecot] exim/kmail vs. dovecot
by Kristian Koehntopp 07 Dec '07

07 Dec '07

I am using exim via dovecot_deliver to store messages in Maildir in my $HOME. I am using kmail to retrieve stuff. Unfortunately, something in my data crashes dovecot. I was using 1.0.rc14 from opensuse, but downloaded and installed 1.0.8 from the site. Here is the crash: Dec 5 18:05:09 h743107 dovecot: IMAP(kris): file mail-index-transaction.c: line 629 (mail_index_update_flags_range): assertion failed: (seq1 <= seq2 && seq1 > 0) Dec 5 18:05:09 h743107 dovecot: child 13896 (imap) killed with signal 6 Dec 5 18:05:09 h743107 dovecot: IMAP(kris): Raw backtrace: imap [0x8006cf7d] -> imap [0x8006ce58] -> imap(mail_index_update_flags_range+0x194) [0x8004d034] -> imap(mail_index_sync_begin+0x5c9) [0x8004fb79] -> imap(maildir_sync_index_begin+0x61) [0x80021c71] -> imap [0x8002350a] -> imap(maildir_storage_sync_init+0x56) [0x80023646] -> imap(mailbox_sync_init+0x16) [0x8005d566] -> imap(imap_sync_nonselected+0x28) [0x8001b838] -> imap(_cmd_select_full+0xd7) [0x80012c47] -> imap(cmd_select+0x25) [0x80012e25] -> imap [0x800143ea] -> imap[0x8001446c] -> imap(_client_input+0x7d) [0x80014bcd] ->imap(io_loop_handler_run+0x127) [0x80073987]-> imap(io_loop_run+0x28) [0x80072ac8] -> imap(main+0x518) [0x8001d898] -> /lib/libc.so.6(__libc_start_main+0xdc) [0xb7e8d02c] -> imap[0x8000f0c1] I took the liberty to syslog() the seq numbers before the assert and indeed h743107:/etc/dovecot # grep "imap: seq1" /var/log/messages | head -3 Dec 5 18:30:18 h743107 imap: seq1 1 seq2 1 Dec 5 18:30:18 h743107 imap: seq1 1 seq2 1 Dec 5 18:30:18 h743107 imap: seq1 1 seq2 1 h743107:/etc/dovecot # grep "imap: seq1" /var/log/messages | awk '($9 < $7) { print }' Dec 5 18:30:42 h743107 imap: seq1 28 seq2 16 Dec 5 18:32:43 h743107 imap: seq1 28 seq2 16 What exactly is broken here and how can I fix that? Kris -- Kristian =?iso-8859-15?q?K=F6hntopp?= <kris(a)xn--khntopp-90a.de>

3 3

[Dovecot] Compiling with SQL support
by Mark Smith 07 Dec '07

07 Dec '07

Hello all, I am currently having a slight problem (ok well more likely me just not doing it right), with compiling Dovecot with MySQL support. The version is 1.0.8. I have tried running configure with --with-sql and --with-sql-drivers, but this however still does not compile MySQL support, I do no wish to install MySQL on this server, as I am using a network SQL server, but I do have the compiled source available on this server. I have tried running: gcc -shared -fPIC -DHAVE_CONFIG_H -DBUILD_MYSQL \ -I../.. -I../lib -I../lib-settings -I/data/mysql/include/mysql \ driver-mysql.c -o driver_mysql.so -lmysqlclient inside the /src/lib-sql, but this just returns an error that mysqlclient cannot be found. I have tried running dovecot --build-options, but MySQL is not listed here, the operating system is FreeBSD 6.2. The documentation does not seem to be giving any hints as to why this is not working, nor do How Tos. Any help would be appreciated. Mark Smith

1 0