- dovecot - dovecot.org

[Dovecot] Commercial support
by Timo Sirainen 26 Jul '05

26 Jul '05

1.0 release is slowly (but surely :) getting nearer and I'd like to be able to offer commercial support for it for those who want or need it. I have a few different plans for how to do that, but I haven't really decided yet what to do. So I thought I'd ask a few questions here to see how much interest there is currently, which could help me make some decisions sooner. You should probably reply privately to me so this list won't get spammed. So, assume that Dovecot v1.0 will really be stable, will have real documentation, and the support isn't going to be completely in hands of just one or two guys. I think there would basically be two types of support available: 1. Basic support Guaranteed replies to questions within some time interval. - what response times? a few days? - phone support needed? - what would you be willing to pay for it? 2. Mission critical support For those who *really* can't afford any unexpected downtime, and so would be willing to pay more for quick response times. Problems divided to different categories (eg. normal, high, critical) with different response times. - what response times? a few days for normal, about one day for high, less for critical? - sanctions? - customized modifications, kept up-to-date for new Dovecot versions? - what would you be willing to pay for it? I'm not sure if there should be "outsourced email server maintenance" option too. Or maybe some really low cost support for a limited number of questions. Any other ideas, suggestions or tips? Did I miss something important? And finally, would you like to have a job related to Dovecot? :)

2 1

[Dovecot] virtual mailboxes with postfix
by David Cake 26 Jul '05

26 Jul '05

I have set up postfix with virtual mailboxes stored via mysql, and using postfixadmin, and dovecot as pop/imap server My postfix and mysql setup are pretty much standard for postfixadmin, as described here <http://postfixwiki.org/index.php?title=Virtual_Users_and_Domains_with_Couri…> (except for the parts about courier-imap.) Everything appears to be working fine except actually checking and authenticating mail via dovecot. I am fairly sure all I really need is the appropriate incantations in /etc/dovecot/dovecot.conf and dovecot-mysql.conf - does anyone have this set up and working? I should add that I want to allow both virtual mailboxes, and also local accounts, so I presumably need to support two different kinds of authentication. Regards David

2 1

[Dovecot] removing (hopefully) unneeded access to $HOME
by adsmith＠math.duke.edu 25 Jul '05

25 Jul '05

Hi, Thanks for dovecot. It's the best IMAP server ever. Okay, here's my problem: I use mbox INBOXes from /var/spool/mail/%u, and the INDEX lies in /var/spool/mail/dovecot/%d/%u. Users' other folders are found in /%h/mail. Now, I notice that when a user is accessing her INBOX, the imap process cwd's to the user's home, which I'd like to prevent as much as possible. E.g., when the user's client is only watching INBOX, I still see: [root@tock:~]$ lsof | grep home_kt imap 6422 kt cwd DIR 0,17 12288 7602177 /home/kt (other.host:/home/kt) Is there a way I can tweak the dovecot settings so that this cwd isn't holding open the NFS mount? Many thanks, Abe Smith -- # Abraham David Smith, <adsmith(a)math.duke.edu> # # http://fds.duke.edu/db/aas/math/grad/adsmith # # Mathematics Graduate Student, Duke University #

1 1

Re: [Dovecot] pop3 authentication failure - password mismatch
by James Sun 25 Jul '05

25 Jul '05

On 7/22/05, Girish Patangay <girish(a)intoto.com> wrote: > Shouldn't you be using "shadow" instead of passwd for the passdb? > > Just a curious question. > Yes! You are right. "shadow" should work as well. I just give it a try and auth worked! Thanks. However, I am not hitting another problem : no proper permission. If I understand correctly I have set it in dovecot.conf file to use "root" for processing. How come I don't have enough permission? Jul 23 02:26:56 hsiufen dovecot: Dovecot v1.0-stable starting up Jul 23 02:28:10 hsiufen dovecot: pop3-login: Login: jam [24.6.106.170] Jul 23 02:28:10 hsiufen dovecot: POP3(jam): open(/var/mail/.temp.hsiufen.net.15682.f3c4cf83d750e6e4) failed: Permission denied Jul 23 02:28:10 hsiufen dovecot: POP3(jam): file_lock_dotlock() failed with mbox file /var/mail/jam: Permission denied Jul 23 02:28:31 hsiufen dovecot: Killed with signal 2 Any ideas? Jun

3 3

[Dovecot] Re: Bug#319504: Bug in 0.99.14 mbox handling - mail UIDs are renumbered without bumping UIDVALIDITY
by Jaldhar H. Vyas 25 Jul '05

25 Jul '05

On Fri, 22 Jul 2005, David McBride wrote: > Package: dovecot-imapd > Version: 0.99.14-1 > Severity: important > > Hi, > > I think I've identified a bug in Dovecot 0.99.14 as packaged and > distributed by Debian Sarge. I believe the bug lies in the original > Dovecot source, not with any modifications made by Debian. > > Specifically, this bug deals with Dovecot's handling of message unique > identifiers (UIDs) for IMAP clients when using the mbox mailbox storage > format. > David, can you check if the problem persists with 0.99.20050712-1 which is in sid? This is actually the 1.0stable branch of dovecot and has many fixes not included in 0.99.x The package should work correctly on sarge (a proper sarge backport is forthcoming) but you will also need libpq4 from sid and you'll need to make sure dovecot-common is also upgraded to 0.99.20050712-1 also. -- Jaldhar H. Vyas <jaldhar(a)debian.org> La Salle Debain - http://www.braincells.com/debian/

2 1

[Dovecot] dovecot permission denied problems.
by John Mc Donald 25 Jul '05

25 Jul '05

