- dovecot - dovecot.org

[Dovecot] BUG (and suggested fix) in maildir code
by Tom Vajzovic 08 Aug '07

08 Aug '07

Hi all I'm using dovecot 1.0.rc15 to serve a maildir by IMAP. I have an IMAP subdirectory called subscriptions. The messages are in maidir/.subscriptions/cur/ etc. Dovecot is renaming the directory .subscriptions/ to subscriptions/ This means that when my IMAP client requests this directory, it gets the message "no such directory", and dovecot also gives the error message: dovecot: IMAP(tcv): read() failed with subscription file /var/mail/maildir/tcv/subscriptions: Is a directory The two should be able to live happily side by side, with the subscriptions file called "subscriptions" and the maildir called ".subsciptions". The offending function is maildir_subscriptions_convert_099() in src/lib-storage/index/maildir/maildir-storage.c Can someone with developer access please change this so that rename() is not called if subscriptions is a directory. Thanks, Tom

3 3

[Dovecot] dovecot.conf an <TAB> chars
by Sascha Holzleiter 08 Aug '07

08 Aug '07

Hi, I just wanted to "beautify" my dovecot configuration file and as one of the first comments suggests whitespaces and <TAB> should be completly ignored but that doesn't seem to be the case, e.g.: postmaster_address<TAB>= some(a)address.de results in an configuration error as the postmaster_address is not set. Using just a space or replacing the <TAB> char with space chars resolves the problem. This is with dovecot version 1.0.3 on Debian and FreeBSD. Greetings, Sascha

2 1

[Dovecot] Dovecot 1.1alpha2 - (imap) killed with signal 10
by Luca Corti 08 Aug '07

08 Aug '07

