- dovecot - dovecot.org

RE: [Dovecot] mbox folders
by Villalovos, John L 19 May '04

19 May '04

dovecot-bounces(a)dovecot.org wrote: > * Villalovos, John L <john.l.villalovos(a)intel.com> (20040518 13:46): >> The problem I am having is that it seems to want to put folders in: >> >> ~/mail/mail/ > > How is your `default_mail_env' variable configured? I have: [john@webhost john]$ set | grep -i mail MAIL=/var/spool/mail/john MAILCHECK=60 [john@webhost john]$ John -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting Q: What is the most annoying thing on usenet and in e-mail?

2 1

[Dovecot] having hell of the time converting away from UW
by Eric S. Johansson 18 May '04

18 May '04

I just want to check and make sure not missing anything. I'm trying to convert a customer away from UW. unfortunately, all of the mailboxes are in MBX format (my own mistake coming back to haunt me). mailutil doesn't seem to do conversions properly. It keeps complaining about an existing copy of /mbox and only if I say to -merge append will the copy proceed. mailsync doesn't work well with hierarchies of mailboxes. its copies the top level mailboxes but proceeds to get sick on the sub mailboxes. I'm not sure what other tools there are to help me get out from the mbx rathole and over to the maildir wallow. any suggestions?

2 1

[Dovecot] dovecot (mutt?) tells me I have new email (when I don't)
by Charlie Allom 18 May '04

18 May '04

Hi, does anyone else, whilst using mutt, have the problem where you read your new email - then change to another mailbox, *then* mutt tells you that you have new email in the mailbox you just read!? It seems to only happen when I: a) receive email in, say, =mi b) change to, and read email in =mi c) hit 'c' to change to next-unread mailbox d) mutt says "New mail in imap://yeled@localhost/" e) I 'c' back there to =mi and there is no New email - but there are some Old 'unread' emails (ie "O" status in mutt) I've attached the IMAP logs. Of special note is the RECENT after the thread 'a1192' in the file 203.018.243.123.00143-203.031.232.002.57 a1192 OK Status completed. * STATUS "mi" (RECENT 1) a1193 OK Status completed. I believe it's telling mutt that there is a new email in "mi" after I've just read it! a1184 OK Status completed. * 890 FETCH (UID 901 BODY[] {3661} ^^this is the email I just read, and is now "New" again. Subject: test2 Is this a mutt or dovecot bug/feature? Regards, C. -- charlie(a)rubberduck.com - Melbourne, Australia http://rubberduck.com/~yeled/ PGP: 0x14AA7941 || finger yeled(a)lazy.spodder.com

5 5

[Dovecot] maildirsize
by Brian Candler 17 May '04

17 May '04

Hello, Are there plans to implement Maildir++ quotas (maildirsize) in dovecot in the near future? Also - how do things work if you have multiple dovecot frontends accessing an NFS mailstore? If you keep the index files on local disk, and clients connect alternately to different machines, are the stale indexes noticed and corrected? Thanks, Brian.

2 1

[Dovecot] Dovecot vs. Courier-Imap
by Marten Lehmann 17 May '04

17 May '04

Hello, I've heard of both and I already tested and installed both, but I'm not sure which one is better, since both just seem to work and I can't see a difference, except from the point how it's set up and configured. Where are the drawbacks of each one, where are the benefits? I also tested cyrus before, but cyrus is not working well with maildirs. I'm not that into detail of both projects, maybe you can explain a bit. Thanks in advance for every answer! Regards Marten

5 6

[Dovecot] 1.0-test9 released
by Timo Sirainen 17 May '04

17 May '04

http://dovecot.org/test/ - SORT command always replied with NO - Locking fixes. Fixes several crashes, dotlock errors and deadlock errors - When multiple sessions were concurrently modifying mailbox it often mixed up the messages that were supposed to be modified. When expunging it also gave errors such as: Corrupted transaction log file /home/user/Maildir/.INBOX/dovecot.index.log: Expunge range 5..5: UIDs 6..6 doesn't match real UIDs 18..18 Now it doesn't do it as often, but it still does.. I'm not really sure where the bug is. Have to keep looking. This seems much more stable than test8, but because of the above problem I still don't recommend it for more than testing.

1 0

[Dovecot] local auth
by Kees Cook 15 May '04

15 May '04

Is there a way to run dovecot locally as a user, like uw-imap lets you do? I want to use dovecot with fetchmail over ssh... I couldn't find anything in the archives on this. -- Kees Cook @outflux.net

2 1

[Dovecot] can I share IMAP folders for multiple user
by Hitao 14 May '04

14 May '04

Hi, Dear all, Just a bit curious, could I configure dovecot for two users share the access to certain IMAP folders in the mailbox? I searched the list archive and only found http://dovecot.org/list/dovecot/2004-April/003236.html and http://dovecot.org/list/dovecot/2004-April/003168.html, but I am not sure is this the same thing that I want and where could I find more details? Wish you a nice day! Hitao

1 0

[Dovecot] dovecot-1.0-test8 / nfs / maildir / flags issues
by Maikel Verheijen 14 May '04

14 May '04

Hi List, While (bluntly) testing the prerelease version of dovecot on our mailfarm (just for the webmail imap) we noticed some small problems: - While our OLD dovecot/imap drove the load to a maximum of 1 over a day after running, the new dovecot/imap pushes it easily to 20. This is mainly due to a LOT more disk activity. This is probably caused by the fact we a) use indexes on disk and b) there are no indexes left. I hope this will smooth out when most of the indexes are made. - We notice some very strange "delete" flag things in our IMP webmail system (working on a test environment to be more specific). The problem is that if you mark some messages "deleted", a lot of messages that do NOT have "deleted" flag are also in the deleted list. Since nothing changed on the webmail, it must be in the way dovecot responds different in the new version on certain requests. - In the dotlocking code, it seems that dovecot uses time() for it's internal locktime, and uses stat() to see if the file-time of the lock is different. Since we use nfs there might be a time-difference on the file creation and time() when our nfs gets "busy". This happens a lot when the indexes are created for multiple users at the same time resulting in a lot of: May 12 08:57:44 mf1 dovecot[3763]: imap(user(a)domain.tld): Our dotlock file /var/mail/mounted/d/do/domain.tld/user/Maildir/.INBOX/ dovecot.index.log.lock was modified (1084345063 vs 1084345062), assuming it wasn't overridden I am not completely sure if this interrupts imap traffic. I think this MIGHT be solved by storing a stat() time as the locktime instead of a time(), but this might be intentional. - I patched dovecot to report its pid in syslog messages, in order to find the "killed by signal X" where X are mostly 11 and 6 processes. The pids reported do not show up in the rest of the log file, so these may be "disconnected" sessions? It seems that the "old" version has the same problem, and nobody really complained it was broken, so this isn't a big issue. To clarify our setup: We use multiple mail-frontends running dovecot that are load-balanced by a cisco load-balancer. We mount our mailstores from an active-active backend cluster, both nodes export a big partition, and take over the job of the other in case of a problem. This seems to go pretty smooth. Our users are stored in a pgsql database. In our current setup, we run a modified cvs version of dovecot from WAY back, to support nfs. The backdraw is that we can't use the newer dovecot releases, since I couldn't modify the source in the way I did it the first time (with a LOT of help from Timo :P). If anyone has some ideas on where to look and where to test in order to get our problems more clear, I would be very grateful :) Kind regards, Maikel Verheijen Ladot Nederland BV.

5 5

[Dovecot] Problem building 1.0-test7 : missing header
by Curtis Maloney 13 May '04

13 May '04

Greetings, I recently rolled out Dovecot in our small (<30 people) company, and have been mightily impressed by the quality, performance and ease of use. I was hoping to use the new versions soon, as I'd like to start using CRAM-MD5 (much more common in mail clients than DIGEST-MD5), but found the 0.99.11 versions too unstable. So, I tried to build last nights CVS snapshot (May 10th), only to have the make break at this point: make[3]: Entering directory `/home/src/dovecot-1.0-test7/src/lib-index' make[3]: *** No rule to make target `mail-index-util.h', needed by `mail-cache.o'. Stop. I know it's not much, but it's a start at giving back a little. Hope it helps. -- Curtis Maloney

5 4