I am trying to setup dovecot on a FC4 machine. Access to the machine is provided through pam. When I login to the machine my home directory is mounted over nfs from a central file server. I have dovecot installed and running but it can't seem to access my home directory. When I try and access my mail I get the following three lines in /var/log/maillog: > Jul 25 12:46:04 escher imap-login: Login: ###### [::ffff:###.###.###.###] > Jul 25 12:46:04 escher dovecot: chdir(/home/######) failed with uid > ####: Permission denied > Jul 25 12:46:04 escher dovecot: child 13182 (imap) returned error 89 The uid that is used is the one associated with my home directory. As far as I understand it when you connect to dovecot the imap connection setuid's to the uid of the authenticated user so there should be no permission problems. To try and help in the debugging process I also setup a local user "testimap" using > /usr/sbin/useradd -d /tmp/testimap testimap I then try to use thunderbird to connect to it and I get the following in /var/log/maillog > Jul 25 12:54:54 escher imap-login: Login: testimap > [::ffff:###.###.###.###] > Jul 25 12:54:54 escher imap(testimap): mbox: Can't create root IMAP > folder /tmp/testimap/mail: Permission denied > Jul 25 12:54:54 escher imap(testimap): MAIL environment missing and > autodetection failed (home /tmp/testimap) > Jul 25 12:54:54 escher dovecot: child 13360 (imap) returned error 89 Can anyone tell me what I am doing wrong here? TIA, John. -- ================================== John Mc Donald, Dept. of Computer Science, National University of Ireland, Maynooth, Co. Kildare, Ireland. Email : johnmcd(a)cs.nuim.ie Tel: +353-1-7084589 Fax: +353-1-7083848 Web: http://www.cs.nuim.ie/~johnmcd GnuPG Key: http://www.cs.nuim.ie/~johnmcd/public_key.asc ==================================

2 2

[Dovecot] inotify support in dovecot
by Reuben Farrelly 25 Jul '05

25 Jul '05

Hi, I note that dovecot supported inotify from -test77, and now the Linux kernel supports it starting from linux-2.6.13-rc3. So in theory I should be set to go. I'm using an -mm kernel, and it was built with inotify, on FC4/devel. However when trying to build with it using --with-notify=inotify, I always seem to be getting this message: checking for poll... yes configure: error: inotify requested but not available, check for existence of <linux/inotify.h> /bin/sh ./config.status --recheck What is required for inotify to be recognised and built into dovecot? I've tried copying the header from linux-2.6/include/linux/inotify.h to the /usr/include/linux directory, but that didn't help - and seems wrong to do anyway. Has anyone else had any experiences with inotify/dovecot? reuben

2 3

[Dovecot] 1.0-test79
by Timo Sirainen 25 Jul '05

25 Jul '05

http://dovecot.org/test/ Now checks that field alignmentations are in indexes as they're expected. test78 crashed if it was wrong, earlier versions ignored the problem (and crashed with 64bit systems). Now if it's wrong, it prints error to log file and recreates the index. That means you probably should delete all dovecot.index files to avoid tons of errors in log files. Only mbox users need to do this. - LSUB: Don't crash if .subscriptions file can't be opened. Also in general give proper "permission denied" error if LIST/LSUB failed because of permission problems. - Maildir: Fix deadlocking when saving messages (noticeable with copying lots of messages with Thunderbird) - LDAP: user_global_uid/gid wasn't working. Also now they support having user/group names from /etc/passwd instead of just numbers. - passwd-file now supports variables in filename, so you can do eg. args = /etc/passwd.%d - Open/close PAM session if -session option is given. Patch by Pasi Sjöholm. - Added tb-extra-mailbox-sep workaround for Thunderbird+mbox problems.

6 9

[Dovecot] dovecot 1.0-stable (050721) rpm for FC3
by James Sun 25 Jul '05

25 Jul '05

OK, thanks for the all the helps I got from the list. I finally managed to get stable 1.0 (050721) built and running. To avoid the same hassels for others, I made an rpm. You can check it out at http://linux.junsun.net/rpms My main motivation to upgrade to this version is to avoid the "Status: O" header re-write bug in 0.99 versions. Cheers. Jun

1 0

[Dovecot] ssl_cipher_list
by Robert Allerstorfer 24 Jul '05

24 Jul '05

Hi, I have noticed the 'ssl_cipher_list' directive in the 1.0-test snapshots which is not in 0.99. It's default value seems to be "all:!low". However, this would not be compatible with openssl's cipher listing format. Thus, I would vote to change it's format to be openssl compatible. To be compatible, it has to be changed to "ALL:!LOW" (just upercased in this case). IMO, this would be helpful because executing openssl ciphers -v 'all:!low' would not return any cipher, but openssl ciphers -v 'ALL:!LOW' would return the expected cipher list such as ADH-AES256-SHA SSLv3 Kx=DH Au=None Enc=AES(256) Mac=SHA1 DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 DHE-DSS-AES256-SHA SSLv3 Kx=DH Au=DSS Enc=AES(256) Mac=SHA1 AES256-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA1 ADH-AES128-SHA SSLv3 Kx=DH Au=None Enc=AES(128) Mac=SHA1 DHE-RSA-AES128-SHA SSLv3 Kx=DH Au=RSA Enc=AES(128) Mac=SHA1 DHE-DSS-AES128-SHA SSLv3 Kx=DH Au=DSS Enc=AES(128) Mac=SHA1 AES128-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(128) Mac=SHA1 DHE-DSS-RC4-SHA SSLv3 Kx=DH Au=DSS Enc=RC4(128) Mac=SHA1 EXP1024-DHE-DSS-RC4-SHA SSLv3 Kx=DH(1024) Au=DSS Enc=RC4(56) Mac=SHA1 export EXP1024-RC4-SHA SSLv3 Kx=RSA(1024) Au=RSA Enc=RC4(56) Mac=SHA1 export EXP1024-DHE-DSS-DES-CBC-SHA SSLv3 Kx=DH(1024) Au=DSS Enc=DES(56) Mac=SHA1 export EXP1024-DES-CBC-SHA SSLv3 Kx=RSA(1024) Au=RSA Enc=DES(56) Mac=SHA1 export EXP1024-RC2-CBC-MD5 SSLv3 Kx=RSA(1024) Au=RSA Enc=RC2(56) Mac=MD5 export EXP1024-RC4-MD5 SSLv3 Kx=RSA(1024) Au=RSA Enc=RC4(56) Mac=MD5 export EXP-KRB5-RC4-MD5 SSLv3 Kx=KRB5 Au=KRB5 Enc=RC4(40) Mac=MD5 export EXP-KRB5-RC2-CBC-MD5 SSLv3 Kx=KRB5 Au=KRB5 Enc=RC2(40) Mac=MD5 export EXP-KRB5-DES-CBC-MD5 SSLv3 Kx=KRB5 Au=KRB5 Enc=DES(40) Mac=MD5 export EXP-KRB5-RC4-SHA SSLv3 Kx=KRB5 Au=KRB5 Enc=RC4(40) Mac=SHA1 export EXP-KRB5-RC2-CBC-SHA SSLv3 Kx=KRB5 Au=KRB5 Enc=RC2(40) Mac=SHA1 export EXP-KRB5-DES-CBC-SHA SSLv3 Kx=KRB5 Au=KRB5 Enc=DES(40) Mac=SHA1 export KRB5-RC4-MD5 SSLv3 Kx=KRB5 Au=KRB5 Enc=RC4(128) Mac=MD5 KRB5-DES-CBC3-MD5 SSLv3 Kx=KRB5 Au=KRB5 Enc=3DES(168) Mac=MD5 KRB5-RC4-SHA SSLv3 Kx=KRB5 Au=KRB5 Enc=RC4(128) Mac=SHA1 KRB5-DES-CBC3-SHA SSLv3 Kx=KRB5 Au=KRB5 Enc=3DES(168) Mac=SHA1 EDH-RSA-DES-CBC3-SHA SSLv3 Kx=DH Au=RSA Enc=3DES(168) Mac=SHA1 EXP-EDH-RSA-DES-CBC-SHA SSLv3 Kx=DH(512) Au=RSA Enc=DES(40) Mac=SHA1 export EDH-DSS-DES-CBC3-SHA SSLv3 Kx=DH Au=DSS Enc=3DES(168) Mac=SHA1 EXP-EDH-DSS-DES-CBC-SHA SSLv3 Kx=DH(512) Au=DSS Enc=DES(40) Mac=SHA1 export DES-CBC3-SHA SSLv3 Kx=RSA Au=RSA Enc=3DES(168) Mac=SHA1 EXP-DES-CBC-SHA SSLv3 Kx=RSA(512) Au=RSA Enc=DES(40) Mac=SHA1 export EXP-RC2-CBC-MD5 SSLv3 Kx=RSA(512) Au=RSA Enc=RC2(40) Mac=MD5 export RC4-SHA SSLv3 Kx=RSA Au=RSA Enc=RC4(128) Mac=SHA1 RC4-MD5 SSLv3 Kx=RSA Au=RSA Enc=RC4(128) Mac=MD5 EXP-RC4-MD5 SSLv3 Kx=RSA(512) Au=RSA Enc=RC4(40) Mac=MD5 export ADH-DES-CBC3-SHA SSLv3 Kx=DH Au=None Enc=3DES(168) Mac=SHA1 EXP-ADH-DES-CBC-SHA SSLv3 Kx=DH(512) Au=None Enc=DES(40) Mac=SHA1 export ADH-RC4-MD5 SSLv3 Kx=DH Au=None Enc=RC4(128) Mac=MD5 EXP-ADH-RC4-MD5 SSLv3 Kx=DH(512) Au=None Enc=RC4(40) Mac=MD5 export DES-CBC3-MD5 SSLv2 Kx=RSA Au=RSA Enc=3DES(168) Mac=MD5 RC2-CBC-MD5 SSLv2 Kx=RSA Au=RSA Enc=RC2(128) Mac=MD5 EXP-RC2-CBC-MD5 SSLv2 Kx=RSA(512) Au=RSA Enc=RC2(40) Mac=MD5 export RC4-MD5 SSLv2 Kx=RSA Au=RSA Enc=RC4(128) Mac=MD5 EXP-RC4-MD5 SSLv2 Kx=RSA(512) Au=RSA Enc=RC4(40) Mac=MD5 export I want dovecot to only accept high encrypted ciphers, thus it should support ssl_cipher_list = ALL:!ADH!LOW:!SSLv2:!EXP:+HIGH:+MEDIUM corresponding to a openssl list such as DHE-RSA-AES256-SHA SSLv3 Kx=DH Au=RSA Enc=AES(256) Mac=SHA1 DHE-DSS-AES256-SHA SSLv3 Kx=DH Au=DSS Enc=AES(256) Mac=SHA1 AES256-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA1 KRB5-DES-CBC3-MD5 SSLv3 Kx=KRB5 Au=KRB5 Enc=3DES(168) Mac=MD5 KRB5-DES-CBC3-SHA SSLv3 Kx=KRB5 Au=KRB5 Enc=3DES(168) Mac=SHA1 EDH-RSA-DES-CBC3-SHA SSLv3 Kx=DH Au=RSA Enc=3DES(168) Mac=SHA1 EDH-DSS-DES-CBC3-SHA SSLv3 Kx=DH Au=DSS Enc=3DES(168) Mac=SHA1 DES-CBC3-SHA SSLv3 Kx=RSA Au=RSA Enc=3DES(168) Mac=SHA1 DHE-RSA-AES128-SHA SSLv3 Kx=DH Au=RSA Enc=AES(128) Mac=SHA1 DHE-DSS-AES128-SHA SSLv3 Kx=DH Au=DSS Enc=AES(128) Mac=SHA1 AES128-SHA SSLv3 Kx=RSA Au=RSA Enc=AES(128) Mac=SHA1 DHE-DSS-RC4-SHA SSLv3 Kx=DH Au=DSS Enc=RC4(128) Mac=SHA1 KRB5-RC4-MD5 SSLv3 Kx=KRB5 Au=KRB5 Enc=RC4(128) Mac=MD5 KRB5-RC4-SHA SSLv3 Kx=KRB5 Au=KRB5 Enc=RC4(128) Mac=SHA1 RC4-SHA SSLv3 Kx=RSA Au=RSA Enc=RC4(128) Mac=SHA1 RC4-MD5 SSLv3 Kx=RSA Au=RSA Enc=RC4(128) Mac=MD5 This would really make "Dovecot (...) written with security primarily in mind" Thanks for consideration! rob.

2 2

[Dovecot] feature or bug on delete?
by Cor Bosman 23 Jul '05

23 Jul '05

RFC 3501 mentions this: The DELETE command MUST NOT remove inferior hierarchical names. For example, if a mailbox "foo" has an inferior "foo.bar" (assuming "." is the hierarchy delimiter character), removing "foo" MUST NOT remove "foo.bar". It is an error to attempt to delete a name that has inferior hierarchical names and also has the \Noselect mailbox name attribute (see the description of the LIST response for more details). It is permitted to delete a name that has inferior hierarchical names and does not have the \Noselect mailbox name attribute. In this case, all messages in that mailbox are removed, and the name will acquire the \Noselect mailbox name attribute. This is what dovecot does: . create foo . OK Create completed. . create foo/bar . OK Create completed. . list "" "*" * LIST (\HasChildren) "/" "foo" * LIST (\HasNoChildren) "/" "foo/bar" . OK List completed. (some other output removed here) . delete foo . OK Delete completed. . list "" "*" * LIST (\HasNoChildren) "/" "foo/bar" . OK List completed. Reading the above section, shouldnt I be seeing a: * LIST (\Noselect \HasChildren) "/" "foo" Regards, Cor

2 2

[Dovecot] Assertion failure in mail-index-transaction.c
by Todd Burroughs 23 Jul '05

23 Jul '05

I just noticed one instance of this in the current CVS version: dovecot: Jul 18 15:25:48 Error: 5962 IMAP(mailuser): mbox sync: Expunged message reappeared in mailbox /mailhome/new/o/h/mailuser/mbox (UID 2834 < 2872) dovecot: Jul 18 15:25:48 Error: 5962 IMAP(mailuser): file mail-index-transaction.c: line 129 (mail_index_buffer_convert_to_uids): assertion failed: (*seq != 0) dovecot: Jul 18 15:25:48 Error: child 5962 (imap) killed with signal 6 (gdb) bt full #0 0xffffe410 in ?? () No symbol table info available. #1 0xbffff438 in ?? () No symbol table info available. #2 0x00000006 in ?? () No symbol table info available. #3 0x0000174a in ?? () No symbol table info available. #4 0xb7ef1d41 in raise () from /lib/tls/libc.so.6 No symbol table info available. #5 0xb7ef3529 in abort () from /lib/tls/libc.so.6 No symbol table info available. #6 0x0809a96a in i_internal_panic_handler ( fmt=0x6 <Address 0x6 out of bounds>, args=0x174a <Address 0x174a out of bounds>) at failures.c:374 No locals. #7 0x0809ad84 in i_panic ( format=0x80a772c "file %s: line %d (%s): assertion failed: (%s)") at failures.c:173 No locals. #8 0x08082711 in mail_index_buffer_convert_to_uids (t=0x80d14b8, array=0x80d14d0, range=1) at mail-index-transaction.c:129 view = (struct mail_index_view *) 0x80cfdc0 rec = Variable "rec" is not available. (gdb) bt #0 0xffffe410 in ?? () #1 0xbffff438 in ?? () #2 0x00000006 in ?? () #3 0x0000174a in ?? () #4 0xb7ef1d41 in raise () from /lib/tls/libc.so.6 #5 0xb7ef3529 in abort () from /lib/tls/libc.so.6 #6 0x0809a96a in i_internal_panic_handler ( fmt=0x6 <Address 0x6 out of bounds>, args=0x174a <Address 0x174a out of bounds>) at failures.c:374 #7 0x0809ad84 in i_panic ( format=0x80a772c "file %s: line %d (%s): assertion failed: (%s)") at failures.c:173 #8 0x08082711 in mail_index_buffer_convert_to_uids (t=0x80d14b8, array=0x80d14d0, range=1) at mail-index-transaction.c:129 #9 0x08083b87 in mail_index_transaction_commit (t=0x80d14b8, log_file_seq_r=0xbffff65c, log_file_offset_r=0xbffff660) at mail-index-transaction.c:183 #10 0x080703f4 in mbox_sync (mbox=0x80c5bc0, flags=Variable "flags" is not available. ) at mbox-sync.c:1623 #11 0x080710c9 in mbox_storage_sync_init (box=0x80c5bc0, flags=MAILBOX_SYNC_FLAG_FULL_READ) at mbox-sync.c:1700 #12 0x0808ef01 in mailbox_sync_init (box=0x0, flags=MAILBOX_SYNC_FLAG_FULL_READ) at mail-storage.c:334 #13 0x0805eb58 in imap_sync_nonselected (box=0x80c5bc0, flags=MAILBOX_SYNC_FLAG_FULL_READ) at imap-sync.c:166 #14 0x080580f6 in _cmd_select_full (cmd=0x80beba8, readonly=0) at cmd-select.c:39 #15 0x08058281 in cmd_select (cmd=0x80beba8) at cmd-select.c:92 #16 0x0805986b in _client_input (context=0x80beb68) at client.c:334 #17 0x0809ff3a in io_loop_handler_run (ioloop=0x80bd9b0) at ioloop-poll.c:184 #18 0x0809f569 in io_loop_run (ioloop=0x80bd9b0) at ioloop.c:218 #19 0x08060657 in main (argc=1, argv=0xbffffa34, envp=0xbffffa3c) at main.c:228 (gdb) p seq $1 = (uint32_t *) 0x80d4d18 (gdb) p *seq $2 = 0 (gdb) p view->map $3 = (struct mail_index_map *) 0x80c5fd0 (gdb) p *view->map $4 = {refcount = 3, hdr = {major_version = 7 '\a', minor_version = 0 '\0', base_header_size = 120, header_size = 200, record_size = 36, compat_data = "\001\b\004", indexid = 1113829460, flags = 0, uid_validity = 1113827022, next_uid = 2872, messages_count = 929, recent_messages_count = 0, seen_messages_count = 810, deleted_messages_count = 0, first_recent_uid_lowwater = 0, first_unseen_uid_lowwater = 1149, first_deleted_uid_lowwater = 2846, log_file_seq = 8, log_file_int_offset = 27912, log_file_ext_offset = 27912, sync_size = 9241460, sync_stamp = 1113863658, day_stamp = 1121659200, day_first_uid = {2855, 2849, 2849, 2753, 2753, 2753, 2491, 187}}, hdr_base = 0x80c60b0, records = 0x80c61d8, records_count = 929, extension_pool = 0x80ce490, extensions = { buffer = 0x80ce4c0, element_size = 28}, ext_id_map = {buffer = 0x80ce588, element_size = 4}, mmap_base = 0x0, mmap_size = 0, mmap_used_size = 0, buffer = 0x80c61b8, hdr_copy_buf = 0x80c6090, keyword_idx_map = { buffer = 0x0, element_size = 0}, write_to_disk = 0} (gdb) p t $5 = (struct mail_index_transaction *) 0x80d14b8 (gdb) p *t $6 = {refcount = 1, view = 0x80cfdc0, appends = {buffer = 0x80d4830, element_size = 8}, first_new_seq = 930, last_new_seq = 953, expunges = { buffer = 0x80d4810, element_size = 8}, updates = {buffer = 0x0, element_size = 0}, last_update_idx = 0, pre_hdr_change = '\0' <repeats 119 times>, pre_hdr_mask = '\0' <repeats 119 times>, post_hdr_change = '\0' <repeats 28 times>, "O\v", '\0' <repeats 89 times>, post_hdr_mask = '\0' <repeats 28 times>, "\001\001\001\001", '\0' <repeats 87 times>, ext_rec_updates = {buffer = 0x80d4750, element_size = 8}, ext_resizes = {buffer = 0x0, element_size = 0}, ext_resets = {buffer = 0x0, element_size = 0}, keyword_updates = {buffer = 0x0, element_size = 0}, keyword_resets = {buffer = 0x80d4730, element_size = 8}, cache_trans_ctx = 0x0, hide_transaction = 0, no_appends = 0, external = 1, pre_hdr_changed = 0, post_hdr_changed = 1, log_updates = 1} (gdb) p j $7 = 2 (gdb) p range $8 = 1

2 1

[Dovecot] pop3 authentication failure - password mismatch
by James Sun 23 Jul '05

23 Jul '05

I tried to run dovecot 1.0 built by myself but encountered the above problem. See the error traces below. First of all, the password and user are correct, as it worked with the 0.99 rpm version of dovecot. I also hand verified with ssh. I also attached the dovecot config file below. Any ideas? Jun fetchmail output on client: ------------------------------------- fetchmail: POP3< +OK Dovecot ready. fetchmail: POP3> CAPA fetchmail: POP3< +OK fetchmail: POP3< CAPA fetchmail: POP3< TOP fetchmail: POP3< USER fetchmail: POP3< UIDL fetchmail: POP3< RESP-CODES fetchmail: POP3< PIPELINING fetchmail: POP3< SASL PLAIN fetchmail: POP3< . fetchmail: POP3> USER jam fetchmail: POP3< +OK fetchmail: POP3> PASS * fetchmail: POP3< -ERR Authentication failed. fetchmail: Authentication failed. maillog on dovecot server: -------------------------------------- Jul 22 18:28:18 hsiufen dovecot: auth(default): passwd(jam,24.6.106.170): password mismatch Jul 22 18:28:19 hsiufen dovecot: pop3-login: Aborted login [24.6.106.170] Jul 22 18:29:32 hsiufen dovecot: Killed with signal 2 dovecot.conf ------------------ protocols = imap imaps pop3 pop3s listen = * ssl_disable = no disable_plaintext_auth = no protocol imap { login_executable = /root/local/encap/dovecot-1.0/libexec/dovecot/imap-login mail_executable = /root/local/encap/dovecot-1.0/libexec/dovecot/imap } protocol pop3 { login_executable = /root/local/encap/dovecot-1.0/libexec/dovecot/pop3-login mail_executable = /root/local/encap/dovecot-1.0/libexec/dovecot/pop3 } auth_executable = /root/local/encap/dovecot-1.0/libexec/dovecot/dovecot-auth auth_verbose = yes auth default { mechanisms = plain passdb = passwd userdb = passwd user = root }

2 3

[Dovecot] Stable Version
by Marc Perkel 22 Jul '05

22 Jul '05

I'm very new to Dovecot - still testing it - and planing to convert in the futire. I see a lot of rapid development here which I like. But I'm wondering if there is any kind of schedule for blessing 1.0 as official - or - what the custom is for a stable release. Just trying to think about when to jump in. I'm fairly brave, but the feature I need we just added today. -- Marc Perkel - marc(a)perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

2 1

[Dovecot] 1.0-test78
by Timo Sirainen 22 Jul '05

22 Jul '05

http://dovecot.org/test/ Fixes: - Crashes in non-x86 64bit systems - Bugs in cache file header caching (you probably should delete all dovecot.index.cache files to be sure the bug won't haunt you in future) - FETCH ENVELOPE patch by Chris Wakelin (I'll try to figure out what to do with the list patch later) Known bugs left: - Thunderbird + maildir: moving lots of messages from mailbox to another may cause deadlock (lock timeouts in half a minute or so and fails the operation). - I guess I should try to look at the Thunderbird + POP3 + lots of messages -> DELE error too again.. - I've heard that 1.0-tests are a lot slower than 0.99.x or 1.0-stable when checking new mail (with kmail), ie. client asking STATUS of all mailboxes. I've looked at their strace outputs and the difference (5-10x slower) comes from 1.0-test waiting longer in poll() for client input, which doesn't really make any sense to me. Can anyone verify this or think of reasons why this could happen? Maybe I'm setting some socket option differently, although I don't think I've changed anything..

8 15

[Dovecot] 1.0-stable and nfs
by Cyril Feraudet 22 Jul '05

22 Jul '05

Hi all, I've a little pb with 1.0-stable on nfs share without lockd : with : - lock_method = dotlock - mmap_disable = yes I've : - dovecot: Jul 22 11:58:33 Error: IMAP(xxxxxxxx): open() failed with index file (null): Bad address with : - lock_method = dotlock - mmap_disable = no I've : - dovecot: Jul 22 11:59:47 Error: IMAP(xxxxxxxx): lock_method=dotlock and mmap_disable=no combination isn't supported. You don't _really_ want it anyway. Someone have an idea ? Thanks, Cyril Feraudet

2 3

[Dovecot] dovecot starts and exit immediately? - help needed
by James Sun 22 Jul '05

22 Jul '05

Since nobody answered my previous question on dovecot marking new mails as old mails, I decided to build a version of dovecot of my own to debug. I downloaded and compiled dovecot 1.0 (stable). After setting up the conf file, I ran dovecot but it exited immediate with status 0. As a result, remote client cannot connect and retrieve mails. There is no man page, and I only found two command line options, -F and -c. None of these options seem to matter. Any suggestions? I must have done something simple and wrong here. Jun

2 4

[Dovecot] Bug in 0.99.14 mbox handling - mail UIDs are renumbered without bumping UIDVALIDITY
by David McBride 22 Jul '05

22 Jul '05

Package: dovecot-imapd Version: 0.99.14-1 Severity: important Hi, I think I've identified a bug in Dovecot 0.99.14 as packaged and distributed by Debian Sarge. I believe the bug lies in the original Dovecot source, not with any modifications made by Debian. Specifically, this bug deals with Dovecot's handling of message unique identifiers (UIDs) for IMAP clients when using the mbox mailbox storage format. Some background for those not familiar with the details; (I had to look a lot of this stuff up; see also http://www.ietf.org/rfc/rfc2060.txt) --- 8< -------------------------------------------------------------- All IMAP servers are required to maintain unique identifiers for each email in an IMAP mailbox that are persistent between sessions. Dovecot stores the unique identifiers for each email in an mbox in an X-UID header. Clients which maintain a local cache of already-retrieved emails use an email's UID as a key; thus, if the UID of a particular email were to change on a server then the client's cached state would be invalid. To cope with the case that the UIDs need to be invalidated, whether because the original store has been lost or for some other reason, there is also the UIDVALIDITY number. This 32bit integer must be increased to some higher value to indicate that any previously cached email ids are now invalid. In Dovecot-managed mbox files, this number is stored in the X-IMAPbase header in the first message of that mbox and is typically the uid-invalidation time expressed in unix timestamp format (ie the number of seconds elapsed since the epoch.) --- 8< -------------------------------------------------------------- Okay, the actual bug: Dovecot routinely (and apparently unneccessarily) renumbers all of the UIDs in our mbox-backed mailboxes without updating the UIDVALIDITY count. This results in caching mail clients (such as Evolution and Thunderbird) presenting the incorrect email to the user when browsing their mail. Configuration: We are using Dovecot as a standalone daemon (ie without using inetd.) We have configured the default mail environment with the following string: default_mail_env = mbox:%h/Mail/:INBOX=%h/.email:INDEX=MEMORY ie each end-user's primary INBOX is an mbox, ~/.email, and other IMAP folders are also stored as mboxes in the directory ~/Mail/. Indexes are maintained in memory but are not stored on disk. I don't think any of the rest of the configuration is relavant, but I'm happy to detail anything else about the setup if needed. Reproducing the bug: I'm afraid I don't have a proper protocol dump demonstrating this bug, so I'm just going to describe all of the end-user steps to recreate the problem: 1) Connect to the Dovecot IMAP service with a caching mail client, such as Evolution or Thunderbird. Download a local copy of the IMAP server contents of a test mbox-backed mailbox to the local cache. For example, I have a test mbox with old root mail. Messages are numbered from 1 to 163. The most recent message has an X-UID: field of 163. 2) Delete one of the messages in the middle of the mailbox. For example, mark the second-oldest message in the mailbox, which has a UID of 2, for deletion. Expunge the mailbox. 3) The UIDs of the other messages at this point have not been altered. Disconnect from the IMAP server. (With Evolution, I actually had to restart the program to reproduce this bug.) 4) Reconnect to the IMAP service, and allow the client to re-sync. You will find that the X-UID of all of the messages after the one that was deleted have been decremented -- and, if you're using a caching client, all of the message *bodies* will appear to have been shifted down by one. Reading the headers in the mbox file directly, Dovecot has renumbered all of the UIDs from 1 to N but not altered the UIDVALIDITY field: dwm@kalimdor $ grep X-UID: Root X-UID: 1 X-UID: 2 [... all numbers between 2 and 161 follow ...] X-UID: 161 X-UID: 162 dwm@kalimdor $ grep X-IMAPbase: Root X-IMAPbase: 1063356421 162 1063356421 == Sept 2003, when the mailbox was first created. This is a bug. Either Dovecot should not renumber the UIDs of each message, or (if it really is necessary), it should increase the UIDVALIDITY field to some higher number to invalidate the caches stored by any remote clients. This bug wasn't observed when using previous versions of Dovecot (we were previously using 0.99.10.6 before this upgrade without noticing anything broken.) I'm hoping someone familiar with the source tree can identify and suggest a fix relatively quickly; failing that, I'll take a look around to see if I can work out where the problem is and implement a fix it myself. Cheers, David -- David McBride <dwm(a)tastycake.net>

1 0

[Dovecot] Changes made to imap descriptor handling in test78?
by Dominic Marks 22 Jul '05

22 Jul '05

Hello, What has changed from test77 to test78 in the way imap manages its descriptors? I upgraded to test78 this morning on a small site which I use as a testbed for testing various things. Running the same copy of my kqueue patch with test77 works quite well [*], with test78 imap has some problems. Here is some debugging output I recorded: Jul 14 12:55:27 egg dovecot: imap-login: Login: user=<dom>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, SSL Jul 14 12:55:30 egg dovecot: IMAP(dom): kqueue was given an unknown descriptor 1, -1: No such file or directory The second line points refers to io_loop_handler_remove, the tcp/ip socket (1) is having the read filter (-1) removed, suspending events from the socket, or at least, that is what should be happening. From kevent(2) for ENOENT: [ENOENT] The event could not be found to be modified or deleted. This suggests to me that we are incorrectly calling io_loop_handler_remove before we should. This error happens immediately after a client opens their mailbox. I have checked pop3 and it does not share the problem. I'm going to have a look at the CVS mail archive to see if I can work out what has changed. [*] Occasionally I was receiving ENOENT in test77 also in io_loop_handler_remove, but only occasionally, perhaps a few times a day for each client. This also didn't occur when opening the mailbox, but some time later. I'm still looking for the trigger for that. Cheers, -- Dominic Marks

2 1

[Dovecot] dovecot pop3s delivers new messages as old (unread) messages ...
by James Sun 22 Jul '05

22 Jul '05

I just set up dovecot on fedora core 3 with only pop3s protocol enabled. On my client machine, I use fetchmail to get the mail and then go through procmail and eventually ready by mutt. Everything seems to work fine, except that all new emails are marked old unread emails (i.e., marked with 'O' flag instead of 'N'). This is annoying because some open source lists are so large that I really rely on the "N" flag to read my emails. I tested the same client setting with gmail and my isp (comcast) pop3 accounts. They work fine - new mails are marked as "N". This makes me suspect dovecot is not set up correctly or something on the pop3 server machine is not right. Anybody has an idea? Thanks in advance. Jun Here are more detailed info: -bash-3.00# rpm -qa | grep dovecot dovecot-0.99.13-3.FC3 /etc/dovecot.conf: ---------------------------- protocols = pop3s imap_listen = [::] pop3_listen = [::] imaps_listen = [::] pop3s_listen = [::] ssl_cert_file = /usr/share/ssl/certs/dovecot.pem ssl_key_file = /usr/share/ssl/private/dovecot.pem login_dir = /var/run/dovecot-login login = imap login = pop3 mbox_locks = fcntl auth = default auth_mechanisms = plain auth_userdb = passwd auth_passdb = pam auth_user = root auth_verbose = no .fetchmailrc on client machine -------------------------------------- poll mypop.server.com protocol pop3 user "jsun" password "xxxx" is jsun here ssl

2 3

[Dovecot] Double Emails
by Matt Juszczak 22 Jul '05

22 Jul '05

Hi all, I originally posted this on postfix's mailing list but then realized that this COULD be a pop3 server problem since that downloads and deletes mail. This has only been happening since I upgraded from .99 to 1.0-7 ... Our users have been reporting double messages in their inbox, as well as emails that they deleted a long time ago reappearing. The only thing in my maillog is a bunch of: mbox sync: UID inserted in the middle of mailbox /home/sdf/mail/Level3 (6293 > 3) Thats happening for IMAP folder and /var/mail/* mbox folders alike. I can't seem to figure out the problem, but we have at least 50 customers calling in today alone to complain about double messages. More are probably experiencing it and just not calling. Any ideas? Thanks! -Matt

3 5

Re: [Dovecot] Update notifier
by Sebastjan Trepca 22 Jul '05

22 Jul '05

Great! Yes, of course, I just didn't knew that plugins are supported. Are there any documents on this subject? How do you add a plugin to dovecot? Just compile it and copy it to dovecot's lib/imap (like in example) ? Thanks, Sebastjan On 7/22/05, Timo Sirainen <tss(a)iki.fi> wrote: > On Fri, 2005-07-22 at 12:08 +0200, Sebastjan Trepca wrote: > > I'm trying to add a code in dovecot that will notify my services when > > a message is updated/added/moved/copied. I checked dovecot code a bit > > and mail-storage.c seems to be a nice place for tracking but I'm not > > sure if I can track all changes there. > > There are no update/move commands in IMAP, so you'll just need to hook > into saving and copying. Normally copying also goes through save unless > you're using maildir + maildir_copy_with_hardlinks=yes. > > See quota plugin for example how to hook into saving and copying: > http://dovecot.org/patches/1.0/quota.tar.gz > > Probably better to do it as a plugin than directly modify the sources, > so you don't have to keep patching it for each new release. > > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.0 (GNU/Linux) > > iD8DBQBC4PdEyUhSUUBViskRApj9AJoCzEM8iNRNaEIcHdGxZDKoSbatFQCfaTMc > 62w52fPQr0uE8wb1A8y9kUY= > =9gtQ > -----END PGP SIGNATURE----- > > >

2 1

[Dovecot] Another minor IMAP LIST issue
by Chris Wakelin 22 Jul '05

22 Jul '05

I've just noticed that Dovecot 1.0-stable and 1.0-test78 don't include mbox folders with names beginning with "." in the IMAP LIST output. These are often used to store "hidden" folders for storing things like IMAP client configuration (e.g. Pine 4.x, IMHO, Prayer). Usually the user shouldn't be able to see these, but there are occassions when they might. It seems to me to be better to let the client decide. As I understand it, the IMAP RFC suggests that if you can "SELECT folderpath" a folder, you should also be able to list it with 'LIST "" "folderpath"' I've written a patch against 1.0-stable (it also works with test78) to add an extra namespace option "showdotfiles" (default "no"), to include folders beginning with "." (but excluding ".imap" and "." and ".." for obvious reasons!). It's used as follows :- # default namespace namespace private { separator = "/" prefix = inbox = yes showdotfiles = yes } # for backwards compatibility with UW-IMAP: namespace private { separator = "/" prefix = "mail/" hidden = yes showdotfiles = yes } ... Let me know if you find it useful! Best Wishes, Chris -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094 diff -ruN dovecot-1.0-stable.orig/src/imap/cmd-list.c dovecot-1.0-stable/src/imap/cmd-list.c --- dovecot-1.0-stable.orig/src/imap/cmd-list.c Fri Mar 18 20:00:44 2005 +++ dovecot-1.0-stable/src/imap/cmd-list.c Wed Jul 20 16:36:51 2005 @@ -293,6 +293,8 @@ list_flags = ctx->list_flags; if (*ns->prefix == '\0' || ns->inbox) list_flags |= MAILBOX_LIST_INBOX; + if (ns->showdotfiles) + list_flags |= MAILBOX_LIST_DOTFILES; ctx->list_ctx = mail_storage_mailbox_list_init(ns->storage, cur_ref, cur_mask, list_flags); diff -ruN dovecot-1.0-stable.orig/src/imap/namespace.c dovecot-1.0-stable/src/imap/namespace.c --- dovecot-1.0-stable.orig/src/imap/namespace.c Mon Jan 31 16:37:54 2005 +++ dovecot-1.0-stable/src/imap/namespace.c Wed Jul 20 16:36:51 2005 @@ -31,7 +31,7 @@ { struct namespace *ns; const char *sep, *type, *prefix; - int inbox, hidden, subscriptions; + int inbox, hidden, showdotfiles, subscriptions; ns = p_new(pool, struct namespace, 1); @@ -40,6 +40,7 @@ prefix = getenv(t_strdup_printf("NAMESPACE_%u_PREFIX", num)); inbox = getenv(t_strdup_printf("NAMESPACE_%u_INBOX", num)) != NULL; hidden = getenv(t_strdup_printf("NAMESPACE_%u_HIDDEN", num)) != NULL; + showdotfiles = getenv(t_strdup_printf("NAMESPACE_%u_SHOWDOTFILES", num)) != NULL; subscriptions = getenv(t_strdup_printf("NAMESPACE_%u_SUBSCRIPTIONS", num)) != NULL; @@ -58,6 +59,7 @@ ns->prefix = p_strdup(pool, prefix); ns->inbox = inbox; ns->hidden = hidden; + ns->showdotfiles = showdotfiles; ns->subscriptions = subscriptions; ns->storage = mail_storage_create_with_data(data, user); if (ns->storage == NULL) { diff -ruN dovecot-1.0-stable.orig/src/imap/namespace.h dovecot-1.0-stable/src/imap/namespace.h --- dovecot-1.0-stable.orig/src/imap/namespace.h Mon Jan 31 16:37:54 2005 +++ dovecot-1.0-stable/src/imap/namespace.h Wed Jul 20 16:36:51 2005 @@ -16,7 +16,7 @@ char *prefix; size_t prefix_len; - int inbox, hidden, subscriptions; + int inbox, hidden, showdotfiles, subscriptions; struct mail_storage *storage; }; diff -ruN dovecot-1.0-stable.orig/src/lib-storage/index/mbox/mbox-list.c dovecot-1.0-stable/src/lib-storage/index/mbox/mbox-list.c --- dovecot-1.0-stable.orig/src/lib-storage/index/mbox/mbox-list.c Mon Jan 31 16:37:55 2005 +++ dovecot-1.0-stable/src/lib-storage/index/mbox/mbox-list.c Wed Jul 20 16:36:51 2005 @@ -225,13 +225,19 @@ enum imap_match_result match, match2; int ret, noselect; - /* skip all hidden files */ - if (fname[0] == '.') + /* skip all hidden files unless show dotfiles is set*/ + if (fname[0] == '.' && !(ctx->flags & MAILBOX_LIST_DOTFILES)) return 0; /* skip all .lock files */ len = strlen(fname); if (len > 5 && strcmp(fname+len-5, ".lock") == 0) + return 0; + + /* skip ".imap" "." and ".." directories in case we show dotfiles */ + if (((len == 5) && strcmp(fname, ".imap") == 0) || + ((len == 1) && fname[0] == '.') || + ((len == 2) && strcmp(fname, "..") == 0)) return 0; /* check the mask */ diff -ruN dovecot-1.0-stable.orig/src/lib-storage/mail-storage.h dovecot-1.0-stable/src/lib-storage/mail-storage.h --- dovecot-1.0-stable.orig/src/lib-storage/mail-storage.h Mon Jan 31 16:37:55 2005 +++ dovecot-1.0-stable/src/lib-storage/mail-storage.h Wed Jul 20 16:36:51 2005 @@ -16,7 +16,8 @@ MAILBOX_LIST_SUBSCRIBED = 0x01, MAILBOX_LIST_FAST_FLAGS = 0x02, MAILBOX_LIST_CHILDREN = 0x04, - MAILBOX_LIST_INBOX = 0x04 + MAILBOX_LIST_INBOX = 0x04, + MAILBOX_LIST_DOTFILES = 0x08 }; enum mailbox_flags { diff -ruN dovecot-1.0-stable.orig/src/master/mail-process.c dovecot-1.0-stable/src/master/mail-process.c --- dovecot-1.0-stable.orig/src/master/mail-process.c Tue Feb 8 10:30:11 2005 +++ dovecot-1.0-stable/src/master/mail-process.c Wed Jul 20 16:36:51 2005 @@ -175,6 +175,8 @@ env_put(t_strdup_printf("NAMESPACE_%u_INBOX=1", i)); if (ns->hidden) env_put(t_strdup_printf("NAMESPACE_%u_HIDDEN=1", i)); + if (ns->showdotfiles) + env_put(t_strdup_printf("NAMESPACE_%u_SHOWDOTFILES=1", i)); t_pop(); } } diff -ruN dovecot-1.0-stable.orig/src/master/master-settings.c dovecot-1.0-stable/src/master/master-settings.c --- dovecot-1.0-stable.orig/src/master/master-settings.c Mon Jan 31 16:37:55 2005 +++ dovecot-1.0-stable/src/master/master-settings.c Wed Jul 20 16:36:51 2005 @@ -194,6 +194,7 @@ DEF(SET_STR, location), DEF(SET_BOOL, inbox), DEF(SET_BOOL, hidden), + DEF(SET_BOOL, showdotfiles), { 0, NULL, 0 } }; diff -ruN dovecot-1.0-stable.orig/src/master/master-settings.h dovecot-1.0-stable/src/master/master-settings.h --- dovecot-1.0-stable.orig/src/master/master-settings.h Mon Jan 31 16:37:55 2005 +++ dovecot-1.0-stable/src/master/master-settings.h Wed Jul 20 16:36:51 2005 @@ -163,6 +163,7 @@ int inbox; int hidden; + int showdotfiles; }; struct server_settings {

3 5

[Dovecot] subscriptions vs mailboxlist
by Marc Perkel 22 Jul '05

22 Jul '05

Is there a way to change the name of the .subscriptions file that dovecot looks for to .mailboxlist to be compatible with WU-IMAP? It would be handy for testing and conversion if you had that. BTW - I'm a new user and your software is very well designed. -- Marc Perkel - marc(a)perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

2 1

[Dovecot] Errors after moving to Maildir from mbox format
by Gabe Granger 22 Jul '05

22 Jul '05

Hi All, Over the weekend I bit the bullet and migrated my entire office from server to another and converted everything from MBOX to Maildir. Althought it took ages and their we're a few little problems along the way, the migration was a complete success with no users reporting any problems(Mbox used to always cause file lock ups) or even noticing anything had changed... Which is great!:) I'm starting to see some issues currently only with my Mail. In the log files I'm getting loads of the following for at lease 20 different emails Jul 19 12:12:27 server imap(Some-user): Error parsing IMAP envelope: "Tue, 27 May 2003 16:33:07 +0100" "Re: 2U rack cases + PSU" (("Some User" NIL "some-user" "somedomain.foo")) (("Some User" NIL "some- user" "somedomain.foo")) (("Some Userr" NIL "some-user" "somedomain.foo")) (("Some User" NIL "some-user" "some-other- domain.foo")) NIL NIL "<000f01c32462$699a7130$7264a8c0@Microtech>" NIL I did a find in my Mail.app on my mac and discovered that although my client can find the message based on Subject, it fails to locate its mailbox/mailfolder when I select the message I get the following response The message from Some User <some=user(a)some-other-domain.foo> concerning “RE: 2U rack cases + PSU” has not been downloaded from the server. You need to take this account online in order to download it. The account is fully online, does or has anyone here come across this error? I'm guessing there is a problem within the email file itself. I'm using ServerSide Debian 3.1 Sendmail 8.13 Dovecot 0.99.14-1 ClientSide OSX 10.4 Mail.app Any help / pointers would be great. Gabe

2 1

[Dovecot] Corrupted indices (and accidental checkin)
by Thomas Wouters 22 Jul '05

22 Jul '05

I've seen a number of corrupted-index problems pop up on our test-dovecot servers (used by a few people at the office), and I'm wondering why corrupt indices don't just automatically get deleted ? Something like: if (!MAIL_INDEX_IS_IN_MEMORY(index)) { unlink(index->filepath); } in src/lib-index/mail-index.c:mail_index_set_error() comes to mind. It seems to me like it should work, anyway. You can still treat the error like it's currently treated (as fatal), but at least it won't pop up the next time you try to perform the same action, or trigger the same corrupted entry another way. By the way, I also noticed what is probably an accidental checkin in src/lib-storage/index/maildir/maildir-storage.c:maildir_get_control_path(), where it tries to migrate control files from the default location to the configured location. I think Timo wrote that patch for my colleage Cor, and then accidentily checked it in with: ---------------------------- revision 1.100 date: 2005-06-09 14:31:43 +0000; author: cras; state: Exp; lines: +22 -4 Replaced ':' and ',' character usages with #defines, so they can be changed easily if needed. The patch is 'broken' anyway; it tries to use rename() to move the old control files to the new location, but that doesn't quite work between different filesystems (and that happens to be what we want to do ;). A better way to handle it would probably be to read in the data from the old location, and then write it out to the new location, in a normal load/save procedure. But I think we'll just do the move manually, after all, as it's just a few dozen different accounts at the moment. I'm not sure about the value of the 'implicit' controlfile migration that dovecot currently does. -- Thomas Wouters <thomas(a)xs4all.net> Hi! I'm a .signature virus! copy me into your .signature file to help me spread!

2 1

[Dovecot] Few questions
by Sebastjan Trepca 22 Jul '05

22 Jul '05

Is there a way to list all keywords a mailbox uses? I fetch flags for all messages and then gorup them, but this is a very nasty solution. What's the situation with full text search? Will it ever be implemented? Is it already? Text search on my 0.99.14 is quite slow. Don't understand why no IMAP server wants to implement this feature. Does Dovecot support plugins? Thank you, Sebastjan

2 3

[Dovecot] CR LF in stable
by Thomas Hummel 22 Jul '05

22 Jul '05

Hello, It seems that mbox format mailboxes holding \r\n (CR + LF) character sequences (instead of \n only) still cause assertion failures when moving messages from one folder to another. -- dovecot: Jul 19 17:14:52 Error: IMAP(dovetest): file istream-raw-mbox.c: line 38 3 (istream_raw_mbox_get_body_size): assertion failed: (rstream->body_offset != ( uoff_t)-1) -- I seems to work in -test78 though. Is there any plan to handle this in -stable branch ? -- Thomas Hummel | Institut Pasteur <hummel(a)pasteur.fr> | Pôle informatique - systèmes et réseau

2 1

[Dovecot] deleting folders containing subfolders with thunderbird (mbox format) bug
by John Bramley 22 Jul '05

22 Jul '05

When using Thunderbird (dovecot-0.99.13-3.FC3) on Fedora connecting to dovecot-0.99.13-3.FC3 I am having problems deleting folders which have been created with the 'Allow your new folder to contain: Folders only' option picked. The folder appears to get deleted but upon restarting Thunderbird the folder still appears to be there but clicking on it I get the error: 'The current command did not succeed. The mailserver responded: Mailbox doesn't exist: <mailbox name>'. Upon investigation when creating and deleting a folder called 'bilbo' to contain subfolders only: Thunderbird sends 'create bilbo/' imap command and then 'subscribe bilbo/' Dovecot creates a directory 'bilbo' and adds 'bilbo/' to the .subscriptions file which all works ok. Upon trying to delete the folder and confirming that it should be deleted Thunderbird sends: 'delete bilbo/' dovecot replies 'OK Delete completed' Then thunderbird sends 'unsubscribe bilbo/' dovecot replies 'NO Invalid mailbox name' which Thunderbird ignores and all seems to have gone ok until thunderbird is restarted and the folder reappears in the folder list but nothing can be done with it. I believe that if a client sends an 'unsubscribe' command to a mailbox that is currently subscribed the imap server should unsubscribe it - even if the actual mailbox doesn't exist (unsubscribe and then delete seems to work when testing using telnet to port 143 to send imap commands). Dovecot does allow mailboxes to be unsubscribed if they don't exist if they don't have a tailing '/' character (so deleting folders set to contain only messages in Thunderbird works ok). I expect that everything works ok using Maildir mailboxes because then there is no need to mark folders containing folders with a '/' because all folders can contain messages and folders. For my own purposes I have hacked the mbox_get_mailbox_name_status function in src/lib-storage/index/mbox/mbox-storage.c to add a check to see if the mailbox name is already subscribed to and if it is then return status = MAILBOX_NAME_EXISTS, before the 'if (!mbox_is_valid_create_name(storage, name))' check which is returning status = MAILBOX_NAME_INVALID, which seems to work ok for me. UW-imap works ok I'm surprised at this bug (or am I doing something completely wrong), surely lots of people use Thunderbird with dovecot, do they not create sub-folders in folders, or are they all using Maildir format, or do they never find the 'Server supports folders that contain sub-folders and messages' advanced option so they are never able to create folders within folders in the first place? John.

2 1

[Dovecot] Failed to create storage with data - possible reasons?
by vmstech 22 Jul '05

22 Jul '05

Hi I'm getting this error with my attempt at setting up dovecot for virtual mail accounts: Failed to create storage with data: /home/vhostpath/usersname/Maildir/ I cant establish any cause. I dont think its permissions as it was saying 'Permission denied' till I fixed that and the UID and GID are those of the directories owner. I was prompted bythe log files to set the minimum and maximum uid range, which made the prompt go away, but I still have this problem. Can anyone tell me what else might cause this error? Thanks glenn

2 2

[Dovecot] Dovecot 0.99.11 config
by nickr 22 Jul '05

22 Jul '05

I am at wits end...So far it seems dovecot is light years ahead of UW-IMAP. Glad to have UW-IMAP behind me...well almost. My setup = Sendmail 8.13.4 with Procmail delivery to /var/spool/mail/<userfile> openssl 0.9.8 dovecot 0.99.11 I want to continue to use the standard mbox with all the user's mail stored in /var/spool/mail/<userfile>. User's are known to this mail server via NIS and ALL data is mounted accress NFS in read only mode on this machine, including ~home directories. I want to run dovecot like UW-IMAP...trying to keep it simple-->mail delivery to mbox /var/spool/mail/<username>. My /etc/dovecot.conf: I tried both default_ mail_env = INBOX:/var/spool/mail/%u:INBOX:INDEX=MEMORY with and with out the INBOX:INDEX=MEMORY I want to disable the indicies feature. We don't need it we're about 20 engineers or so who want to continue to use the /var/spool/mail mbox-the original Sendmail location. Most users are downloading every piece of mail through OutHouse or Pine, aka OutLook. I keep getting failed to create storage meaages in /var/log/maillog... Jul 21 15:53:26 mailtest pop3-login: Login: nickr [::ffff:172.26.64.2] Jul 21 15:53:26 mailtest pop3(nickr): Failed to create storage with data: INBOX:/var/spool/mail/nickr Jul 21 15:53:26 mailtest dovecot: child 4773 (pop3) returned error 89 Permissions info for /var/spool/mail/nickr: drwxrwxrwt 3 root mail 4096 Jul 21 15:43 mail [root@mailtest mail]# ls -la nickr total 4204 drwxrwxrwx 2 nickr mail 4096 Jul 21 15:19 . drwxrwxrwt 3 root mail 4096 Jul 21 15:43 .. -rwxrwxrwx 1 nickr ftp 0 Jul 21 14:56 inbox -rwxrwxrwx 1 nickr mail 2375 Jul 21 15:12 msg.FAUO -rwxrwxrwx 1 nickr mail 4256870 Jul 20 16:55 nickr As you can see I am spoping just fine.... Thanks in advance for ANY help!!!!!!!!!

2 1

[Dovecot] Update notifier
by Sebastjan Trepca 22 Jul '05

22 Jul '05

Hi, I'm trying to add a code in dovecot that will notify my services when a message is updated/added/moved/copied. I checked dovecot code a bit and mail-storage.c seems to be a nice place for tracking but I'm not sure if I can track all changes there. Does anyone have any experience with this topic or ideas? Thanks, Sebastjan

2 1

[Dovecot] passwd-file command doesn't support %d
by Marc Perkel 22 Jul '05

22 Jul '05

Trying this and it doesn't work: passdb = passwd-file /etc/vmail/test.%d Apparently it doesn't expand the %d according to the log file. -- Marc Perkel - marc(a)perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

2 1

[Dovecot] Dovecot vs.Clients - strange behaviour, diagnostics sought
by Jeroen Scheerder 22 Jul '05

22 Jul '05

I've been experimenting with dovecot-1.0-stable on Solaris. Storage format is mbox. Dovecot, in test, runs in parallel with an UW IMAP, with dovecot running SSL-only on port 994. It seems to work to some extent: * dovecot runs * authentication works * SSL works * all manual IMAP functionality checks seem to work fine However, I'm running into issues with IMAP clients. * Null client: I started by using telnet as a client, and talking IMAP manually. Seems OK. * Mutt: "mutt -f imap://my.imap.server:994" seems to work well, although mutt keeps reporting details about the SSL certificate, informs me that it belongs to the proper server and is a valid Globalsign-issued certificate -- and keeps insisting I either reject it or accept it once. * Apple Mail (Panther's version, 1.3.11 (v622)) works, though it seems to have problems with large mailboxes. Then again, it had these same problems with other IMAP servers as well. * Thunderbird doesn't work at all. After some waiting, it bums out and reports: Unable to connect to your IMAP server. You may have exceeded the maximum number of conenctions to this server. If so, use the Advanced IMAP Server Settings dialog to reduce the number of cached connections. Note that it never even shows an authentication dialog, and the only thing I see in dovecot's log that relates to Thunderbirds attempt is: dovecot: Jul 20 09:41:09 Info: imap-login: Disconnected: \ Inactivity [131.211.143.87] I'm at a loss as to what's causing this. On the one hand, dovecot seems operational, on the other hand at least one client can do nothing with it. All debugging/logging options are enabled. What am I missing?

5 8

[Dovecot] bug in dovecot search
by Cor Bosman 22 Jul '05

22 Jul '05

A007 search from phyllis * SEARCH 484 A007 UID SEARCH CHARSET "US-ASCII" ALL FROM {7} phyllis * SEARCH 007 UID SEARCH CHARSET "US-ASCII" ALL FROM "phyllis" * SEARCH Regards, Cor

3 3

Fwd: [Dovecot] Very slow select() command on large mailboxes
by Sebastjan Trepca 22 Jul '05

22 Jul '05

Maildir, its easier to export and can support hardlinks. What kind of optimizations did you have in mind? What's the downside of mbox? Problem is that version 1.0 is only test release for now. On 7/14/05, Timo Sirainen <tss(a)iki.fi> wrote: > > On Thu, 2005-07-14 at 11:59 +0200, Sebastjan Trepca wrote: > > Hi, > > > > I'm trying to decide if I could use you mail server in our enviroment > > which has about 10k users and mailboxes size about ~1GB. > > So I made a few tests and it all worked quite fast, except that select > > command on large mailboxes. The first time I select a mailbox which > > has 10k messages it takes about 4s to process. I am deliberately > > trying this on a Celeron 850Mhz, 512 MB memory and some shitty > > hard-drive to maximize the times. > > So why is this so slow? Does it index the messages on select? It's > > even slower when I have some new messages in folder, more that I have > > more I wait. So I presume it must be something with indexing? Anyway, > > how could I optimize this? Why don't you index when a mail arrives > > instead of on select? > > mbox or maildir? mbox can be optimized in different ways with > 1.0-stable/test releases, but maildir itself needs to be rescanned all > too often.. > > >

2 1

[Dovecot] configuration of user_global_uid and user_global_gid
by KATOH Yasufumi 22 Jul '05

22 Jul '05

Hi. I'm configuring LDAP auth with dovecot (cvs trunk at 14, July) as follows: /etc/dovecot/dovecot.conf: passdb ldap { args = /etc/dovecot/dovecot-ldap.conf } userdb ldap { args = /etc/dovecot/dovecot-ldap.conf } /etc/dovecot/dovecot-ldap.conf: user_attrs = mail,homeDirectory,mailbox,,, user_global_uid = 10000 user_global_gid = 1000 But "user_global_uid" and "user_global_gid" definition does not work. dovecot: Jul 14 11:50:36 Error: auth(default): ldap(test(a)example.jp,127.0.0.1): ui d not in user_attrs and no default given in user_global_uid dovecot: Jul 14 11:50:36 Error: auth(default): ldap(test(a)example.jp,127.0.0.1): gi d not in user_attrs and no default given in user_global_gid How do I configure to enable "user_global_uid" and "user_global_gid"? Does my configuration have any problem? -- karma(a)jazz.email.ne.jp / KATOH Yasufumi

2 1

[Dovecot] Changing port?
by Matt Juszczak 22 Jul '05

22 Jul '05

Hi all, Trying to setup a test copy of dovecot on my box before I "really" use it. I have it installed into a test dir (/usr/local/dovecot instead of /usr/local), and I've got a config file with valid dirs, etc. Only thing is ... I can't find a way to set the port in the protocol pop3 {} section. Its documented in the "listen" directive area at the top of the config file that says its possible, but no other mention of it is ever made. How can I make my test copy listen on port 111? :) Regards, Matt

2 1

[Dovecot] Can't connect to auth server
by Todd Burroughs 22 Jul '05

22 Jul '05

I've been seeing these errors intermittently for a while now. Here's an example from the logs: dovecot: Jul 12 15:59:05 Error: imap-login: Can't connect to auth server at default: Resource temporarily unavailable The error is EAGAIN. Sometimes it will resolve itself after a few minutes and sometimes it needs to be restarted (it may fix itself, I usually get a phone call if it goes on for very long). I've looked while the problem is occuring and dovecot and dovecot-auth don't have an excessive number of file descriptors open, maybe 10 or 20. Any ideas or anything else to look at? The system is SuSE Linux 9.2 running kernel 2.6.x. We have seen some odd things happen with these systems, so it is possible that it is not dovecot. The kernel doesn't log anything unusual and other processes seem happy. Todd

2 1

[Dovecot] test76-77 dies at SIGHUP
by Johan Fredin 22 Jul '05

22 Jul '05

Hello people This is on OpenBSD/sparc64. After chickening along with 0.99 for a while, I finally upgraded to 1.0-test. I started out with test73, which worked fine. With the upgrade to test76, I lost the ability to SIGHUP dovecot when I rotated it's logfile. Dovecot would just die abruptly, not a trace in the log. I just upgraded to test77, but the problem is still there. I've put up my logfile and the last bit of a ktrace here: http://legonet.org/~griffin/tmp/dovecot/ The ktrace is partitial mostly because it contains usernames, I can edit those out and upload the hole shebang if that'll help. I'd appreciate any tips/pointers on this one! /Johan

3 2

[Dovecot] 0.99.14 and nfs
by Cyril Feraudet 22 Jul '05

22 Jul '05

Hi, somebody have an idea to make dovecot working safly with nfs without lockd ? It seems working without problem except for files ".customflags" and ".subscriptions" is exists a patch for use the dotlock locking method for these files ? Thanks, Cyril Feraudet

3 4

[Dovecot] test77, yahoo & fetchmail
by Chris Spiegel 21 Jul '05

21 Jul '05

I've run into a rather narrowly scoped problem .. On test77 and test78, mails from Yahoo's webmail are seen, by fetchmail using imaps, to have a 0-length body. When fetching, it claims "0 body octets". Other mail clients (mutt, kmail) can view the messages fine. pop3s retrieval works as well. Every other email I've received so far works fine. It's just those sent by Yahoo's webmail service that have the problem. imaps retrieval does, however, work fine with test76. Let me know if there's anything I can do to help track this down. Thanks, Chris

2 1

[Dovecot] Re: Dovecot 0.99.11 config
by nickr 21 Jul '05

21 Jul '05

----- Original Message ----- From: nickr To: dovecot(a)dovecot.org Sent: Thursday, July 21, 2005 4:19 PM Subject: Dovecot 0.99.11 config I am at wits end...So far it seems dovecot is light years ahead of UW-IMAP. Glad to have UW-IMAP behind me...well almost. My setup = Sendmail 8.13.4 with Procmail delivery to /var/spool/mail/<userfile> openssl 0.9.8 dovecot 0.99.11 I want to continue to use the standard mbox with all the user's mail stored in /var/spool/mail/<userfile>. User's are known to this mail server via NIS and ALL data is mounted accress NFS in read only mode on this machine, including ~home directories. I want to run dovecot like UW-IMAP...trying to keep it simple-->mail delivery to mbox /var/spool/mail/<username>. My /etc/dovecot.conf: I tried both default_ mail_env = INBOX:/var/spool/mail/%u:INBOX:INDEX=MEMORY with and with out the INBOX:INDEX=MEMORY I want to disable the indicies feature. We don't need it we're about 20 engineers or so who want to continue to use the /var/spool/mail mbox-the original Sendmail location. Most users are downloading every piece of mail through OutHouse or Pine, aka OutLook. I keep getting failed to create storage meaages in /var/log/maillog... Jul 21 15:53:26 mailtest pop3-login: Login: nickr [::ffff:172.26.64.2] Jul 21 15:53:26 mailtest pop3(nickr): Failed to create storage with data: INBOX:/var/spool/mail/nickr Jul 21 15:53:26 mailtest dovecot: child 4773 (pop3) returned error 89 Permissions info for /var/spool/mail/nickr: drwxrwxrwt 3 root mail 4096 Jul 21 15:43 mail [root@mailtest mail]# ls -la nickr total 4204 drwxrwxrwx 2 nickr mail 4096 Jul 21 15:19 . drwxrwxrwt 3 root mail 4096 Jul 21 15:43 .. -rwxrwxrwx 1 nickr ftp 0 Jul 21 14:56 inbox -rwxrwxrwx 1 nickr mail 2375 Jul 21 15:12 msg.FAUO -rwxrwxrwx 1 nickr mail 4256870 Jul 20 16:55 nickr As you can see I am spoping just fine.... Thanks in advance for ANY help!!!!!!!!!

1 0

[Dovecot] linux 2.4 vs 2.6 kernel
by vmstech 20 Jul '05

20 Jul '05

hi I read ( I think in dovecot wiki) that ext2 or ext3 fs on a 2.4 kernel can get slow due to the number of files in a directory. Does anyone know if kernel 2.6 has similar limitation? I'm not at that point now, but before the box goes live, I'm wondering if I should resolve that. Glenn

14 25

[Dovecot] Debian has moved to 1.0stable
by Jaldhar H. Vyas 20 Jul '05

20 Jul '05

Now that sarge has been released, I have as requested moved Debians' Dovecot packages to the 1.0stable branch. Most of the work was actually done by Fabio Tranchitella who is joining me as co-maintainer. The new packages should be available in sid later today. A backport to sarge will also be provided as soon as I can get around to it. Please report all problems to the Debian bug tracking system (see http://bugs.debian.org for instructions or use the reportbug package) not to me directly so that Fabio can also see. -- Jaldhar H. Vyas <jaldhar(a)debian.org> La Salle Debain - http://www.braincells.com/debian/

1 0

Re: [Dovecot] linux 2.4 vs 2.6 kernel
by Paul Vatta 20 Jul '05

20 Jul '05

> > >> ------------------------------------------------------------------------ > We were posed with the same dilemma, but it was due to the need to stick with RHEL supplied packages (ReiserFS does not come with RHEL) that we stayed with ext3. Our old production mail server, running our in-house flavour of Linux, was based on the 2.4 kernel with ReiserFS. We load tested Dovecot with maildir under RHEL3 (2.4 kernel) using ext3 and found it was unable to standup to our requirements. In part this was due to an inordinate imap-login / pop-login processes being created and hanging around under RHEL3. Using RHEL4 (2.6 kernel), we found we were able to handle the required load - this is the configuration we went live with. Processes ended cleanly too (result of the improved schedular and how it interacted with our IBM x445 and its NUMA architecture?) and the I/O issues seemed to have been resolved - ext3 was fine. >> Subject: >> Re: [Dovecot] linux 2.4 vs 2.6 kernel >> From: >> Marc Perkel <marc(a)perkel.com> >> Date: >> Mon, 18 Jul 2005 18:33:54 -0700 >> >> CC: >> dovecot(a)dovecot.org >> >> >> >> >> Curtis Maloney wrote: >> >>> Marc Perkel wrote: >>> >>>> Actually - yes. Same problem. But the solution is to use the Reiser >>>> Filesystem. It doesn't have the ext3 problem. >>> >>> >>> >>> Now, I don't want to start a religious war, but... >>> >>> Ext2 has the advantages that 1) it can fall back to ext2 in recovery >>> cases, and 2) because of that, it has all the well-tested ext2 >>> recovery tools available. >>> >>> People I know who've used Reiser say it's wonderfuly fast, but if it >>> corrupts, well... save your time, and go straight to restoring your >>> backups. >>> >>> Also, take a look at the tune2fs options. I understand -O dir_index >>> will set it to use a b-tree index for faster handling of large >>> directories. >>> >>> -- >>> Curtis Maloney >>> cmaloney(a)cardgate.net >> >> >> I've been using it for 5 years and it works great. It specifically >> eliminates the speed problems of Maildir where you have thousands of >> files in a single directory. And it has infinite inodes so you never >> run out of them. Reiser is ideal for email systems. >> >>------------------------------------------------------------------------ >> >>_______________________________________________ >>dovecot mailing list >>dovecot(a)dovecot.org >>http://dovecot.org/cgi-bin/mailman/listinfo/dovecot >>

