- dovecot - dovecot.org

[Dovecot] Startup Problem
by Tobias Sasse 15 Aug '03

15 Aug '03

Hello, i don't like asking stupid questions in mailinglist, 'cause i guess you got something better to do than answer it. But well this is an exception, because i didn't find anything on google. Here comes my problem: I'm using a NetBSD 1.6.0 System with the latest dovecot build. i want to start dovecot imapd by: root@balin:[/etc]$ ./rc.d/dovecot start Starting dovecot. Fatal: Error in configuration file /usr/pkg/etc/dovecot.conf line 88: Missing value This is my error ;) This is the line 88 in my conf file. maildir:/home/%u/mail the maildir was created by 'makemaildir mail' and exists: root@balin:[/home/tobi]$ ls -all total 18 drwxr-xr-x 4 tobi users 512 Aug 15 09:11 . drwxr-xr-x 3 root wheel 512 Aug 13 01:18 .. drwx------ 5 tobi users 512 Aug 14 12:47 mail there it is. in default option of the maildir line dovecot starts without problems but i really want to have my mails in /home/%u/mail and not in /var/mail/%1u/%u/mail So could somebody please put some light on it? Thank you, Tobi

2 1

[Dovecot] joys of transition.
by Eric S. Johansson 15 Aug '03

15 Aug '03

Red Hat 8.0 stock dovecot 99.10 for a variety of reasons, I decided to cut over to dovecot this morning. I extracted all of my mailboxes from mbx purgatory back to mbox purgatory, set up dovecot and proceed to get authentication failures. (am using simple password based authentication either direct or through pam) I turned authentication verbosity on and got: Aug 14 11:51:38 harvee dovecot: Dovecot starting up Aug 14 11:51:46 harvee dovecot-auth: PAM: pam_authenticate(esj) failed: Authentication failure Aug 14 11:51:49 harvee dovecot-auth: PAM: pam_authenticate(esj) failed: Authentication failure Aug 14 11:51:52 harvee imap-login: Aborted login [192.168.0.10] not very informative. I already know that I can't login. So I fire up ethereal and capture the following transaction: * OK dovecot ready. 1 authenticate login 1 NO Unsupported authentication mechanism. 2 login "esj" "no peeking" 2 NO Authentication failed. 3 authenticate login 3 NO Unsupported authentication mechanism. 4 login "esj" "no peeking" 4 NO Authentication failed. 5 logout * BYE Logging out 5 OK Logout completed. hmm no unsupported authentication mechanism. So that means all authentication methods works right? ;-) looking a little further into the configuration, I see instructions to change auth_methods to add plain in front of digest-md5 (or is it digest_md5, both forms are present in the configuration file). No luck. Doing so gives me the following error message: Fatal: Error in configuration file /usr/local/etc/dovecot.conf line 430: Unknown setting: methods so, I'm not sure what to look for. It's probably something simple but googling didn't reveal anything pertinent although it turned up something amusing[1]and dovecot does apply. Suggestions or clues would be welcome. FYI, you probably could use a little bit more detail in the install instructions. For example instructing user to create a dovecot user and group name would be useful as would be a startup/shutdown script for init.d. I also find the SSL configuration lacking. On the other hand, I have enough scar tissue from certificates and mini-CA setups to hate them till the end of time. If I get them working better, I'll document and send it to the list. ---eric [1]http://www.oblomovka.com/eldritch/iag/ob1-5.htm

2 2

[Dovecot] error in config file?
by Robert S. Jagger 15 Aug '03

15 Aug '03

When I start dovecot I am getting an error about the ocnfig file. watson:~# /etc/init.d/dovecot start Starting mail server: dovecotFatal: Error in configuration file /etc/dovecot.conf line 185: Missing value So I look int /etc/dovecot.conf and line 185 is mbox:~/mail/:INBOX=/var/mail/%u/ Which seems like valid syntax according to the docs. I am using dovecot 0.99.10-2

2 1

[Dovecot] Mozilla
by Stefan Sels 14 Aug '03

14 Aug '03

Hi, I hope this problem is not answered before. Mozilla is making trouble with searching and subscribing folders. Do I have to change the "namespace" ? If I start a search (other than just in To & CC or subject) mozilla complains about a closed connection. A fresh mozilla installation just lists no folder beside "Inbox". Regards, Stefan Sels

3 4

[Dovecot] Hardlinks in copy
by Andreas Aardal Hanssen 12 Aug '03

12 Aug '03

Hi, Dovecotters. In the Maildir code, dovecot-0.99.10/src/lib-storage/index/maildir/maildir-copy.c, I see that hardlinks are used. It seems that (line 185) if MAILDIR_COPY_WITH_HARDLINKS is exported, then copying is attempted by using link. Having problems reading the source / flow of control, I resort to this list. When a file is linked, the mtime is naturally kept on the destination. This gives the destination message the same internaldate as the original. The destination mailbox would then be likely to get an arrival with an earlier internaldate than its newest message. The IMAP protocol says to bump UIDVALIDITY when this happens. Does Dovecot always bump UIDVALIDITY when messages are copied, or is not the mtime used for internaldate? Best regards, Andreas -- Andreas Aardal Hanssen

