December 2008 - dovecot

[Dovecot] [PATCH, RFC] add APOP authentication mechanism
by Andrey Panin 14 Aug '17

14 Aug '17

Hello all, this patch add APOP authentication mechanism to dovecot 1.0-test23. Please take a look. Best regards. -- Andrey Panin | Linux and UNIX system administrator pazke(a)donpac.ru | PGP key: wwwkeys.pgp.net

3 2

[Dovecot] Missing return-path on vacation messages
by Stephen Vaughan 30 Jul '09

30 Jul '09

Hi, I can see this has been discussed previously, was just wondering if it's been fixed in v1.1.x? -- Best Regards, Stephen

3 11

[Dovecot] Connecting to dovecot
by Grant Lowe 06 Jul '09

06 Jul '09

Hi All, I've got a brand new dovecot installation. I'm new to dovecot, so please be gentle :-) Anyway, I'm getting some errors when I try to connect to dovecot. I've tried searching the web and haven't been able to find a lot of information. Here's the config info: # dovecot --version 1.1.2 # dovecot -n sudo dovecot -n # 1.1.2: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot.log ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot//login login_executable: /usr/local/libexec/dovecot/imap-login mail_location: /var/mail/%u auth default: verbose: yes passdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: static args: uid=vmail gid=vmail home=/var/mail/%u # Here are the errors I'm getting. dovecot: Sep 16 18:44:15 Info: imap-login: Login: user=<wfoatst>, method=PLAIN, rip=172.20.58.4, lip=172.20.8.215 dovecot: Sep 16 18:44:15 Error: IMAP(wfoatst): mail_location not set and autodetection failed: Mail storage autodetection failed with ho me=/var/mail/wfoatst Thanks!

3 3

[Dovecot] Spliting Folders for Efficiency
by Daniel Watts 28 Jun '09

28 Jun '09

Dear Timo, Would there be any sense in giving Dovecot the option to split folders into multiple subfolders when they reached a specified size (probably message count) limit? Dovecot would monitor folders and when they reached, say, 10,000 messages, silently split the folder on the filesystem to ensure that access remains fast. I know that Dovecot scales very well but this would give practically unlimited storage capability and also keep things fast. You could even have it so that the latest 100 messages are kept in their own folder for fast access. .Folder.new .Folder.cur .Folder.tmp could become: .Folder__1.new .Folder__1.cur .Folder__1.tmp and .Folder__2.new .Folder__2.cur .Folder__2.tmp with Dovecot merging them before display as just "Folder" within the mail client. This could be further extended so that Dovecot could be configured to store 'old' message folders in a separate location. We could then have slower+cheaper+larger storage mounted so that 'old mail' does not take up the expensive local SCSI disks on the machine. Mail from 2 years ago is much less likely to be accessed than mail from the last week. This would provide very neat behind-the-scenes archiving functionality. Looking forward to hearing your thoughts. Best, Daniel -- Squirrelmail Stable 1.4.8 (and developing on 1.5.2) PHP 5.x Hardened with Eaccelerator Apache 2.x Mysql 5.0.x Imapproxy over Dovecot 1.0.rc27 with Maildir all running on Gentoo Linux for ~5,000 users.

7 11

[Dovecot] compressed mbox patch
by Axel Thimm 16 Jun '09

16 Jun '09

Some ages ago there existed a compressed mbox patch, but now all I can find are posting about it. Does such a beast exist and would it remotely apply to today's dovecot? If not, is there any hope that something like that emerges? Thanks! -- Axel.Thimm at ATrpms.net

3 5

[Dovecot] Authentication cache, failure to login after changed password
by Tom Sommer 16 Jun '09

16 Jun '09

Hi, I have an issue with the authentication cache. When a user changes his password, the cache doesn't seem to get flushed. Meaning the user is unable to log in to his IMAP account after changing his password. Flow: - Log into IMAP account using pass1 - Approved - Stored in auth cache - Change password to pass2 in MySQL - Log into IMAP account using pass2 - Access is denied - Restart dovecot - Log into IMAP account using pass2 - Approved I'd really like to continue to use the auth cache, is there any solution to the above? perhaps a way to debug the cache and auth process? I wasn't able to activate auth_debug without restarting Dovecot and solving the problem. Using version 1.1.1, MySQL userdb, with "nopassword=Y". Maybe it's due to nopassword? Thanks -- Tom

2 16

[Dovecot] Feature Missing OUTBOX Folder
by Frank Doege 01 Jun '09

01 Jun '09

Hi Dovecot People, i have switched my system from courier-imap to dovecot and iam quite happy with it, the performance is well and i had nearly no problems. One little feature iam missing is in Courier i had a folder called "Outbox" there i could paste mails which i want to sent out. In some networks its not always available to sent mails via port 21, i know i could just set up my email server to another port but it was a nice feature. Is this a big afford or is it just alittle hack ? could it done via a little plugin ? Thanks Timo & all others for the great work ! Frank