5 7

[Dovecot] Compiling under Fedora Core 4 - Problem
by Marc Perkel 19 Jul '05

19 Jul '05

OK - trying to migrate to dovecot and I like what I see so far, but having a hard time getting it to work. I decided to go with the 1.0 version because I need to get away from the ~/Mail namespace. I'm trying to port from a Linuxconf virtual WU-IMAP type config. So - I compiled but then decided I wanted mysql so I tried to reconfigure and now getting compile errors. Looks like I'm missing something? /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x25): In function `report_errors': : undefined reference to `ERR_get_error_line_data' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0xa4): In function `vio_ssl_read': : undefined reference to `SSL_read' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0xc5): In function `vio_ssl_read': : undefined reference to `SSL_get_error' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0xf9): In function `vio_ssl_write': : undefined reference to `SSL_write' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x22d): In function `vio_ssl_close': : undefined reference to `SSL_shutdown' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x23d): In function `vio_ssl_close': : undefined reference to `SSL_free' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x35c): In function `sslaccept': : undefined reference to `SSL_new' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x372): In function `sslaccept': : undefined reference to `SSL_clear' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x380): In function `sslaccept': : undefined reference to `SSL_get_session' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x38f): In function `sslaccept': : undefined reference to `SSL_SESSION_set_timeout' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x3a3): In function `sslaccept': : undefined reference to `SSL_set_fd' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x3b1): In function `sslaccept': : undefined reference to `SSL_set_accept_state' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x3bf): In function `sslaccept': : undefined reference to `SSL_do_handshake' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x3d5): In function `sslaccept': : undefined reference to `SSL_get_peer_certificate' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x3e3): In function `sslaccept': : undefined reference to `X509_get_subject_name' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x3fb): In function `sslaccept': : undefined reference to `X509_NAME_oneline' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x40b): In function `sslaccept': : undefined reference to `X509_get_issuer_name' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x423): In function `sslaccept': : undefined reference to `X509_NAME_oneline' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x433): In function `sslaccept': : undefined reference to `X509_free' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x453): In function `sslaccept': : undefined reference to `SSL_get_shared_ciphers' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x4c1): In function `sslaccept': : undefined reference to `SSL_free' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x53b): In function `sslconnect': : undefined reference to `SSL_new' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x54d): In function `sslconnect': : undefined reference to `SSL_clear' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x55b): In function `sslconnect': : undefined reference to `SSL_get_session' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x56a): In function `sslconnect': : undefined reference to `SSL_SESSION_set_timeout' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x57e): In function `sslconnect': : undefined reference to `SSL_set_fd' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x58c): In function `sslconnect': : undefined reference to `SSL_set_connect_state' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x59a): In function `sslconnect': : undefined reference to `SSL_do_handshake' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x607): In function `sslconnect': : undefined reference to `SSL_free' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x8): In function `get_dh512': : undefined reference to `DH_new' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x2a): In function `get_dh512': : undefined reference to `BN_bin2bn' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x49): In function `get_dh512': : undefined reference to `BN_bin2bn' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x67): In function `get_dh512': : undefined reference to `DH_free' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x9a): In function `report_errors': : undefined reference to `ERR_get_error_line_data' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0xcd): In function `vio_set_cert_stuff': : undefined reference to `SSL_CTX_use_certificate_file' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0xf1): In function `vio_set_cert_stuff': : undefined reference to `SSL_CTX_use_PrivateKey_file' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0xfd): In function `vio_set_cert_stuff': : undefined reference to `SSL_CTX_check_private_key' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x14e): In function `vio_set_cert_stuff': : undefined reference to `ERR_print_errors_fp' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x1c1): In function `vio_set_cert_stuff': : undefined reference to `ERR_print_errors_fp' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x1e9): In function `vio_verify_callback': : undefined reference to `X509_STORE_CTX_get_current_cert' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x1f3): In function `vio_verify_callback': : undefined reference to `X509_STORE_CTX_get_error' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x1fb): In function `vio_verify_callback': : undefined reference to `X509_STORE_CTX_get_error_depth' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x209): In function `vio_verify_callback': : undefined reference to `X509_get_subject_name' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x223): In function `vio_verify_callback': : undefined reference to `X509_NAME_oneline' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x271): In function `vio_verify_callback': : undefined reference to `X509_get_issuer_name' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x285): In function `vio_verify_callback': : undefined reference to `X509_NAME_oneline' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x2e7): In function `new_VioSSLConnectorFd': : undefined reference to `TLSv1_client_method' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x2f2): In function `new_VioSSLConnectorFd': : undefined reference to `SSL_CTX_new' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x30c): In function `new_VioSSLConnectorFd': : undefined reference to `SSL_CTX_set_cipher_list' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x326): In function `new_VioSSLConnectorFd': : undefined reference to `SSL_CTX_set_verify' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x350): In function `new_VioSSLConnectorFd': : undefined reference to `SSL_CTX_load_verify_locations' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x379): In function `new_VioSSLConnectorFd': : undefined reference to `SSL_CTX_ctrl' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x381): In function `new_VioSSLConnectorFd': : undefined reference to `DH_free' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x394): In function `new_VioSSLConnectorFd': : undefined reference to `SSL_CTX_set_default_verify_paths' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x3bc): In function `new_VioSSLConnectorFd': : undefined reference to `SSL_load_error_strings' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x3cd): In function `new_VioSSLConnectorFd': : undefined reference to `OPENSSL_add_all_algorithms_noconf' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x422): In function `new_VioSSLAcceptorFd': : undefined reference to `TLSv1_server_method' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x42d): In function `new_VioSSLAcceptorFd': : undefined reference to `SSL_CTX_new' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x447): In function `new_VioSSLAcceptorFd': : undefined reference to `SSL_CTX_set_cipher_list' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x469): In function `new_VioSSLAcceptorFd': : undefined reference to `SSL_CTX_ctrl' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x483): In function `new_VioSSLAcceptorFd': : undefined reference to `SSL_CTX_set_verify' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x49c): In function `new_VioSSLAcceptorFd': : undefined reference to `SSL_CTX_set_session_id_context' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x4c6): In function `new_VioSSLAcceptorFd': : undefined reference to `SSL_CTX_load_verify_locations' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x4ef): In function `new_VioSSLAcceptorFd': : undefined reference to `SSL_CTX_ctrl' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x4f7): In function `new_VioSSLAcceptorFd': : undefined reference to `DH_free' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x50a): In function `new_VioSSLAcceptorFd': : undefined reference to `SSL_CTX_set_default_verify_paths' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x532): In function `new_VioSSLAcceptorFd': : undefined reference to `SSL_load_error_strings' /usr/lib/mysql/libmysqlclient.a(viosslfactories.o)(.text+0x543): In function `new_VioSSLAcceptorFd': : undefined reference to `OPENSSL_add_all_algorithms_noconf' collect2: ld returned 1 exit status make[3]: *** [dovecot-auth] Error 1 make[3]: Leaving directory `/ctyme/linuxapps/dovecot/dovecot-1.0-test78/src/auth' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/ctyme/linuxapps/dovecot/dovecot-1.0-test78/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/ctyme/linuxapps/dovecot/dovecot-1.0-test78' make: *** [all] Error 2 -- Marc Perkel - marc(a)perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

