- dovecot - dovecot.org

[Dovecot] Configuration Question.
by James Andrews 23 Dec '06

23 Dec '06

Hi Everyone. I have recently installed dovecot for the first time on a RHEL3 server. I have it working for the most part, but am a bit baffled by part of the configuration, something that I am sure I am just doing incorrectly. I can successfully access my normal mailbox which is in /var/spool/ mail/username, but I also want to create mail folders, and that's the problem I am having. I want the folders to live in ~/mail/ I have tried default_mail_env = mbox:~/mail/:INBOX=/var/spool/mail/%u and default_mail_env = maildir:~/mail:INBOX=/var/spool/mail/%u What on earth am I doing wrong? I'm sure it's something small that I just don't understand. Thanks James

4 4

[Dovecot] Bug: (dovecot-auth), exited on signal 6
by art 23 Dec '06

23 Dec '06

Hello What additional information I should give? uname -a FreeBSD mail 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #1: Thu Oct 19 16:57:14 UTC 2006 root@:/usr/obj/usr/src/sys/my i386 mail# dovecot --version 1.0.rc15 mail# dovecot --build-options Build options: ioloop=kqueue notify=kqueue openssl SQL drivers: mysql Passdb: checkpassword pam passwd passwd-file sql Userdb: checkpassword passwd prefetch passwd-file sql static Dec 19 12:49:42 mail dovecot: auth(default): cache(m52(a)academ.org): Password mismatch Dec 19 12:49:42 mail dovecot: auth(default): file passdb-blocking.c: line 125 (passdb_blocking_verify_plain): assertion failed: (request->extra_fields == NULL) Dec 19 12:49:42 mail dovecot: child 91510 (auth) killed with signal 6 Dec 19 09:20:39 mail pid 96304 (dovecot-auth), uid 65534: exited on signal 6 Dec 19 09:43:31 mail pid 21093 (dovecot-auth), uid 65534: exited on signal 6 Dec 19 09:49:54 mail pid 36637 (dovecot-auth), uid 65534: exited on signal 6 Dec 19 10:02:08 mail pid 40803 (dovecot-auth), uid 65534: exited on signal 6 Dec 19 10:52:43 mail pid 50557 (dovecot-auth), uid 65534: exited on signal 6 Dec 19 10:57:30 mail pid 91182 (dovecot-auth), uid 65534: exited on signal 6 Dec 19 11:33:11 mail pid 94522 (dovecot-auth), uid 65534: exited on signal 6 Dec 19 11:38:21 mail pid 27978 (dovecot-auth), uid 65534: exited on signal 6 Dec 19 11:43:22 mail pid 32969 (dovecot-auth), uid 65534: exited on signal 6 Dec 19 11:48:31 mail pid 36764 (dovecot-auth), uid 65534: exited on signal 6 Dec 19 11:53:32 mail pid 40849 (dovecot-auth), uid 65534: exited on signal 6 Dec 19 11:58:41 mail pid 45037 (dovecot-auth), uid 65534: exited on signal 6 Dec 19 12:03:52 mail pid 49541 (dovecot-auth), uid 65534: exited on signal 6 Dec 19 12:08:51 mail pid 54324 (dovecot-auth), uid 65534: exited on signal 6 Dec 19 12:14:02 mail pid 58746 (dovecot-auth), uid 65534: exited on signal 6 Dec 19 12:19:02 mail pid 63283 (dovecot-auth), uid 65534: exited on signal 6 Dec 19 12:24:11 mail pid 68142 (dovecot-auth), uid 65534: exited on signal 6 Dec 19 12:29:22 mail pid 72969 (dovecot-auth), uid 65534: exited on signal 6 Dec 19 12:34:21 mail pid 77396 (dovecot-auth), uid 65534: exited on signal 6 Dec 19 12:39:32 mail pid 81976 (dovecot-auth), uid 65534: exited on signal 6 Dec 19 12:44:36 mail pid 86217 (dovecot-auth), uid 65534: exited on signal 6 Dec 19 12:44:41 mail pid 91404 (dovecot-auth), uid 65534: exited on signal 6

