- dovecot - dovecot.org

[dovecot] Something wrong in SSL ?
by Juha Ylitalo 14 Apr '03

14 Apr '03

Operating system: FreeBSD 4.7-RELEASE-p10 Dovecot: 0.99.8.1 I've used openssl to generate personal CA and I've used that one to generate certificate for my web server. When I tried to go through same pattern for generating certificate for IMAP server from CA, I ended up in situation, where both mutt and evolution keep on rejecting my certificates.

2 2

[Daniel Silverstone <dsilvers@digital-scurf.org>] Re: lua 5.0
by Per Olofsson 13 Apr '03

13 Apr '03

FYI. /Pelle

1 0

[dovecot] Maildir problem?
by Maikel Verheijen 11 Apr '03

11 Apr '03

Hey list, Today I cvs updated to the most recent dovecot, to test with the recent improvements on the dovecot-uidlist file, and came acros the following: Apr 11 12:49:36 pc-5-046 imap(): Corrupted index file (in-memory index for /var/mail/mounted/test.com/maikel/Maildir//.Sent Items): Filename mismatch for UID 1: 1050058115.P3401Q0M675362.pc-5-046.test.nl:2,S vs 1050057888.P3371Q0M138398.pc-5-046.test.nl I am using a front-end back-end construction, But I am testing on the backend only (non-nfs), because the subscriptions file isn't nfs safe yet. shouldn't the uidl files be leading over the indexes? And shouldn't the indexes be updated as well? Thank you, Maikel Verheijen.

1 0

[dovecot] Maildir syncing rewrite
by Timo Sirainen 10 Apr '03

10 Apr '03

It finally seems to be working. I've done some testing now and it seems to be working fine. If you have time, see if you can get it to break (especially with INDEX=memory or by manually modifying the maildir). The UIDs are kept in Courier-compatible dovecot-uidlist file (so "mv courierimapuiddb dovecot-uidlist" should work). The great thing about this code is that we never wait for lock. If we can't lock, we simply use the old uidlist file to sync whatever we can, which should be everything but the very newest mails just being delivered and processed by another Dovecot. Of course, if they share index files, we're still blocking there. I named the file as "dovecot-uidlist" instead of ".uidlist" because I finally realized that files beginning with dot conflict with the mailbox namespace. I should rename .customflags and .subscriptions files as well. Also if I move .imap.index* files into root dir, I'll have to rename them too. new/ directory is now scanned every time to see if there's new mail. cur/ directory is scanned if index file's timestamp differs from cur/ dir's timestamp. uidlist file is reread if it's device/inode changes. You can get the sources from either CVS, or 0.99.9-test2 from http://dovecot.procontrol.fi/test/

3 5

[dovecot] dovecot-0.99.9-test2 probs
by Mark E. Mallett 10 Apr '03

10 Apr '03

Hi- Tried 0.99.9-test2 -- had to go back. Various problems in the log. Here's one: Apr 10 08:56:25 mercury mem[10754]: imap(user0): msync() failed with index data file /users/8b/user0/Maildir/.INBOX/.imap.index.data: Cannot allocate memory Apr 10 08:56:25 mercury mem[10754]: imap(user0): Corrupted index data file /users/8b/user0/Maildir/.INBOX/.imap.index.data: Missing location field for record 156 Apr 10 08:56:25 mercury mem[10754]: imap(user0): msync() failed with index data file /users/8b/user0/Maildir/.INBOX/.imap.index.data: Cannot allocate memory Here's another: Apr 10 18:56:59 mercury mem[13376]: pop3(user1): Corrupted index file /users/30/user1/Maildir/.INBOX/.imap.index: index.next_uid (2365) > uidlist.next_uid (2364) And another: Apr 10 19:09:24 mercury mem[10892]: pop3(user2): Corrupted index file /users/39/user2/Maildir/.INBOX/.imap.index: index.next_uid (10422) > uidlist.next_uid (10420) Apr 10 19:09:24 mercury mem[10892]: pop3(user2): Corrupted index file (in-memory index for /users/39/user2/Maildir): Filename mismatch for UID 1: 1050015983.28176.mercury.mv.net vs 1046192106.460.mercury.mv.net Apr 10 19:09:24 mercury mem[10892]: pop3(user2): No INBOX for user And a ton of these, without any other entry for the process ID (which I assume is the number after "child"): Apr 10 19:09:33 mercury dovecot: child 1645 (imap) killed with signal 11

1 0

[dovecot] compilation errors
by Mark E. Mallett 10 Apr '03

10 Apr '03

Hi- I always encounter the same two minor compilation issues which are easily addressed simply by a quick edit, but this time I figured I'd mention it in case you can work around it. This is on a BSD/OS 4.2 system. First, the generated config.h always creates a definition for OFF_T_MAX which conflicts with the one in the system's limits.h config.h defines: #define OFF_T_MAX LLONG_MAX whereas /usr/include/machine/limits.h defines: #define OFF_T_MAX UQUAD_MAX /* max value for an off_t */ I simply comment out the definition from config.h . Second, in src/lib/mmap-anon.c there's a preprocessor conditional: #if SSIZE_T_MAX >= LLONG_MAX (etc) Unfortunately /usr/include/machine/limits.h defines LLONG_MAX thusly: #define LLONG_MAX (__extension__(9223372036854775807LL)) (evidently to suppress pedantic warnings about the gcc long long constant extension) but the cpp prepreprocessor stumbles over this comparison. This might be fixed in a later gcc, I dunno- it's gcc 2.95.2 here. Yours, -mm-

1 0

[dovecot] dovecot and virtual users
by Jej 10 Apr '03

10 Apr '03

Hello, I set up a virtual smtp with exim (mails stored in /var/virtual/{domain}/{user}, passwd in /etc/virtual/{domain}.passwd). I have a patched pop3 server to deal with these mail boxes. Would it be possible to use dovecot as imap server, or (even better) for imap and pop3, with this virtual domain model ? Thanks, read you. -- jej

2 1

[dovecot] Error: child 12625 (imap) killed with signal 12
by Johan Willard 09 Apr '03

09 Apr '03

Hi! I have tried to install dovecot as my imap service on my FreeBSD server. At first all looked fine and worked flawless. But after a while i started to get errors. The imap process dies with signal 12 when the client tries to check the contens of the folder. dovecot: Apr 07 09:55:17 Error: child 12625 (imap) killed with signal 12 Any ideas what may cause this problem? MvH Johan Willard

3 6

[dovecot] New installation - error 89 on connect
by David Knudsen 09 Apr '03

09 Apr '03

I've recently installed dovecot (0.99.8.1) from the Debian/woody backport at 'deb http://src.braincells.com/debian woody/' Previously, all mail have been delivered to mbox'es in ~/Mail by exim/procmail -- ~/Mail/inbox being my main mailbox. Whenever I attempt to connect with an IMAP client, the connection is closed and the following error is reported in /var/log/syslog: imap-login: Login: dk [192.168.0.2] imap(dk): Unknown client workaround: outlook-idle^I### dovecot: child 17653 (imap) returned error 89 What does error 89 signify? My current configuration is: (non-comment lines only) imap_listen = 192.168.0.2 imaps_listen = * login = imap login = pop3 verbose_proctitle = yes client_workarounds = oe6-fetch-no-newmail outlook-idle mailbox_check_interval = 60 auth = default auth_mechanisms = plain auth_userdb = passwd auth_passdb = pam auth_user = root auth_verbose = yes In my confusion, I blindly tried changing settings, attempting to get a different error message at least. :-) These are the settings I have tried, without success: default_mail_env = mbox:~/Mail:INBOX=~/Mail/inbox mail_full_filesystem_access = yes mbox_locks = fcntl auth_passdb = shadow There is no subdirectories in ~/Mail, neither visible nor hidden. I did try to read the docs, and I did browse the mailing list archives, but either I missed something or it is not there. Any ideas? Thank you, David Knudsen

2 2

[dovecot] Re: command line version of dovecot?
by Timo Sirainen 09 Apr '03

09 Apr '03

On Wed, 2003-04-09 at 18:52, Kyler Laird wrote: > > There's the "imap" binary that should do exactly that. Usually installed > > into /usr/local/libexec/dovecot/imap > > Ah! That's just the kind of solution I sought. > > Unfortunately it doesn't seem to work for me. It doesn't > appear (via strace) to read any configuration file. It just > looks in /var/mail/[user] for a Maildir. I need to to go to > the Maildir in the user's home (and follow other behaviors > defined in the config file). It should look into ~/Maildir first, then ~/mail and ~/Mail unless it's overridden in MAIL environment. You probably have MAIL=/var/mail/user set, which is why it looks into there. Currently it doesn't read any configuration file, and I'm not sure if I should make it do that.. Well, it could be useful but I'd have to figure out how to prevent unneeded code duplication for config file parsing. All settings are passed via environment settings, but they're not documented (they're basically uppercased versions of the setting names in config file). > Should I have found all of this in some documentation? I > appreciate the help but I feel like I should be reading > about this on my own somewhere. doc/mail-storages.txt explains the MAIL environment.

1 0