As promised, here is the bug report: # dovecot -n # 1.1.alpha2: /usr/local/etc/dovecot.conf protocols: imap pop3 ssl_cert_file: /etc/postfix/server.pem ssl_key_file: /etc/postfix/server.pem login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login mail_location: maildir:/mnt/shared/mail/%u:INDEX=/var/indexes/%u mail_drop_priv_before_exec: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 auth default: passdb: driver: pam passdb: driver: passwd userdb: driver: passwd socket: type: listen client: path: /usr/local/var/run/dovecot/auth-client mode: 436 master: path: /usr/local/var/run/dovecot/auth-master mode: 384 user: root group: dovecot #uname -a Linux ns2 2.6.21-2-sparc64 #1 Thu Jul 12 12:33:00 UTC 2007 sparc64 GNU/Linux # cat /etc/debian_version lenny/sid Mailstore is NFS mounted, indexes on local disk. I'm upgrading from dovecot 1.0.3, the client is Evolution. When accessing any directory besides Inbox I get temporary failure and in the logs I see Aug 8 01:23:39 ns2 dovecot: child 25167 (imap) killed with signal 10 here is a bt full of the core dump: GNU gdb 6.4.90-debian Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "sparc-linux-gnu"...Using host libthread_db library "/lib/libthread_db.so.1". Reading symbols from /lib/libdl.so.2...done. Loaded symbols for /lib/libdl.so.2 Reading symbols from /lib/libc.so.6...done. Loaded symbols for /lib/libc.so.6 Reading symbols from /lib/ld-linux.so.2...done. Loaded symbols for /lib/ld-linux.so.2 Core was generated by `imap'. Program terminated with signal 10, Bus error. #0 mailbox_list_index_sync_write_dir (ctx=0xf75e8, sync_dir=0xf7650, offset_pos=<value optimized out>, partial=true) at mailbox-list-index-sync.c:594 594 new_dir->count = nondeleted_count; (gdb) bt full #0 mailbox_list_index_sync_write_dir (ctx=0xf75e8, sync_dir=0xf7650, offset_pos=<value optimized out>, partial=true) at mailbox-list-index-sync.c:594 dir = <value optimized out> recs = <value optimized out> i = <value optimized out> j = <value optimized out> count = <value optimized out> __PRETTY_FUNCTION__ = "mailbox_list_index_sync_write_dir" #1 0x0007afdc in mailbox_list_index_sync_write (ctx=0xf75e8) at mailbox-list-index-sync.c:867 ret = <value optimized out> #2 0x0007b270 in mailbox_list_index_sync_commit (_ctx=<value optimized out>) at mailbox-list-index-sync.c:918 ctx = (struct mailbox_list_index_sync_ctx *) 0xf75e8 ret = 0 #3 0x00034384 in index_list_sync_deinit (ctx=0xe13f0, status_items=0, status_r=<value optimized out>) at index-mailbox-list-sync.c:204 box = (struct mailbox *) 0xe0b98 list = <value optimized out> ilist = <value optimized out> view = <value optimized out> tmp_status = {messages = 247, recent = 0, unseen = 0, uidvalidity = 1179084420, uidnext = 248, first_unseen_seq = 0, keywords = 0x0} status = (struct mailbox_status *) 0xffb3d594 uid = <value optimized out> seq = <value optimized out> #4 0x0007f57c in mailbox_sync_deinit (_ctx=0xffb3d6b4, status_items=0, status_r=0x0) at mail-storage.c:509 ctx = (struct mailbox_sync_context *) 0x0 #5 0x0002f078 in imap_sync_nonselected (box=0xe0b98, flags=<value optimized out>) at imap-sync.c:210 ctx = (struct mailbox_sync_context *) 0x0 sync_rec = {seq1 = 4289976032, seq2 = 634052, type = 4289976088} #6 0x0002745c in _cmd_select_full (cmd=0xd9338, readonly=false) at cmd-select.c:39 client = (struct client *) 0xd7840 storage = (struct mail_storage *) 0xd5de0 box = (struct mailbox *) 0xe0b98 status = {messages = 666088, recent = 836034, unseen = 1, uidvalidity = 585071112, uidnext = 4160102400, first_unseen_seq = 836008, keywords = 0x1e} mailbox = 0xdc640 "Archivio.storico.2003" #7 0x000275f8 in cmd_select (cmd=0xd9338) at cmd-select.c:93 No locals. #8 0x00028be0 in client_command_input (cmd=0xd9338) at client.c:491 client = (struct client *) 0xd7840 __PRETTY_FUNCTION__ = "client_command_input" #9 0x00028cd0 in client_command_input (cmd=0xd9338) at client.c:548 command = <value optimized out> client = (struct client *) 0xd7840 __PRETTY_FUNCTION__ = "client_command_input" #10 0x00029348 in _client_input (client=0xd7840) at client.c:584 cmd = <value optimized out> __PRETTY_FUNCTION__ = "_client_input" #11 0x00095f10 in io_loop_handler_run (ioloop=<value optimized out>) at ioloop-epoll.c:201 ctx = <value optimized out> event = (const struct epoll_event *) 0xd4a30 list = (struct io_list *) 0xd78a8 io = (struct io_file *) 0xd7490 tv = {tv_sec = 9, tv_usec = 945402} events_count = <value optimized out> t_id = 2 msecs = <value optimized out> ret = 1 i = 0 call = <value optimized out> #12 0x00095184 in io_loop_run (ioloop=0xd49b0) at ioloop.c:303 No locals. #13 0x000311b0 in main (argc=<value optimized out>, argv=0xcc030, envp=0x0) at main.c:299 No locals.

2 1

[Dovecot] OpenBSD and too many open files
by Bryan Vyhmeister 07 Aug '07

07 Aug '07

