- dovecot - dovecot.org

[Dovecot] Corrupted index file
by Frank Hart 09 Feb '05

09 Feb '05

I've recently switched from Courier-imap to dovecot and I'm impressed with it's speed and reliability. However, my index file gets regularly corrupted: Feb 8 21:23:16 hive imap(hart): Corrupted index file /home/hart/Maildir/.INBOX/.imap.index: index.next_uid (129) > uid_rec.uid (128) dovecot version: 0.99.13-3 Debian sid) I use dovecot in combination with mutt, procmail and postfix. If I rename the last received mail I can use my inbox folder again (until the next time the index gets corrupted). Debian bug# 294284 -- make install, not war

2 2

[Dovecot] Server going crazy!!!
by poohba＠blkpoohba.dyndns.org 09 Feb '05

09 Feb '05

I have dovecot-0.99.11-1FC3.4. I use Pine on the server and Outlook 2003 on remote computers to access IMAP and POP3 to access via my blackberry 7100t. It seems that after using IMAP and then going back to pine it somehow refreshes everything and all the messages are picked up on my blackberry once again as if the emails are new. So everything that is in my inbox is now pushed or grabbed by my blackberry as new messages when they are not and have been read already (at least most of them). Why is this happening? ## Dovecot 1.0 configuration file base_dir = /var/run/dovecot/ protocols = imap imaps pop3 pop3s imap_listen = [::] pop3_listen = [::] imaps_listen = [::] pop3s_listen = [::] log_timestamp = "%b %d %H:%M:%S " login_dir = /var/run/dovecot-login login_chroot = yes login = imap login = pop3 default_mail_env = mbox:/home/%u/mail:INBOX=/var/spool/mail/%u mbox_locks = fcntl auth = default auth_mechanisms = plain auth_userdb = passwd auth_passdb = pam auth_user = root

2 1

[Dovecot] Multiple auth sections, stable branch - 7/2/05
by Andrew Hutchings 07 Feb '05

07 Feb '05

Hi, Great job with the dovecot 1.0 stable branch, much more stable than the test57 I was using. Only one slight oddity, I know multiple auth sections is not stable yet but I am finding that one auth section at random is being ignored at login time (acknowledges it at startup). The auth section that is ignored is the same each time, but different on each server I use it on and changes at random after modifying the dovecot.conf file. Used both my test57 (hacked to remove the auth command) conf file and a new one I created using today's stable branch conf file. I sorted a work around by duplicating the failing auth sectio with a different name in each server and it works great! :) If this is easy thing to fix, great, you are still our hero either way Timo, you have made our mail server -> cluster migrations much less painless. Regards Andrew -- Andrew Hutchings Linux Guru Netserve Consultants Ltd. http://www.domaincity.co.uk/

1 0

[Dovecot] crash with test62
by Juergen Daubert 07 Feb '05

07 Feb '05

Hi, Got the following today with test62 and mbox: IMAP(juergen): Fixed index file /home/juergen/Mail/.imap/INBOX/dovecot.index: recent_messages_count 19 -> 0 imap-login: Login: juergen [192.168.0.1] file mail-index-sync-ext.c: line 118 (mail_index_sync_deinit_handlers): assertion failed: (size <= synch_size) child 31196 (imap) killed with signal 6 after that I had to delete dovecot.index to be able to select the folder. And another one: IMAP(juergen): Corrupted transaction log file /home/juergen/Mail/.imap/dovecot/dovecot.index.log: record size too small (type=0x0, size=0) imap-login: Login: juergen [192.168.0.1] IMAP(juergen): Transaction log file /home/juergen/Mail/.imap/dovecot/dovecot.index.log: marked corrupted Greetings Juergen -- Juergen Daubert | mailto:jue@jue.li Korb, Germany | http://jue.li/crux

2 1

[Dovecot] Migrating from mbox to maildir: Message ordering?
by Ian R. Justman 06 Feb '05

06 Feb '05

Hi, all. I have been playing with the notion of migrating some of my folders to maildir because it's a lot easier to manage that way from a reader standpoint. The big question I have is how do I maintain message ordering in each folder? When I use a mail program to do the migration from mbox to maildir, selecting "order received ascending", it works nicely, but one very small problem: When I go to look at the newly-populated folder, everything is in reverse order. I've tried it with T'bird and I've tried it with Pine. Both yield the same results. I'm thinking the issue might be with Dovecot. Or is it a peculiarity with maildir? Or am I better off using other means to convert a mbox folder to maildir? I like maintaining the message delivery order so especially items like mailng list threads can (normally) flow right. I don't always trust the message's date field because it CAN be faked (and sometimes is by the sender, whether accidental or intentional). And while we're on the subject, since maildir's a file-per-message mailstore, what happens to ordering when you delete a message and a new message arrives? However, otherwise, everything else is working beautifully. I haven't gone into bashing the living hell out of it to make sure it REALLY works The testing was done with Dovecot 1.0test62, Thunderbird 1.0, and Pine 4.62. Both mbox and maildir folderstores are on the same machine and Dovecot's configured to use both with a maildir in the user's directory, oddly enough, called "maildir", for their maildir store. Thanks in advance for any help anyone can render. --Ian.

3 3

[Dovecot] pam_mkhomedir and dovecot
by Ben Halicki 03 Feb '05

03 Feb '05