2 1

[Dovecot] dovecot(pam_unix)[13823]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost
by Dovecot 19 Jul '05

19 Jul '05

I installed Dovecot on our FC3 sendmail server and get this from our Dallas office ( out of state to me ). dovecot(pam_unix)[13823]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost Only one Dallas user can get mail (pop3 or imap). All local users work fine. I ended upgoing back to UW and all works fine. What should I look for? Thanks

1 0

Re: [Dovecot] linux 2.4 vs 2.6 kernel
by Brian Bartholomew 19 Jul '05

19 Jul '05

I can heartily recommend reiserfs on kernel 2.4 for Intel and Sparc. My spam filtering setup currently has 27K files in a quarantine dir, and it works just fine. In a year and a half over 50 machines I've had three corrupted reiserfs filesystems, none of them on production machines, at least one of which I can blame on a bad disk. I would not be surprised to learn they were all bad disks, because the disks are five+ years old. For the last one I moved the bad dir aside where it sat peacefully for a week, and when I fsck'ed it the more aggressive mode of fsck coredumped partway through and it became unaccessable. I then restored it from the tar I had made prior. Brian

1 0

[Dovecot] IMAP: Get rid of non-existent folders below INBOX
by André Wendt 19 Jul '05

19 Jul '05

Hi, I am using Debian Sarge w/ dovecot-imapd package 0.99.14-1. Squirrelmail created three folders below INBOX, Drafts/Sent/Trash, that I already had elsewhere. Thus, I deleted them (through SqM). However, both Thunderbird and Squirrelmail still show these folders anyway. When I select them, I keep getting "Mailbox does not exist" errors. I already tried to move all .imap.index* files in .INBOX/ out of the way -- dovecot created new ones but the folders still appear. I am stuck. How can I prevent dovecot from advertising those non-existent folders? Is this an index-structure problem? I'd appreciate any suggestions. Thanks, -- André

3 2

[Dovecot] UID errors?
by Matt Juszczak 18 Jul '05

18 Jul '05

Hi all, Keep getting these messages: Jul 18 09:48:47 orxon dovecot: POP3(d2525): mbox sync: UID inserted in the middle of mailbox /var/mail/d2525 (109 > 3) Jul 18 09:48:47 orxon dovecot: POP3(d2525): X-IMAPbase uid-last unexpectedly points outside mbox file /var/mail/d2525 For a bunch of users. Any ideas?

2 2

[Dovecot] dovecot(pam_unix)[13823]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost
by Donald Gunn 18 Jul '05

18 Jul '05

I installed Dovecot on our FC3 sendmail server and get this from our Dallas office. dovecot(pam_unix)[13823]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost Only one user can get mail (pop3 or imap). All local users work fine. I ended upgoing back to UW and all works fine. What should I look for? Thanks

1 0

[Dovecot] issues/workarounds to build dovecot on OSX
by OpenMacNews 17 Jul '05

17 Jul '05

