- dovecot - dovecot.org

[Dovecot] 0.99.10-test12
by Timo Sirainen 19 Jun '03

19 Jun '03

http://dovecot.procontrol.fi/test/ I should have released 0.99.10 already I think.. There's just two annoying problems that I think should be fixed first: - PAM: If user gives a wrong password, dovecot-auth process sleeps for two seconds, blocking everyone else who are trying to authenticate at the time. So using PAM isn't very good idea at the moment. - OpenSSL problems. Are they really my fault? I have no idea what I could be doing wrong. Maybe some compile option is wrong? Also I should try to use pkg-config to get compile flags if it exists in configure. The new things in -test12 then: - We sync mailbox less often. Only NOOP and CHECK will force a mailbox sync now. Other commands do it also but only if mailbox hasn't been synced in last 5 seconds. Maybe this reduces some I/O. At least a bit less stat() calls :) - Dirty maildir flag flushing work now. Meaning that if you change message flags but rename() fails because you're out of quota, the flags are changed in index file and dirty-flag is set. Once in a while it tries to flush the dirty flags by rename()ing the file again. - IMAP RFC requires that NUL characters are never sent to client. We do now the same as UW-IMAP by sending ascii 128 chars instead.

5 11

[Dovecot] 0.99.10-test13
by Timo Sirainen 18 Jun '03

18 Jun '03

http://dovecot.procontrol.fi/test/ - Hopefully OpenSSL is fixed :) - We sometimes produced invalid ENVELOPE with 8bit headers. That could really have broken things (broke it in test12). So, what's left is to make PAM work well..

4 3

[Dovecot] Multiple auth howto
by ohp＠pyrenet.fr 18 Jun '03

18 Jun '03

Howdi. I'm new to dovcot (just succeded in compiling on unixware 713 today) I'm noww configuring for tests on other port. The sample configuration file is pretty well documented, however, I don't understand how I can firstt authenticate against passwd/shadow if not found against pgsql. What's the syntax? Please cc responses as I'm subscribed to digest TIA Reghards -- Olivier PRENANT Tel: +33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: ohp(a)pyrenet.fr ------------------------------------------------------------------------------ Make your life a dream, make your dream a reality. (St Exupery)

3 4

[Dovecot] imaps now works!
by Farkas Levente 18 Jun '03

18 Jun '03

thanks! -- Levente "Si vis pacem para bellum!"

1 0

[Dovecot] SASL Support
by Ken Crain 16 Jun '03

16 Jun '03

I need to support Outlook/Outlook Express users of Sendmail with SMTP Authorization. From what I can see, the LOGIN method available in Outlook/Outlook Express is the only applicable way to go at this time. It appears it is not supported in Dovecot right now. Is this correct and, if so, how would I go about adding this support?

2 1

[Dovecot] crash on LIST command
by Wouter Van Hemel 16 Jun '03

16 Jun '03

Hello, I'm experiencing a reproducable crash in the imap daemon of dovecot 0.99.9.1 when running the next commands (sniffed from a sylpheed session): [cocaine:~] telnet ice 143 Trying 192.168.196.1... Connected to ice. Escape character is '^]'. * OK dovecot ready. 1 NOOP 1 OK NOOP completed. 2 LOGIN wouter password 2 OK Logged in. 3 NAMESPACE 3 BAD Error in IMAP command: Unknown command 'NAMESPACE' 4 LIST "" "" * LIST (\Noselect) "/" "" 4 OK List completed. 5 LIST "" "%" Connection closed by foreign host. [cocaine:~] _ The log shows this: Jun 16 02:48:09 ice imap-login: Login: wouter [192.168.196.5] Jun 16 02:48:19 ice dovecot: child 1870 (imap) killed with signal 11 Looks like a segfault. [...] Core was generated by `imap'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/lib/libc.so.4...done. Reading symbols from /usr/libexec/ld-elf.so.1...done. #0 0x8058469 in mbox_list_inbox (ctx=0x8098080) at mbox-list.c:333 333 if (ctx->dir->virtual_path != NULL) (gdb) bt #0 0x8058469 in mbox_list_inbox (ctx=0x8098080) at mbox-list.c:333 #1 0x805809e in mbox_list_mailbox_next (ctx=0x8098080) at mbox-list.c:193 #2 0x804b75a in list_unsorted (client=0x8096080, ctx=0x8098080, reply=0x807ed06 "LIST", sep=0xbfbffac4 "/", listext=0) at cmd-list.c:234 #3 0x804b9fa in _cmd_list_full (client=0x8096080, lsub=0) at cmd-list.c:341 #4 0x804ba8b in cmd_list (client=0x8096080) at cmd-list.c:365 #5 0x804d39e in client_handle_input (client=0x8096080) at client.c:306 #6 0x804d43d in _client_input (context=0x8096080) at client.c:342 #7 0x8078c87 in io_loop_handler_run (ioloop=0x808d060) at ioloop-poll.c:210 #8 0x8078745 in io_loop_run (ioloop=0x808d060) at ioloop.c:295 #9 0x80524a9 in main (argc=1, argv=0xbfbffc2c, envp=0xbfbffc34) at main.c:166 #10 0x8049eb5 in _start () (gdb) _ This crash happens when adding an imap account to the sylpheed mailer. I also noticed other problematic log entries, which might or might not be related: Jun 16 00:28:36 ice imap-login: Login: wouter [192.168.196.5] Jun 16 00:28:36 ice imap(wouter): open() failed with file /usr/home/wouter/.mail/.imap/INBOX/.customflags: No such file or directory Jun 16 00:28:36 ice imap(wouter): Can't create temp index /usr/home/wouter/.mail/.imap/INBOX/.temp.hostname.domainname.tld.1728: No such file or directory ... this happens when an imap user connects and opens his/her INBOX for the first time, and the /usr/home/username/.mail/ directory doesn't exist yet. My DEFAULT_MAIL_ENV settings: #default_mail_env = mbox:~/.mail:INBOX=/var/mail/%u default_mail_env = mbox:/usr/home/%u/.mail:INBOX=/var/mail/%u (tried both) Manually adding the ~/.mail directory with mkdir takes care of the problem, but shouldn't this directory be created automatically when it doesn't exist? I can't expect every user to log in and first make this mail directory before they can use their mail account. Dovecot also refuses to show any folders at all, such as the INBOX, when it can't find it's mail(folders) directory. Is this intentional? Dovecot is running on a pretty standard (i386) FreeBSD 4.4 test machine with postfix and normal mbox-formatted inbox files. Thanks for any suggestions, wouter

