- dovecot - dovecot.org

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 23 Jul '05

23 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