2 1

[Dovecot] auto-detection of user mailbox type
by John Harper 23 Dec '06

23 Dec '06

The config file indicates that if mail_location is empty, dovecot will try to find the mailboxes automatically (and by implication determine if the user is using mbox or Maildir format). But if the mbox inbox is non-standard (I have procmail delivering to ~/.mail) then one needs to specify mail_location = mbox:~/mail:INBOX=~/.mail and presumably dovecot will no longer try to determine what each user is doing. I'd like to slowly convert users from mbox to Maildir (putting DEFAULT=Maildir/ in the users' .procmailrc accomplishes that from the delivery side) and have dovecot still automatically figure out which way to work, based on finding ~/Maildir (or not). Somehow I don't think mail_location = maildir:~/Maildir:mbox:~/mail:INBOX=~/.mail is going to do what I want. I saw the example on multiple mailboxes using namespaces, but I confess I'm not clear on that especially with ragard to the INBOX setting. I know I can set mail_location on a per-user basis using the userdb (eg ldap) but was hoping to avoid that. Is there a way to specify the details of the mbox configuration, but have dovecot instead use Maildir if that exists? Thanks, John Harper ------------------------------------------------- Senior Systems Administrator Information and Instructional Technology Services University of Toronto Scarborough harper(a)utsc.utoronto.ca

2 3

[Dovecot] Lazy expunge plugin
by Timo Sirainen 23 Dec '06

23 Dec '06

There's now a plugin called lazy_expunge in CVS. Instead of EXPUNGE expunging the mails directly, they're moved to a mailbox with same name in another namespace where user can still copy the mails back. Also DELETEd mailboxes are moved to another namespace. See http://wiki.dovecot.org/Plugins/Lazyexpunge for more information. This is similar to Cyrus's two phase expunge: http://www-uxsup.csx.cam.ac.uk/~dpc22/cyrus/two_phase_expunge.html

2 2

[Dovecot] TR: Mail location
by Fatou Ndiaye 23 Dec '06

23 Dec '06

