- dovecot - dovecot.org

[Dovecot] 0.99.13-rc2
by Timo Sirainen 21 Dec '04

21 Dec '04

http://dovecot.org/rc/ Another one. Unless there are some bugs this will be the final version in a few days. * GNUTLS support hasn't been working for a while, so it's not even tried to be used anymore unless explicitly wanted. + Added CRAM-MD5 authentication mechanism. Patch by Joshua Goodall + Added SMD5 password scheme support and changed MD5 scheme with LDAP to act as PLAIN-MD5 rather than as MD5crypt. Patch by Joshua Goodall + Workaround for some POP3 client bugs: if message doesn't contain the "end of headers" empty line, add it automatically. - SQL and LDAP authentication was broken - SEARCH UNKEYWORD wasn't working

2 1

[Dovecot] Stalled Authentication, Great Clues
by Richard Petty 21 Dec '04

21 Dec '04

I've just installed Dovecot 0.99.12.1 onto a White Box EL 3 server. I'm mostly following the email server setup instructions at http://www.wanderingbarque.com/mailserver.html and getting Dovecot to work is the last task to complete. I've compiled Dovecot with LDAP support. I'm authenticating Postfix via SASL to the LDAP database just fine, and I also authenticate and manipulate LDAP info from JAMM very well, too. However, Dovecot authentication seem to hang up when a correct password is submitted (POP or IMAP... it doesn't matter). Here's an example of the problem: [root@kayak /etc] telnet localhost 110 Trying 127.0.0.1... Connected to localhost.bramble.com (127.0.0.1). Escape character is '^]'. +OK dovecot ready. user repetty(a)bizzy.mine.nu +OK pass bogeybogey sadf hello? ^] telnet> q Connection closed. As you can see, once I hit the return key to submit the password I do not get another prompt. In fact, Dovecot doesn't respond at all although it seems to respond to the escape character just fine. Additionally, dovecot-auth starts soaking up CPU time... until I kill the process (dovecot-auth must be killed manually.) 22:15:32 up 32 days, 21:40, 5 users, load average: 1.05, 1.02, 0.98 121 processes: 119 sleeping, 2 running, 0 zombie, 0 stopped CPU states: cpu user nice system irq softirq iowait idle total 50.5% 0.0% 0.5% 0.0% 0.0% 0.0% 48.8% cpu00 66.7% 0.0% 0.0% 0.0% 0.0% 0.0% 33.2% cpu01 34.4% 0.0% 1.1% 0.0% 0.0% 0.0% 64.3% Mem: 318260k av, 300740k used, 17520k free, 0k shrd, 24380k buff 141540k actv, 28364k in_d, 3864k in_c Swap: 655352k av, 80868k used, 574484k free 94736k cached PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND 23846 dovecot 25 0 1928 1928 1352 R 49.7 0.6 27:30 0 dovecot-auth 23847 dovecot 15 0 1072 1072 868 S 0.0 0.3 0:00 1 imap-login 23848 dovecot 15 0 1072 1072 868 S 0.0 0.3 0:00 1 imap-login 23849 dovecot 15 0 1160 1160 936 S 0.0 0.3 0:00 1 imap-login 23850 dovecot 15 0 1136 1136 928 S 0.0 0.3 0:00 0 pop3-login 23851 dovecot 15 0 1140 1140 928 S 0.0 0.3 0:00 1 pop3-login 23852 dovecot 15 0 1140 1140 928 S 0.0 0.3 0:00 0 pop3-login 23858 dovecot 15 0 1068 1068 868 S 0.0 0.3 0:00 0 imap-login 23870 dovecot 15 0 1064 1064 864 S 0.0 0.3 0:00 1 pop3-login 23886 dovecot 15 0 1060 1060 864 S 0.0 0.3 0:00 1 pop3-login 23916 dovecot 15 0 1064 1064 864 S 0.0 0.3 0:00 0 pop3-login From the client's point of view, the server never seems to come back after the account password is submitted. Dovecot's log shows that it eventually times out the client, although the client never seems to get wind of this: pop3-login: Dec 19 22:13:08 Info: Disconnected: Inactivity [192.168.0.6] I know that Dovecot is connecting to the LDAP server because if I mess up the Dovecot LDAP password in the dovecot.conf file I get an authentication error (as I should): dovecot-auth: Dec 19 20:52:19 Error: LDAP: ldap_simple_bind_s() failed (dn cn=dovecot,dc=dillo,dc=info): Invalid credentials Again, if client submits an incorrect email account password everything works as it should: Dovecot tells the client that the password is incorrect, over and over, if necessary. However, if the password is entered correctly then Dovecot hangs up for good. --Richard