2 1

[Dovecot] 0.99.10-test5
by Timo Sirainen 12 Aug '03

12 Aug '03

Again at http://dovecot.procontrol.fi/test/ if someone wants to test it. - new index file code should work now - mbox support is completely broken - caching isn't very smart yet. it always caches only what client requested at the time - header caching might have some problems actually now that I think of it.. I was anyway going to change a bit how it worked.

2 1

[Dovecot] CVS/test version config/build failures on FreeBSD
by Mike Brown 11 Aug '03

11 Aug '03

While diagnosing a problem I was having with IMAP and SSL (which I ended up fixing by simply upgrading from 0.99.9.1 to 0.99.10, and possibly affected by upgrading openssl libs from 0.9.7a to 0.9.7.b), I attempted to try the CVS version of Dovecot. When using the CVS version, apparently I have to first generate 'configure' using autogen.sh (?). This was the result of that, on FreeBSD 4.8-STABLE (2003-08-06): # ./autogen.sh automake: configure.in: installing `./install-sh' automake: configure.in: installing `./mkinstalldirs' automake: configure.in: installing `./missing' configure.in: 3: required file `./config.h.in' not found automake: configure.in: installing `./depcomp' configure.in:3: warning: do not use m4_patsubst: use patsubst or m4_bpatsubst configure.in:13: warning: AC_ARG_PROGRAM invoked multiple times configure.in:1126: warning: do not use m4_regexp: use regexp or m4_bregexp autoheader: `config.h.in' is created And then... # ./configure checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... no checking for mawk... no checking for nawk... nawk checking whether make sets ${MAKE}... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for style of include used by make... GNU checking for gcc... gcc checking for C compiler default output... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking dependency style of gcc... gcc checking for strerror in -lcposix... no checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking dependency style of gcc... (cached) gcc checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for gcc option to accept ANSI C... none needed checking for inline... inline checking build system type... i386-unknown-freebsdelf4.8 checking host system type... i386-unknown-freebsdelf4.8 checking for ranlib... ranlib checking for ld used by GCC... /usr/libexec/elf/ld checking if the linker (/usr/libexec/elf/ld) is GNU ld... yes checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes loading cache /dev/null within ltconfig ./ltconfig: .: /dev/null: not a regular file ltconfig: you must specify a host type if you use `--no-verify' Try `ltconfig --help' for more information. configure: error: libtool configure failed I also attempted to use 0.99.11-test4 from http://dovecot.procontrol.fi/test/, but this failed to build: [...] Making all in maildir gcc -DHAVE_CONFIG_H -I. -I. -I../../../.. -I../../../../src/lib -I../../../../src/lib-mail -I../../../../src/lib-imap -I../../../../src/lib-index -I../../../../src/lib-index/maildir -I../../../../src/lib-storage -I../../../../src/lib-storage/index -I/usr/local/include -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -c maildir-copy.c make: don't know how to make ../../../../src/lib-storage/index/index-expunge.h. Stop *** Error code 1 Stop in /usr/local/src/dovecot/dovecot-0.99.11-test4/src/lib-storage/index. Just thought you'd like to know :) -Mike

3 8

[Dovecot] Some benchmarking
by Timo Sirainen 11 Aug '03

11 Aug '03

So I finally got the new mail caching code fully working in normal conditions. Index rebuilding and some error correction still needs a bit work. mbox is also still broken. Anyway, I was mostly interested how fast Dovecot now works with my 367000 LKML mails, but thought I'd have to get something to compare the results against, so here's Dovecot vs. Courier. Results against older Dovecot would have been pretty boring, the older Dovecot could never perform threading without opening all the files and reading References-headers from them. Sorting would could have been done from cache if IMAP ENVELOPEs were cached, I'd estimate maybe 2-3x larger user CPU usage with it and a _lot_ larger cache file since it would have stored from, to, etc. fields in it. Results against Cyrus would be interesting. I'll probably do those sometimes later too.. Last I checked, Cyrus was very slow at inserting the mails into it's database, it took .. was it 1-3 hours to insert all those mails, while a simple copying took maybe 20 mins. Anyway, Cyrus's caching is pretty dummy as well so I'd expect Dovecot to be many times faster in threading and likely somewhat faster in sorting.

3 2

[Dovecot] Direct RADIUS support, not via PAM
by Jethro R Binks 08 Aug '03

08 Aug '03

Hi, I'm currently testing dovecot to authenticate user passwords against a radius server, via pam_radius_auth, and that seems to work fine. However, I am running other software (Exim MTA) that also authenticates via radius, using the radiusclient library from: http://www.mcs.de/~lf/radius/ Is there any chance that this library could be used by Dovecot as a further authentication option, and save me having two separate radius configurations for two different (but related) pieces of software, and the need to install pam_radius_auth, which I don't otherwise use? Jethro. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Jethro R Binks Computing Officer, IT Services University Of Strathclyde, Glasgow, UK

2 1

[Dovecot] Slow bulk deleting
by Leslie Viljoen 07 Aug '03

07 Aug '03

Hi! I am finding Dovecot very slow to delete large numbers of messages. IS this a known problem? Leslie

2 2