hi all, a few notes/issues re: building dovecot on OSX. first, after DL of cvs-head, % autogen.sh reports: autogen.sh: line 2: libtoolize: command not found o OSX, 'libtoolize' has been sed'd to glibtoolize. couple of ways to deal with this: (a) edit in autogen.sh aclocal --- libtoolize --force +++ glibtoolize --force automake --add-missing autoheader autoconf (b) run % autoreconf -i -f instead (c) i suppose yout can link: % ln -s /usr/bin/glibtoolize /usr/bin/libtoolize imho, too 'kludgy' ... never tried it. (d) put some sort of conditional in autogen.sh ... many options of course e.g.: HOSTTYPE=`uname` if [ "$HOSTTYPE" == "Darwin" ]; then LIBTOOLIZE=glibtoolize else LIBTOOLIZE=libtoolize fi fwiw, i'm using (b) --> % autoreconf -i -f successfully. next, dovecot's ./configure fails at the check for openssl: ... checking whether va_lists can be copied by value... yes ./configure: line 27241: syntax error near unexpected token `SSL,' ./configure: line 27241: ` PKG_CHECK_MODULES(SSL, openssl)' % within a pkg-config stanza ... as pkg-config does not exist on OSX, a couple of hacks in 'configure.in': =================================================== (EDITOR) configure.in @1032 if test "$want_openssl" = "yes" && test "$have_ssl" = "no"; then --- if pkg-config --exists openssl; then +++ if test -f openssl; then --- PKG_CHECK_MODULES(SSL, openssl) CFLAGS="$CFLAGS $SSL_CFLAGS" =================================================== , followed, of course, by another: % autoreconf -i -f take care of the problem. with changes as above, 'configure' with: ./configure \ --prefix=/usr/local/dovecot \ --exec-prefix=/usr/local/dovecot \ --bindir=/usr/local/dovecot/bin \ --sbindir=/usr/local/dovecot/sbin \ --libexecdir=/usr/local/dovecot/libexec \ --libdir=/usr/local/dovecot/lib \ --includedir=/usr/local/dovecot/include \ --sysconfdir=/var/Settings/Dovecot \ --localstatedir=/var/Process \ --mandir=/var/Documentation/man \ --datadir=/var/Data/Dovecot \ --with-ssl=openssl --with-ssldir=/usr/local \ --with-rundir=/var/Process/dovecot \ --with-moduledir=/usr/local/dovecot-modules \ --enable-shared \ --enable-static \ --enable-ipv6 \ --with-pgsql \ --disable-debug completes sueccessfully, as do: make make check make install resulting in: % ls -aR .: . .. libexec sbin ./libexec: . .. dovecot ./libexec/dovecot: . checkpassword-reply dovecot-auth imap-login pop3-login .. deliver imap pop3 rawlog ./sbin: . .. dovecot dovecotpw as, i believe, expected. now, onward! cheers, richard

1 0

[Dovecot] "dovecot virgin": 1st questions ...
by OpenMacNews 17 Jul '05

17 Jul '05

hi all, "uncle"! i've thrown up my hands with cyrus, and am looking for a 'better alternative' ... i'm brand new to dovecot (haven't even built it yet ...), and have spent the last while reading through the LIST archives here. apart from the TECHNICAL aspects, which seem _more_ than adequate/competitive, i'm most attracted by a comment abt this LIST/community: > awesome technical support with patient developer-dudes on hand which, in a nutshell, is what i seem to be missing. so, i'm preparing to "take the plunge" w/ dovecot. two preliminary questions, if i might: (1) what sort of *interest* is there here (Timo? others?) in Dovecot on OSX? i'm usually able to get most anything up-n-runnig on my OSX boxes, but i'd like to join a community where every issue-on-Mac is not simply ignored/slammed ... and there might be folks willing to work with me on issues (2) here-we-go-again with the Maildir/Mbox decision :-) what's the latest thinking/recommendation here wrt mailbox/mdir? my specifics are -- i intend to backend Dovecot with Exim ... and will run my server 'closed box' ... i.e., no file-system-related User accounts. rather, just 'virtual' spaces. i'm leaning towards Maildir's one-flat-file-per-message format, with an eventual/possible move to storage in PostgreSQL if/when Dovecot adds the capability ... thoughts? (yes, i know, y'all must've had the discussion a g'zillion times ... a pointer to a good/relevant thread is great too!) cheers, richard

2 2

[Dovecot] Authentication feature I need
by Marc Perkel 17 Jul '05

17 Jul '05

OK - here's whay I need to make it work for my Linuxconf compatible authentication system. First - a question: Will this work? I can find docs on "virtualfile. auth virtualfile { mechanisms = plain digest-md5 userdb = passwd-file /etc/vmail/passwd.%d passdb = passwd-file /etc/vmail/shadow.%d user = root } Then - since the dmain name selects the passwd file, if there were a feature to make %n be us user instead of the whole email address then I have what I need. Password files are placed in the /etc/vmail directory as follows: /etc/vmail/passwd.domain1 /etc/vmail/shadow.domain1 /etc/vmail/passwd.domain2 /etc/vmail/shadow.domain2 The password and shadow files are exactly the same format as the /etc/password and /etc/shadow files. The user name within the files would be the %n part of the email address passed to authenticate with. Basically the password file names are /etc/vmail/passwd.%d with the user withing the file being %n. marc:x:40000:12:Marc Perkel:/vhome/perkel.com/home/marc:/bin/false test:x:40001:12::/vhome/perkel.com/home/test:/bin/false dd:x:40002:12:Atia:/vhome/perkel.com/home/dd:/bin/false test2:x:40003:12::/vhome/perkel.com/home/test2:/bin/false

2 3

[Dovecot] Feature Request - Authentication Scheme - Linuxconf
by Marc Perkel 17 Jul '05

17 Jul '05

This would make my life a lot easier in migrating to Dovecot. And it should be really easy to implement. Here's how linuxconf does it: Password files are placed in the /etc/vmail directory as follows: /etc/vmail/passwd.domain1 /etc/vmail/shadow.domain1 /etc/vmail/passwd.domain2 /etc/vmail/shadow.domain2 The password and shadow files are exactly the same format as the /etc/password and /etc/shadow files. The user name within the files would be the %n part of the email address passed to authenticate with. Basically the password file names are /etc/vmail/passwd.%d with the user withing the file being %n. marc:x:40000:12:Marc Perkel:/vhome/perkel.com/home/marc:/bin/false test:x:40001:12::/vhome/perkel.com/home/test:/bin/false dd:x:40002:12:Atia:/vhome/perkel.com/home/dd:/bin/false test2:x:40003:12::/vhome/perkel.com/home/test2:/bin/false It also makes merging several servers with separate passwd/shadow files into one virtual system because all you have to do is copy their existing passwd/shadow files into the /etc/vmail directory and rename them with the domain at the end. So - wouldn't that be easy to add? Sure would make migrating easy for me. -- Marc Perkel - marc(a)perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

2 4

[Dovecot] user_db, uid/gid and maildir
by vmstech 17 Jul '05

17 Jul '05

Im experimenting with putting all my virtual users mail under 1 directory with belonging to a system user created for the purpose. The mode on the directory (and subdirectories) is 770. I keep all my virtual users details in a postgres database. My interpretation of the wiki documentation is that if the user_db query returns a uid column and a gid column containing the numeric uid and gid of the owner of the directory, then dovecot should have no problem using mail in these folders. Is that correct? (I'm actually getting permission errors appear in the log file on the directories when I try and attach with a client, which reports "Cannot get LIST information for pattern `*' on IMAP server a.b.com unknown".) thanks Glenn

1 0

[Dovecot] Authenticaing in postgresql
by vmstech 17 Jul '05

17 Jul '05

Hi all - Im new to dovecot and actually all things email serverish. I spent last week wrestling with exim4, and this week its dovecots turn. I'm trying to connect as an imap user (from evolution) and not actually able to make a successful login. I have default_pass_scheme=PLAIN, and am using pass authentication in evolution client. Its the only one available after it queries the server for available types. I'm not getting any errors appear in either the postgres or dovecot log files (anymore :-) that is). I'm getting the exact query I'd like to see in the dovecot log file, after I entering the password in the client, but unfortunately it doesnt give me the reply. I can key this exact query in to the psql client and get the correct answer. dovecots logs don't tell me if I have success or failure. The auth_db query has only 1 column. I have no idea where to go from here - would love a hint thanks Glenn

1 1

Re: [Dovecot] New to dovecot, little luck - signal 10 death for imap
by Jeroen Scheerder 15 Jul '05

15 Jul '05

Peter Evans wrote: > Jeroen Scheerder (Jeroen.Scheerder(a)phil.uu.nl) wrote: > >>However, whenever a mailbox is selected, the imap subprocess dies. >>Jul 13 14:52:05 localhost dovecot: imap-login: Login: js [127.0.0.1] >>Jul 13 14:52:07 localhost dovecot: child 8082 (imap) killed with signal 10 > > > You're going to have to help us to help you. 10 is bus error (I think) > which is badness. > > OS, > version of dovecot > etc. > > you might want to debug a coredump, that will tell you where/why its > dying too. I would merrily gdb into a coredump and stacktrace away, if a core dump were created. No such luck. I'm now logging directly to file using syslog, after having started dovecot. There is no limit on coredumps: % limit cputime unlimited filesize unlimited datasize unlimited stacksize 8MB coredumpsize unlimited descriptors 64 vmemorysize unlimited % more /tmp/dovecot* :::::::::::::: /tmp/dovecot-info.log :::::::::::::: dovecot: Jul 13 15:27:35 Info: Dovecot v1.0-stable starting up dovecot: Jul 13 15:28:21 Info: imap-login: Login: avank [127.0.0.1] :::::::::::::: /tmp/dovecot.log :::::::::::::: dovecot: Jul 13 15:28:21 Error: child 14882 (imap) killed with signal 10 Environmental details: Solaris 7 (sparc) dovecot 1.0-stable compiled with ldap support using gcc 3.3.4 4.0.0 4.0.1 (no difference here) configured for mbox support with locking matching procmail's delivery locking strategies with authentication using passwd/shadow native databases A header dump shows nothing suspect: % elfdump -d /phil/sunos/sparc/pkg/dovecot-1.0-stable/libexec/dovecot/imap Dynamic Section: .dynamic index tag value [0] NEEDED 0x1 libsocket.so.1 [1] NEEDED 0x117 librt.so.1 [2] NEEDED 0x140 libc.so.1 [3] NEEDED 0x397 libnsl.so.1 [4] NEEDED 0x3b3 libdl.so.1 [5] RPATH 0x3cc /phil/sw/sunos/sparc/lib [snip] Will try on Solaris 10.

4 9

[Dovecot] OS X Mail.app 2 (Tiger) + dovecot -> new mail count doubled
by Alan Schmitt 14 Jul '05

14 Jul '05

Hello, I've noticed a strange bug with Mail.app 2 (from OS X.4) and dovecot, and I'm trying to identify where it comes from. I have a bunch of mailboxes that can receive new mail (delivered by procmail) and I have Mail set up as to automatically synchronize all maiboxes. When I start up Mail, the count for new mail is doubled in every mailbox that I have not seen yet. Looking at a mailbox restores the correct count (mail is not actually duplicated, it's just the new mail counter that is wrong). Has anyone else seen this? Would this bug be from Mail.app or from dovecot? (I suspect the former.) Thanks a lot, Alan Schmitt

3 6

[Dovecot] Very slow select() command on large mailboxes
by Sebastjan Trepca 14 Jul '05

14 Jul '05

Hi, I'm trying to decide if I could use you mail server in our enviroment which has about 10k users and mailboxes size about ~1GB. So I made a few tests and it all worked quite fast, except that select command on large mailboxes. The first time I select a mailbox which has 10k messages it takes about 4s to process. I am deliberately trying this on a Celeron 850Mhz, 512 MB memory and some shitty hard-drive to maximize the times. So why is this so slow? Does it index the messages on select? It's even slower when I have some new messages in folder, more that I have more I wait. So I presume it must be something with indexing? Anyway, how could I optimize this? Why don't you index when a mail arrives instead of on select? Thanks for help and keep doing a great job with Dovecot. Sebastjan

4 3

[Fwd: Re: [Dovecot] Dovecot and ActiveDirectory]
by Chris Wakelin 14 Jul '05

14 Jul '05

Oops! Thought I'd CC'd this to the list. Sorry, Oliver! Chris -------- Original Message -------- Date: Wed, 13 Jul 2005 20:09:35 +0100 From: Chris Wakelin <c.d.wakelin(a)reading.ac.uk> To: Jeroen Scheerder <Jeroen.Scheerder(a)phil.uu.nl> CC: Chris Wakelin <c.d.wakelin(a)reading.ac.uk> Subject: Re: [Dovecot] Dovecot and ActiveDirectory Jeroen Scheerder wrote: > Chris Wakelin (13/7/05 16:08 +0100) [Re: [Dovecot] Dovecot and > ActiveDirectory]: > > >>I've got it working via PAM and pam_ldap on Solaris. [..] > > > That's exactly what I'm striving to do. > > I've never set up LDAP authentication for Solaris itself, and actually > never used PAM before. > > If I may be so bold, could I bother you for details about your > configuration in these respects? /opt/RDGpldap/etc/ldap.conf: host xxx.rdg.ac.uk base dc=xxxxx,dc=ad,dc=rdg,dc=ac,dc=uk binddn cn=xxxuser,cn=users,dc=xxxxx,dc=ad,dc=rdg,dc=ac,dc=uk bindpw xxxpasswd nss_map_objectclass posixAccount user nss_map_objectclass shadowAccount user nss_map_attribute uid sAMAccountName nss_map_attribute homeDirectory unixHomeDirectory nss_map_attribute shadowLastChange pwdLastSet nss_map_objectclass posixGroup group nss_map_attribute uniqueMember member pam_login_attribute sAMAccountName pam_filter objectclass=User pam_password ad xxxuser is a read-only account in the AD. /etc/pam.conf: ... dovecot auth required /opt/RDGpldap/lib/pam_ldap.so dovecot account required /opt/RDGpldap/lib/pam_ldap.so dovecot session required /opt/RDGpldap/lib/pam_ldap.so dovecot.conf: auth_username_translation = AaBbCcDdEeFfGgHhIiJjKkLlMmNnOoPpQqRrSsTtUuVvWwXxYyZz auth default { mechanisms = plain login passdb = pam userdb = passwd user = root } The auth_username_translation is because AD users are case-insensitive but UNIX ones aren't! We have users in both AD and UNIX (but could use something like "userdb=static uid=xxxx gid=yyyy home=/var/mail/%Lu" assuming xxxx:yyyy has appropriate permissions on the spool files) pam_ldap-178 was configured with ./configure --prefix=/opt/RDGpldap \ --with-ldap-conf-file=/opt/RDGpldap/etc/ldap.conf Hope this helps, Chris -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

1 0

Re: [Dovecot] problem with server certificate: dovectot.pem
by Joseph Tam 14 Jul '05

14 Jul '05

> Date: Wed, 13 Jul 2005 23:46:33 +0300 > From: vladone <vladone(a)spaingsm.com> > Subject: [Dovecot] problem with server certificate: dovectot.pem > > I have an mail server with postfix and dovecot. > All works fine, but now is change my domain. After changed > configurations i can receive (or send) mail without STARTTLS, > but when i try to use this option i receive: > "TLS handshake failure. Invalid server certificate (Key material > mismatch)" > > I dont know what is this. > I use certificate that is generate with script for dovecot (that work > at begining). > Even i try to rebuild this certificate acording with new domain but > nothing. > Where is my problem? Yes, of course. Certificates are made out to a particular hostname (e.g. smtp.wahtever.com) and if you change your server hostname or move it to another server, a new certificate will have to be made out to the new hostname. You could also configure your client ignore certificate mismatches, but this wouldn't be the best option. Joseph Tam <tam(a)math.ubc.ca>

1 0

[Dovecot] Search with specified charset
by Chris Wakelin 13 Jul '05

13 Jul '05

I've seen a problem with searching in the Prayer webmail client that turns out to be caused by Prayer insisting on a charset called "ISO-8859-1" and Dovecot, using Solaris iconv, not recognising it (all the Solaris 8 iconv modules appear to be "ISO8859-1" etc. or just "8859-1"). This isn't a problem in Linux: % iconv --list | grep 8859.1/ 8859_1// ISO-8859-1// ISO8859-1// ISO885911// ISO_8859-1// I've hacked together a patch for Dovecot to try matching without the "ISO-" prefix if matching fails at first, which works for Solaris (as would creating an extra symbolic link in /usr/lib/iconv or hacking Prayer to use "ISO8859-1") and it doesn't break Linux, but it's not pretty :( Better may be to try substituting underscores, hyphens, spaces(?) and nothing in the string, but that makes the change much more complicated! Best Wishes, Chris --- dovecot-1.0-stable/src/lib-charset/charset-iconv.c.orig Mon Jan 31 16:37:55 2005 +++ dovecot-1.0-stable/src/lib-charset/charset-iconv.c Wed Jul 13 21:47:03 2005 @@ -36,9 +36,17 @@ ascii = FALSE; cd = iconv_open("UTF-8", charset); if (cd == (iconv_t)-1) { - if (unknown_charset != NULL) - *unknown_charset = TRUE; - return NULL; + /* Try matching charset without "ISO" prefix */ + if (strncasecmp(charset, "ISO-", 4) == 0 || + strncasecmp(charset, "ISO ", 4) == 0) + cd = iconv_open("UTF-8", charset + 4); + else if (strncasecmp(charset, "ISO", 3) == 0) + cd = iconv_open("UTF-8", charset + 3); + if (cd == (iconv_t)-1) { + if (unknown_charset != NULL) + *unknown_charset = TRUE; + return NULL; + } } } @@ -137,9 +145,17 @@ cd = iconv_open("UTF-8", charset); if (cd == (iconv_t)-1) { - if (unknown_charset != NULL) - *unknown_charset = TRUE; - return NULL; + /* Try matching charset without "ISO" prefix */ + if (strncasecmp(charset, "ISO-", 4) == 0 || + strncasecmp(charset, "ISO ", 4) == 0) + cd = iconv_open("UTF-8", charset + 4); + else if (strncasecmp(charset, "ISO", 3) == 0) + cd = iconv_open("UTF-8", charset + 3); + if (cd == (iconv_t)-1) { + if (unknown_charset != NULL) + *unknown_charset = TRUE; + return NULL; + } } if (unknown_charset != NULL) -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

1 0

[Dovecot] problem with server certificate: dovectot.pem
by vladone 13 Jul '05

13 Jul '05

Hi! I have an mail server with postfix and dovecot. All works fine, but now is change my domain. After changed configurations i can receive (or send) mail without STARTTLS, but when i try to use this option i receive: "TLS handshake failure. Invalid server certificate (Key material mismatch)" I dont know what is this. I use certificate that is generate with script for dovecot (that work at begining). Even i try to rebuild this certificate acording with new domain but nothing. Where is my problem? P.S. All works before changed my domain!!!

1 0

[Dovecot] file locks
by Obantec Support 13 Jul '05

13 Jul '05

Hi I am trying to install 1.0 stable from source on a test server running 0.99 on FC3. i did basic ./configure etc and get this result Jul 13 17:24:26 proteus4 dovecot: Dovecot v1.0-stable starting up Jul 13 17:24:35 proteus4 dovecot: POP3(obantec): open(/var/spool/mail/.temp.proteus4.4485.e3eec7b26a559bac) failed: Permission denied Jul 13 17:24:35 proteus4 dovecot: POP3(obantec): file_lock_dotlock() failed with mbox file /var/spool/mail/obantec: Permission denied Jul 13 17:24:35 proteus4 dovecot: pop3-login: Login: obantec [192.168.0.10] when trying to access a test account. permissions all look as per old 0.99 which did work. Mark

3 5

[Dovecot] Minor bugs still in test77
by Chris Wakelin 13 Jul '05

13 Jul '05

Thinking of patches I always apply, I've got a couple (attached) that fix minor bugs and maybe should be applied - or implemented better and then applied ;) - to the main distribution? 1) LIST bugs: LIST "~/mail/" "" and LIST "" "~/mail/" (where "~/mail/" is a namespace prefix) don't reply the same way as UW-IMAP does and in at least the first case, still violates the spec (your fix breaks, as namespace_find() modifies its argument) The second issue breaks Pine 4.x, I think. 2) Angle-addresses If a header address is just "<someone(a)somewhere.org>" rather than "Someone <someone(a)somewhere.org>" or "someone(a)somewhere.org", then the FETCH ... ENVELOPE command responds with "" as the personal name, rather than NIL, which may confuse clients (without being wrong, technically, I think). (In case anyone's interested, I also use patches to: 1) fix the 64bit issue mentioned earlier today 2) introduce extra logging of LIST, SUBSCRIBE and UNSUBSCRIBE (for debugging during our migration from UW-IMAP) 3) rename .subscriptions to .mailboxlist and store folder names in it including the namespace prefix (to emulate UW-IMAP) 4) implement a Reading-specific hashing algorithm for the mail spool location as an extra variable modifier "%H" (e.g. "/export/mail/%Hu/%u/INBOX") 5) remove the need for /dev/urandom, which isn't available on our mail server (though there is a Solaris patch available to create it). 6) add an option to hide "AUTH=PLAIN" in the CAPABILITY string as Pine 4.x complains loudly when this is advertised on a non-SSL connection ) Best Wishes, Chris -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094 --- dovecot-1.0-test77.orig/src/imap/cmd-list.c Sun Apr 17 17:37:05 2005 +++ dovecot-1.0-test77/src/imap/cmd-list.c Wed Jul 13 16:10:27 2005 @@ -372,7 +372,8 @@ concept which probably no other client uses than Pine. Just try our best to emulate UW-IMAP behavior and hopefully we're fine. */ - ns = namespace_find(client->namespaces, &ref); + const char *ref_copy = t_strdup(ref); + ns = namespace_find(client->namespaces, &ref_copy); if (ns == NULL) { const char *empty = ""; ns = namespace_find(client->namespaces, &empty); @@ -405,6 +406,28 @@ } client_send_tagline(cmd, "OK List completed."); } else { + + if (*ref == '\0' && !lsub) { + /* LIST "" "something" */ + const char *mask_copy = t_strdup(mask); + ns = namespace_find(client->namespaces, &mask_copy); + if (ns == NULL) { + const char *empty = ""; + ns = namespace_find(client->namespaces, &empty); + } + if (*ns->prefix != '\0' && *mask_copy == '\0') { + /* namespace, return it */ + string_t *str = t_str_new(64); + str_printfa(str, "* LIST (\\Noselect) \"%s\" ", + ns->sep_str); + imap_quote_append_string(str, ns->prefix, + FALSE); + client_send_line(client, str_c(str)); + client_send_tagline(client, "OK List completed."); + return TRUE; + } + } + ctx = p_new(cmd->pool, struct cmd_list_context, 1); ctx->ref = ref; ctx->mask = mask; --- dovecot-1.0-test77.orig/src/lib-mail/message-address.c Fri Apr 8 12:16:36 2005 +++ dovecot-1.0-test77/src/lib-mail/message-address.c Wed Jul 13 16:15:15 2005 @@ -140,6 +140,10 @@ return -1; ctx->addr.name = p_strdup(ctx->pool, str_c(ctx->str)); + if (*ctx->addr.name == '\0') { + /* Cope with "<address>" without display name */ + ctx->addr.name = NULL; + } if (parse_angle_addr(ctx) < 0) { /* broken */ ctx->addr.domain = p_strdup(ctx->pool, "SYNTAX_ERROR");