2 2

[Dovecot] Postfix + dovecot-auth
by Timo Sirainen 20 Dec '04

20 Dec '04

I wrote a patch to Postfix which now supports SMTP AUTH using dovecot-auth. This time it doesn't need any Dovecot libraries and it's backwards compatible with Cyrus SASL by default. You'll just need to set one variable in Postfix config file to enable it. Patches and instructions in: http://dovecot.org/patches/postfix/ Not very well tested yet though. And it doesn't work with 1.0-test59, you'll need to have at least today's nightly snapshot.

1 0

[Dovecot] 1.0-test59 on OpenBSD: Undefined symbol `_strtoull' referenced
by Wouter Van Hemel 20 Dec '04

20 Dec '04

Hello, dovecot-1.0-test59 compilation fails on an old OpenBSD version with: var-expand.c:19: Undefined symbol `_strtoull' referenced from text segment collect2: ld returned 1 exit status *** Error code 1 Stop in /root/dovecot-1.0-test59/src/auth (line 392 of Makefile). [...] OpenBSD should have strtoull starting from about version 3.2.

3 4

[Dovecot] Just delete that index
by Doug Luce 20 Dec '04

20 Dec '04

I get a few messages of this ilk each day: Dec 16 01:56:31 aurora dovecot: IMAP(doug): Corrupted index cache file /home/doug/Maildir/.users.joe/dovecot.index.cache: indexid changed I usually address this by deleting dovecot.* in the directory of issue. I was thinking that I could instead just have the server delete these files and attempt to recreate them, and skipping that error message unless the re-created files are also corrupted. Any problems with this approach? Thanks, Doug

2 2

[Dovecot] panic with search
by Kazuo Moriwaka 20 Dec '04

20 Dec '04