-----Message d'origine----- De : Fatou Ndiaye [mailto:fatou.ndiaye@orange.sn] Envoyé : jeudi 21 décembre 2006 08:47 À : 'Dovecot Mailing List' Cc : 'Timo Sirainen' Objet : Mail location Hi all, Is it possible to have two mail locations in the dovecot.conf? In fact, the disk where were the mailboxes is almost full and It will be easier for me to just add an other disk hotplug and add an other mail location. -----Message d'origine----- De : dovecot-bounces(a)dovecot.org [mailto:dovecot-bounces@dovecot.org] De la part de Timo Sirainen Envoyé : mercredi 16 août 2006 13:02 À : Marcin Deranek Cc : dovecot(a)dovecot.org Objet : Re: [Dovecot] dovecot 1.0rc6 and LDAP problem On Wed, 2006-08-16 at 09:38 +0200, Marcin Deranek wrote: > Aug 15 18:58:36 ftp dovecot: login: tried to change state 2 -> 2 (if you > can't login at all, see src/lib/fdpass.c) I'm not sure about the LDAP problems, but this is interesting. Are you using login_process_per_connection=yes or no?

2 1

[Dovecot] umask 007 ineffective with newly created Maildir message
by Steve James 22 Dec '06

22 Dec '06

This is for Dovecot 1.0.rc15 from Debian Backports on 3.1 Stable, x86; Filesystems are local reiserfs; IMAPs client is KMail 1.9.5 Non-default settings in dovecot.conf: protocols = imaps ssl_cert_file = /etc/dovecot/mail.cert.pem ssl_key_file = /etc/dovecot/mail.key.pem mail_location = maildir:/var/mail/ambrosia.plus.com/%n mail_extra_groups = mail first_valid_uid = 1000 first_valid_gid = 1000 umask = 007 maildir_copy_with_hardlinks = yes To reproduce:- 1. Using your IMAP client with two IMAP accounts, copy a message from a folder in one account, to a folder in the other account 2. See that the newly created message file is -rw------- If a message is moved between folders on the _same_ account, however, the group permissions are preserved (ie not masked off). So it seems that the umask option is ineffective when the imap daemon creates a new maildir message file. Thanks, Steve. -- BOFH excuse #400: We are Microsoft. What you are experiencing is not a problem; it is an undocumented feature.

4 4

[Dovecot] Assertion failed
by Steven F Siirila 22 Dec '06

22 Dec '06

We have been running 1.0-rc15 for some time on a very small set of users. We recently have increased the user population and just ran into a problem with one user. That user is using a client we apparently had not tested yet and is causing us to get these errors in the logs: [Host name, IP address, and user name are not real] Dec 21 15:23:00 [hostname] dovecot: imap-login: Login: user=<username>, method=PLAIN, rip=10.10.10.10, lip=10.10.10.11, TLS Dec 21 15:23:00 [hostname] dovecot: IMAP(username): file strfuncs.c: line 151 (p_strdup_until): assertion failed: ((const char *) start <= (const char *) end) Dec 21 15:23:00 [hostname] dovecot: child 7151 (imap) killed with signal 6 -- Steven F. Siirila Office: Lind Hall, Room 130B Internet Services E-mail: sfs(a)umn.edu Office of Information Technology Voice: (612) 626-0244 University of Minnesota Fax: (612) 626-7593

2 1

[Dovecot] Deleting mail accounts older than 6 monthes
by Najib Abi Fadel 22 Dec '06

22 Dec '06

Hi, i have a mail server with many users and i am using dovecot as pop3 server. I was wondering if there is a way to detect the last date each user logged in to the server for retrieving his mail. I need to delete the users that has not logged in to their accounts the last 6 monthes. Many thanks for any help. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

4 5

[Dovecot] dbox support state
by Farkas Levente 22 Dec '06

22 Dec '06

hi, what is the current state of dovecot dbox support? is it stable, fast and usable? is it have current advantage over maildir or it will only have when it'll be optimized? is it worth to choose as a default mailbox format in a new dovecot install? thanks. yours. -- Levente "Si vis pacem para bellum!"

3 4

Re: [Dovecot] dbox support state
by Bill Boebel 22 Dec '06

22 Dec '06

On Fri, December 22, 2006 2:14 am, Steffen Kaiser <skdovecot(a)smail.inf.fh-bonn-rhein-sieg.de> said: > On Thu, 21 Dec 2006, Timo Sirainen wrote: > >> One optimization left for it would be to not store flags and keywords to >> the dbox files at all, but keep everything in index files. Once I get >> that implemented, I'll start benchmarking it. Of course the problem with >> that is that it relies on index files completely then. > > IMHO this is not good for disaster recovery and makes life needlessly hard > in such case. Esp. when both files become out-of-sync, you need a cunning > tool to re-construct any good state, rather than a simple "REINDEX". This > should apply to each kind of "index" file. Also, consider upgrades to > newer index file formats etc.pp. > > Are there really that many writes of message attributes? I mean, there is > only an improvement because you have just one write into the indexes > rather than two, one to the indexes and one into the message. > You've wrote that you reserve space for the flags in mbox, in case they > get updated, so you reduce the probability to rewrite the whole mbox for > each flag. Doing so should apply to dbox as well? It should be an option. Big mail systems can benefit from this optimization, but many systems may not see anything noticeable. You can do a lot of cool things with your storage once you're dealing with write-once mail data, where all actions after receiving a message get written somewhere outside of where the mail content is stored... including expunges. This is a step in that direction. Bill

1 0