I posted some questions a few months back and received lots of great help in getting my dovecot/postfix/LDAP setup working. Initially, I ran into the pipe failed too many open files error. I am running this setup on OpenBSD/sparc64 4.1-stable and so I put dovecot in its own class and upped the maxfiles setting for that class. This was back with dovecot 1.0 and everything worked fine. I just recently upgraded to dovecot 1.0.2 from ports and now I am having the same problems again. I moved kern.maxfiles for that class from 2048 up to 3404 and yet I still run into the error. When I do, I have to restart dovecot to get things running again. Output of: su -c dovecot root -c 'ulimit -a' time(cpu-seconds) unlimited file(blocks) unlimited coredump(blocks) unlimited data(kbytes) 1048576 stack(kbytes) 8192 lockedmem(kbytes) 634482 memory(kbytes) 1898080 nofiles(descriptors) 3404 processes 1044 sysctl kern.maxfiles gives: kern.maxfiles=3404 My main IMAP accounts reside on this server and I have somewhere in the 25000 range of stored messages. Could this be causing the issue? I only have maybe a dozen other users using this server right now but I am planning on putting 500 users on it soon. I added another heavy IMAP user shortly before these problems started but I don't know if that has anything to do with it or not. Likewise, I am not sure if the dovecot 1.0.2 upgrade had any effect either although it did coincide. Any ideas? Thank you. Bryan

4 15

Re: [Dovecot] OpenBSD and too many open files
by Bryan Vyhmeister 07 Aug '07

07 Aug '07

On Aug 7, 2007, at 10:29 AM, Quentin Garnier wrote: >> Well, I have not had a single instance of the "Too many files" error >> since. Everything is working smoothly. I'll see about getting the >> patch into OpenBSD if possible. I'll get that tutorial done as well. > > I'll send a mail to bugs(a)openbsd.org with the patch. Sounds great. Thank you. Bryan

1 0

[Dovecot] vfile ACL's
by Benjamin R. Haskell 07 Aug '07

07 Aug '07

(Sorry for the impatience. This was one of several questions in my email from yesterday. I thought I might have better luck being more direct.) Is there a way to set ACL's, using the vfile backend, on a truly global basis? or hierarchically (i.e. .Maildir.Sub inherits from .Maildir)? The wiki page says: "The default ACLs for mailboxes is to give owner all permissions and other users none. Mailboxes in public namespaces don't have owners, so by default no-one can access them." Is this configurable? Thanks, Ben

2 2

[Dovecot] Best way to change PACKAGE_STRING & VERSION_STRING
by David Favor 07 Aug '07

07 Aug '07

Let me know the best way to change the source tree to add in a time to be output from 'dovecot --version'. I've tried the following with no success: mkdir -p /build/work/dovecot-1.1alpha2 cd /build/work/dovecot-1.1alpha2 export LDFLAGS='-L/common/pkgs/sqlite-3.4.1.1/lib64 -R/common/pkgs/sqlite-3.4.1.1/lib64' export PACKAGE_STRING='dovecot 1.1alpha2-2007-08-07' export PACKAGE_VERSION='1.1alpha2-2007-08-07' export CPPFLAGS='-pipe -O2 -I/common/pkgs/sqlite-3.4.1.1/include' unset CDPATH make distclean ./configure --prefix=/common/pkgs/dovecot-1.1alpha2 --disable-nls --disable-ipv6 --with-db --with-sql=plugin --with-sqlite --with-mysql --with-postgresql --with-ssl=openssl --with-ssldir=/etc/pki/dovecot --with-notify=inotify --with-ioloop=epoll --without-vpopmail --with-ldap=plugin --without-gssapi make -e make check rm -rf /common/pkgs/dovecot-1.1alpha2 make install Thanks. -- Like feeling your best ever, all day, every day? Email join(a)RadicalHealth.com for the easy way.

2 1

[Dovecot] Latest 1.1 tree build failure
by David Favor 07 Aug '07

07 Aug '07