1 0

[Dovecot] Dovecot and ActiveDirectory
by Hoffmann, Oliver 13 Jul '05

13 Jul '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! Is there a solution to auth dovecot against an windows active directory? i've tried this config: - --- # Space separated list of LDAP hosts to use. host:port is allowed too. hosts = dc.foo.bar # Distinguished Name - the username used to login to the LDAP server dn = cn=oh,cn=Users,dc=foo,dc=bar # Password for LDAP server dnpass = password # LDAP protocol version to use. Likely 2 or 3. ldap_version = 3 # LDAP base base = cn=Users,dc=foo,dc=bar # Dereference: never, searching, finding, always #deref = never # Search scope: base, onelevel, subtree scope = subtree # User attributes in order: user_attrs = uid,homeDirectory,,,uidNumber,gidNumber # Filter for user lookup. Some variables can be used: #user_filter = (&(objectClass=posixAccount)(uid=%u)) # Password checking attributes in order: pass_attrs = uid,userPassword # Filter for password lookups #pass_filter = (&(objectClass=posixAccount)(uid=%u)) # Default password scheme. "{scheme}" before password overrides this. #default_pass_scheme = CRYPT # You can use same UID and GID for all user accounts if you really want # to. # If the UID/GID is still found from LDAP reply, it overrides these values. #user_global_uid = #user_global_gid = - --- but got this error: - --- dovecot-auth: Jul 13 16:42:09 Error: ldap(oh): unknown user - --- thx & greets oliver -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (MingW32) iD8DBQFC1S162+wHtX4o3oARAo+SAJ9EGVQPXBG+gtZmcbkOjMiy0xF2JACgigDs +6q+EW0zjsICqME310Ky41M= =sMRS -----END PGP SIGNATURE-----

2 1

[Dovecot] New to dovecot, little luck - signal 10 death for imap
by Jeroen Scheerder 13 Jul '05

13 Jul '05

Hi, I'm a new prospective dovecot user. I'm planning to migrate a medium-scale mail site (a few thousand users) from UW to something better. I've set up dovecot on a test system. I can connect and authenticate just fine. IMAP clients get to see the right mailboxes. However, whenever a mailbox is selected, the imap subprocess dies. The log shows: Jul 13 14:52:05 localhost dovecot: imap-login: Login: js [127.0.0.1] Jul 13 14:52:07 localhost dovecot: child 8082 (imap) killed with signal 10 When I either telnet to it manually or run the "imap" process in a terminal window, everything seems to work: ---- Snip ---- * PREAUTH [CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS] Logged in as js x select INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 1300 EXISTS * 0 RECENT * OK [UNSEEN 2] First unseen. * OK [UIDVALIDITY 1119092680] UIDs valid * OK [UIDNEXT 1590] Predicted next UID x OK [READ-WRITE] Select completed. x fetch 1 full * 1 FETCH (FLAGS (\Seen) INTERNALDATE "18-Jun-2005 05:00:02 +0200" RFC822.SIZE 1773 ENVELOPE ("Sat, 18 Jun 2005 05:00:01 +0200 (MET DST)" "Waarschuwing: uw inbox overschrijdt 80% van de groottelimiet (18-06-2005)" (("Super-User" NIL "helpdesk" "phil.uu.nl")) (("Super-User" NIL "helpdesk" "phil.uu.nl")) (("Super-User" NIL "helpdesk" "phil.uu.nl")) ((NIL NIL "js" "phil.uu.nl")) NIL NIL NIL "<20050618030001.B5F3952048(a)goedel.admin.phil.uu.nl>") BODY ("text" "plain" ("charset" "us-ascii") NIL NIL "7bit" 1082 25)) x OK Fetch completed. x fetch 1 body[text] * 1 FETCH (BODY[TEXT] {1082} Beste Jeroen Scheerder, [...] Met vriendelijke groet, het systeembeheer. ) x OK Fetch completed. x list * * * LIST (\Noselect \HasChildren) "/" "Archive/" [...] * LIST (\Unmarked) "/" "INBOX" x OK List completed. ---- Snip ---- I'm at a loss here, and no amount of logging or sniffing with tcpdump has revealed anything interesting so far. Does anyone else see these "signal 10" aborts? Is there any way in which I can force a coredump (in case it's *really* a bus error)? Regards, Jeroen.

1 0

Re: [Dovecot] mysql
by John Peacock 13 Jul '05

13 Jul '05

Peter Evans wrote: > Because you might, just possibly want performance that > doesn't resemble mollasses in midwinter? > Optionally, you might even want something where the response > time is deterministic. I think you need to take your biases and go someplace else. If you don't like MySQL because of some personal bias, then don't use it. Anyone halfway competent can build Dovecot themselves and not rely on some third-party RPM's that have dependencies. This is a discussion list for Dovecot. Please try and stay on topic... John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4720 Boston Way Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5747

1 0

Re: [Dovecot] mysql
by Andrew Hutchings 13 Jul '05

13 Jul '05

Peter Evans wrote: > Dominic Marks (dom(a)goodforbusiness.co.uk) wrote: > > Because you might, just possibly want performance that > doesn't resemble mollasses in midwinter? > Optionally, you might even want something where the response > time is deterministic. > > Points at the company mail system here for a prime example > of why not to use mysql. But then again, this is actually > a prime example of "it works, but we don't know how." > > P > > We use mysql here as it makes a perfect integration with the rest of our systems, we have over 6000 mail accounts (probably closer to 7000 now) on it and the mysql lookup time is pretty much instant, the load never goes above 0.5 on the systems (2x1GHz Epias on round robin with replicated databases on each) and most of that is because the POP/IMAP servers are also round robin MX servers so Exim can take a chunk out of the CPU. Regards Andrew -- Andrew Hutchings (A-Wing) - Linux Guru Netserve Consultants - http://www.domaincity.co.uk/ A-Wing Internet Services - http://www.a-wing.co.uk/ Random quote 2: "In most countries selling harmful things like drugs is punishable. Then howcome people can sell Microsoft software and go unpunished?" - Hasse Skrifvars

1 0

[Dovecot] Headers "missing" in new CVS version
by Todd Burroughs 13 Jul '05

13 Jul '05

We're experiencing an odd problem with dovecot "losing" headers. This started happening with the CVS release as of July 4 and still happens with July 12. It was working properly June 28. It does not happen using pine or thunderbird. It happens using webmail (twig). When you open the inbox, you see subject, etc. When you open a mail, all of the headers are gone. Returning to the inbox, all the headers are missing. It seems to cache this as well. After returning to the older dovecot, all of the headers are missing. Deleting the cache files fixes this and there does not seem to be any mbox corruption. It does not log any errors or crash. Todd Burroughs

2 1

[Dovecot] separate SSL certificates for pop3s and imaps
by Michael Weiser 13 Jul '05

13 Jul '05

Hi, I'm migrating a uw-imap installation to dovecot. With uw-imap I had different SSL certificates and keys for ipop3d and imapd. How can I configure dovecot to do the same with its pop3s and imaps services? Thanks in advance, -- _________________________creating IT solutions Michael Weiser science + computing ag bei Eisenbahn und Haefen Postfach 11 02 63 Hagellocher Weg 71-75 47142 Duisburg 72070 Tuebingen, Germany phone +49 203 52 26341 www.science-computing.de

2 2

[Dovecot] add inotify support to dovecot
by Johannes Berg 13 Jul '05

13 Jul '05

Hi, attached patch against test76 adds inotify support and the --with-notify=... configure option that defaults to the current check for dnotify using no special method if dnotify cannot be compiled, and can be set to none, dnotify and inotify. If it is set to dnotify or inotify, failure to compile a test program results in an error. Also, it adds | file change notification method ..... : <method> to the output at the end of configure. The only thing I don't like about this patch is the fact that I had to add a field notify_context to struct io, but I didn't see a different way to handle this. Also, the patch doesn't support the condition parameter, it simply always asks for all the relevant changes. I don't really see that it is useful for in the context of file system notifications anyway. I modeled this after ioloop-notify-dn.c with my other patch applied to it, if you don't like the other patch you'll want to "revert" that change in the new ioloop-notify-inotify.c file as well. Oh, and obviously I didn't include patches to configure and all the Makefiles, so of course you'll have to run automake. But you already knew that :) I only tested this with maildir. I did add IN_MODIFY so I think it should work with mbox too, but someone should probably verify. Have fun, johannes

2 2

[Dovecot] sorting question
by Johannes Berg 13 Jul '05

13 Jul '05

Hi, If I understand the thread sorting algorithm correctly (from draft-ietf-imapext-sort-17.txt and the code), it will sort like this (where I use numbers instead of dates with higher numbers being newer mails) 4 10 3 11 2 12 1 13 etc into all the lower levels. Thunderbird will actually sort this like this: 1 13 2 12 3 11 4 10 where threads are sorted by the newest child in them. Now, I am thinking that evolution simply uses dovecot's THREAD feature and doesn't implement anything itself, so that if I wanted to have that kind of threading, I'd have to implement it in dovecot. Would this be easy? I'm thinking that I should just treat all nodes as if they were dummy nodes in sort_root_nodes, but that only fixes the first level afaict, because later dates are not propagated up. Essentially, I think what the algorithm tb uses does is not use a nodes date as it's sorting criterion, but it's newest child, and apply this rule recursively. Does anyone else think this feature would be useful? I regularly end up almost missing mail because it is sorted at such a low position and I don't see the thread at all.. johannes

4 5

[Dovecot] Dovecot runs as ...
by Matt Juszczak 13 Jul '05

13 Jul '05

Hi all, We're using LDAP 100% for everything ... So does that mean that for the following user, I can put another user, like nobody? user = root I guess that user still has to be able to access /var/mail and such, correct?

2 1

[Dovecot] 1.0-test77
by Timo Sirainen 12 Jul '05

12 Jul '05

http://dovecot.org/ It's hot in here. Something like 25-30c for many days now. My brains don't work in that heat. So, this is still not an 1.0-alpha1. I'll put it out when I think the release will actually be fully working :) Changes since test76: - Fixes to FETCHing MIME body parts, especially with message/rfc822 attachments. We hadn't been handling this entirely correctly ever (this part of IMAP spec was pretty difficult for me to understand earlier..). This also caused Dovecot to sometimes disconnect clients fetching [n.MIME] body parts earlier, if someone had that problem. - Maildir: Several bugs fixed with APPEND/COPYing mails - mbox: Keywords weren't stored to index with APPEND - inotify patch by Johannes Berg (and possibly broken by me). Can be enabled with --with-notify=inotify parameter to configure. - SEARCH now doesn't fail if a messageset outside valid range is given to it. Some mobile IMAP client was broken because this didn't work. - Cache mail headers when saving mails to mbox. We should cache everything, but this is a start.. - And other cache file fixes/optimizations

2 3

[Dovecot] PERMANENTFLAGS bug?
by Nils Henrik Tvetene 12 Jul '05

12 Jul '05

Hi, Im new to the list, so might be a FAQ allthough I havent found it anywhere: When I try to connect to dovecot/imap from snappermail (palm), I get a IMAP protocol error. The complaint is about: OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft ) \*)] Flags permitted. As you can see, theres an extra " )" after "Draft". Any clues on how to fix/bypass this? Regards, Nils Henrik Tvetene

3 5

[Dovecot] Dovecot 1.0-stable mbox performance and disconnections
by Chris Wakelin 12 Jul '05

12 Jul '05

I've got some of our busiest users now using Dovecot instead of UW-IMAP with mbox-format mailboxes and predominantly Outlook Express as the client. Doing some perfomance monitoring (with Solaris 8 process accounting), it looks like Dovecot needing to read only 30-50% of the disk blocks needed by UW-IMAP, but I was hoping for better! What seems to happen, is that most of the connections use only a small number of blocks (due to Dovecot indexes, presumably) but occassionally a process will read lots of blocks, sometimes even more than a UW-IMAP session. Is this expected, or is something going wrong with the index updates? I have the default sync settings, I think (mbox_dirty_syncs = yes, mbox_very_dirty_syncs = no, mbox_lazy_writes = yes) My INBOX is an extreme example with ~10,000 messages and most processes reading a few hundred blocks but a couple using 20,000 or so! Also, Dovecot seems to be dropping connections, sometimes, for no good reason (putting some extra i_info lines suggests for "inactivity"). Thunderbird tends to reconnect automatically, though. It seems it may be happening at the end of an IDLE command, something like:- 4 IDLE + idling * 1005 EXISTS DONE * 1005 EXPUNGE but then the expected 4 OK Idle completed never comes. Has anybody else seen this? Best Wishes, Chris -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

2 2

[Dovecot] newbie questions
by Stewart Dean 12 Jul '05

12 Jul '05

Thanks in advance for your patience and assistance. Since a system administrator's work is most successful when nobody knows you've done anything....(ugly that...you get neither raises nor equipment funding as a result), I prefer to learn from other's experiences rather than fail in the same pits. We are considering a switch from UW to Dovecot, since our users persist in using the INBOX as a file cabinet (maybe 25% use homedir folders) and we currently have, I think, .mbox INBOXes which are thus getting massively unmanageable and fragile. Machine config: Running IBM AIX 5.2/5.3 on an F80 with 4GB memory (may be upgraded to 16GB), with IBM's sendmail binary at V8.11.6p2, hand compiled procmail at 3.22, 64-bit binary from C for AIX V6.0 Some questions I couldn't find answered in the docs: 1) Crispin of UW has a formats.txt file in which he lists and evaluates the various formats. He calls the INBOX format type we use .unix (one big honking flat file). Q1: Is this what is described in the Dovecot docs mail-storages.txt file as .mbox? 2) Authentication: The DC docs don't mention using NIS/yp for authentication, that I can find. Q2: Does DC support NIS/yp authentication? I guess I could periodically do a ypcat passwd to a file and point DC at it... 3) on IBM's AIX Unix... Q3: Is there anyone out there running DC on AIX? 5.x or 4.3.3? JFS or JFS2? 4) Inbox location/format: = I will want to move from our legacy .mbox format to, I suppose, the DC default of Maildir++. = I will want to do this in groups over time, rather than all at once, so both formats will have to work = The legacy location of INBOXes has been /var/spool/mail/<userid>. The docs appear to say that Maildir format INBOXes should be in ~/Maildir. Q4:Can the INBOXes be in two location, the converted new Maildirs in ~, and the old unconverted in vsm? Or will I have to override the DC cfg'ed INBOX location to be VSM until I get them all converted and then move them all to ~/Maildir and change the DC config to that? 5) Some mention was made of procmail configuration issues Q5: Can procmail support both formats/locations, or will I have to put changes in the migrated users' procmailrc (what fun!)? Again, thanks! -- ==== 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

5 4

[Dovecot] mysql
by Jim Edwards 12 Jul '05

12 Jul '05

Hello, Does dovecot require mysql in order to work? Fedora rpms are claiming mysql dependencies. I'm sure you're aware of the long-lived arguement of postgresql v. mysql. If it wasn't your intention to force this, then please snarl at Red Hat. If it was your intention, then grrrrr! Thanks for this product. I like it for it's speed and stability. Jim Edwards

4 3

[Dovecot] bug: very strange behavior with pop3
by Yannick Majoros 12 Jul '05

12 Jul '05

Hello, We have some strange problem which could be related to authentication here. All our user info is in an openldap directory. We normally use pam/getpwent in dovecot to access our user accounts, via nss_ldap/pam_ldap, but we tried to connect directly to the ldap server, with the very same results. We have one user (out of 100) which just cannot use dovecot with pop3. His login/password are accepted, and then dovecot doesn't say anything. I am sure it isn't a client issue: same result with Eudora, Thunderbird and while directly connecting through openssl to POP3s port and "talking POP3". Here is some session transcript: +OK dovecot ready. USER rinstalle +OK PASS M=/)p365 +OK Logged in. And it then stops responding (without giving a reason, breaking the connection). Nothing in the logs, it sees this as a regular login and that's all... Now, it seems that when I copy this user in ldap, the new one occasionaly works. I first thought it did depend on the user name (uid or dn), but it doesn't seem to be the case. I think it is just random. Here is an ldif of this user: dn: uid=rinstalle,ou=divers,ou=login,ou=Autres,ou=Personnes,dc=inma,dc=ucl,dc= ac,dc=be uid: rinstalle cn: compte foireux homeDirectory: /home/xx sn: xxxx uidNumber: 9999 objectClass: top objectClass: person objectClass: inetOrgPerson objectClass: posixAccount gidNumber: 999 ... And getent result (with nss_ldap): #getent passwd rinstalle rinstalle:x:9999:999:compte foireux:/home/xx: To be complete, I should mention that it _does_ work when using local password files... I solved the user problem just by copying his entry a few times. Now, I don't think it is purely ldap-related, as the login _is_ accepted. Is there some guru out here who could help us? Thank you, -- ---------------------------------------------------------------------- Yannick Majoros http://www.inma.ucl.ac.be/~majoros Informaticien AUTO-INMA/FSA/UCL CSAM 4, avenue G. Lemaître B-1348 Louvain-la-Neuve Belgium Tel: +32-10-47.80.10 Fax: +32-10-47.21.80 #JAPH : http://www.inma.ucl.ac.be/~majoros/japh.txt Si vous avez des problèmes pour afficher ce message (accents qui ne passent pas, signature électronique, ...) votre système de mail n'est pas conforme aux standards, voir http://www.inma.ucl.ac.be/~majoros/email.html ----------------------------------------------------------------------

2 4

[Dovecot] weird IDLE behaviour
by Johannes Berg 12 Jul '05

12 Jul '05

Hi, So I was testing things with inotify notifications enabled and noticed that when I a) select a mailbox other than the inbox b) IDLE c) copy mail into the /new folder in that mailbox nothing happens! So I straced it and it always opens the inbox's new/ and cur/ directories for notifications. Is that the correct behaviour? I assumed that if I select some mailbox other than the inbox, IDLE should inform me of status updates in that box, since RFC 2177 says: The Internet Message Access Protocol [IMAP4] requires a client to poll the server for changes to the selected mailbox (new mail, deletions). Now, I get this behaviour by applying the attached patch. But even if I'm wrong, dovecot doesn't implement any sensible behaviour, as it only ever creates *any* notifications during IDLE when the INBOX is selected. [hm. note that I'm only testing maildir] johannes

2 1

[Dovecot] xinetd + dovecot
by vlad 12 Jul '05

12 Jul '05

Hello dovecot, Help me running imapd & pop3d server on xinetd. My file: # cat /etc/xinetd.d/pop-3 service pop3 { disable = no socket_type = stream protocol = tcp wait = no user = root server = /usr/libexec/dovecot/pop3-login } ####################################### # cat /etc/xinetd.d/imap service imap { disable = no socket_type = stream protocol = tcp wait = no user = root server = /usr/libexec/dovecot/imap-login flags = IPv4 log_type = FILE /var/log/mail/dovecot log_on_success = PID HOST USERID } ####################################### But... # nmap 192.168.1.1 Starting nmap 3.70 ( http://www.insecure.org/nmap/ ) at 2005-07-12 16:53 YEKST Interesting ports on myhost.ru (192.168.1.1): (The 1653 ports scanned but not shown below are in state: closed) PORT STATE SERVICE 25/tcp open smtp 80/tcp open http 110/tcp open pop3 143/tcp open imap 3128/tcp open squid-http ########### # telnet 192.168.1.1 143 Trying 192.168.1.1... Connected to 192.168.1.1. Escape character is '^]'. Fatal: EOF while reading environment from master Connection closed by foreign host. # telnet 192.168.1.1 110 Trying 192.168.1.1... Connected to 192.168.1.1. Escape character is '^]'. Fatal: EOF while reading environment from master Connection closed by foreign host. Help :) -- With best wishes, vlad mailto:faktroot@mail.ru System/Network Administrator TV/Video Engineer ICQ 163227020 ---------------------------------------------- В любом из нас спит гений. И с каждым днем все крепче...

2 1

[Dovecot] POP retrieval, then reading, of mail does not udpate server status.
by Paul Vatta 12 Jul '05