Hello, My imap daemon get SIGABRT with following message. "pool_data_stack_realloc(): stack frame changed" This is caused with cvs head sources.(and or not with my last 2 patches.) This causes while doing search command. This is IMAP command log: --------------------------------------------------------------------------- * PREAUTH [CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS] Logged in as mailtest * select inbox * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 135 EXISTS * 0 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1102574212] UIDs valid * OK [UIDNEXT 139] Predicted next UID * OK [READ-WRITE] Select completed. * search body "hoge" imap(mailtest): Panic: pool_data_stack_realloc(): stack frame changed Aborted --------------------------------------------------------------------------- I'll attach backtrace just before print panic messages. If maildir and messages are need for debug, please request to me. thanks, -- Kazuo Moriwaka moriwaka(a)valinux.co.jp (gdb) bt #0 printf_string_upper_bound (format_p=0xbffff848, args=0xbffff884 "`$B}?(x??(Bq\n\b$B8y(B\f\b\210w\f\b$B8x(B?\017e\n\b\210w\f\b$BPw(B\f\b") at printf-upper-bound.c:78 #1 0x080a7640 in default_handler (prefix=0x80c226a "Panic: ", f=0x41149fe0, format=0x80c3300 "pool_data_stack_realloc(): stack frame changed", args=0xbffff884 "`$B}?(x??(Bq\n\b$B8y(B\f\b\210w\f\b$B8x(B?\017e\n\b\210w\f\b$BPw(B\f\b") at failures.c:99 #2 0x080a76b8 in default_panic_handler (format=0x80c3300 "pool_data_stack_realloc(): stack frame changed", args=0xbffff884 "`$B}?(x??(Bq\n\b$B8y(B\f\b\210w\f\b$B8x(B?\017e\n\b\210w\f\b$BPw(B\f\b") at failures.c:115 #3 0x080a786a in i_panic (format=0x80c3300 "pool_data_stack_realloc(): stack frame changed") at failures.c:173 #4 0x080afd33 in pool_data_stack_realloc (pool=0x80c7788, mem=0x80c77d0, old_size=256, new_size=8192) at mempool-datastack.c:110 #5 0x080a650f in buffer_alloc (buf=0x80c77b0, size=8192) at buffer.c:32 #6 0x080a6c74 in buffer_check_limits (buf=0x80c77b0, pos=1, data_size=4096) at buffer.c:57 #7 0x080a6a49 in buffer_copy (_dest=0x80c77b0, dest_pos=1, _src=0x80c7950, src_pos=0, copy_size=4096) at buffer.c:227 #8 0x080a6acd in buffer_append_buf (dest=0x80c77b0, src=0x80c7950, src_pos=0, copy_size=4096) at buffer.c:240 #9 0x080a0a71 in message_search_body_block (ctx=0xbffffa00, block=0x80c7950) at message-body-search.c:229 #10 0x080a0e4e in message_search_body (ctx=0xbffffa00, input=0x80de170, part=0x80dede0) at message-body-search.c:336 #11 0x080a1135 in message_body_search_ctx (ctx=0xbffffa60, input=0x80ddf08, part=0x80dede0) at message-body-search.c:408 #12 0x080a11ff in message_body_search (key=0x80d4f60 "hoge", charset=0x0, unknown_charset=0xbffffabc, input=0x80ddf08, part=0x80dede0, search_header=0) at message-body-search.c:433 #13 0x0807f58a in search_body (arg=0x80d4f38, context=0xbffffb40) at index-search.c:467 #14 0x08098278 in search_arg_foreach (arg=0x80d4f38, callback=0x807f4f0 <search_body>, context=0xbffffb40) at mail-search.c:81 #15 0x080982a8 in mail_search_args_foreach (args=0x80d4f38, callback=0x807f4f0 <search_body>, context=0xbffffb40) at mail-search.c:93 #16 0x0807f82b in search_arg_match_text (args=0x80d4f38, ctx=0x80dec88) at index-search.c:545 #17 0x08080011 in search_match_next (ctx=0x80dec88) at index-search.c:813 #18 0x080800bf in index_storage_search_next (_ctx=0x80dec88) at index-search.c:837 #19 0x08098e38 in mailbox_search_next (ctx=0x80dec88) at mail-storage.c:397 #20 0x0805787c in imap_search (client=0x80d0cf8, charset=0x0, sargs=0x80d4f38) at cmd-search.c:32 #21 0x08057baf in cmd_search (client=0x80d0cf8) at cmd-search.c:97 #22 0x08059c2e in client_handle_input (client=0x80d0cf8) at client.c:324 #23 0x08059d2e in _client_input (context=0x80d0cf8) at client.c:368 #24 0x080ae2f8 in io_loop_handler_run (ioloop=0x80cfa58) at ioloop-poll.c:184 #25 0x080ad4c1 in io_loop_run (ioloop=0x80cfa58) at ioloop.c:218 #26 0x080637d0 in main (argc=1, argv=0xbffffdd4, envp=0xbffffddc) at main.c:224 (gdb) up #1 0x080a7640 in default_handler (prefix=0x80c226a "Panic: ", f=0x41149fe0, format=0x80c3300 "pool_data_stack_realloc(): stack frame changed", args=0xbffff884 "`$B}?(x??(Bq\n\b$B8y(B\f\b\210w\f\b$B8x(B?\017e\n\b\210w\f\b$BPw(B\f\b") at failures.c:99 99 (void)printf_string_upper_bound(&format, args); (gdb) up #2 0x080a76b8 in default_panic_handler (format=0x80c3300 "pool_data_stack_realloc(): stack frame changed", args=0xbffff884 "`$B}?(x??(Bq\n\b$B8y(B\f\b\210w\f\b$B8x(B?\017e\n\b\210w\f\b$BPw(B\f\b") at failures.c:115 115 (void)default_handler("Panic: ", log_fd, format, args); (gdb) up #3 0x080a786a in i_panic (format=0x80c3300 "pool_data_stack_realloc(): stack frame changed") at failures.c:173 173 panic_handler(format, args); (gdb) up #4 0x080afd33 in pool_data_stack_realloc (pool=0x80c7788, mem=0x80c77d0, old_size=256, new_size=8192) at mempool-datastack.c:110 110 i_panic("pool_data_stack_realloc(): stack frame changed"); (gdb) list 105 /* @UNSAFE */ 106 if (new_size == 0 || new_size > SSIZE_T_MAX) 107 i_panic("Trying to allocate %"PRIuSIZE_T" bytes", new_size); 108 109 if (dpool->data_stack_frame != data_stack_frame) 110 i_panic("pool_data_stack_realloc(): stack frame changed"); 111 112 if (mem == NULL) 113 return pool_data_stack_malloc(pool, new_size); 114 (gdb) p dpool $18 = (struct datastack_pool *) 0x80c7788 (gdb) p *dpool $19 = {pool = {get_name = 0x80afbd5 <pool_data_stack_get_name>, ref = 0x80afbdf <pool_data_stack_ref>, unref = 0x80afc0d <pool_data_stack_unref>, malloc = 0x80afc70 <pool_data_stack_malloc>, free = 0x80afcc4 <pool_data_stack_free>, realloc = 0x80afcec <pool_data_stack_realloc>, clear = 0x80afdd0 <pool_data_stack_clear>, alloconly_pool = 1, datastack_pool = 1}, refcount = 1, data_stack_frame = 5} (gdb) p *dpool->data_stack_frame Cannot access memory at address 0x5 (gdb) p dpool->data_stack_frame $20 = 5 (gdb) p data_stack_frame $21 = 7