5 7

[Dovecot] odd epoll() errors
by Ralf Hildebrandt 02 Apr '09

02 Apr '09

>From my log: Dec 29 16:43:58 postamt dovecot: Dovecot v1.1.7 starting up Dec 29 16:43:59 postamt dovecot: Fatal: imap-login: epoll_create(): Too many open files Dec 29 16:43:59 postamt dovecot: Temporary failure in creating login processes, slowing down for now Dec 29 16:43:59 postamt dovecot: Fatal: imap-login: epoll_create(): Too many open files Dec 29 16:43:59 postamt dovecot: Fatal: pop3-login: epoll_create(): Too many open files Dec 29 16:43:59 postamt dovecot: Fatal: imap-login: epoll_create(): Too many open files Dec 29 16:43:59 postamt dovecot: Fatal: imap-login: epoll_create(): Too many open files Dec 29 16:43:59 postamt dovecot: Fatal: pop3-login: epoll_create(): Too many open files Dec 29 16:44:59 postamt dovecot: Fatal: imap-login: epoll_create(): Too many open files Dec 29 16:44:59 postamt dovecot: Fatal: pop3-login: epoll_create(): Too many open files Dec 29 16:44:59 postamt dovecot: Fatal: pop3-login: epoll_create(): Too many open files Dec 29 16:44:59 postamt dovecot: Fatal: imap-login: epoll_create(): Too many open files Dec 29 16:44:59 postamt dovecot: child 15976 (login) returned error 89 (Fatal failure) Dec 29 16:44:59 postamt dovecot: child 15977 (login) returned error 89 (Fatal failure) Dec 29 16:44:59 postamt dovecot: child 15978 (login) returned error 89 (Fatal failure) Dec 29 16:44:59 postamt dovecot: child 15979 (login) returned error 89 (Fatal failure) Dec 29 16:44:59 postamt dovecot: child 15981 (login) returned error 89 (Fatal failure) Dec 29 16:44:59 postamt dovecot: child 15982 (login) returned error 89 (Fatal failure) Dec 29 16:44:59 postamt dovecot: Fatal: imap-login: epoll_create(): Too many open files Dec 29 16:45:59 postamt dovecot: Fatal: pop3-login: epoll_create(): Too many open files Dec 29 16:45:59 postamt dovecot: Fatal: pop3-login: epoll_create(): Too many open files Dec 29 16:45:59 postamt dovecot: child 17052 (login) returned error 89 (Fatal failure) Dec 29 16:45:59 postamt dovecot: child 17053 (login) returned error 89 (Fatal failure) Dec 29 16:45:59 postamt dovecot: child 17054 (login) returned error 89 (Fatal failure) Dec 29 16:45:59 postamt dovecot: child 17055 (login) returned error 89 (Fatal failure) Dec 29 16:45:59 postamt dovecot: child 17056 (login) returned error 89 (Fatal failure) Dec 29 16:45:59 postamt dovecot: child 17057 (login) returned error 89 (Fatal failure) Dec 29 16:45:59 postamt dovecot: Fatal: imap-login: epoll_create(): Too many open files Dec 29 16:46:59 postamt dovecot: Fatal: pop3-login: epoll_create(): Too many open files Dec 29 16:46:59 postamt dovecot: Fatal: pop3-login: epoll_create(): Too many open files Dec 29 16:46:59 postamt dovecot: child 17984 (login) returned error 89 (Fatal failure) Dec 29 16:46:59 postamt dovecot: child 17985 (login) returned error 89 (Fatal failure) Dec 29 16:46:59 postamt dovecot: child 17986 (login) returned error 89 (Fatal failure) Dec 29 16:46:59 postamt dovecot: child 17987 (login) returned error 89 (Fatal failure) Dec 29 16:46:59 postamt dovecot: child 17988 (login) returned error 89 (Fatal failure) Dec 29 16:46:59 postamt dovecot: child 17989 (login) returned error 89 (Fatal failure) Dec 29 16:46:59 postamt dovecot: child 17990 (login) returned error 89 (Fatal failure) Dec 29 16:46:59 postamt dovecot: Fatal: imap-login: epoll_create(): Too many open files Dec 29 16:47:59 postamt dovecot: Fatal: pop3-login: epoll_create(): Too many open files Dec 29 16:47:59 postamt dovecot: Fatal: pop3-login: epoll_create(): Too many open files Dec 29 16:47:59 postamt dovecot: child 18791 (login) returned error 89 (Fatal failure) Dec 29 16:47:59 postamt dovecot: child 18792 (login) returned error 89 (Fatal failure) Dec 29 16:47:59 postamt dovecot: child 18793 (login) returned error 89 (Fatal failure) Dec 29 16:47:59 postamt dovecot: child 18794 (login) returned error 89 (Fatal failure) Dec 29 16:47:59 postamt dovecot: child 18796 (login) returned error 89 (Fatal failure) Dec 29 16:47:59 postamt dovecot: Fatal: imap-login: epoll_create(): Too many open files Dec 29 16:47:59 postamt dovecot: Fatal: imap-login: epoll_create(): Too many open files Dec 29 16:48:59 postamt dovecot: Fatal: pop3-login: epoll_create(): Too many open files Dec 29 16:48:59 postamt dovecot: Fatal: imap-login: epoll_create(): Too many open files Dec 29 16:48:59 postamt dovecot: child 19618 (login) returned error 89 (Fatal failure) Dec 29 16:48:59 postamt dovecot: child 19614 (login) returned error 89 (Fatal failure) Dec 29 16:48:59 postamt dovecot: child 19620 (login) returned error 89 (Fatal failure) Dec 29 16:48:59 postamt dovecot: Fatal: imap-login: epoll_create(): Too many open files Dec 29 16:48:59 postamt dovecot: Fatal: imap-login: epoll_create(): Too many open files Dec 29 16:48:59 postamt dovecot: Fatal: pop3-login: epoll_create(): Too many open files Dec 29 16:48:59 postamt dovecot: Fatal: imap-login: epoll_create(): Too many open files ... Dec 29 20:58:59 postamt dovecot: Fatal: imap-login: epoll_create(): Too many open files Dec 29 20:58:59 postamt dovecot: child 5268 (login) returned error 89 (Fatal failure) Dec 29 20:58:59 postamt dovecot: child 5269 (login) returned error 89 (Fatal failure) Dec 29 20:58:59 postamt dovecot: child 5274 (login) returned error 89 (Fatal failure) Dec 29 20:58:59 postamt dovecot: Fatal: imap-login: epoll_create(): Too many open files -- Ralf Hildebrandt (Ralf.Hildebrandt(a)charite.de) snickebo(a)charite.de Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de "Java is, in many ways, C++--." - Michael Feldman.