12 Jul '05

We are currently using the version of Dovecot (0.99.11) that comes with Redhat Enterpise Linux version 4, running on an IBM x445 server (8 CPU, hyperthreading on, 14GB RAM) using the maildir format. We have had to patch this with a change from 0.99.12 so that it doesn't incorrectly report SASL capability upon connection but otherwise it is the version supplied with the OS (we do this to ensure that we don't deviate from the supplied packages too much). The problem encountered is the status of emails on the server isn't being updated. The POP client (Eudora 6.2 in this instance) will retrieve the message, have the message read, apparently update the status on the server (via the "Check Mail" function), but yet the status on the server has not been updated as read (verified by going into our IMP Webmail client, and looking at the mail message in the mailstore - there is no ".S" extension). Using the IMAP protocol doesn't bring about this behaviour. The inconsistency The inconsistency between POP clients and the server status doesn't occur when it comes to deleting messages. Is this a bug, or have we misunderstood how the POP protocol works. Looking at the following: http://www.eudora.com/techsupport/kb/2587hq.html I'm guessing that the POP protocol doesn't update the status? Your confirmation would be most appreciated. Thanks, Paul P.S. As an aside, if you are hesitant about the move from mbox to maildir, don't consider this an obstacle. Our migration was painless and the benefits far outweigh the conversion effort. Dovecot has introduced huge improvements over our Qpopper/UW-IMAP configuration.

2 1

[Dovecot] Calypso or Opera Mail problem?
by Obantec Support 12 Jul '05

12 Jul '05

Hi Are there any know issues with dovecot using pop3 & (Calypso or Opera Mail) ? Jul 11 09:14:47 proteus2a pop3(cambcom_brianlj): File isn't in mbox format: /var/spool/mail/cambcom_brianlj Jul 11 09:14:47 proteus2a pop3(cambcom_brianlj): Couldn't open INBOX: Internal error occurred. Error report written to server log. [2005-07-11 09:14:47 there is a file cambcom_brianlj and using webmin or neomail the mails can be read. Mark -- Obantec Support

2 1

Re: [Dovecot] mysql
by Dominic Marks 12 Jul '05

12 Jul '05

On Tuesday 12 July 2005 14:55, Peter Evans wrote: > Tomi Hakala (tomi.hakala(a)clinet.fi) wrote: > > Jim Edwards wrote: > > > Does dovecot require mysql in order to work? > > > > For common email serving with IMAP and POP3, no. > > For IMAP and POP3 session proxying with 1.0-test releases, yes. > > Ew, YUCK. > Why does everyone think $DATABASE is the panacea for all ills? Why you think this is a misuse of a database? Shared network storage might not have been the original purpose, but most DBs can do a pretty good job of this. > Just because they can't/won't cope with multiplicity, does not > mean that X megabytes of general purpose database and all the > overheads have to be used. I can't tell if you have a problem with databases in general, or just the MySQL implementation from this. I guess that you could modify the code easily to use another DBMS which is much smaller such as sqlite. > If it's just proxying, why can't it speak LDAP, or even just a > plain file ... Why write code from scratch when you can use an API for a trusted piece of software which is likely to be available on most systems already? > P > > (I haven't looked at 1.0-test-903 yet, I think I'm still on 70 > something, but no way am I installing mysql ...) Cheers, -- Dominic Marks

1 0

[Dovecot] Mail spools keep getting corrupted with .99.x
by Matt Juszczak 12 Jul '05

12 Jul '05

Hi all, My mail spools (mbox format) keep getting corrupted with .99.x. I was thinking of running dovecot-stable-20050709.tar.gz ... is this fairly stable? Also, can I use the .99 config file with that code? Thanks! -MAtt

2 1

[Dovecot] Dovecot without a chroot
by Matt Juszczak 12 Jul '05

12 Jul '05

Hi all, We're running dovecot without a chroot (mail admin's request), but we're running it as a non-priv'd user with proper firewall setup. Does this seem to be an OK and average setup? Or is it considered a MUST to chroot something like the imapd daemon, etc. Thanks! -Matt

2 1

[Dovecot] multiple instances of dovecot ?
by Flavien 12 Jul '05

12 Jul '05

Hello, I got a dovecot server running on a Debian Linux machine. I'd like to run another instance of it. I start it with another config file with debug output on stderr. The auth parameters are different : dovecot1: Imapd only, listens on 143, auth=/etc/passwd dovecot2: Imapd only, listens on 144, auth=mysql It kinda works... But... How does one instance of it recognizes the right "imap-login" it should talk to ? What happens in my tests, you guess it: dovecot1 talks to imap-login2, trying to authenticate users that are in /etc/password against mysql... # dovecot -F -c dovecot-config2.conf dovecot: Jul 05 22:49:03 Info: Dovecot starting up dovecot-auth: Jul 05 22:49:04 Info: MySQL: connected to localhost dovecot-auth: Jul 05 22:49:04 Info: Login process 6 connected dovecot-auth: Jul 05 22:49:04 Info: Login process 7 connected dovecot-auth: Jul 05 22:49:04 Info: Login process 6 sent handshake: PID 26368 dovecot-auth: Jul 05 22:49:04 Info: Login process 8 connected dovecot-auth: Jul 05 22:49:04 Info: Login process 7 sent handshake: PID 26369 dovecot-auth: Jul 05 22:49:04 Info: Login process 8 sent handshake: PID 26370 dovecot-auth: Jul 05 22:49:27 Info: Login process 9 connected dovecot-auth: Jul 05 22:49:27 Info: Login process 9 sent handshake: PID 26374 dovecot-auth: Jul 05 22:50:02 Info: Login process 10 connected dovecot-auth: Jul 05 22:50:02 Info: Login process 10 sent handshake: PID 26402 dovecot-auth: Jul 05 22:50:02 Info: MySQL: Performing query: SELECT password FROM users WHERE uid='flavien' dovecot-auth: Jul 05 22:50:02 Info: mysql(flavien): Unknown user 'flavien' is not known to the sql db. It's thunderbird trying to get my regular mail using the config1 on port 143, and it has nothing to do with the instance 2 whose output I'm just looking at !!! Any hint ? A+ Flavien.

2 1

[Dovecot] Connection dropped by imap server Query: CAPABILITY
by Srinivas 12 Jul '05

12 Jul '05

Hi all, I have installed squirrelmail-1.4.4 and dovecot 0.9.11 on a debian sarge machine. The tls/ssl support is disabled from both squirrelmail and dovecot imap server. When i try to login i get the following error message: ERROR: ERROR : Connection dropped by imap-server. Query: CAPABILITY If i give wrong password, it gives the message Unknown user or password incorrect. which is fine. The file /var/log/mail.err, is appended with the following message: Jul 5 18:40:20 server dovecot: chdir(/home/username) failed with uid 1240: Permission denied Jul 5 18:40:20 server dovecot: child 20807 (imap) returned error 89 when i run the command: dovecot -c /etc/dovecot.conf it gives the following error: Fatal: listen(143) failed: Address already in use Later i enabled tls in squirrelmail and dovecot.conf. i got the following error: Warning: fgets(): SSL: fatal protocol error in /usr/share/squirrelmail/functions/imap_general.php on line 88 ERROR: ERROR : Connection dropped by imap-server. Query: CAPABILITY Any suggestions? Thank you Srinivas _______________________________________________ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com

2 1

[Dovecot] cannot download eMails from POP3
by Bastian 12 Jul '05

12 Jul '05

Hi dovecot users, IŽve got a problem with downloading emails: dovecot is installed and configured, I can login but I cannot download mails wich are at my harddisc. After trying to download an email thatŽs in the logfile: pop3-login: Jul 05 10:41:00 Info: Login: webmaster(a)myDomain.de [xx.xxx.xx.xxx] dovecot-auth: Jul 05 10:41:00 Info: Login process 9 disconnected dovecot-auth: Jul 05 10:41:00 Info: Login process 9 connected dovecot-auth: Jul 05 10:41:00 Info: Login process 9 sent handshake: PID 5754 QueryŽs are successfully, like they are required in dovecot-mysql.conf: First password clear, then home directory (/var/opt/vmail/myDomain.de/webmaster), uid and gid. My eMails are at /var/opt/vmail/myDomain.de/webmaster/Maildir/new, does dovecot automatically search for emails in Maildir/new? IŽve no idea, why I cannot download any eMails :( Can you help me? Thank you Bye, Bastian

2 1

[Dovecot] Altering newly created mailboxes
by Thomas Wouters 12 Jul '05

12 Jul '05

There seems to be a bug in updating uid/uidvalidity when copying mail to an empty or newly created mailbox: <new connection> . OK Logged in. . CREATE testfolder4 . OK Create completed. . SUBSCRIBE testfolder4 . OK Subscribe completed. . SELECT otherfolder * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 3 EXISTS * 0 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1121171128] UIDs valid * OK [UIDNEXT 4] Predicted next UID . OK [READ-WRITE] Select completed. . UID COPY 1 testfolder4 . NO Internal error occured. Refer to server log for more information. [2005-07-12 15:05:45] . SELECT testfolder4 . NO Internal error occured. Refer to server log for more information. [2005-07-12 15:05:49] <wait a while, doing nothing else> . SELECT testfolder4 * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 1 EXISTS * 1 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1121173545] UIDs valid * OK [UIDNEXT 2] Predicted next UID . OK [READ-WRITE] Select completed. The errorlog entries for those two errors are: Jul 12 15:05:45 dovecot0 dovecot: IMAP(ynnoz): Corrupted index file /var/run/dovecot-index/ynnoz/.testfolder4/dovecot.index: uid_validity = 0, next_uid = 2 Jul 12 15:05:49 dovecot0 dovecot: IMAP(ynnoz): Corrupted index file /var/run/dovecot-index/ynnoz/.testfolder4/dovecot.index: uid_validity = 0, next_uid = 2 I also managed to trigger an assertion failure this way, by trying another COPY after that first failure: . UID COPY 1 testfolder6 . NO Internal error occured. Refer to server log for more information. [2005-07-12 15:16:54] . UID COPY 1 testfolder6 Connection closed by foreign host. The errors for that connection are: Jul 12 15:16:54 dovecot0 dovecot: IMAP(ynnoz): Corrupted index file /var/run/dovecot-index/ynnoz/.testfolder6/dovecot.index: uid_validity = 0, next_uid = 2 Jul 12 15:17:01 dovecot0 dovecot: IMAP(ynnoz): Corrupted index file /var/run/dovecot-index/ynnoz/.testfolder6/dovecot.index: uid_validity = 0, next_uid = 2 Jul 12 15:17:01 dovecot0 dovecot: IMAP(ynnoz): file mail-index-transaction.c: line 128 (mail_index_buffer_convert_to_uids): assertion failed: (*seq != 0) Jul 12 15:17:01 dovecot0 dovecot: child 6666 (imap) killed with signal 6 Another assertion error I triggered was by trying another SELECT right after the failed SELECT (after the failed COPY): Jul 12 15:14:04 dovecot0 dovecot: IMAP(ynnoz): Maildir /var/spool/mail/.4a/S/tmp/ynnoz/.testfolder5 sync: UIDVALIDITY changed (1121174026 -> 1121174044) Jul 12 15:14:09 dovecot0 dovecot: IMAP(ynnoz): Corrupted transaction log file /var/run/dovecot-index/ynnoz/.testfolder5/dovecot.index.log: Append with UID 1, but next_uid = 2 Jul 12 15:14:12 dovecot0 dovecot: IMAP(ynnoz): file mail-index-view.c: line 595 (mail_index_view_open): assertion failed: (index->map != NULL) Jul 12 15:14:12 dovecot0 dovecot: child 6654 (imap) killed with signal 6 I was able to reproduce this on a near-virgin test76 -- it has one patch that should not interfere; we use default_mail_env = maildir:%Nu:INDEX=/var/run/dovecot-index/%u where %N is a new var_expand character that looks up the argument in a NIS map (we store actual maildir location there, for scalability.) The INDEX setting we use might matter, though. But it feels like a missing update-uid or invalidate-uid call somewhere, I just don't know where :) -- Thomas Wouters <thomas(a)xs4all.net> Hi! I'm a .signature virus! copy me into your .signature file to help me spread!

1 0

[Dovecot] Re: separate SSL certificates for pop3s and imaps
by sean finney 11 Jul '05

11 Jul '05

On Thu, Jul 07, 2005 at 08:58:35PM +0300, dovecot-request(a)dovecot.org wrote: > Hi, > > I'm migrating a uw-imap installation to dovecot. With uw-imap I had > different SSL certificates and keys for ipop3d and imapd. How can I > configure dovecot to do the same with its pop3s and imaps services? i run dovecot in a multihomed server with three different names: mail.foo.edu smtp.foo.edu imap.foo.edu which, for ssl purposes, means we need three different certs to keep applications happy. my approach is to start a seperate dovecot process for each address, and manage the configuration in three seperate files, each one telling dovecot to specifically bind to only one address, and use a seperate runtime directory specific to that address. so for example, in my initscript, instead of just doing something like: start() { echo -n $"Starting $prog: " daemon $prog -c /etc/dovecot.conf RETVAL=$? echo [ $RETVAL -eq 0 ] && touch /var/lock/subsys/$prog return $RETVAL } i do something like: start() { echo -n $"Starting $prog: " for s in imap mail smtp; do mkdir -p /var/run/dovecot/${s}.foo.edu daemon $prog -c /etc/dovecot/${s}.foo.edu.conf done RETVAL=$? echo [ $RETVAL -eq 0 ] && touch /var/lock/subsys/$prog return $RETVAL } where the value of the ssl cert config is different in each of the files. you could extend this to also have one config file to only listen for pop and the other only for imap. hth, sean

4 5

[Dovecot] Creating encrypted passwords for new users /etc/imap.passwd
by John_R._McWade 09 Jul '05

09 Jul '05

Hello. I've been attempting to locate information on how to actually create the encrypted passwords for a new user in /etc/imap.passwd file. Im really going into this blindly, not having ever used dovecot before, and really just need to be pointed to any existing resources on this topic. This is a setup of dovecot (w/ sendmail,squirrelmail) on FC2. I've got one successful auth so far as a test user, with their info cut/pasted directly from /etc/passwd (it works) whereas using {PLAIN}password causes dovecot to drop the connection with an aborted login. So what I'm actually looking for is a resource or a quick response regarding the actual creation of the encrypted password in /etc/passwd style. Any clues on where I should look for this info? John

2 1

[Dovecot] io leak when dnotify is enabled but not available
by Johannes Berg 08 Jul '05

08 Jul '05

Hi, When dnotify is enabled, but not in the kernel, there's an io leak: $ /sbin/dovecot --exec-mail imap * PREAUTH [CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS] Logged in as johannes a select inbox * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 787 EXISTS * 0 RECENT * OK [UIDVALIDITY 1106061449] UIDs valid * OK [UIDNEXT 790] Predicted next UID a OK [READ-WRITE] Select completed. b IDLE imap(johannes): Error: fcntl(F_NOTIFY) failed: Invalid argument imap(johannes): Error: fcntl(F_NOTIFY) failed: Invalid argument + idling DONE b OK Idle completed. q logout * BYE Logging out q OK Logout completed. imap(johannes): Warning: I/O leak: 0x10068ff0 (8) Attached patch fixes it, I hope the patch is correct :) johannes

1 0

[Dovecot] stat() failed with mbox /var/mail/%u
by Jungshik Shin 08 Jul '05

08 Jul '05