Suggestions of how to fix this? mkdir -p /build/work/dovecot-1.1-alpha1 cd /build/work/dovecot-1.1-alpha1 export LDFLAGS='-L/common/pkgs/sqlite-3.4.1.1/lib64 -R/common/pkgs/sqlite-3.4.1.1/lib64' export CPPFLAGS='-pipe -O2 -I/common/pkgs/sqlite-3.4.1.1/include' unset CDPATH make distclean ./configure --prefix=/common/pkgs/dovecot-1.1-alpha1 --disable-nls --disable-ipv6 --with-db --with-sql=plugin --with-sqlite --with-mysql --with-postgresql --with-ssl=openssl --with-ssldir=/etc/pki/dovecot --with-notify=inotify --with-ioloop=epoll --without-vpopmail --with-ldap=plugin --without-gssapi make ... ... ... mv -f .deps/auth-master-listener.Tpo .deps/auth-master-listener.Po make[3]: *** No rule to make target `auth-module.o', needed by `dovecot-auth'. Stop. make[3]: Leaving directory `/build/work/dovecot-1.1-alpha1/src/auth' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/build/work/dovecot-1.1-alpha1/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/build/work/dovecot-1.1-alpha1' make: *** [all] Error 2 exp=0, got ec=2, abort=1 -- Like feeling your best ever, all day, every day? Email join(a)RadicalHealth.com for the easy way.

2 2

[Dovecot] dovecot + LDAP-SASL ?
by Hadmut Danisch 07 Aug '07

07 Aug '07

Hi, just a question: I know that dovecot supports SASL authentication and supports LDAP. Which means that dovecot performs the SASL methods itself and stores the plaintext secret on LDAP. But it is also possible to have the LDAP do the SASL work and dovecot just pass SASL messages through? Even when the LDAP server uses a proprietary SASL method not supported by dovecot? regards Hadmut

3 3

[Dovecot] Ideas for Webmail/OTP
by Frank Behrens 07 Aug '07

07 Aug '07

I want to discuss some problems/enhancements for dovecot in a webmail/otp setup. For access to an IMAP server like dovecot I see different client types: a) a "normal" MUA installed in a more or less trusted environment b) remote access via "webmail" from untrusted environments For a) I see with dovecot and other IMAP servers no problems, tricky is the setup for b). If you use a webmail client in an untrusted environment the risk is high, that keyloggers and other malware steal your password. One easy solution is to use One-Time-Passwords (OTP). The otp setup for interactive logins (e.g. ssh) is easy, but until now I did not find any easy to use solution for webmail. The main problems I see - In most cases a webmail client does not hold a persistent connection to the IMAP server, but makes a login for every request. - The webmail clients are not prepared to display the otp password challenge to the user. When we say "otp" with IMAP we further have to distinguish a) the OTP SASL authentication mechanism b) OTP configured by PAM. I believe a) is implemented in new dovecot 1.1 version, but I prefer b), because - it works with many clients without special client support - all authentication setup is central in the os. All above described problems are not specially linked to dovecot, but I believe with dovecot there is an easy solution to solve them. :-) Solution 1: When PAM is configured for IMAP the user can use a one-time-password in the same way as before. The problem is, that the user must know the sequence number for the password (otp challenge), so we need a way to display it. The PAM module supplies the otp challenge in the conversation function, but the challenge is not processed by the IMAP server. My proposal: The IMAP server stores the challenge from the conversation function and includes it in the LOGIN response, when the login was not successful. So a user can try a login with a wrong dummy password and get knowlegdge about the current otp sequence. The webmail server should be extended in a way, that it displays the complete IMAP error message, when a login fails. Solution 2: Webmail clients do not use persistent connections in most cases. A OTP login needs different passwords for every displayed web page. My proposal: Use dovecot's login cache and do not ask the os for every login. :-) Solution 3: When we configure PAM we can restrict/allow it's use depending on IP address of client. Unfortunately with a webmail client the IMAP client is always the the webserver. It should be possible, that the webserver forwards the client IP address to the IMAP server. Furthermore to use dovecot's login cache as described above in a safe manner, the IP address should be compared, too. My proposal: Create a new IMAP command "XSETREMOTEIP". With this IMAP extension a client can set the real IP address of remote client. The access to this command is restricted to the webserver with a new configuration parameter "trusted clients", which holds an IP address with mask. I ask to discuss these solutions. It seems to work, I'm making the first tests now. I have patches for dovecot and squirrelmail, but they are very "quick and dirty". They show a possible solution, but not a clean implementation. Do you believe, that we can build a good webmail system this way, or do you have better solutions? Regards, Frank -- Frank Behrens, Osterwieck, Germany PGP-key 0x5B7C47ED on public servers available.

7 19