3 4

[Dovecot] IMAP ACLs and global ACLs in v1.2
by Timo Sirainen 23 Feb '09

23 Feb '09

I just committed code for IMAP ACL support based on the code from Kolab people. I did quite large changes though. I also changed how global ACLs are handled. Previously local ACLs could override global ACLs, but now that users are able to modify the ACLs I think it should be the other way around. From what I've heard global ACLs are typically added for things like 1) disallowing user from doing something in specific mailboxes such as expunge messages, 2) giving a specific master user access to some mailboxes ONLY, such as voicemail. For 1) case a user really shouldn't be able to grant himself privileges back but still should be able to share the mailbox to others (so the global ACL should have 'a' privilege). For 2) case a user shouldn't be able to remove privileges from the voicemail. So now the user can freely update the local ACLs in whatever way he wants. But in the end if there are any global ACLs, all the local ACLs for those identifiers are ignored. Also local negative identifiers are ignored, so that e.g. global "user=foo lr" can't be disabled by a local "-user=foo lr" ACL. I guess I should update the Wiki ACL page about how exactly the ACLs are applied now that they're well in my memory. :) One thing I'm not really sure about is the "owner" handling. IMAP ACL specifications have no such concept. I think many/most other servers simply add a default ACL for the user name directly. It's a useful concept though, especially with the global ACLs. So currently Dovecot replies: x getacl inbox * ACL "inbox" "owner" lrwstiekxacd x OK Getacl completed. But should it just internally convert "owner" to "username" when replying? But then again if there's a separate rule directly for the "username" it breaks. Do any of the existing ACL-capable IMAP clients want to see the username in the ACL reply or can they handle "owner" just fine? Also what about global ACLs? The current code just lists them twice with local ACLs, which is definitely wrong: x getacl foo * ACL "foo" "xx" w "xx" lr "owner" lrwstiekxacd x OK Getacl completed. Perhaps the global ACLs could have a prefix character? Maybe '#'? Which reminds me, the current dovecot-acl file is mapped to IMAP ACLs like this: dovecot-acl : IMAP ACL - anyone : anyone - authenticated : authenticated - owner : owner - user=name : name - group=name : $name - group-override=name : !$name So all global ACLs would get the # prefix, like #anyone, #name, #!$name. Any thoughts? BTW. Listing shared mailboxes still doesn't work. I guess we'll see tomorrow if I still have energy to get that done.

6 14

[Dovecot] DIGEST-MD5 user/realm mismatch with Postfix
by Darren Pilgrim 22 Feb '09

22 Feb '09

This is a follow-on to the "SQL field format for digest-md5?" thread. After some additional debugging, I've found the problem is a mismatch in what Dovecot expects and Postfix uses for the user and realm. For a username "user(a)example.com" and password "sekret", Dovecot expects: username = "user" realm = "example.com" but Postfix sends the checksum of: username = "user(a)example.com" realm = "" How do I fix this?

2 1