Hi all, Just wondering if anyone has successfully managed to configure pam_mkhomedir and dovecot, so that users home directories are automatically created? As far as I can tell, the login process runs as a non-root user, which results in a permission denied error while trying to create the users home directory. I'm not sure if this error is specific to dovecot or pam though. Any thoughts would be greatly appreciated. Thanks, Ben Halicki Information Technology Officer Macquarie Textiles Group Ltd Phone: 02 6043 0235 Fax: 02 60411 321 E-mail ben.halicki(a)macquarietextiles.com.au

2 1

[Dovecot] Dovecot doesn't call pam_open_session, thus dodging pam_mkhomedir
by Nicolas Lopez 03 Feb '05

03 Feb '05

I hit a small snag using Dovecot-imapd smoothly in my environment with maildir and most of my accounts in LDAP. Since the accounts are created through a web interface on another server home directories on the mail server don't get created automatically. There's the handy pam module pam_mkhomedir.so to automagically create home directories, but unfortunatly Dovecot wasn't calling pam_open_session to run the session setup pam modules. I made a small patch to passdb-pam.c to call pam_open_session between pam_acct_mgmt and pam_get_item and now I my home dirs are automagically created and everyone is happy. So, I figured I'd share the little patch in case someone else finds it useful. My patch doesn't properly close the session which will probably iritate more advanced session modules that actually have something to clean up, oh well. Aside from manually having to create home directories Dovecot-imapd has been working really well for us for a number of months, I just finally got around to dealing with the home dir creation issue. - Nick Lopez nlopez(a)espri.arizona.edu

3 3

[Dovecot] Dovecot doesn't call pam_open_session, thus dodging pam_mkhomedir (fwd)
by Pasi Sjoholm 02 Feb '05

02 Feb '05

On Tue, 1 Feb 2005, it was written: > Nicolas Lopez wrote: > > maildir and most of my accounts in LDAP. Since the accounts are created > > through a web interface on another server home directories on the mail > > server don't get created automatically. There's the handy pam module > > pam_mkhomedir.so to automagically create home directories, but > > unfortunatly Dovecot wasn't calling pam_open_session to run the session > > setup pam modules. I made a small patch to passdb-pam.c to call > > pam_open_session between pam_acct_mgmt and pam_get_item and now I my > > home dirs are automagically created and everyone is happy. > > So, I figured I'd share the little patch in case someone else finds it > > useful. My patch doesn't properly close the session which will probably > > iritate more advanced session modules that actually have something to > > clean up, oh well. This patch closes the session.. but you will see many "opened session\n closed session"-lines on your log files. =) --cut-- --- src/auth/passdb-pam.c-org 2004-10-07 08:38:28.000000000 +0300 +++ src/auth/passdb-pam.c 2004-10-07 08:38:59.000000000 +0300 @@ -193,6 +193,18 @@ return status; } + if ((status = pam_open_session(pamh, 0)) != PAM_SUCCESS) { + *error = t_strdup_printf("pam_open_session(%s) failed: %s", + user, pam_strerror(pamh, status)); + return status; + } + + if ((status = pam_close_session(pamh, 0)) != PAM_SUCCESS) { + *error = t_strdup_printf("pam_close_session(%s) failed: %s", + user, pam_strerror(pamh, status)); + return status; + } + status = pam_get_item(pamh, PAM_USER, (linux_const void **)&item); if (status != PAM_SUCCESS) { *error = t_strdup_printf("pam_get_item(%s) failed: %s", --cut-- > I am running dovecot-0.99.13 on FC2 with pam_mkhomedir, and it has been > working fine. Not sure why you are having a problem. If I could just > figure out how to get Exim to do the same, I'd be happy :-) I think that Fedora has probably patched that version of dovecot which they are providing. -- Pasi Sjöholm

1 0

[Dovecot] test61 ./configure fails on OpenBSD 3.6
by Jamie Herre 02 Feb '05

02 Feb '05

Test version 61 ./configure is failing on my OpenBSD 3.6-stable system. The following corrects the problem. Would it be possible to test for gnu99 option before using it in subsequent tests? --- configure.in.orig Fri Jan 14 14:04:10 2005 +++ configure.in Fri Jan 14 16:44:22 2005 @@ -236,7 +236,7 @@ # say specifically that we want C99 features. # we can make use of GNU features as well, so don't use -std=c99. - CFLAGS="$CFLAGS -std=gnu99" + CFLAGS="$CFLAGS -std=gnu9x" fi dnl **

2 2

[Dovecot] dovecot-stable branch
by Timo Sirainen 01 Feb '05

01 Feb '05

To confuse Dovecot versioning even more, I've added "dovecot-stable" module into CVS. This is a version of Dovecot before the recent keyword changes but with several bugfixes backported to it. It's thought to be mostly stable. I intend to keep it updated with important bugfixes and with other simple bugfixes. Although I'm not sure if I'll make a large code base upgrade once keyword changes are stable. This is mostly meant for people who _really_ want to use 1.0-test codebase in production right now. Perhaps it's already more stable than 0.99.x, but upgrading should probably be made easier for v1.0. The dovecot-stable module itself is just a hack that will go away at some point. Once the main codebase is stable enough for v1.0 beta release, I'll make a stable branch instead in the main dovecot module (and probably with different RCS than CVS).

6 10