Hello, Over the last 12 hours or so, I've been wrestling with a mysterious dovecot issue. After upgrading a mail server I'm helping my friend with maintaining from Fedora Core1 to Fedora Core4, I realized that I couldn't use UW-IMAP4 anymore (well, I can compile it myself, but it turned out that UW-IMAP was the main cause of the server's having load average as high as 30 from time to time so that I decided to move onto dovecot). Although I loved to migrate to maildir, I didn't dare to tackle the migration (I have a lot more important things to do :-)) to maildir. Instead, I thought that dovecot's indexing of mbox files should make the performance of the server a lot better than UW-IMAP. (in addition, we upgraded the HW from P3 800MHz single to P4 dual 3GHz). Last night, I experimented with several mboxes of one user's account (INBOX in /var/mail/<userid> and others in ~/mail/) and it worked perfectly well. So, I moved mboxes of other users and launched 'dovecot' informing users that the mail server is back up again. However, it didn't work with inbox (for IMAP) and POP3. There's no problem accessing mail folders in '~/mail', but accessing /var/mail/%u (inbox for IMAP) and using the same folder with POP3 didn't work. The error I got in the log file is: Jul 8 01:17:24 biosoft dovecot: pop3-login: Login: xyz123 [::ffff:1xx.2yy.zz.178] Jul 8 01:17:24 biosoft dovecot: POP3(xyz123): stat() failed with mbox file /var/mail/xyz123: Permission denied Jul 8 00:34:45 biosoft dovecot: imap-login: Login: xyz123 [::ffff:1xx.2yy.zz.178] Jul 8 00:34:45 biosoft dovecot: auth(default): Error sending status request (Operation not permitted) Jul 8 00:34:45 biosoft dovecot: imap-login: Login: xyz123 [::ffff:1xx.2yy.zz.178] Jul 8 00:34:45 biosoft dovecot: IMAP(xyz123): stat() failed with mbox file /var/mail/xyz123: Permission denied ls -ld / /var /var/mail/ /var/mail/xyz123 drwxr-xr-x 23 root root 4096 Jul 7 19:28 / drwxr-xr-x 26 root root 4096 Jul 7 23:35 /var drwxrwxrwt 2 root mail 4096 Jul 8 00:36 /var/mail/ -rw-rw---- 1 xyz123 mail 130751237 Jul 7 23:37 /var/mail/xyz123 I tried various combinations of permissions and ownerships for /var/mail (1777, 2775) and /var/mail/<userid>, but nothing made any difference. I also tweaked mbox locking methods ('dotlock fcntl' or 'fcntl' alone) When I came across this problem with the latest stable (2005-07-06), I went back to FC4's default package (0.99??), but with a slightly different error message in the log file, basically I had the same problem. I kept the default values for most configuration parameters. What I changed are listed below: mail_extra_groups = mail pop3_uidl_format = %08Xv%08Xu protocols = imap imaps pop3s default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u Also attached is the entire /etc/dovecot.conf I'm really desperate to get some enlightening answers on this problem, for which I'll really appreciate you. Thanks tons in advance, Jungshik ## Dovecot 1.0 configuration file # '#' character and everything after it is treated as comments. Extra spaces # and tabs are ignored. If you want to use either of these explicitly, put the # value inside quotes, eg.: key = "# char and trailing whitespace " # Default values are shown after each value, it's not required to uncomment # any of the lines. Exception to this are paths, they're just examples # with real defaults being based on configure options. The paths listed here # are for configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var # --with-ssldir=/usr/share/ssl # Base directory where to store runtime data. #base_dir = /var/run/dovecot/ # Protocols we want to be serving: # imap imaps pop3 pop3s protocols = imap imaps pop3s # IP or host address where to listen in for connections. It's not currently # possible to specify multiple addresses. "*" listens in all IPv4 interfaces. # "[::]" listens in all IPv6 interfaces, but may also listen in all IPv4 # interfaces depending on the operating system. You can specify ports with # "host:port", although with multiple protocols you probably want to move this # setting inside protocol imap/pop3 { ... } section, so you can specify # different ports for IMAP/POP3. listen = [::] # IP or host address where to listen in for SSL connections. Defaults # to above if not specified. #ssl_listen = # Disable SSL/TLS support. #ssl_disable = no # PEM encoded X.509 SSL/TLS certificate and private key. They're opened before # dropping root privileges, so keep the key file unreadable by anyone but # root. Included doc/mkcert.sh can be used to easily generate self-signed # certificate, just make sure to update the domains in dovecot-openssl.cnf #ssl_cert_file = /usr/share/ssl/certs/dovecot.pem #ssl_key_file = /usr/share/ssl/private/dovecot.pem # File containing trusted SSL certificate authorities. Usually not needed. #ssl_ca_file = # Request client to send a certificate. #ssl_verify_client_cert = no # SSL parameter file. Master process generates this file for login processes. # It contains Diffie Hellman and RSA parameters. #ssl_parameters_file = /var/run/dovecot/ssl-parameters.dat # How often to regenerate the SSL parameters file. Generation is quite CPU # intensive operation. The value is in hours, 0 disables regeneration # entirely. #ssl_parameters_regenerate = 24 # SSL ciphers to use #ssl_cipher_list = all:!low # Disable LOGIN command and all other plaintext authentications unless # SSL/TLS is used (LOGINDISABLED capability). Note that 127.*.*.* and # IPv6 ::1 addresses are considered secure, this setting has no effect if # you connect from those addresses. #disable_plaintext_auth = yes # Use this logfile instead of syslog(). /dev/stderr can be used if you want to # use stderr for logging (ONLY /dev/stderr - otherwise it is closed). #log_path = # For informational messages, use this logfile instead of the default #info_log_path = # Prefix for each line written to log file. % codes are in strftime(3) # format. #log_timestamp = "%b %d %H:%M:%S " ## ## Login processes ## # Directory where authentication process places authentication UNIX sockets # which login needs to be able to connect to. The sockets are created when # running as root, so you don't have to worry about permissions. Note that # everything in this directory is deleted when Dovecot is started. login_dir = /var/run/dovecot-login # chroot login process to the login_dir. Only reason not to do this is if you # wish to run the whole Dovecot without roots. # http://wiki.dovecot.org/Rootless #login_chroot = yes # User to use for the login process. Create a completely new user for this, # and don't use it anywhere else. The user must also belong to a group where # only it has access, it's used to control access for authentication process. # Note that this user is NOT used to access mails. # http://wiki.dovecot.org/UserIds #login_user = dovecot # Set max. process size in megabytes. If you don't use # login_process_per_connection you might need to grow this. #login_process_size = 32 # Should each login be processed in it's own process (yes), or should one # login process be allowed to process multiple connections (no)? Yes is more # secure, espcially with SSL/TLS enabled. No is faster since there's no need # to create processes all the time. #login_process_per_connection = yes # Number of login processes to create. If login_process_per_user is # yes, this is the number of extra processes waiting for users to log in. #login_processes_count = 3 # Maximum number of extra login processes to create. The extra process count # usually stays at login_processes_count, but when multiple users start logging # in at the same time more extra processes are created. To prevent fork-bombing # we check only once in a second if new processes should be created - if all # of them are used at the time, we double their amount until limit set by this # setting is reached. This setting is used only if login_process_per_use is yes. #login_max_processes_count = 128 # Maximum number of connections allowed in login state. When this limit is # reached, the oldest connections are dropped. If login_process_per_user # is no, this is a per-process value, so the absolute maximum number of users # logging in actually login_processes_count * max_logging_users. #login_max_logging_users = 256 # Greeting message for clients. #login_greeting = Dovecot ready. ## ## Mail processes ## # Maximum number of running mail processes. When this limit is reached, # new users aren't allowed to log in. #max_mail_processes = 1024 # Show more verbose process titles (in ps). Currently shows user name and # IP address. Useful for seeing who are actually using the IMAP processes # (eg. shared mailboxes or if same uid is used for multiple accounts). #verbose_proctitle = no # Show protocol level SSL errors. #verbose_ssl = no # Valid UID range for users, defaults to 500 and above. This is mostly # to make sure that users can't log in as daemons or other system users. # Note that denying root logins is hardcoded to dovecot binary and can't # be done even if first_valid_uid is set to 0. #first_valid_uid = 500 #last_valid_uid = 0 # Valid GID range for users, defaults to non-root/wheel. Users having # non-valid GID as primary group ID aren't allowed to log in. If user # belongs to supplementary groups with non-valid GIDs, those groups are # not set. #first_valid_gid = 1 #last_valid_gid = 0 # Grant access to these extra groups for mail processes. Typical use would be # to give "mail" group write access to /var/mail to be able to create dotlocks. #mail_extra_groups = mail_extra_groups = mail # ':' separated list of directories under which chrooting is allowed for mail # processes (ie. /var/mail will allow chrooting to /var/mail/foo/bar too). # This setting doesn't affect login_chroot or auth_chroot variables. # WARNING: Never add directories here which local users can modify, that # may lead to root exploit. Usually this should be done only if you don't # allow shell access for users. See doc/configuration.txt for more information. #valid_chroot_dirs = # Default chroot directory for mail processes. This can be overridden for # specific users in user database by giving /./ in user's home directory # (eg. /home/./user chroots into /home). Note that usually there is no real # need to do chrooting, Dovecot doesn't allow users to access files outside # their mail directory anyway. #mail_chroot = # Default MAIL environment to use when it's not set. By leaving this empty # dovecot tries to do some automatic detection as described in # doc/mail-storages.txt. There's a few special variables you can use, eg.: # # %u - username # %n - user part in user@domain, same as %u if there's no domain # %d - domain part in user@domain, empty if there's no domain # %h - home directory # # See doc/variables.txt for full list. Some examples: # # default_mail_env = maildir:/var/mail/%1u/%u/Maildir # default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u # default_mail_env = mbox:/var/mail/%d/%n/:INDEX=/var/indexes/%d/%n # #default_mail_env = default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u # If you need to set multiple mailbox locations or want to change default # namespace settings, you can do it by defining namespace sections: # # You can have private, shared and public namespaces. The only difference # between them is how Dovecot announces them to client via NAMESPACE # extension. Shared namespaces are meant for user-owned mailboxes which are # shared to other users, while public namespaces are for more globally # accessible mailboxes. # # REMEMBER: If you add any namespaces, the default namespace must be added # explicitly, ie. default_mail_env does nothing unless you have a namespace # without a location setting. Default namespace is simply done by having a # namespace with empty prefix. #namespace private { # Hierarchy separator to use. You should use the same separator for all # namespaces or some clients get confused. '/' is usually a good one. #separator = / # Prefix required to access this namespace. This needs to be different for # all namespaces. For example "Public/". #prefix = # Physical location of the mailbox. This is in same format as # default_mail_env, which is also the default for it. #location = # There can be only one INBOX, and this setting defines which namespace # has it. #inbox = yes # If namespace is hidden, it's not advertised to clients via NAMESPACE # extension or shown in LIST replies. This is mostly useful when converting # from another server with different namespaces which you want to depricate # but still keep working. For example you can create hidden namespaces with # prefixes "~/mail/", "~%u/mail/" and "mail/". #hidden = yes #} # Space-separated list of fields to initially save into cache file. Currently # these fields are allowed: # # flags, date.sent, date.received, size.virtual, size.physical # mime.parts, imap.body, imap.bodystructure # # Different IMAP clients work in different ways, so they benefit from # different cached fields. Some do not benefit from them at all. Caching more # than necessary generates useless disk I/O, so you don't want to do that # either. # # Dovecot attempts to automatically figure out what client wants and it keeps # only that. However the first few times a mailbox is opened, Dovecot hasn't # yet figured out what client needs, so it may not perform optimally. If you # know what fields the majority of your clients need, it may be useful to set # these fields by hand. If client doesn't actually use them, Dovecot will # eventually drop them. # # Usually you should just leave this field alone. The potential benefits are # typically unnoticeable. #mail_cache_fields = # Space-separated list of fields that Dovecot should never save to cache file. # Useful if you want to save disk space at the cost of more I/O when the fields # needed. #mail_never_cache_fields = # Like mailbox_check_interval, but used for IDLE command. #mailbox_idle_check_interval = 30 # Allow full filesystem access to clients. There's no access checks other than # what the operating system does for the active UID/GID. It works with both # maildir and mboxes, allowing you to prefix mailboxes names with eg. /path/ # or ~user/. #mail_full_filesystem_access = no # Maximum allowed length for mail keyword name. It's only forced when trying # to create new keywords. #mail_max_keyword_length = 50 # Save mails with CR+LF instead of plain LF. This makes sending those mails # take less CPU, especially with sendfile() syscall with Linux and FreeBSD. # But it also creates a bit more disk I/O which may just make it slower. #mail_save_crlf = no # Use mmap() instead of read() to read mail files. read() seems to be a bit # faster with my Linux/x86 and it's better with NFS, so that's the default. # Note that OpenBSD 3.3 and older don't work right with mail_read_mmaped = yes. #mail_read_mmaped = no # Don't use mmap() at all. This is required if you store indexes in remote # filesystems (NFS or clustered filesystem). #mmap_disable = no # Don't write() to mmaped files. This is required for some operating systems # which use separate caches for them, such as OpenBSD. #mmap_no_write = no # Locking method for index files. Alternatives are fcntl, flock and dotlock. # Dotlocking uses some tricks which may create more disk I/O than other locking # methods. #lock_method = fcntl # By default LIST command returns all entries in maildir beginning with dot. # Enabling this option makes Dovecot return only entries which are directories. # This is done by stat()ing each entry, so it causes more disk I/O. # (For systems setting struct dirent->d_type, this check is free and it's # done always regardless of this setting) #maildir_stat_dirs = no # Copy mail to another folders using hard links. This is much faster than # actually copying the file. This is problematic only if something modifies # the mail in one folder but doesn't want it modified in the others. I don't # know any MUA which would modify mail files directly. IMAP protocol also # requires that the mails don't change, so it would be problematic in any case. # If you care about performance, enable it. #maildir_copy_with_hardlinks = no # Which locking methods to use for locking mbox. There's four available: # dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe # solution. If you want to use /var/mail/ like directory, the users # will need write access to that directory. # fcntl : Use this if possible. Works with NFS too if lockd is used. # flock : May not exist in all systems. Doesn't work with NFS. # lockf : May not exist in all systems. Doesn't work with NFS. # # You can use multiple locking methods; if you do the order they're declared # in is important to avoid deadlocks if other MTAs/MUAs are using multiple # locking methods as well. Some operating systems don't allow using some of # them simultaneously. #mbox_read_locks = fcntl #mbox_write_locks = dotlock fcntl mbox_read_locks = fcntl mbox_write_locks = fcntl # Maximum time in seconds to wait for lock (all of them) before aborting. #mbox_lock_timeout = 300 # If dotlock exists but the mailbox isn't modified in any way, override the # lock file after this many seconds. #mbox_dotlock_change_timeout = 30 # When mbox changes unexpectedly we have to fully read it to find out what # changed. If the mbox is large this can take a long time. Since the change # is usually just a newly appended mail, it'd be faster to simply read the # new mails. If this setting is enabled, Dovecot does this but still safely # fallbacks to re-reading the whole mbox file whenever something in mbox isn't # how it's expected to be. The only real downside to this setting is that if # some other MUA changes message flags, Dovecot doesn't notice it immediately. # Note that a full sync is done with SELECT, EXAMINE, EXPUNGE and CHECK # commands. #mbox_dirty_syncs = yes # Like mbox_dirty_syncs, but don't do full syncs even with SELECT, EXAMINE, # EXPUNGE or CHECK commands. If this is set, mbox_dirty_syncs is ignored. #mbox_very_dirty_syncs = no # Delay writing mbox headers until doing a full write sync (EXPUNGE and CHECK # commands and when closing the mailbox). This is especially useful for POP3 # where clients often delete all mails. The downside is that our changes # aren't immediately visible to other MUAs. #mbox_lazy_writes = yes # umask to use for mail files and directories #umask = 0077 # Drop all privileges before exec()ing the mail process. This is mostly # meant for debugging, otherwise you don't get core dumps. It could be a small # security risk if you use single UID for multiple users, as the users could # ptrace() each others processes then. #mail_drop_priv_before_exec = no # Set max. process size in megabytes. Most of the memory goes to mmap()ing # files, so it shouldn't harm much even if this limit is set pretty high. #mail_process_size = 256 # Log prefix for mail processes. See doc/variables.txt for list of possible # variables you can use. #mail_log_prefix = "%Us(%u): " ## ## IMAP specific settings ## protocol imap { # Login executable location. login_executable = /usr/libexec/dovecot/imap-login # IMAP executable location #mail_executable = /usr/libexec/dovecot/imap # This would write rawlogs into ~/dovecot.rawlog/ directory: mail_executable = /usr/libexec/dovecot/rawlog /usr/libexec/dovecot/imap # Maximum IMAP command line length in bytes. Some clients generate very long # command lines with huge mailboxes, so you may need to raise this if you get # "Too long argument" or "IMAP command line too large" errors often. #imap_max_line_length = 65536 # Support for dynamically loadable modules. #mail_use_modules = no #mail_modules = /usr/lib/dovecot/imap # Send IMAP capabilities in greeting message. This makes it unnecessary for # clients to request it with CAPABILITY command, so it saves one round-trip. # Many clients however don't understand it and ask the CAPABILITY anyway. #login_greeting_capability = no # Workarounds for various client bugs: # oe6-fetch-no-newmail: # Never send EXISTS/RECENT when replying to FETCH command. Outlook Express # seems to think they are FETCH replies and gives user "Message no longer # in server" error. Note that OE6 still breaks even with this workaround # if synchronization is set to "Headers Only". # outlook-idle: # Outlook and Outlook Express never abort IDLE command, so if no mail # arrives in half a hour, Dovecot closes the connection. This is still # fine, except Outlook doesn't connect back so you don't see if new mail # arrives. # netscape-eoh: # Netscape 4.x breaks if message headers don't end with the empty "end of # headers" line. Normally all messages have this, but setting this # workaround makes sure that Netscape never breaks by adding the line if # it doesn't exist. This is done only for FETCH BODY[HEADER.FIELDS..] # commands. Note that RFC says this shouldn't be done. # tb-negative-fetch: # Thunderbird sometimes messed up some calculations and wants to read # the message past it's end, giving negative size to FETCH BODY[]<..> # command. This workaround just hides the error message. #imap_client_workarounds = outlook-idle } ## ## POP3 specific settings ## protocol pop3 { # Login executable location. #login_executable = /usr/libexec/dovecot/pop3-login # POP3 executable location #mail_executable = /usr/libexec/dovecot/pop3 # Don't try to set mails non-recent or seen with POP3 sessions. This is # mostly intended to reduce disk I/O. With maildir it doesn't move files # from new/ to cur/, with mbox it doesn't write Status-header. #pop3_no_flag_updates = no # Support LAST command which exists in old POP3 specs, but has been removed # from new ones. Some clients still wish to use this though. Enabling this # makes RSET command clear all \Seen flags from messages. #pop3_enable_last = no # POP3 UIDL format to use. You can use following variables: # # %v - Mailbox UIDVALIDITY # %u - Mail UID # %m - MD5 sum of the mailbox headers in hex (mbox only) # %f - filename (maildir only) # # If you want UIDL compatibility with other POP3 servers, use: # UW's ipop3d : %08Xv%08Xu # Courier version 0 : %f # Courier version 1 : %u # Courier version 2 : %v-%u # Cyrus (<= 2.1.3) : %u # Cyrus (>= 2.1.4) : %v.%u # # Note that Outlook 2003 seems to have problems with %v.%u format which is # Dovecot's default, so if you're building a new server it would be a good # idea to change this. %08Xu%08Xv should be pretty fail-safe. pop3_uidl_format = %08Xv%08Xu # Support for dynamically loadable modules. #mail_use_modules = no #mail_modules = /usr/lib/dovecot/pop3 # Workarounds for various client bugs: # outlook-no-nuls: # Outlook and Outlook Express hang if mails contain NUL characters. # This setting replaces them with 0x80 character. # oe-ns-eoh: # Outlook Express and Netscape Mail breaks if end of headers-line is # missing. This option simply sends it if it's missing. #pop3_client_workarounds = } ## ## Authentication processes ## # You can have multiple authentication processes. With plaintext authentication # the password is checked against each process, the first one which succeeds is # used. This is useful if you want to allow both system users (/etc/passwd) # and virtual users to login without duplicating the system users into virtual # database. # Executable location #auth_executable = /usr/libexec/dovecot/dovecot-auth # Set max. process size in megabytes. #auth_process_size = 256 # Authentication cache size in kilobytes. #auth_cache_size = 0 # Time to live in seconds for cached data. After this many seconds a cached # record is forced out of cache. #auth_cache_ttl = 3600 # Space separated list of realms for SASL authentication mechanisms that need # them. You can leave it empty if you don't want to support multiple realms. # Many clients simply use the first one listed here, so keep the default realm # first. #auth_realms = # Default realm/domain to use if none was specified. This is used for both # SASL realms and appending @domain to username in plaintext logins. #auth_default_realm = # List of allowed characters in username. If the user-given username contains # a character not listed in here, the login automatically fails. This is just # an extra check to make sure user can't exploit any potential quote escaping # vulnerabilities with SQL/LDAP databases. If you want to allow all characters, # set this value to empty. #auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ # Username character translations before it's looked up from databases. The # value contains series of from -> to characters. For example "#@/@" means # that '#' and '/' characters are translated to '@'. #auth_username_translation = # Username to use for users logging in with ANONYMOUS SASL mechanism #auth_anonymous_username = anonymous # More verbose logging. Useful for figuring out why authentication isn't # working. #auth_verbose = no # Even more verbose logging for debugging purposes. Shows for example SQL # queries. #auth_debug = no auth default { # Space separated list of wanted authentication mechanisms: # plain digest-md5 cram-md5 apop anonymous mechanisms = plain # Password database specifies only the passwords for users. # http://wiki.dovecot.org/Authentication # passwd: /etc/passwd or similiar, using getpwnam() # shadow: /etc/shadow or similiar, using getspnam() # pam [<service> | *]: PAM authentication # checkpassword <path>: checkpassword executable authentication # passwd-file <path>: passwd-like file with specified location # vpopmail: vpopmail authentication # ldap <config path>: LDAP, see doc/dovecot-ldap.conf # sql <config path>: SQL database, see doc/dovecot-sql.conf passdb = pam # User database specifies where mails are located and what user/group IDs # own them. For single-UID configuration use "static". # http://wiki.dovecot.org/Authentication # http://wiki.dovecot.org/VirtualUsers # passwd: /etc/passwd or similiar, using getpwnam() # passwd-file <path>: passwd-like file with specified location # static uid=<uid> gid=<gid> home=<dir template>: static settings # vpopmail: vpopmail library # ldap <config path>: LDAP, see doc/dovecot-ldap.conf # sql <config path>: SQL database, see doc/dovecot-sql.conf userdb = passwd # User to use for the process. This user needs access to only user and # password databases, nothing else. Only shadow and pam authentication # requires roots, so use something else if possible. Note that passwd # authentication with BSDs internally accesses shadow files, which also # requires roots. Note that this user is NOT used to access mails. # That user is specified by userdb above. user = root # Directory where to chroot the process. Most authentication backends don't # work if this is set, and there's no point chrooting if auth_user is root. #chroot = # Number of authentication processes to create #count = 1 # Require a valid SSL client certificate or the authentication fails. #ssl_require_client_cert = no } # PAM doesn't provide a way to get uid, gid or home directory. If you don't # want to use a separate user database (passwd usually), you can use static # userdb. #auth onlypam { # mechanisms = plain # userdb = static uid=500 gid=500 home=/var/mail/%u # passdb = pam # user = dovecot-auth #} #auth ldap { # mechanisms = plain # userdb = ldap /etc/dovecot-ldap.conf # passdb = ldap /etc/dovecot-ldap.conf # user = dovecot-auth #} #auth virtualfile { # mechanisms = plain digest-md5 # userdb = passwd-file /etc/passwd.imap # passdb = passwd-file /etc/passwd.imap # user = dovecot-auth #} # It's possible to export the authentication interface to other programs, # for example SMTP server which supports talking to Dovecot. Client socket # handles the actual authentication - you give it a username and password # and it returns OK or failure. So it's pretty safe to allow anyone access to # it. Master socket is used to a) query if given client was successfully # authenticated, b) userdb lookups. # listener sockets will be created by Dovecot's master process using the # settings given inside the auth section #auth default_with_listener { # mechanisms = plain # passdb = passwd # userdb = pam # socket listen { # master { # path = /var/run/dovecot/auth-master # #mode = 0600 # # Default user/group is the one who started dovecot-auth (root) # #user = # #group = # } # client { # path = /var/run/dovecot-auth-client # mode = 0660 # } # } #} # connect sockets are assumed to be already running, Dovecot's master # process only tries to connect to them. They don't need any other settings # than path for the master socket, as the configuration is done elsewhere. # Note that the client sockets must exist in login_dir. #auth external { # socket connect { # master { # path = /var/run/dovecot/auth-master # } # } #}

2 2

[Dovecot] "Leave a copy on server" not marking messages as read...
by Matt Juszczak 07 Jul '05

07 Jul '05

Hi all, Our customers who have "Leave a copy on server" with POP3 continue to check their email, and each time they check it it re-downloads all emails (so it doesn't seem to be updating those messages already downloaded). Any ideas? Thanks! -Matt

1 0

[Dovecot] IMAP Folders
by Matt Juszczak 07 Jul '05

07 Jul '05

Hi all, We're using the mbox format and I tried setting up IMAP on my boss's computer tonight. He likes subfolders, and although they work, he can't seem to remove subfolders once he created them, nor create new folders without using something other than his mail client (like mkdir from the command line). Any ideas on this? Does dovecot just not officially support IMAP and subfolders with the mbox format? Or could it be a permissions issue? -Matt

2 1

[Dovecot] RE: dovecot not able to access sentmail folder in home directory(chdir)
by vineet 07 Jul '05

07 Jul '05

problem is solved the problem was with the access permissions to the folder having the users' folders make sure that dovecot has the permission to access the folders containg the users' folders vineet _______________________________________________ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com

1 0