2 1

[Dovecot] Error indexing mbox file /var/mail/seb: LF not found where expected
by Sebastian 20 Dec '04

20 Dec '04

Howdy all, Dec 19 14:24:53 dev imap(seb): Error indexing mbox file /var/mail/seb: LF not found where expected I just installed version dovecot-0.99.12.1 for the first time on FreeBSD 4.10 stable. This error occurs when I try to check my mail from a remote client and I have new messages. Here is my configuration: http://unf.be/dovecot.conf It's very close to the default install. In attempts to remedy the problem, I set "mail_read_mmaped = no", but the problem persists. I'm not sure if it's relevent, but I'm receiving mail with postfix and my mail file has lines that end with \r\n Thanks in advance for any help Sebastian -- ------------- buddhahead(a)gmail.com

1 1

[Dovecot] Auth Mechanism
by Tom Allison 19 Dec '04

19 Dec '04

Uh... I'm trying to debug an application and keep running into this: DEBUG: Sending: 1 AUTHENTICATE CRAM-MD5 DEBUG: Sent 25 bytes DEBUG: Read: 1 NO Authentication failed: Unsupported authentication mechanism DEBUG: Read: * BYE Disconnected for inactivity. So is this really asking for "digest-md5" or am I S.O.L? IIRC these are different protocols, but it's a bit early for my head to get this together.

2 2

[Dovecot] Authentication problems
by Rory Campbell-Lange 19 Dec '04

19 Dec '04

Hi. I aim to provide pop3 and imap services to a few users. At the moment I only offer imap for squirrelmail users. However, I can't login successfully for pop3. It appears to be trying to auth against PAM, rather than directly using the passwd-file. Thoughts? Thanks, Rory Config: uthenticatprotocols = pop3 imap ssl_disable = yes login = imap login = pop3 mail_extra_groups = mail auth = default auth_mechanisms = plain auth_userdb = passwd-file /etc/dovecot.passwd.conf auth_user = root auth_verbose = yes Password file: # squirrelmail imap users user1:xe9l8sIMpcTsg:1008:1008::::chroot:Maildir:/home/cmp/Maildir/user1 user2:m7VKCgWVmZYMY:1008:1008::::chroot:Maildir:/home/cmp/Maildir/user2 user3:ELh9mthLVjEG2:1008:1008::::chroot:Maildir:/home/cmp/Maildir/user3 # normal users xyz1:QtR.iN1DbL/UM:1004:1004::::chroot:mbox:/var/mail/xyz1 xyz2:y38.qLIgrvYic:1002:1002::::~/Mail:mbox:/var/mail/xyz2:INDEX=/home/xyz2 ... Problem shown in log: Dec 19 16:45:30 localhost dovecot-auth: PAM: pam_authenticate(xyz2) failed: User not known to the underlying authentication module Dec 19 16:45:30 localhost pop3-login: Aborted login [ipaddress] -- Rory Campbell-Lange <rory(a)campbell-lange.net> <www.campbell-lange.net>

2 1

[Dovecot] 1.0-test59
by Timo Sirainen 19 Dec '04

19 Dec '04

http://dovecot.org/test/ No-one had been testing 1.0-tests with Evolution? It was pretty much completely broken with messages having attachments. - test58's output stream code change were entirely wrong and caused bad breakages with mbox. - Named pipes are now treated as write-only mboxes (blocks if no-one is reading, perhaps it should timeout in a few seconds?) - FETCH BODY[n.xxx] replies were all wrong - LDAP authentication was crashing - pop3_uidl_format=%f from Andrey test60 will probably have keyword support. Its index file code is already working, with ability to set over 500k different keywords per mailbox (because message record size is limited to 65535 bytes - should be enough for everyone :). Code is still missing to notify other session about keyword changes, and storing the keywords into mbox/maildir. For mbox I can use X-Keywords header. There should probably be some configurable limit to how many keywords to set per mailbox.. Dovecot shouldn't mind if the X-Keywords header is huge, but other programs might. For maildir then.. I think I'll just implement it backwards compatible with 0.99.x, ie. store in maildir filename with a-z letters. That would make max. 26 keywords per mailbox. Except maybe I shouldn't limit it to that. The rest could be stored only in indexes. That however would make it necessary to keep indexes backwards compatible forever so data is not lost.

3 2