3 6

[Dovecot] Dovecot will not run on secure kernel.
by Ola Garstad 16 Jun '03

16 Jun '03

I am trying to run Dovecot on RH 7.3 with Linux kernel 2.4.20 + GrSecurity patch. I downloaded the RPM yesterday and installed it. When I start Dovecot the kernel reports: kernel: grsec: From 192.168.1.22: attempt to overstep process limit by (dovecot:14491) UID(0) EUID(0), parent (dovecot:23872) UID(0) EUID(0) I have never seen this problem in the 3 years I have used GrSecurity together with a lot of programs. GrSecurity explains: "Enforce RLIMIT_NPROC on execs. Users with a resource limit on processes will have the value checked during execve() calls. The current system only checks the system limit during fork() calls." Any ideas why Dovecot causes this problem? -- Ola

2 1

[Dovecot] more newline related errors
by Mike Brown 16 Jun '03

16 Jun '03

Should I be concerned about these errors? imap(msun): Jun 13 13:21:38 Error: Error indexing mbox file /home/msun/mail/Deleted Messages: LF not found where expected imap(msun): Jun 13 13:39:08 Error: Corrupted binary tree for index /home/msun/mail/.imap/INBOX/.imap.index: lookup returned index outside range (1 >= 0) imap(msun): Jun 13 13:44:07 Error: IndexID mismatch for binary tree file /home/msun/mail/.imap/INBOX/.imap.index.tree imap(msun): Jun 13 13:44:07 Error: IndexID mismatch for binary tree file /home/msun/mail/.imap/INBOX/.imap.index.tree imap(msun): Jun 13 13:44:07 Error: IndexID mismatch for modify log file /home/msun/mail/.imap/INBOX/.imap.index.log imap(msun): Jun 14 12:07:42 Error: Error indexing mbox file /home/msun/Mailbox: LF not found where expected imap(msun): Jun 14 12:08:27 Error: Corrupted index file /home/msun/mail/.imap/INBOX/.imap.index: Sequence 1 not found from binary tree (1 msgs says header) imap(msun): Jun 14 12:08:27 Error: Corrupted index file /home/msun/mail/.imap/INBOX/.imap.index: Sequence 1 not found from binary tree (1 msgs says header) imap(msun): Jun 14 12:08:27 Error: Corrupted index file /home/msun/mail/.imap/INBOX/.imap.index: Sequence 1 not found from binary tree (1 msgs says header) imap(msun): Jun 14 12:14:23 Error: IndexID mismatch for binary tree file /home/msun/mail/.imap/INBOX/.imap.index.tree imap(msun): Jun 14 12:14:23 Error: IndexID mismatch for binary tree file /home/msun/mail/.imap/INBOX/.imap.index.tree imap(msun): Jun 14 12:14:23 Error: IndexID mismatch for modify log file /home/msun/mail/.imap/INBOX/.imap.index.log imap(msun): Jun 15 11:34:58 Error: Error indexing mbox file /home/msun/Mailbox: LF not found where expected There was a patch required for the POP3 server to read mbox files that did not precede "From " lines with a blank line. Perhaps this is related? Thanks

3 2

[Dovecot] bug in search? (fwd)
by Mark E. Mallett 14 Jun '03

14 Jun '03

I received this report and am passing it along.. mm > If all messages are marked for deletion, the following command returns > an empty list: > SEARCH DELETED > If all messages BUT one are marked for deletion the same command returns > a list of every message but one. > > If parens are used it works fine. > SEARCH (DELETED)

2 1

[Dovecot] Deleting NFS-mounted Maildir subfolders fails
by Christian Ehrhardt 14 Jun '03

14 Jun '03

Hi, [ please CC me on replies, I'm not subscribed to the list ] I'm using dovecot-99.9.1 with a little hack to get authentication to work the way we want it. The server is running on a Solaris 9 host and user homes are mounted via NFS from a Solaris 8 server (Version doesn't seem to matter). Almost everything's fine but I can't delete maildir subfolders if these reside on a non local NFS-directory. The reason given is that the directory isn't empty and hence can't be deleted. Most likely the following happens: dovecot has the index file and other stuff in the maildir subfolder opened via NFS. When the delete request comes in dovecot deletes these files but doesn't close them. On normal unix file systems this is no Problem but with Solaris NFS these file's aren't actually deleted until they are (explicitly or implicitly) closed. Instead they are renamed to .nfs.<some digits>. These files will automatically vanish once they are closed. However, as long as they exist it is impossible to delete the directory where these files reside and rmdir fails. This is not a big deal and one may argue that dovecot is fine and the NFS implementation is in error. However, it would be cool if dovecot could atttempt to close all administrative files before it deletes them (or at least before it tries to delete the directory where these files reside). regards Christian Ehrhardt -- THAT'S ALL FOLKS!

2 1