- dovecot - dovecot.org

[Dovecot] Will pay $500 towards a Dovecot feature
by Marc Perkel 25 May '07

25 May '07

10 days ago I proposed this addition (see below) to Dovecot and got a lot of positive response. I would like to make it happen. I'm willing to contribute $500 to the development of this feature. It doesn't have to be implemented perfectly but needs to be workable to the extent that I can telnet into the Dovecot server and run it manually from the command line. I want to at least be able to run a simple script that I will write to add or remove someone from a black list text file. Timo has limited time but has indicated that he will allow it as a kind of undocumented feature (or wiki documented only). This is a sort of proof of concept feature and if it ever becomes a standard the standard will probably be different. However, we should implement it in a way that would be as close to a standard as possible. So - I'm looking for a programmer to make it happen. I'm also looking for others who might also kick in a few bucks as well if necessary. Here's the rough spec. ---------- Here's some thoughts I'd like to throw out there. I know it's not standard IMAP protocol but someone has to try new ideas first and I want to see what people (Timo) think of this. IMAP establishes a connection between the client and the server. Wouldn't it be great if it could be a conduit to let custom Thunderbird plugins talk to custom server application over the IMAP interface? For example, personalized server settings. Suppose for example I want Thunderbird to edit my server side white lists or black lists or any other setting? Wouldn't it be nice if IMAP supported these changes? The connection is made. It's a secure connection that's been authenticated. Lets use it! Here's my initial thoughts on this. Suppose we extended IMAP to include an EXECUTE command as follows: EXECUTE command parameter, parameter .... On the server side is a config file that has the commands that execute will allow and what programs they run. When the execute command is seen by Dovecot then Dovecot runs the program in the list with the parameters passed. For example, suppose there is a command to add a user to a server side blacklist. 100 execute blacklist add joe(a)smith.com 100 ok Dovecot would open a two way connection to the server application allowing the client to talk to any application that is configured and can send and receive text. The connection persists until the server end terminates or the client closes the connection. With a tool like this one can write generic applications easily that would greatly expand what email clients can do interacting with the server. Not only can setting be changes but you could interact with server side calendars, pick up voice messages from phone systems, run any sort of groupware, all over a generic IMAP connection with this simple extension. Example: 100 EXECUTE calendar 100 ok 100 list schedule today 8:00 10:00 100 8:00 make coffee 100 9:00 meeting with boss 100 9:30 Call Joe Blow at 415-555-1212 100 ok 100 quit 100 ok One thing I'd like to use it for is an outgoing SMTP connection to send outgoing email over IMAP. A session might look like this: 999 EXECUTE smtp 999 220 darwin.ctyme.com ESMTP Exim 4.67 Sun, 13 May 2007 06:52:26 -0700 999 helo ctyme.com 999 250 darwin.ctyme.com Hello localhost [127.0.0.1] 999 mail from:marc@perkel.com 999 250 OK 999 rcpt to:dovecot@dovecot.org 999 250 Accepted ...... 999 quit 999 OK Config File: There would have to be a config file that would be a table of what command run what. An example might look like this: calendar: /usr/bin/dovecot/calendar blacklist: /etc/exim/scripts/blacklist Probably might eventually want to add UID/GID and root directory restrictions for security. Login information and connection IP should be passed in the environment.

17 30

Re: [Dovecot] Converting mbox to Maildir, all prior read messages are downloaded as new
by Eric and Barbara Sammons 24 May '07

24 May '07

Can you elaborate on this convert plugin? I have not heard of it and am curious if it is available in 0.99. Thank you! Bruce Bodger wrote: > > On May 24, 2007, at 3:22 PM, Eric and Barbara Sammons wrote: > >> I am running dovecot 0.99. Everything works great; however, now I am >> looking at several different tools to convert mbox to Maildir. It >> seems the tools, mb2md.pl, perfect_maildir.pl, and others all do what >> they claim; however, when the messages are converted and they are >> stored in Maildir/cur, the email clients download these messages as new. > > Like you, I played with all the available scripts. Settled on using > ONLY Dovecot's convert plugin to convert a uw-imap mbox system to > Dovecot maildir. Believe it or not, it ran 100% perfectly and users > never even noticed the switch! > > Good luck. > B. Bodger > New York, NY >

3 2

[Dovecot] quota plugin
by maximatt 24 May '07

24 May '07

hi... i not undestand this plugin (quota) , because if i set a value 10240 (like in example) when i send a 4 messages with attaches sizes like 4MB they do not nothing, but if i want to send a message like 12MB the dont me do that, but in the first way the user inbox have like 20MB. ¿:(? i have these settings for this plugin: protocol imap { mail_plugins= quota imap_quota } plugin { quota= maildir:storage=10240 } ¿can anybody explain me that? :( thanks in advance!!! :)

1 0

[Dovecot] needing UNSELECT to notice new mail?
by Greg Troxel 24 May '07

24 May '07

I am running NetBSD/i386 3.1ish and 4.0ish dovecot 1.0.0 procmail delivering into maildirs gnus from CVS head emacs 21.4 thunderbird 2 gnome mail-notification 4 configured to required SSL. Basically everything works fine except that in gnus typing 'g' in the *Group* buffer, which is supposed to check for new mail and list the number of new messages, fails to notice new mail. Notably, gnus does not do an UNSELECT or CLOSE when it is done with a group. So basically the following sequence of commands SELECT "INBOX" blah blah EXPUNGE STATUS "INBOX" shows no unseen but really there is one With (setq nnimap-need-unselect-to-notice-new-mail t) gnus will do UNSELECT before STATUS, and then things work fine. Another gnus user reports what seems like the same problem with Courier IMAP. So, is dovecot complying with the IMAP spec here? Is there some notion of a transaction bracketed by SELECT/{UNSELECT,CLOSE}, and is that using something like READ COMMITTED isolation so that it doesn't see messages added by other transactions? Or should dovecot be not relying on cached state and revalidate the mailbox on STATUS, even if it is already SELECTED? Further, is it the group's opinion that a well-behaved client would UNSELECT or CLOSE when the user takes an action that indicates being finished with a mailbox? Or is it reasonable to leave a mailbox SELECTed as an optimization. It seems that for Thunderbird, etc., the user sits in INBOX with IDLE, but with gnus I tend to be in *Group* with no mailboxes selected.

2 4

[Dovecot] unexpected error message (maildir_sync_index)
by Kyle Wheeler 24 May '07

24 May '07

Hello, I recently saw these errors in my log, and one of my users complained that Dovecot disconnected him unexpectedly. Any idea what might have happened? dovecot: Error: IMAP(bmoore(a)forkit.org): file maildir-sync.c: line 1075 (maildir_sync_index): assertion failed: (uid > prev_uid) dovecot: Error: IMAP(bmoore(a)forkit.org): Raw backtrace: /usr/local/libexec/dovecot/imap [0x80b6501] -> /usr/local/libexec/dovecot/imap [0x80b641c] -> /usr/local/libexec/dovecot/imap(maildir_sync_index+0x902) [0x8069042] -> /usr/local/libexec/dovecot/imap [0x8069243] -> /usr/local/libexec/dovecot/imap(maildir_storage_sync_init+0x48) [0x8069428] -> /usr/local/libexec/dovecot/imap(imap_sync_init+0x40) [0x8062590] -> /usr/local/libexec/dovecot/imap(cmd_sync+0x71) [0x80626d1] -> /usr/local/libexec/dovecot/imap(cmd_noop+0x26) [0x8059cc6] -> /usr/local/libexec/dovecot/imap [0x805b878] -> /usr/local/libexec/dovecot/imap [0x805b907] -> /usr/local/libexec/dovecot/imap(_client_input+0x6c) [0x805bfbc] -> /usr/local/libexec/dovecot/imap(io_loop_handler_run+0x120) [0x80bc7e0] -> /usr/local/libexec/dovecot/imap(io_loop_run+0x28) [0x80bb808] -> /usr/local/libexec/dovecot/imap(main+0x4b0) [0x8063fd0] -> /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xc8) [0xb7e7eea8] -> /usr/local/libexec/dovecot/imap [0x8056a11] dovecot: Error: child 8418 (imap) killed with signal 6 ~Kyle -- All we have to decide is what to do with the time that is given us. -- Gandalf the Grey

2 2

[Dovecot] Timeout while waiting for shared lock for index file /var/mail/XXX/Maildir/dovecot.index
by Giannis Zachariadis 24 May '07

24 May '07

Hello, I'm using dovecot v1.0rc23 for about 500 users since february with no particular problems. I'm using Maildir format and ldap authentication. A recently added user can't check his mails any more. In the logs I get May 23 14:35:58 mailsrv deliver(XXXX): [ID 702911 mail.error] Timeout while waiting for shared lock for index file /var/mail/XXXX/Maildir/dovecot.index The user connects with IMAP to retreive his mails. Currently I can login to his account with pop3 and retreive the mails, but when it comes to IMAP I get this error and no mail at all. thanks in advance, -- giannis.

2 1

[Dovecot] Updated v1.1 and summer plans
by Timo Sirainen 24 May '07

24 May '07

Webmail.us will be sponsoring my Dovecot development for this summer. Other companies are also welcome to participate in the costs. Participation gets you: - listed in Credits in www.dovecot.org - listed in AUTHORS file - you can tell me how you want to use the feature and I'll make sure that it supports it (within reasonable limits) For already implemented v1.1 features, see http://www.dovecot.org/list/dovecot/2007-April/021974.html Some of those features require some more testing (new SORT and THREAD code especially) and a bit of fixes to mailbox list indexes. Otherwise I think it's working pretty well already, I've been using it for a long time for my own mails. Upcoming v1.1 features, more or less implemented in this order: - Index file optimizations: http://www.dovecot.org/list/dovecot/2007-May/022591.html - Less indexing for POP3 users (both in pop3 and in deliver) - Replace Squat FTS indexes with my new design - Configurable mail_log plugin - Limit number of connections for a user - A combined LIST + STATUS command (or possibly NOTIFY extension? http://tools.ietf.org/html/draft-gulbrandsen-imap-notify-03) - Fully supported shared mailboxes and IMAP ACL extension: http://www.dovecot.org/list/dovecot/2007-April/021624.html - Remote (shared) mailboxes. Automatic proxying, but possibly also support for MAILBOX-REFERRALS extension if it's not much extra trouble (few clients support it, so probably not worth the trouble unless it can be done in a couple of hours) - Remove unused keywords from mailboxes - Some other small things Upcoming v1.1/v1.2/v2.0 features (planned to be implemented at the end of the summer): - virtual mailboxes: http://www.dovecot.org/list/dovecot/2007-May/022828.html - dbox redesign: http://www.dovecot.org/list/dovecot/2007-May/022602.html Implementing the above features will keep me busy for most of the summer, but there have also been requests for replication support (http://www.dovecot.org/list/dovecot/2007-May/022792.html) I'm interested in implementing it as well, but unfortunately it looks like I don't have time for it at least for the next 3 months or so. There's already at least one company that's willing to pay for replication, but if you're also interested please let me know. Perhaps someone else could implement it instead (if you're interested, please let me know), or if not it'll just have to wait until I have time for it.

6 10

[Dovecot] dovecot, uidplus and apple mail.app (was: Re: Will pay $500 towards a Dovecot feature = calender ?)
by DINH Viêt Hoà 24 May '07

24 May '07

On 5/24/07, Robert Schetterer <robert(a)schetterer.org> wrote: > DINH Viêt Hoà schrieb: > > On 5/24/07, Timo Sirainen <tss(a)iki.fi> wrote: > >> On Thu, 2007-05-24 at 09:37 +0200, Adi Kriegisch wrote: > >> > As a calendaring solution with group calendars and all the like, use > >> CalDAV > >> > -- a webdav extension designed for exactly that purpose. There is an > >> > excellent implementation available at: http://rscds.sourceforge.net/ > >> (also > >> > Apple has released their calendar server supporting caldav open > >> source). > >> > >> I'm using iCal in my OSX Laptop and Evolution in Linux Desktop. Once OSX > >> 10.5 is released with its CalDAV support I'm planning on installing some > >> CalDAV server and probably implement dovecot-auth support for it. > >> > >> Perhaps some day in future I'll also implement CalDAV, but first I'll > >> need to write a web server. :) > > > > CalDAV server of Apple is open-sourced. > > I heard that Cyrus Daboo was involved in :) > > That suggests it could be a good implementation. > > > hi @ll i have a customer who uses > ical apple with a apache webdav setup , this seems to works nice, > but there are a lot of problems with apple mail and imap about apple mail and imap, I think that's because apple mail uses UIDPLUS to work properly. -- DINH Viêt Hoà

1 0

Re: [Dovecot] Will pay $500 towards a Dovecot feature = calender ?
by Robert Schetterer 24 May '07

24 May '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Curtis Maloney schrieb: > Robert Schetterer wrote: >> Hi all, i think sombody would have like to a imap calender solution >> implemented in dovecot? Am i right here? >> >> You can have simular right now using thunderbird , lightning, kolab >> plugin, ( should be shown in horde webmail too ) > > I tried the kolab plugin... it never worked for me. So disappointed - > especially since synchronising my contacts/calendar between sites would > be very valuable. > > -- > Curtis Maloney > cmaloney(a)cardgate.net > Hi Curtis, sorry to hear this, i know kolab extension is still beta but it works for me in small setups, maybe you should inform the devolopers about your problems and they may help you - -- Mit freundlichen Gruessen Best Regards Robert Schetterer https://www.schetterer.org Munich/Bavaria/Germany -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGVW5XfGH2AvR16oERAv4tAJ9d5ijEXK7F/cujwCp32dm9diMeQwCfQNwb N8RDveBHLqW73zZABw6z6GA= =EDpj -----END PGP SIGNATURE-----

1 0

[Dovecot] Old style qouta to new style convert?
by Mart Pirita 24 May '07

24 May '07

Tere. I'm using Debian, postfix & dovecot, with system quotas and settings in dovecot.conf: default_mail_env = maildir:%h/Maildir:INDEX=/var/spool/dovecot/index/%u:CONTROL=/var/spool/dovecot/control/%u But if system quota is full, users won't get new messages but won't get also any kind information, and also in mail.log is nothing. Is this normal? Should I use dovecot -s own quota with postfix or dovecot own LDA is needed? And how to convert these index and control files into users homedir? Just making changes in dovecot.conf seems not be good idea? Or it is and the control and indexes will be created again? -- Mart

2 1

[Dovecot] Courier migrating issues: indexes, maildirsize, update query
by Jan van den Berg 24 May '07

24 May '07

Hi, (my first post to the list) I'm in the process of testing Dovecot to see whether it meets our needs to replace our current Courier setup which serves well over 100.000 mailboxes (pop3 and imap: mysql with NFS) So far dovecot seems pretty straight forward; however I ran into a couple of things that I'm curious about. 1. What's the deal with dovecot.index/dovecot.index.log/dovecot.index.cache. I understand Dovecot uses this for POP3 primarily but this will no doubt cause a lot of overhead on our platform. Also getting this to work with our NFS setup would be a pain (locking etc.). I've been following this discussion: http://www.dovecot.org/list/dovecot/2006-January/thread.html#10758; and it ends with C. Malony suggesting that an disable index option would be in place; but no further action is taken. Basically I want to get rid of the index files (courier also doesn't use any). Any suggestions; will there be a disable-index option? 2. One of the reasons we want to get rid of Courier is because the maildirsize is often incorrect. Whether this is because of a bad Courier implementation or NFS issues or whatever, I haven't figured out yet. But I'd like to test this function in Dovecot; but there seems to be very little documentation. I read the link http://wiki.dovecot.org/Quota/Dict but this info is too scarce. Any pointers on where to go? 3. In our MySQL setup we have a field with the latest poptime and pophost (IP). This info can come in handy when troubleshooting or filtering out inactive mailboxes. With our Courier setup this field gets updated by a rather elaborate script that checks the logs and runs updates queries. I could get this to work for Dovecot; but with Dovecot being more actively in development, I wonder could this be a feature; like after a user_query, another update query? Cheers, Jan

3 6

[Dovecot] May 21 09:13:14 mail dovecot: imap-login: No authentication sockets found
by dhottinger＠harrisonburg.k12.va.us 23 May '07

23 May '07

I started getting this message this morning: May 21 09:13:14 mail dovecot: imap-login: No authentication sockets found Ive been runing dovecot on a fc6 dell poweredge 2950 for about 4 weeks now with no issues. Im authenticating against openldap 2.3.27. It appears ok. I restarted ldap, and dovecot, and everything looked fine for a few minutes, then this started again. I have around 720 users. Is there a setting in the dovecot.conf that I can use to fix this? Or is the problem elsewhere? -- Dwayne Hottinger Network Administrator Harrisonburg City Public Schools

5 11

[Dovecot] Quota Limits Newbie Question
by Craig Carriere 23 May '07

23 May '07

I have Dovecot 1.0 running on a SLES 10 mail server using postfix 2.2 and amvisd-maia. The mailboxes are stored in Maildir format with all the domains and users stored in a mySQL database. I would like to implement quotas for the system and have looked at the VDA patch for postfix and/or quotas within Dovecot. Any advantages to either? From what I can see from a couple of searches, Dovecot does not appear to respond either to the sender or recipient when they are over quota while one can set-up postfix-vda to do so which would be of value. Thank you for the time and input.

1 0

[Dovecot] index-related crash in dovecot 1.0.0
by J.Wendland＠scan-plus.de 23 May '07

23 May '07

Hi, dovecot crashes with the following trace when accessing some Maildirs: dovecot: 2007-05-16 13:30:09 Error: IMAP(6126360): file index-mail-headers.c: line 260 (index_mail_parse_header): assertion failed: (part != NULL) dovecot: 2007-05-16 13:30:09 Error: IMAP(6126360): Raw backtrace: imap [6126360] [0x80b6d6b] -> imap [6126360] [0x80b6769] -> imap [6126360] [0x808abda] -> imap [6126360](message_parse_header+0x56) [0x80b2166] -> imap [6126360](index_mail_parse_headers+0x113) [0x808ad03] -> imap [6126360] [0x80891bb] -> imap [6126360](index_mail_get_special+0x112) [0x8089632] -> imap [6126360] [0x806dc3b] -> imap [6126360](mail_get_special+0x16) [0x80a7cf6] -> imap [6126360] [0x805dc2f] -> imap [6126360](imap_fetch+0xf3) [0x805d7b3] -> imap [6126360](cmd_fetch+0xff) [0x805845f] -> imap [6126360](cmd_uid+0x52) [0x805b272] -> imap [6126360] [0x805be65] -> imap [6126360] [0x805bddb] -> imap [6126360](_client_input+0x6d) [0x805bf4d] -> imap [6126360](io_loop_handler_run+0x128) [0x80bd1a8] -> imap [6126360](io_loop_run+0x28) [0x80bc618] -> imap [6126360](main+0x69) [0x80645c9] -> /lib/libc.so.6(__libc_start_main+0x9e) [0x400383be] -> imap [6126360] [0x8056a01] dovecot: 2007-05-16 13:30:09 Error: child 6845 (imap) killed with signal 6 The command leading to the crash is (line wrapped for readability): UID FETCH 1:214748367 (UID ENVELOPE BODYSTRUCTURE INTERNALDATE RFC822.SIZE FLAGS BODY.PEEK[HEADER.FIELDS (Importance X-Priority Priority X-PIM-INFOS Content-Type Date)]) When I connect to dovecot and simply fetch with the following command: UID FETCH 1:* (ENVELOPE) dovecot seems to updates its dovecot.index.cache files and the crash never appears again. I have a mailbox that can be used to reproduce the error. Best wishes, Jörg # dovecot --version 1.0.0 # dovecot -n # /etc/dovecot/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot-error.out info_log_path: /var/log/dovecot.out log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login login_greeting: DVAG IMAP server ready login_process_per_connection: no login_chroot: no login_greeting_capability: yes login_processes_count: 5 login_max_connections: 2048 max_mail_processes: 2048 verbose_proctitle: yes mail_extra_groups: mail default_mail_env: maildir:%h/Maildir mail_location: maildir:%h/Maildir mail_read_mmaped: yes maildir_copy_with_hardlinks: yes mail_drop_priv_before_exec: yes mail_executable: /usr/local/bin/dovecot-postlogin mail_plugins: quota imap_quota acl namespace: type: private separator: . prefix: INBOX. location: maildir:%h/Maildir inbox: yes auth default: mechanisms: plain login master_user_separator: * worker_max_count: 64 passdb: driver: passwd-file args: /etc/dovecot/dovecot-master.pwd master: yes passdb: driver: checkpassword args: /usr/local/bin/checkpassword-zob userdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf plugin: quota: maildir:storage=0 acl: vfile:/etc/dovecot/acls -- Sicherheit - Verfügbarkeit - Kontinuität ------------------------------------------------------------------------- IT-Service-Management von ScanPlus GmbH Tel. +49 731 92013 150 Lise-Meitner-Straße 5, D-89081 Ulm, Germany Fax. +49 731 92013 29 150 Web: http://www.scan-plus.de/ Mail: wendland(a)scan-plus.de -------------------------------------------------------------------------

2 5

[Dovecot] dovecot + ldap tls
by aza zel 23 May '07

23 May '07

hi... i trying to have a secure conetion between dovecot and directory server, but i cant do it. The documentation are so poor ( http://wiki.dovecot.org/AuthDatabase/LDAP) these are my configurations files: (pre: i have a directory server accepting secure conections (port 389 via TLS and port 636 via SSL). File "/opt/csw/etc/dovecot-ldap.conf": hosts=100.0.4.98 dn = cn=bindmailusers,cn=mailusers,dc=prueba,dc=uy dnpass =passbindmailUsers tls = yes ldap_version = 3 base= cn=mailUsers,dc=prueba,dc=uy deref = never scope = subtree user_attrs = uidnumber=uidnumber, gidnumber=gidnumber,homedirectory=homedirectory, mailbox=mailbox user_filter = (&(objectClass=mailaccount)(uid=%u)(disableimap=FALSE)) pass_attrs = uid=uid,userpassword=password pass_filter= (&(objectClass=mailaccount)(uid=%u)(disableimap=FALSE)) default_pass_scheme = CRYPT user_global_uid =12356 user_global_gid =12356 File "/opt/csw/etc/openldap/ldap.conf" (openldap client): TLS_REQCERT allow host 100.0.4.98 TLS_CACERT /opt/csw/etc/postfix/ldap-cert/cacert.pem these are my log file: # tail dovecot-log.log : : dovecot: May 22 15:48:31 Error: auth(default): LDAP: ldap_start_tls_s() failed: Can't contact LDAP server any suggest :( -- Salu2 ;)

2 2

[Dovecot] need some help please
by Paul A 23 May '07

23 May '07

We currently had dovecote 99 running and ran into some issues with it, mainly our pop3 sessions timeout and were slow. I upgraded to the latest version and im serving imap with pop3 using pam. Heres my pam file: [root@pop etc]# cat /etc/pam.d/dovecot #%PAM-1.0 auth required pam_unix.so nullok account required pam_unix.so The problem I'm having is I can authenticate to imap, but it's very slow, however pop3 doesn't work at all. I have auth debug set and I can see the imap authentication but not pop3. Here is my config file. ssl_disable: yes login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login mail_location: maildir:/home/%1u/%u/Maildir mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 auth default: debug: yes debug_passwords: yes passdb: driver: pam args: dovecot passdb: driver: passwd userdb: driver: passwd May 21 13:51:15 pop dovecot: imap-login: Login: user=<test>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured May 21 13:51:38 pop dovecot: auth(default): passwd(test,127.0.0.1): lookup May 21 13:51:53 pop dovecot: IMAP(ftest): Disconnected: Logged out May 21 13:51:54 pop dovecot: imap-login: Login: user=<ftest>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured May 21 13:51:54 pop dovecot: auth(default): pam(ftest,127.0.0.1): lookup service=dovecot May 21 13:51:56 pop dovecot: auth(default): client out: OK 1 user=ftest May 21 13:51:56 pop dovecot: auth(default): passwd(ftest,127.0.0.1): lookup May 21 13:51:56 pop dovecot: auth(default): master out: USER 95 ftest system_user=ftest uid=11094 g id=503 home=/home/f/ftest May 21 13:52:18 pop dovecot: auth(default): pam(ftest,127.0.0.1): lookup service=dovecot May 21 13:52:21 pop dovecot: IMAP(ftest): Time just moved backwards by 1 seconds. I'll sleep now until we're back in pre sent. May 21 13:52:21 pop dovecot: imap-login: Login: user=<ftest>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured May 21 13:52:22 pop dovecot: IMAP(ftest): Disconnected: Logged out Using maildir's with pam authentication, I really would appreciate any help.

3 6

[Dovecot] shared folders
by David Obando 23 May '07

23 May '07

Dear all, I would like to use shared folders but I'm not quite sure whether Dovecot supports it the way I want it: -user A should be able to share a folder with users B, C, D -B, C and D should have read-access to this folder Did anyone implement shared folders like this? Regards, David -- The day microsoft makes something that doesn't suck is the day they start making vacuum cleaners. gpg --keyserver pgp.mit.edu --recv-keys 1920BD87 Key fingerprint = 3326 32CE 888B DFF1 DED3 B8D2 105F 29CB 1920 BD87

2 1

[Dovecot] Quota warning message ala courier
by Ralf Hildebrandt 23 May '07

23 May '07

I have to face it, my users are retards: * either they're using crap MUAs which will not display their quota to them * or they're using POP with "leave mail on server" and will never notice their quota, unless it's too late * and once their quota is exceeded, their mails will bounce -- they'll never notice that, though. Thus I need a feature in dovecot that will tell them via email: Level1: "You ALMOST exceeded your quota, you're at 90% now" Level2: "You're very close to exceededin your quota, you're at 95% now" Level3: "Would you please clean up now? You're at 99% now" -- Ralf Hildebrandt (Ralf.Hildebrandt(a)charite.de) plonk(a)charite.de Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de "Hardware: the parts of a computer that can be kicked." -- Jeff Pesis

4 3

[Dovecot] Quota handling - opportunity for new Feature?
by Charles Marcus 23 May '07

23 May '07

This initial proposal for a Feature Request is the result of my desire to implement quotas, but not have the attendant headaches that inevitably accompany its implementation. Ralf Hildebrandt wrote: > I have to face it, my users are retards: Is there any other kind of user? ;) <snip> > Thus I need a feature in dovecot that will tell them via email: > > Level1: "You ALMOST exceeded your quota, you're at 90% now" > Level2: "You're very close to exceededin your quota, you're at 95% > now" > Level3: "Would you please clean up now? You're at 99% now" What I'd *really* like to see implemented is something along the lines outlined below - but of course, this will depend entirely on whether or not Timo thinks it is doable - or desirable... I know this would only be applicable if also using the dovecot LDA, because what I want to do requires cooperation at both the deliver and pop/imap ends... 1. Have two 'special' user-specific folders (by special, I mean like the Drafts, Sent, Templates folders) that dovecot controls: a) one, that the user has read-only access to and shows up in his folders list, that is used only for system-related messages, like over-quota notices - and maybe even user-specific log-type errors could be delivered here? b) and one (hidden) that the user does *not* have access to, to temporarily hold messages that come in that are unable to be delivered due to an over-quota condition 2. When user is over quota, have LDA deliver to folder b (yes, accept the message for delivery from the sending mta), and then generate an over-quota message that is delivered to folder a. Optionally, a bounce could be generated to the sender, informing them that their message is being 'held in queue' or something to that effect, due to the recipient being over-quota. 3. Once the user deletes enough mail to come back under quota, dovecot would then move messages from the 'over-quota' folder to his Inbox. Ok, am willing to hear reasons how/why this is a terrible idea... :) -- Best regards, Charles Marcus I.T. Director Media Brokers International 678.514.6200 x224 678.514.6299 fax

2 5

[Dovecot] dovecot.pid
by Dehnert James Sr 23 May '07

23 May '07

Can I define where dovecot.pid should be in the config file on 1.0.0? Nothing is being written to /var/run/dovecot, even after I changed the ownership to dovecot. Thanks, Zeke -- James "Zeke" Dehnert mailto:jdehnert@norcalnetworks.com Phone: +1 707.546.6620 x602 Fax: +1 707.324.8043 "Life is racing, everything else is just waiting"

2 1

[Dovecot] dovecot.org moves to a new server
by Timo Sirainen 23 May '07

23 May '07

Parts of dovecot.org will be down for a few hours while I'm moving to a new server (and to a new ISP as well). The new server won't be virtual anymore, so I'm hoping to get a bit better performance from it as well (the old virtual server had some disk I/O hogs). The DNS records have been using 1 hour TTL for last few days, so this move should be fast for everyone. Thanks to Nebula for hosting dovecot.org for the last 7 months. So, beginning the move by shutting down Postfix and Mailman..

4 6

[Dovecot] newbie with dovecot acls needs a little help :-)
by Rachid Zarouali 22 May '07

22 May '07

hy all, i'm trying to make an acl so a local unix user 'sie' can access exalead mboxes. my exalead mboxes are stored in : /opt/exalead/mail/sie/ mailboxes are automatically created every week like sie.2007.W17 for the 17th week of the year. how can i do this ? i've tried several things but none succedded. dovecot version 1.0.rc15 # /etc/dovecot.conf ddIEffective uid=65534, gid=65534 ddILoading modules from directory: /usr/lib64/dovecot/imap ddIModule loaded: /usr/lib64/dovecot/imap/lib01_acl_plugin.so log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot-info.log protocols: imap imaps login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login login_greeting_capability: yes mail_extra_groups: exalead mail_location: mbox:/opt/exalead/mail mail_debug: yes mail_plugins: acl auth default: verbose: yes debug: yes passdb: driver: pam userdb: driver: passwd userdb: driver: prefetch socket: type: listen client: master: path: /var/run/dovecot/auth-master mode: 384 user: exalead group: exalead thanks for your help -- Rachid Zarouali Administrateur Systèmes/Applications AFNIC rachid.zarouali(a)nic.fr 01.39.30.83.47

2 2

[Dovecot] simultaneous access to folder
by David Lee 22 May '07

22 May '07

We have for many years been a UW-IMAP site, with users having their own traditional, private, mbox-format INBOX and folders: almost (but not quite) no complications of shared or simultaneous access. We have just completed a transparent transition to dovecot (official 1.0.0 release). But we have one residual issue affecting one important user account. UW-IMAP specifically only allows single access to "mbox" folders. If different IMAP connections are attempted to such a folder, the latest attempt kills off earlier connections. (That's just the way it works, which was mostly fine for us.) On this particular account we had explicitly set two folders to UW-IMAP's different "mbx" format, so that a group of staff could simultaneously access that folder and delete messages. This is by a single, common, id/pw account. But dovecot doesn't support "mbx" format. Is there a way for us to set up such a group-access folder under dovecot? I've checked wiki pages such as "http://wiki.dovecot.org/SharedMailboxes" but that doesn't seem to be clear on the particular matter of which formats are suitable for such simultaneous access. It talks about different users accessing a folder; in our case it is multiple instances of the the same user. Under dovecot, can we simply let it be "mbox" format? And can dovecot (unlike UW-IMAP) then handle the simultaneous access? [Background: this is just two folders (amongst many) on one username; the overall service successfully handles over 15,000 usernames. And the solution (work-around) will only need to last a few months until that whole account is Exchange-ified (but let's not digress...!)] If I've missed something on the wiki which addresses this matter, point me in the right direction... -- : David Lee I.T. Service : : Senior Systems Programmer Computer Centre : : UNIX Team Leader Durham University : : South Road : : http://www.dur.ac.uk/t.d.lee/ Durham DH1 3LE : : Phone: +44 191 334 2752 U.K. :

2 1

[Dovecot] [PATCH] add some const's
by Andrey Panin 22 May '07

22 May '07

Add some const's. I think patch is self-explaining :) -- Andrey Panin | Linux and UNIX system administrator pazke(a)donpac.ru | PGP key: wwwkeys.pgp.net

2 1

Re: [Dovecot] No authentication sockets found
by Stewart Dean 22 May '07

22 May '07

Back on 5/9, I made a post by this subject http://dovecot.org/list/dovecot/2007-May/022482.html Timo replied: > The error message means that /var/run/dovecot/login directory or its > contents was deleted while Dovecot was running. I'd guess that you start > Dovecot too early and after startup another script goes and deletes the > entire /var/run/ directory. Or maybe that's done in background. Or > something.. and funkypunkydrunky reported: > I have lived the same problem in my system. But not evrytime sometimes it > only happens when i restart dovecot while mta is working. I think postfix > (my mta) cannot connect the new authentication socket. If i need the > restarting dovecot, i restart postfix too. It happens only for the above > situation. This happened again under these circumstances: 1) The machine had been up for 5 days. Having made some changes (largely de-verbosifying the dovecot.conf file), I killed the master dovecot process and restarted it (this before I was informed I could just do a kill -1 to effect the same result with less trouble). > May 14 15:34:09 mercury mail:info dovecot: Dovecot v1.0.0 starting up > > 2) Using TBird a an imap client, I got back on > May 14 15:24:48 mercury mail:info dovecot: auth(default): client out: CONT 1 > May 14 15:24:48 mercury mail:info dovecot: auth(default): client in: CONT 1 AHNkZWFuAEFsYW1hcjJi > May 14 15:24:48 mercury mail:info dovecot: auth(default): pam(sdean,10.20.10.75): lookup service=dovecot > May 14 15:24:49 mercury mail:info sendmail-SndRcv[2220248]: l4EJOief2949348: to=<cooper(a)bard.edu>, delay=00:00:01, xdelay=00:00:01, mailer=local, pri=36928, dsn=2.0.0, stat=Sent > May 14 15:24:49 mercury mail:info dovecot: auth(default): client out: OK 1 user=sdean > May 14 15:24:49 mercury mail:info dovecot: auth(default): master in: REQUEST 6 909440 1 > May 14 15:24:49 mercury mail:info dovecot: auth(default): passwd(sdean,10.20.10.75): lookup > May 14 15:24:49 mercury mail:info dovecot: auth(default): master out: USER 6 sdean system_user=sdean uid=202 gid=200 home=/home/hcrc/sdean > May 14 15:24:49 mercury mail:info dovecot: imap-login: Login: user=<sdean>, method=PLAIN, rip=10.20.10.75, lip=192.246.229.21, TLS > May 14 15:24:49 mercury mail:info dovecot: IMAP(sdean): Effective uid=202, gid=200, home=/home/hcrc/sdean > May 14 15:24:49 mercury mail:info dovecot: IMAP(sdean): mbox: data=/home/hcrc/sdean/mail:INBOX=/var/spool/mail/sdean:INDEX=/var/dcndx/sdean > May 14 15:24:49 mercury mail:info dovecot: IMAP(sdean): mbox: root=/home/hcrc/sdean/mail, index=/var/dcndx/sdean, inbox=/var/spool/mail/sdean > > > 3) 15 seconds after that, I started seeing a slew of these error messages, every 15 seconds or so: > May 14 15:25:03 mercury mail:info imapd[2052334]: Logout user=ot119 host=[10.20.10.10] > May 14 15:25:04 mercury mail:err|error dovecot: imap-login: No authentication sockets found > May 14 15:25:04 mercury mail:err|error dovecot: child 835676 (login) returned error 89 > 4) Since this is the production server, I kill the master dovecot instance and reinvoke dovecot in the foreground. I haven't seen the problem again since....but twice is problematic with just 3 people using DC. Now. My thoughts about what has been suggested so far, first by Timo: 1) This machine had been booted 5 days before so it's not a boot related problem 2) I'd find it hard to believe that something is nuking the contents of /var/run because: a) The directory doesn't exist by default in AIX; I created it for the DC install b) I have cron jobs that do cleanup with /var/log, /var/log/arc and /var/spool/mqueue, but nothing that does anything to /var/run 3) /var/run is local to the DC host and is not exported 4) funkypunkydrunky's comments about interaction with the MTA (sendmail in my case) seem unlikely, since it doesn't use SSL...or the same ports My questions: 1) What is happening? This is OpenSSL related, yes? 2a) Will this affect my production UWIMAP (which also supports/utilizes SSL)? If it doesn't, I can take my time debugging it (given that there are only 3 IT guys using DC currently), instead of frantically shutting it up by rebooting ASAP. I /think/ previously established DC connections continued to work 2b) How will this affect other imaps DC nex and pre-extant connections? I'm thinking of putting the whole IT dept on DC, but it'd be good to know how flaky things would get if/when this happens again. 3) What can I do to debug it, given that it happens infrequently and of no known causation? What should I check and look for afterwards? I guess I could put a cronjob that checks that /var/run/dovecot/login/ default= and ssl-parameters.dat exists periodically ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

3 5

[Dovecot] per user quota using LDAP entries
by Kenneth Oncinian 22 May '07

22 May '07

Hi List, This is my first post to this list so please be gentle :-). First of all, kudos to the developers of dovecot! Im trying to implement quota, and I followed the instructions in the wiki. My problem is the quota specified per user is not being honored, only the global quota setting. I do have an "quota = maildir:storage=204800" in the plugin area and enabled quota in the mail_plugins for both imap and pop3. This is my user attribute in /etc/dovecot-ldap.conf: user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid,mailQuota=quota wherein the "mailQuota" attribute has an entry of "mailQuota: maildir:storage=30720". So i was expecting of a 300MB quota for that user, but dovecot is using the global quota of 200MB instead of 300MB. My dovecot version is 1.0.0 My dovecot.conf: ----------------------- # /etc/dovecot.conf log_path: /var/log/dovecot.log protocols: imap pop3 login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no mail_location: /var/mail/vhost/%u mail_debug: yes maildir_copy_with_hardlinks: yes maildir_copy_preserve_filename: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota trash mail_plugins(imap): quota imap_quota trash mail_plugins(pop3): quota mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: passwd userdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: prefetch plugin: quota: maildir:storage=204800 trash: /etc/dovecot-trash.conf --- my dovecot-ldap.conf ------------------------------------------ hosts = localhost.localdomain dn = "cn=Directory Manager" dnpass = "xxxxxx" tls = no auth_bind = no ldap_version = 3 base = ou=people, dc=xx, dc=xx, dc=xx user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid,mailQuota=quota pass_attrs = uid=user,userPassword=password pass_filter = (&(objectClass=posixAccount)(uid=%u)) default_pass_scheme = LDAP-MD5 -------------- sample LDAP query: ------------------------------ ldapsearch -x -Z '(uid=kenneth.oncinian)' # LDAPv3 # base <> with scope sub # filter: (uid=kenneth.oncinian) # requesting: ALL # # kenneth.oncinian, People, ph.panasonic.com dn: uid=kenneth.oncinian,ou=People, dc=xx,dc=xx,dc=xx givenName: Kenneth sn: Oncinian telephoneNumber: xxx-xxxx loginShell: /bin/bash gidNumber: 2516 uidNumber: 1000 mail: kenneth.oncinian(a)xx.xx.xx facsimileTelephoneNumber: xxx xxxx objectClass: top objectClass: person objectClass: organizationalPerson objectClass: inetorgperson objectClass: posixAccount objectClass: account objectClass: mailgroup objectClass: mailgroupmanagement objectClass: mailgroupmanagement-globalconfig objectClass: mailgroupmember objectClass: mailrecipient objectClass: netscapemailserver objectClass: nsmailclient objectClass: ntuser objectClass: sambaSamAccount objectClass: proxyaccess objectClass: jabberaccess uid: kenneth.oncinian preferredLanguage: en cn: Kenneth Oncinian homeDirectory: /var/mail/vhost/kenneth.oncinian ou: Information Systems Department (ISD) x500UniqueIdentifier: mailAlternateAddress: koncinian(a)gmail.com ntUserDomainId: kenneth.oncinian ntUserCreateNewAccount: true ntUserDeleteAccount: true sambaSID: S-1-5-21-1685363153-499155089-1962420841-3000 sambaPrimaryGroupSID: S-1-5-21-1685363153-499155089-1962420841-3001 displayName: Kenneth Oncinian sambaPwdMustChange: 2147483647 sambaPasswordHistory: 00000000000000000000000000000000000000000000000000000000 00000000 sambaAcctFlags: [U ] myproxyaccess: yes myjabberaccess: yes sambaPwdCanChange: 1179303932 sambaLMPassword: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx sambaNTPassword: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx sambaPwdLastSet: 1179303932 mailQuota: maildir:storage=30720 # search result search: 3 result: 0 Success # numResponses: 2 # numEntries: 1 -- snip-- thanks and best regards, Kenneth

2 2

[Dovecot] Something about IMAP log
by Mu-Cheng Hsieh 22 May '07

22 May '07

Hi When the user used POP3 to handle her/his mailbox, we could know something happened as below. May 16 10:16:29 server dovecot: [ID 107833 local5.info] POP3(user): Disconnected: Logged out top=675/723063, retr=0/0, del=1/675, size=18124546 However, if the user used IMAP, we can not know what happened. May 18 15:25:42 server dovecot: [ID 107833 local5.info] IMAP(user): Disconnected: Logged out Is it possible to log something (e.g. delete or expunge) through IMAP? Thanks. -- Mu-Cheng Hsieh

2 1

Re: [Dovecot] Conflict -> Dovecot + Maildrop (maildirsize)
by Kenny Dail 21 May '07

21 May '07

> As I said in my original mail, this is simply a configuration issue: > > Looks like you're trying to tell the quota in bytes to Dovecot. Dovecot > wants it to be in kilobytes in its configuration file / userdb (it still > writes it in bytes to maildirsize, as you can see above it writes 1GB * > 1024 value in there). > > Where do you get the quota value for Dovecot? Divide it by 1024 and > it'll work right. I also use maildrop + dovecot. My quotas are stored in a mysql DB in couriers expected format: 50000000S (note the S on the end for storage). It makes for a very ugly userdb query trying to get that formatted to dovecot style of "maildir:storage=48828:ignore=Trash" How much would it take to allow dovecot's quota plugin to alternately accept "maildir:50000000S:ignore=Trash"? -- Kenny Dail <kend(a)amigo.net>

2 1

[Dovecot] Conflict -> Dovecot + Maildrop (maildirsize)
by Roberto Gonzalez Azevedo 21 May '07

21 May '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm having some problems with quota from sql (maildir++) and dovecot + maildrop. I'm using maildrop for MDA and dovecot as IMAP server. When an e-mail arrives, maildrop calculates the quota and updates the 'maildirsize' file. When i use dovecot (webmail, thunderbird) it updates the 'maildirsize' too, overwriting it, but in a different way. Both programas don't use the same pattern for 'maildirsize'. Let me show: 'maildirsize' with maildrop: " 1073741824S 117395679 1760 3675 1 3675 1 1610 1 1612 1 3222 2 9641 1 9641 1 5301 1 6415 1 11716 2 15419 1 15419 1 " 'maildirsize' with dovecot: " 1099511627776S 585847701 102542 5504023 959 " In both examples the quota is 1GB (1073741824S). And now ? Does anybody known how to fix that ? thanks - -- - ---------------------------- Roberto Gonzalez Azevedo Rio de Janeiro, Brazil -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFGQcttF+EMwkXLsEwRAoUOAKC0VXeC4USHyxOhsE5TQixk77hpmwCgxk5P ABOk8XHurCx/gEnd5StCkB8= =B+0f -----END PGP SIGNATURE-----

3 6

[Dovecot] mail_location %d expansion
by Mark Par 21 May '07

21 May '07

hi, i'm trying to read the mails of virtual users by setting the value of mail_location to /mail/virtual/%d/%u/Maildir. however, the %d does not resolve to the domain. i am using ldap as my passdb and userdb. what am i missing here? using this telnet session, | $ telnet localhost imap | Trying 209.235.254.94... | Connected to localhost | Escape character is '^]'. | * OK Dovecot ready. | 1 login foo.bar(a)mydom.com TopSecret | 1 OK Logged in. | 2 select inbox | 2 NO Internal error occurred. Refer to server log for more information. [2007-05-21 04:32:42] here are the relative entries from the log: | May 21 04:32:42 localhost dovecot: auth(default): auth(iris.lames(a)pointwest.com.ph,xx.xx.xx.xx): username changed foo.bar(a)mydom.com -> foo.bar | May 21 04:32:42 localhost dovecot: auth(default): ldap(foo.bar,xx.xx.xx.xx): result: uid(user)=foo.bar uidNumber(userdb_uid)=2301 gidNumber(userdb_gid)=2301 userPassword(password)=TopSecret | May 21 04:32:42 localhost dovecot: auth(default): client out: OK 1 user=foo.bar | May 21 04:32:42 localhost dovecot: auth(default): master in: REQUEST 3 99112 1 | May 21 04:32:42 localhost dovecot: auth(default): prefetch(foo.bar,xx.xx.xx.xx): success | May 21 04:32:42 localhost dovecot: auth(default): master out: USER 3 foo.bar uid=2301 gid=2301 | May 21 04:32:42 localhost dovecot: imap-login: Login: user=<foo.bar>, method=PLAIN, rip=xx.xx.xx.xx, lip=xx.xx.xx.xx, secured | May 21 04:32:42 localhost dovecot: IMAP(foo.bar): mkdir(/mail/virtual//foo.bar/Maildir/cur) failed: Permission denied | May 21 04:32:59 ptwest1 dovecot: IMAP(foo.bar): mkdir(/mail/virtual//foo.bar/Maildir/cur) failed: Permission denied dovecot --version: 1.0rc29 dovecot.conf: ssl_disable: yes ssl_cert_file: ssl_key_file: disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login verbose_proctitle: yes first_valid_gid: 0 mail_extra_groups: mail mail_location: maildir:/share/mail/virtual/%d/%u/Maildir imap_client_workarounds: delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf userdb: driver: prefetch dovecot-ldap.conf: auth_bind = no hosts = localhost base = dc=mycompany,dc=com dn = uid=dovecot,ou=auth,dc=mycompany,dc=com dnpass = TooMuchToAsk pass_attrs = uid=user,userPassword=password,uidNumber=userdb_uid,gidNumber=userd b_gid pass_filter = (&(objectClass=posixAccount)(uid=%n)) default_pass_scheme = PLAIN ldap_version = 3

2 1

[Dovecot] LDAP for Virtual Domains
by Bryan Vyhmeister 21 May '07

21 May '07

Is anyone using LDAP along with Dovecot where mail is being accessed in the form of /var/vmail/${domain}/${user}? I have not figured out how to extract the domain from LDAP in order to make this work. I know this is sparse information but maybe there is an easy fix. If not, I can post more information. Bryan

6 13

[Dovecot] [Blasphemy] Can I build dovecot with "-fstack-protector"?
by Ralf Hildebrandt 21 May '07

21 May '07

I tried building dovecot using : CPPFLAGS="-fstack-protector" LDFLAGS="-lssp" ./configure That would result in a proper build, yet the binary would complain once being run: dlopen(/usr/local/lib/dovecot/imap/lib10_quota_plugin.so) failed: /usr/local/lib/dovecot/imap/lib10_quota_plugin.so: undefined symbol: __stack_chk_fail_local Error: imap dump-capability process returned 89 and the like. So: Is it possible at all? And sorry for the blasphemy of daring to ask this in the first place :) -- Ralf Hildebrandt (Ralf.Hildebrandt(a)charite.de) plonk(a)charite.de Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de First Law of System Requirements: "Anything is possible if you don't know what you're talking about..."

3 14

[Dovecot] NFS lock contention for dovecot-uidlist
by Doug Council 21 May '07

21 May '07

We are in the process of migrating away from Courier-IMAP/POP3 and Maildrop. I want to use Dovecot (LDA, IMAP, POP3). During my testing, it has worked great except for dotlocking on the dovecot-uidlist file. The problem: When a delivery is being made with deliver and a mail client has the mailbox open (Thunderbird in this case), neither Thunderbird or deliver can get a dotlock on the dovecot-uidlist file, causing both deliver and Thunderbird to hang until the dotlock timeout runs out and the lock gets replaced. Once the lock is replaced, both will go about their business until the next lock miss and hang again. Eventually, everything is delivered and Thunderbird wakes up. Looking at each of the processes with truss, they are looping trying to stat the dotcot-uidlist.lock file, which no longer exists. We are using NFS, and based on reading through the mailing list archives, it can be a little difficult to get working reliably. But, I've read quite a few posts with our same or similar configuration having good luck with the setup. To reduce multiple box access-issues for now, I've been doing all testing with a single NFS client. Our configuration: NetApp filers for storage FreeBSD 6.2-RELEASE NFS clients Postfix 2.3.9 MTA Dovecot 1.0.0 LDA for local deliveries Dovecot 1.0.0 IMAP for pickup My dovecot.conf file is at the end of this message. NFS access cachcing on the FreeBSD has been disabled (vfs.nfs.access_cache_timeout = 0, see NFS mount options below). Postfix destination recipient and concurrency limit for the Dovecot LDA is set to 1. The NFS mount options: rw,tcp,-r=32768,-w=32768,nfsv3,dumbtimer,noatime,acregmin=0, acregmax=0,acdirmin=0,acdirmax=0 The dovecot.conf file: protocols = imap imaps pop3 pop3s disable_plaintext_auth = no syslog_facility = local0 ssl_cert_file = /nethere/conf/dovecot/ssl-nh-cert.pem ssl_key_file = /nethere/conf/dovecot/ssl-nh-key.pem login_greeting = Server ready. login_log_format_elements = user=<%u> ip=[%r] method=%m encryption=%c pid=%p login_log_format = %U$: %s mail_location = maildir:~/Maildir:INDEX=MEMORY mmap_disable = yes dotlock_use_excl = no lock_method = dotlock first_valid_uid = 200 last_valid_uid = 200 first_valid_gid = 200 last_valid_gid = 200 maildir_copy_with_hardlinks = yes namespace private { prefix = INBOX. inbox = yes } protocol imap { login_executable = /usr/local/libexec/dovecot/imap-login mail_executable = /usr/local/libexec/dovecot/imap imap_client_workarounds = outlook-idle delay-newmail } protocol pop3 { login_executable = /usr/local/libexec/dovecot/pop3-login mail_executable = /usr/local/libexec/dovecot/pop3 pop3_uidl_format = UID%u-%v pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } protocol lda { postmaster_address = postmaster(a)nethere.com sendmail_path = /usr/sbin/sendmail auth_socket_path = /var/run/dovecot/auth-master syslog_facility = mail } auth_executable = /usr/local/libexec/dovecot/dovecot-auth auth default { mechanisms = plain digest-md5 cram-md5 passdb ldap { args = /nethere/conf/dovecot/dovecot-ldap.conf } userdb ldap { args = /nethere/conf/dovecot/dovecot-ldap.conf } user = root socket listen { master { path = /var/run/dovecot/auth-master mode = 0600 user = mailuser group = mailuser } } } It may just be "how it works", but the lock contention seems a little too fragile for busy mailboxes. Does anyone have any ideas? Thanks in advance for any assistance. -Doug

2 3

Re: [Dovecot] LDAP for Virtual Domains
by Bryan Vyhmeister 21 May '07

21 May '07

On May 18, 2007, at 11:33 PM, Daniel L. Miller wrote: >> Thank you for that info. Do you mind posting the relevant portions >> of your Postfix config? > main.cf: > .... > virtual_mailbox_base = /var/mail > virtual_mailbox_domains = <all your external / internal domains here> > virtual_mailbox_maps = ldap:/etc/postfix/maps/ldap-virtual.cf > virtual_uid_maps = static:5000 > virtual_gid_maps = static:8 > virtual_alias_maps = hash:/etc/postfix/maps/virtual-aliases > .... > ##EOF > > ldap-virtual.cf: > server_host = localhost > search_base = ou=People,dc=amfeslan,dc=local > query_filter = (&(mail=%s)) > result_attribute = mail > result_format = /%d/%u/ > version = 3 > > The ldap-virtual settings look a little odd - but I'm rather proud > of my gimmick. You look for the mail address matching the sender > (mail = %s). Return that same address - but format it as domain/ > user. Append it to /var/mail and there it is! > > virtual-aliases is a simple file for me - I haven't settled on an > LDAP implentation for aliases yet I'm satisfied with. I'm using > ldap-account-manager for adminstration, and there's no explicit > provision for aliases within LAM or the base schemas used. I just asked Pascal as well how he gets around Postfix asking for mailacceptinggeneralid in order to allow messages to be accepted. How do you get around that? Dovecot is working fine but I can't get Postfix to accept messages because it keeps trying to find mailacceptinggeneralid. Bryan

3 3

[Dovecot] per-user delivery to commands
by martin f krafft 20 May '07

20 May '07

Hi, we are using dovecot IMAP in a complex virtual setup with almost 4000 accounts; postfix hands over to deliver for local delivery into a home directory as stored in the SQL database. That's /srv/vmail/$DOMAIN/$LOCALPART for most of them, but I'd rather not hardcode this scheme anywhere as it's in SQL. By a policy change, we need to insert a filter in this chain and the filter must be called in such a way that it knows where to find the "home" directory since the command needs to read a configuration file in ~/.mailfilt.rc. Thus I am looking for a way to make deliver pass incoming messages via this filter, but I cannot find any way to do that. Ideally I want this to happen before the LDA runs the mail through sieve. As an alternative, is there a command I can call to make dovecot look up $HOME for me so that I can use the dovecot data in the SQL database without making assumptions about the representation? A command that would proxy and convert my request into an SQL select as per dovecot.conf and feed back the result? Then I could use a Maildir delivery programme or even procmail to do the delivery according to the dovecot configruation. Thanks for any insights, hints, tips, help, jokes, flames, and useful information. -- martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck spamtraps: madduck.bogus(a)madduck.net will kill for oil!

1 1

[Dovecot] CVS to Mercurial switch
by Timo Sirainen 20 May '07

20 May '07

I've been meaning to switch away from CVS for a few years now, but I was never sure what I wanted to switch to, so I kept delaying it. I finally decided yesterday that Mercurial is pretty nice. The Mercurial repository is available from http://hg.dovecot.org/ (has a nice web interface). I wrote a small Mercurial mini-howto below. I'm not a Mercurial expert yet, so if you know better ways to do some things please let me know. The CVS repositories will still exist for a while, but they won't be updated anymore. If you notice the CVS being referenced somewhere (wiki, docs, etc.) please let me know (or fix yourself in wiki). 1. Fetch the initial repository: - ex. CVS HEAD: hg clone http://hg.dovecot.org/dovecot/ - ex. branch_1_0: hg clone http://hg.dovecot.org/dovecot-1.0/ - sieve plugin: hg clone http://hg.dovecot.org/dovecot-sieve-1.0/ The Sieve plugin currently works only with v1.0. I'll make a new "dovecot-sieve" repository for CVS HEAD later. 2. Update the repository: hg pull hg merge # only needed if you had done any changes hg update # to actually see the pulled changes All of this can be done with fetch extension. You can enable it by adding to ~/.hgrc: [extensions] hgext.fetch = After that you can use "hg fetch" which does all the above 3 commands (as far as I know, haven't really tried yet). 3. If you want to modify the sources, add your name to ~/.hgrc so it goes nicely into changelogs: [ui] username = Timo Sirainen <tss(a)iki.fi> You're able to "hg commit" your own changes into your repository. If you want to publish them, use "hg log" to see the changeset ID, and then use "hg export changesetid" to get patch ("hg export tip" might work too if you just want the last change(?)). You can then email the patch to Dovecot mailing list to get it merged. With CVS the ChangeLog file was updated every 15 minutes. Now the ChangeLog file doesn't exist in the repository at all. Instead it's generated with "hg log --style=changelog" when running "make dist".

6 12

Re: [Dovecot] LDAP for Virtual Domains
by Bryan Vyhmeister 20 May '07

20 May '07

On May 18, 2007, at 11:33 PM, Daniel L. Miller wrote: >> Thank you for that info. Do you mind posting the relevant portions >> of your Postfix config? > main.cf: > .... > virtual_mailbox_base = /var/mail > virtual_mailbox_domains = <all your external / internal domains here> > virtual_mailbox_maps = ldap:/etc/postfix/maps/ldap-virtual.cf > virtual_uid_maps = static:5000 > virtual_gid_maps = static:8 > virtual_alias_maps = hash:/etc/postfix/maps/virtual-aliases > .... > ##EOF > > ldap-virtual.cf: > server_host = localhost > search_base = ou=People,dc=amfeslan,dc=local > query_filter = (&(mail=%s)) > result_attribute = mail > result_format = /%d/%u/ > version = 3 > > The ldap-virtual settings look a little odd - but I'm rather proud > of my gimmick. You look for the mail address matching the sender > (mail = %s). Return that same address - but format it as domain/ > user. Append it to /var/mail and there it is! > > virtual-aliases is a simple file for me - I haven't settled on an > LDAP implentation for aliases yet I'm satisfied with. I'm using > ldap-account-manager for adminstration, and there's no explicit > provision for aliases within LAM or the base schemas used. Thank you. I'll try this out. Bryan

1 0

[Dovecot] IMAP "freezing" on OSX
by Ben Carter 20 May '07

20 May '07

Hi, I've got a problem with dovecot on an Intel Mac OSX box. Basically, I was running an older verion (0.8.?, I think), and everything was fine. Then, when I upgraded to 1.0.0 via MacPorts, I found that periodically the system gets into a state where it simply stops dealing with IMAP requests. This tends to manifest itself as Thunderbird simply stalling, not fetching any new messages or folder contents. Sometimes quitting and restarting Thunderbird will help, but at other times the problem persists even afterwards. It seems to be linked to specific mailboxes (or messages?) - often one "problem folder" will reproduce the effect 100% whilst operating on the rest of the mailbox is fine. The problem /seems/ to often start as a result of trying to move messages between folders. I'm not certain if that's a root cause, though, or simply a consequence of "opening" an affected folder to perform the move. I have a spam folder with a large number (>10000) of messages in it, and trying to file stuff in there is a relatively surefire way to generate the problem. Once it's happened once, it inevitably escalates - restarting the client helps a bit, as does restarting dovecot. However, the only way to "fix" it and restore full functionality seems to be to delete all of the index and dovecot* files from the mailbox and folders... it generally takes a day or so after that before things start to go wrong again. All of this seems to point to corruption of the index files in some way, but the log is universally unhelpful - there are no error messages of any kind showing up there. The actual dovecot instance doesn't appear to crash or even "hang" properly - you can still make inbound IMAP connections OK, it's just that they don't ever give a response to commands that touch the affected mailboxes. Sometimes, I end up with temporary files lying around in the folders in the mailbox - apparently mails which were in the process of being moved when the server "gave up". I'm not sure if this is actually part of the problem, though, or just a symptom. My configuration (from dovecot -n) is: # /opt/local/etc/dovecot/dovecot.conf ssl_disable: yes disable_plaintext_auth: no login_dir: /opt/local/var/run/dovecot/login login_executable: /opt/local/libexec/dovecot/imap-login mail_location: maildir:~/Library/Mail/IMAP auth default: passdb: driver: pam args: * userdb: driver: passwd I'm running this on my personal machine, so there's only one user on the system, which I have set up using MailDir (on HFS). There's a fair bit of mail in many of my folders, but I doubt that's the problem as the previous version didn't seem to have any issues... I'm doing mail delivery using postfix directly into the maildir folders. That doesn't seem to be affected at all by this, though - mail still arrives fine even when Dovecot is failing to serve the folder contents to IMAP clients... you just can't see it ^-^ Has anyone seen an effect like this? Or does anyone have any pointers as to what I could try to debug it? Any suggestions would be very greatly appreciated! Thanks! -- Ben Carter - ben(a)gunk.demon.co.uk / ben(a)saillune.net (preferred)

4 6

[Dovecot] Thinking Outside the Box - Extending IMAP
by Marc Perkel 19 May '07

19 May '07

Here's some thoughts I'd like to throw out there. I know it's not standard IMAP protocol but someone has to try new ideas first and I want to see what people (Timo) think of this. IMAP establishes a connection between the client and the server. Wouldn't it be great if it could be a conduit to let custom Thunderbird plugins talk to custom server application over the IMAP interface? For example, personalized server settings. Suppose for example I want Thunderbird to edit my server side white lists or black lists or any other setting? Wouldn't it be nice if IMAP supported these changes? The connection is made. It's a secure connection that's been authenticated. Lets use it! Here's my initial thoughts on this. Suppose we extended IMAP to include an EXECUTE command as follows: EXECUTE command parameter, parameter .... On the server side is a config file that has the commands that execute will allow and what programs they run. When the execute command is seen by Dovecot then Dovecot runs the program in the list with the parameters passed. For example, suppose there is a command to add a user to a server side blacklist. 100 execute blacklist add joe(a)smith.com 100 ok Dovecot would open a two way connection to the server application allowing the client to talk to any application that is configured and can send and receive text. The connection persists until the server end terminates or the client closes the connection. With a tool like this one can write generic applications easily that would greatly expand what email clients can do interacting with the server. Not only can setting be changes but you could interact with server side calendars, pick up voice messages from phone systems, run any sort of groupware, all over a generic IMAP connection with this simple extension. Example: 100 EXECUTE calendar 100 ok 100 list schedule today 8:00 10:00 100 8:00 make coffee 100 9:00 meeting with boss 100 9:30 Call Joe Blow at 415-555-1212 100 ok 100 quit 100 ok One thing I'd like to use it for is an outgoing SMTP connection to send outgoing email over IMAP. A session might look like this: 999 EXECUTE smtp 999 220 darwin.ctyme.com ESMTP Exim 4.67 Sun, 13 May 2007 06:52:26 -0700 999 helo ctyme.com 999 250 darwin.ctyme.com Hello localhost [127.0.0.1] 999 mail from:marc@perkel.com 999 250 OK 999 rcpt to:dovecot@dovecot.org 999 250 Accepted ...... 999 quit 999 OK Who likes this idea?

10 23

[Dovecot] [Fwd: An invitation to the "morg" (Message Organization) mailing list]
by Luigi Rosa 19 May '07

19 May '07

This messages has been posted on SquirrelMail development mailing list. Maybe someone is interested in morg mailing list. Ciao, luigi -------- Original Message -------- Subject: [SM-DEVEL] An invitation to the "morg" (Message Organization) mailing list Date: Sat, 19 May 2007 17:08:03 +0300 To: squirrelmail-devel(a)lists.sourceforge.net Hello all, [Note: Yes, I'm not gone after all... There has been a change of plans! I'll be mostly active, time permitting] There is a new IETF effort on IMAP standards, continuing on the work of "IMAPExt" Working Group which has practically closed now. I'm sending this here because people might be interested in joining it and either contributing actively or simply keeping an eye on what will be available in IMAP servers soon. Personally I'm very interested on message and mailbox annotations / metadata, but some other stuff like dynamic, multi-mailbox, persistent searches and virtual mailboxes might be of more interest to you. Anyway, you can join this effort by subscribing to the morg mailing list: https://www1.ietf.org/mailman/listinfo/morg http://www.ietf.org/maillist.html To quote Dave Cridland about the purpose of the list: ====== Quote start ======== This list has been created to look carefully at how existing mail clients search through, sort, and generally organize email. We're also going to - hopefully - have client developers talk about what they'd like to be able to do. There's another group that might be interested in this, too - the "desktop search" people might well be interested in the ability to search effectively through remote message stores. Kjetil commented (on IMAPEXT) that this area might be very interesting to IMAP webmail people, who can't simply download everything and work locally, so if there are any IMAP webmail developers about it'd be interesting to hear from you, and if anyone knows any, please invite them to join. Meanwhile, we're also going to look at what features we have on the store - the IMAP server - that we can leverage for this. There's a number of RFCs and Drafts in the area of searching, organization, etc, and we'll need to ensure we're all aware of the current state of play. So, IMAP specialists need to start to enumerate these - any volunteers? It occurs to me that both the above might benefit from a Wiki page or two - Lisa, is there an Apps Wiki we can use for this, or should I just set one up? [For anyone new to the IETF, Lisa and Chris are the Applications Area Directors] Finally, we'll look at what new work we can do to satisfy client requirements, write up a draft charter, and move to BOF (the first stage in forming a new IETF working group), aiming to form a new working group to do the work, and produce RFCs as we decide is appropriate. I'd like to take a decision on going down this road after Chicago in the summer, hopefully ready for a BOF at the IETF in December. I personally think our ultimate output is likely to be some Standards Track and some Experimental specifications for extensions, and maybe a couple of Informational documents on how this stuff ties together. I'd also note that searching is something that, like a lot of IETF work, has patent minefields in places - please do read that Note Well stuff, and let us know of any IPR you're aware of as soon as you can. ====== Quote end ======== -- / +--[Luigi Rosa]-- \ Sheridan: We have an open door policy. Ivanova: And an open airlock policy. --"The Illusion of Truth", Babylon 5

1 0

[Dovecot] permissions on some dovecot directories
by Arkadiusz Miskiewicz 19 May '07

19 May '07

Hello, What smallest permissions are needed on directories: /var/run/dovecot /var/run/dovecot/login /var/lib/dovecot dovecot run as dovecot:dovecot. Currently I have 775 dovecot:dovecot /var/run/dovecot 750 root:dovecot /var/run/dovecot/login 755 root:root /var/lib/dovecot -- Arkadiusz Miśkiewicz PLD/Linux Team arekm / maven.pl http://ftp.pld-linux.org/

1 0

[Dovecot] Maildir subfolder conversion from courier-imap
by Remy Blank 19 May '07

19 May '07

Hello, I am trying to convert a maildir that was managed by courier-imap up to now to dovecot. I am using the courier-dovecot-migrate.pl script as follows: courier-dovecot-migrate.pl --convert --recursive ~/Maildir However, this command only seems to convert the base maildir, but not all the subfolders. I thought that that's what the --recursive option was for. Is the command above supposed to convert the base maildir as well as the subfolders, or should I run the command on all subfolders separately (e.g. using a shell script)? Thanks. -- Remy

2 2

Re: [Dovecot] Replication plans
by Bill Boebel 19 May '07

19 May '07

On Fri, May 18, 2007 1:42 am, Troy Benjegerdes <hozer(a)hozed.org> said: > I'm going to throw out a warning that it's my feeling that replication > has ended many otherwise worthwhile projects. Once you go down that > rabbit hole, you end up finding out the hard way that you just can't > avoid the stability, performance, complexity, and whatever problems. > .. > I've found myself pretty much in the same "all roads lead to the > filesystem" situation. I don't want to replicate just imap, I want to > replicate the build directory with my source code, my email, and my MP3 > files. One of the problems with the clustered file system approach seems to be that accessing Dovecot's index, cache and control files are slow over the network. For speed, ideally you want your index, cache and control on local disk... but still replicated to another server. So what about tackling this replication problem from a different angle... Make it Dovecot's job to replicate the index and control files between servers, and make it the file system's job to replicate just the mail data. This would require further disconnecting the index and control files from the mail data, so that there is less syncing required. i.e. remove the need to check directory mtimes and to compare directory listings against the index; and instead assume that the indexes are always correct. Periodically you could still check to see if a sync is needed, but you'd do this must less frequently. I agree that there are already great solutions available for replicated storage, so this would allow us to take advantage of these solutions for the bulk of our storage without impacting the speed of IMAP. Bill

3 2

Re: [Dovecot] dbox redesign
by Bill Boebel 19 May '07

19 May '07

On Sat, May 12, 2007 9:10 am, Timo Sirainen <tss(a)iki.fi> said: > Fast copying > ============ > > Would be nice if copying a message from one mailbox to another wouldn't > require actually reading+writing the whole message contents. But I can't > really figure out how to implement this without requiring that there is > only a single dbox storage which contains the mails for all the > mailboxes, and the mailboxes themselves are just Dovecot's index files > containing pointers to the dbox storage. > > The problem with having everything in one storage is that if the index > files are broken, the messages can't be placed into correct mailboxes > anymore. > > Although one possibility would be treat mailboxes a bit similarly than > keywords. So that when a message is copied to another mailbox, the > message in dbox file is updated to contain information that it exists in > such and such mailboxes. Hmm. Perhaps that would be good enough, yes. > Yes, I think treating mailboxes similary to keywords is ideal. There really is no reason to physically separate mailboxes on disk. All that is needed is this logical separation if it can be done in a reliable way. Or maybe track this in mailbox-specific index files, and also have a corespodning text file that stores a list of messages that are contained in that mailbox... similar to maildir's dovecot-uidlist file. Then if you lose the index you can rebuild the index from the text file. Bill

4 7

[Dovecot] dovecot-shared being ignored?
by bhayden＠umn.edu 19 May '07

19 May '07

So, I'm working on a shared folder. Everything is nice except for one bit. My dovecot-shared file in the Maildir is either being ignored, or doesn't work the way I think it does. Any messages copied into the Maildir using a mail client are mode 660 and owned by the user who did the copy. Perms on the dovecot-shared file are 700 (I'm using Solaris ACLs in addition to the Dovecot ACLs in order to prevent unauthorized access via means that don't pass through Dovecot's IMAP server... ie SFTP/SCP, and so I'm using 700 with a rwx mask and access to the file set per user in the Solaris ACL). The message files being created 660 means they are accessible via SFTP/SCP to anyone in the group, and we have a single one for (nearly) all users. This is not really acceptable, so if anyone can offer guidance on the dovecot-shared that'd be great. I checked the wiki, and it has very minimal information. -Brian

2 1

[Dovecot] Virtual mailbox plans
by Timo Sirainen 18 May '07

18 May '07

Configuration ------------- There could be global and user-specific configuration files, similar to how ACLs work. I think the global virtual mailboxes should be only defaults though, so that users could delete them and create a new mailbox (virtual or non-virtual) with the same name. The global virtual mailboxes could be described in a single file, such as: Trash deleted Work/My Unseen (mailboxes "box1" "box2" "box2/*") or to "tss(a)iki.fi" to "timo.sirainen(a)iki.fi" unseen So the format would be <virtual mailbox name> LF <search condition, allowed to wrap to new line> LF LF <next virtual mailbox, etc.> Per-user virtual mailboxes could also be listed in a similar file. If the search condition is empty, a globally defined virtual mailbox has been deleted. Another way would be to have per-mailbox dovecot-virtual files, but I'm not sure how global virtual mailboxes could then be easily deleted. Also having all of them in a single file makes listing the mailboxes pretty fast. The search condition would be a standard IMAP SEARCH reply, with the exception of the mailboxes parameter to specify what mailboxes are used. Virtual mailboxes would be implemented as a new mail storage backend, so their namespace configuration would be like: namespace private { prefix = "virtual/" location = virtual:~/virtual:GLOBAL=/etc/dovecot/virtual-globals.conf } Syncing ------- ~/virtual directory would contain index files for the virtual mailboxes. If the index files don't exist, a full resync for the virtual mailbox is done. This means opening all the real mailboxes configured for the vbox, running the SEARCH command and adding the returned UIDs to the vbox's indexes. The index would contain at least mailbox ID and message UID numbers. Probably would be a good idea to also save UIDVALIDITY numbers just to be safe, although that's a bit of a waste of space and it could be handled in other ways too, such as changing the mailbox ID whenever its UIDVALIDITY changes.. Mailbox IDs would be mapped to names in mailbox list index. This index already exists, although there still seems to be some bugs in it. At least creating a new list index has a race condition. I should look into making the list index a bit more realiable. Also the list indexes work only with Maildir++ layout currently. After the vbox has initially been synced, it needs to also handle updates. I think optionally the updates could be done the same way as full sync (opening all mailboxes to see if there are changes), but a faster way would be to update the virtual mailboxes immediately when the real mailboxes are being modified. So IMAP, POP3 and deliver all need to be aware of the virtual mailboxes and what real mailboxes are mapped to what virtual ones. Whenever doing a change that causes the message to either be added to or removed from a virtual mailbox according to their rules, the virtual mailbox's index is updated immediately. Being able to determine this change quickly might be the biggest change required to Dovecot's base code. Changes ------- Virtual mailboxes would share their state with the real mailbox, so any flag changes done in the vbox would be immediately changed in the real mailbox as well. The same goes for expunges. Virtual mailboxes' transaction logs would use different records for expunges and removals. Expunges would be handled normally, but removals wouldn't be removed from the in-memory view of the mailbox until EXPUNGE command was given (although they would be removed from dovecot.index immediately, so new sessions wouldn't see them). This makes it possible to have a vbox with only unseen messages, but without the message getting expunged immediately after a client opens the mail. So the EXPUNGE command could act as a "session synchronization" command. And of course it would also expunge the messages that had been marked as \Deleted.

1 0

[Dovecot] deliver exit codes?
by Ralf Hildebrandt 18 May '07

18 May '07

Before switching to dovecot deliver for all local deliveries, I'm calling deliver from maildrop (yes, don't laugh). Snippet from my global /etc/maildroprc: # Store maillist & junk messages directly /^Precedence: ?list/ if ( $MATCH ) { exception { log "Bulk message: $MATCH" #to "$DEFAULT" to "|$DELIVER" } } I replaced to "$DEFAULT" (meaning: delivery to $HOME/Maildir) with to "|$DELIVER" (meaning: pipe the mail into dovecot deliver, and deliver to INBOX = $HOME/Maildir) This works really well, UNLESS a user exceeds his/her quota: In that particular case, deliver fails to deliver the mail and generates a bounce, all on it's own. It's exit status is 0 in that case, so my MTA (postfix) thinks that the mail has been delivered successfully. I'd prefer deliver to return EX_TEMPFAIL, which I can pass through maildrop back to postfix, which will then log a temporary error and will bounce the mail all by itself after 5 days time. But how? -- Ralf Hildebrandt (Ralf.Hildebrandt(a)charite.de) plonk(a)charite.de Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de The Imperial Vendor or Contractor probably told them that droid armies don't need redundant command centers, nor any kind of high availability ... you're supposed to buy several, and cluster them. Redundant Array of Inexpensive Droids?

2 1

[Dovecot] Disable plaintext authentications
by Alexander Moisseev 18 May '07

18 May '07

Dear Sirs, I have Postfix 2.5 with Dovecot 1.0.0 as authentication server. Can I disable SMTP plaintext authentications for WAN clients, but allow it for LAN ones?

2 1

[Dovecot] UID larger than next_uid in file /hosts/domain/user/dovecot-uidlist
by Chris Jeans 18 May '07

18 May '07

I'm having the following problem and would appreciate any help or tips on how to fix it. None of my users can send email via pop3 or imap clients the only consistent thing that i keep seeing in the logs are the following 2 messages: UID larger than next_uid in file /hosts/domain/user/dovecot-uidlist sync: UID inserted in the middle of mailbox After searching the web all I can find is this link http://dovecot.org/list/dovecot-cvs/2007-May/008819.html which deals with Index: maildir-uidlist.c I'm running dovecot 1.0.0 on FreeBSD 6.2. -- Chris Jeans cmjeans(a)gmail.com

2 1

Re: [Dovecot] Replication plans
by Bill Boebel 18 May '07

18 May '07

On Fri, May 18, 2007 1:10 pm, Timo Sirainen <tss(a)iki.fi> said: > On Fri, 2007-05-18 at 12:20 -0400, Bill Boebel wrote: >> So what about tackling this replication problem from a different >> angle... Make it Dovecot's job to replicate the index and control >> files between servers, and make it the file system's job to replicate >> just the mail data. This would require further disconnecting the >> index and control files from the mail data, so that there is less >> syncing required. i.e. remove the need to check directory mtimes and >> to compare directory listings against the index; and instead assume >> that the indexes are always correct. Periodically you could still >> check to see if a sync is needed, but you'd do this must less >> frequently. > > This would practically mean that you want either cydir or dbox storage. > > This kind of a hybrid replication / clustered filesystem implementation > would simplify the replication a bit, but all the difficult things > related to UID conflicts etc. will still be there. So I wouldn't mind > implementing this, but I think implementing the message content sending > via TCP socket wouldn't add much more code anymore. > > The clustered filesystem could probably be used to simplify some things > though, such as UID allocation could be done by renaming a "uid-<next > uid>" file. If the rename() succeeded, you allocated the UID, otherwise > someone else did and you'll have to find the new filename and try again. > But I'm not sure if this kind of a special-case handling would be good. > Unless of course I decide to use the same thing for non-replicated > cydir/dbox. Dbox definitely sounds promising. I'd avoid putting this uid-<nextuid> file in the same location as the mail storage though, because if you can truly keep mail storage isolated and infrequently accessed, then you can do cool things like store your mail data remotely on Amazon S3 or equivalent.

1 0

Re: [Dovecot] LDAP for Virtual Domains
by Bryan Vyhmeister 18 May '07

18 May '07

On May 16, 2007, at 10:29 PM, razor wrote: > 17.05.07 в 05:06 Bryan Vyhmeister в своём письме > писал(а): > >> Is anyone using LDAP along with Dovecot where mail is being >> accessed in the form of /var/vmail/${domain}/${user}? I have not >> figured out how to extract the domain from LDAP in order to make >> this work. I know this is sparse information but maybe there is an >> easy fix. If not, I can post more information. >> >> Bryan > > i am using exim+dovecot+lda+openldap Thank you for the info. Bryan

1 0

[Dovecot] Wiki relating to subscriptions
by Bruce Bodger 17 May '07

17 May '07

On this wiki page http://wiki.dovecot.org/Migration/UW appears this information: "It's possible to keep using the .mailboxlist}} filename (as long as it's in the same directory) by modifying {{{SUBSCRIPTION_FILE_NAME define in src/lib-storage/index/mbox/mbox-storage.h" However, if a user wanted to continue using .mailboxlist wouldn't they also have to change the same define in src/lib-storage/index/ maildir/maildir-storage.h? Also, (regarding v1.0.0 code) the default define in mbox-storage.h is ".subscriptions" whereas the default define in maildir-storage.h is "subscriptions" (no dot) B. Bodger New York, NY

2 1

[Dovecot] Maildir format migration
by Tony Tsang 17 May '07

17 May '07

Hi all, I am planning to use dovecot IMAP on my server. Currently it is running UW-IMAP server with Maildir format storing users' mail. I've found that dovecot uses different Maildir format from UW-IMAP. Is there any configuration option for adapting dovecot to use format used by UW-IMAP? Thanks a lot. Tony.

4 7

[Dovecot] Processing too fast?
by Daniel L. Miller 17 May '07

17 May '07

I'm trying to use Dovecot to make administering ASSP a bit easier. I've created a mailbox with a number of subfolders (Spam, Ham, etc.) and have ASSP setup to save mail in the appropriate folder e.g. /var/mail/ASSP/.INBOX.Ham/new. But I'm having problems with ASSP complaining about the newly created files - I believe the file gets opened, then it disappears before ASSP finishes writing to it. Is Dovecot grabbing the file from "new" and moving it to "cur" faster than ASSP can write? How can I get around this? ASSP only allows for a folder to save each category to - I can't specify an LDA. -- Daniel

4 3

[Dovecot] CONVERT Plugin
by Bruce Bodger 17 May '07

17 May '07

Timo, Running v1.0.0 The convert plugin works pretty damn good! No need to mess with external utilities. One comment, though: Running here on OS X, I configured it with this convert_mail line: convert_mail = mbox:~/Library/Mail/IMAP/:INBOX=/var/mail/%u and mail_location = maildir:~/Maildir The IMAP directory was renamed to IMAP-converted after the process but the inbox (in /var/mail) does not get renamed. The WIKI sounds like it should be renamed to something, too. B. Bodger New York, NY

2 2

[Dovecot] Digest settings
by Kenny Dail 17 May '07

17 May '07

Timo, Wonder if you can tweak the digests to hold more messages? In 5 hours this morning, I've received 6 digests, seems a little excessive to me. -- Kenny Dail <kend(a)amigo.net>

2 1

[Dovecot] dbmail benchmarking
by Timo Sirainen 16 May '07

16 May '07

I thought I'd try benchmarking with dbmail (v2.2.4) to see how much slower a SQL backend could actually be. Skip to bottom for the conclusions. Originally I ran the tests with the databases being in XFS filesystem. MySQL's performance was horrible. It went 3-7x faster with ext3. MySQL 5.0.30 backend (innodb): ./imaptest clients=1 - append=100 seed=1 secs=30 msgs=1000000 logout=0 Logi Sele Appe 100% 100% 100% 5% 1 291 303 So that's 10 messages/sec saved. Now how about with 5 concurrent clients? Logi Sele Appe 100% 100% 100% 5% 5 1259 1332 Pretty well. Then something more generic: ./imaptest clients=1 seed=1 secs=30 msgs=1000000 logout=0 Logi List Stat Sele Fetc Fet2 Stor Dele Expu Appe 100% 50% 50% 100% 100% 100% 50% 100% 100% 100% 30% 5% 1 37 36 75 73 110 34 24 73 78 Without Fetc (header/metadata fetching): Logi List Stat Sele Fet2 Stor Dele Expu Appe 100% 50% 50% 100% 100% 50% 100% 100% 100% 30% 5% 1 94 94 199 283 102 85 198 210 PostgreSQL 8.1.5 backend: ./imaptest clients=1 - append=100 seed=1 secs=30 msgs=1000000 logout=0 Logi Sele Appe 100% 100% 100% 5% 1 267 277 ./imaptest clients=5 - append=100 seed=1 secs=30 msgs=1000000 logout=0 Logi Sele Appe 100% 100% 100% 5% 5 1094 1144 ./imaptest clients=1 seed=1 secs=30 msgs=1000000 logout=0 Logi List Stat Sele Fetc Fet2 Stor Dele Expu Appe 100% 50% 50% 100% 100% 100% 50% 100% 100% 100% 30% 5% 9 29 40 74 72 99 22 12 64 71 ./imaptest clients=1 seed=1 secs=30 msgs=1000000 logout=0 fetch=0 Logi List Stat Sele Fet2 Stor Dele Expu Appe 100% 50% 50% 100% 100% 50% 100% 100% 100% 30% 5% 35 105 95 200 277 54 70 165 175 The last two tests gave "Unexpected tagged reply:" errors that I didn't get with MySQL. So apparently there's some PostgreSQL-specific bug in dbmail. The same values with Dovecot 1.0 + maildir: ./imaptest clients=1 - append=100 seed=1 secs=30 msgs=1000000 logout=0 Logi Sele Appe 100% 100% 100% 5% 1 346 364 ./imaptest clients=5 - append=100 seed=1 secs=30 msgs=1000000 logout=0 Logi Sele Appe 100% 100% 100% 5% 5 1408 1470 ./imaptest clients=1 seed=1 secs=30 msgs=1000000 logout=0 Logi List Stat Sele Fetc Fet2 Stor Dele Expu Appe 100% 50% 50% 100% 100% 100% 50% 100% 100% 100% 30% 5% 1 130 133 259 258 382 123 127 257 271 ./imaptest clients=1 seed=1 secs=30 msgs=1000000 logout=0 fetch=0 Logi List Stat Sele Fet2 Stor Dele Expu Appe 100% 50% 50% 100% 100% 50% 100% 100% 100% 30% 5% 1 155 163 339 478 169 175 338 354 So, what are the conclusions? - In raw append speed dbmail is almost as fast as maildir. - In raw read/write speed maildir is about 1,6 times faster - When adding metadata fetches Dovecot is 4 times faster than dbmail. This is most likely because dbmail doesn't have a cache equivalent to dovecot.index.cache so it has to do the fetches the slow way. I would have liked to also run the generic tests with more than 1 client, but then I start hitting dbmail bugs and the test stops (reported already to their bugtracker).

3 5

[Dovecot] OS X Mail Administration
by Bruce Bodger 16 May '07

16 May '07

I'd like to request some feed back from any OS X Mail Admins on the list, please. Currently running 10.4.9 here using postfix / dovecot and I'm about to take the plunge from mbox to maildir. I just migrated from uw-imap to dovecot. As you're aware, users inbox's are customarily stored in /var/mail/% username and personal folders under /Users/%username/Library/Mail/IMAP. I'd appreciate if you'd share with me the directory structure that you use, or would use in my situation. All mail storage will be on the server so disk space is not an issue. I'm a bit confused whether or not to keep the inbox separate from the other imap structure as is the OS X default: should all mailboxes be under inbox, etc. Your input would be appreciated. Thank you, B. Bodger New York, NY

3 3

[Dovecot] Maildir POP3 "UID larger than next_uid" bug
by Alexander Moisseev 16 May '07

16 May '07

dovecot 1.0.0; Free BSD 6.2; x86; UFS; no NFS IMAP not uses at all, POP3 only Problem description: POP3 client can't fetch second e-mail message from Maildir if first POP3 connect occurs before any message placed in Maildir. Details: 1. POP3-client first time tries to receive mail: May 14 16:17:36 host dovecot: pop3-login: Login: user=<user(a)mydomain.ru>, method=PLAIN, rip=192.168.0.100, lip=192.168.0.3 May 14 16:17:36 host dovecot: POP3(user(a)mydomain.ru): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 dovecot creates Maildir for that user: /var/mail/virtual/mydomain.ru/user/Maildir/ /cur /new /tmp dovecot.index dovecot.index.cache dovecot.index.log 2. Postfix MTA receives message for that user and places it at /var/mail/virtual/mydomain.ru/user/Maildir/new/1179145269.V43I3f5a4M116738.host.mydomain.local 3. POP3-client tries to receive mail: May 14 16:23:09 host dovecot: pop3-login: Login: user=<user(a)mydomain.ru>, method=PLAIN, rip=192.168.0.100, lip=192.168.0.3 May 14 16:23:09 host dovecot: POP3(user(a)mydomain.ru): Disconnected: Logged out top=0/0, retr=1/786, del=1/1, size=770 >>>>> dovecot creates file dovecot-uidlist with next_uid=1 (!!!): 1 1179145056 1 1 1179145269.V43I3f5a4M116738.host.mydomain.local:2, Message fetched successfully. 4. POP3-client tries to receive mail: May 14 16:23:29 host dovecot: pop3-login: Login: user=<user(a)mydomain.ru>, method=PLAIN, rip=192.168.0.100, lip=192.168.0.3 May 14 16:23:29 host dovecot: POP3(user(a)mydomain.ru): UID larger than next_uid in file /var/mail/virtual/mydomain.ru/user/Maildir/dovecot-uidlist (1 >= 1) May 14 16:23:29 host dovecot: POP3(user(a)mydomain.ru): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 File dovecot-uidlist disappears. 5. Postfix MTA receives message for that user and places it at /var/mail/virtual/mydomain.ru/user/Maildir/new/1179145534.V43I3f5a4M116827.host.mydomain.local 6. POP3-client tries to receive mail: May 14 16:47:20 host dovecot: pop3-login: Login: user=<user(a)mydomain.ru>, method=PLAIN, rip=192.168.0.100, lip=192.168.0.3 May 14 16:47:20 host dovecot: POP3(user(a)mydomain.ru): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Dovecot creates file dovecot-uidlist: 1 1179145056 2 1 1179145534.V43I3f5a4M116827.host.mydomain.local Dovecot moves message from new to cur directory and adds flag ":2,": /var/mail/virtual/mydomain.ru/user/Maildir/cur/1179145534.V43I3f5a4M116827.host.mydomain.local:2, Message not fetched. And POP3 client can't fetch it at all. All next messages fetches normally as they arrives. # /usr/local/etc/dovecot.conf protocols: pop3 pop3s ssl_cert_file: /etc/ssl/certs/host.mydomain.ru.crt ssl_key_file: /etc/ssl/private/host.mydomain.ru.key disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/pop3-login login_greeting: POP3 server ready verbose_proctitle: yes first_valid_gid: 0 mail_extra_groups: mail mail_location: maildir:~/Maildir mail_executable: /usr/local/libexec/dovecot/pop3 mail_plugin_dir: /usr/local/lib/dovecot/pop3 pop3_uidl_format: %08Xu%08Xv pop3_client_workarounds: outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login digest-md5 cram-md5 apop ntlm default_realm: mydomain.ru passdb: driver: pam passdb: driver: passwd-file args: /etc/auth/%d/passwd userdb: driver: passwd userdb: driver: static args: uid=5000 gid=5000 home=/var/mail/virtual/%d/%n socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master:

2 1

[Dovecot] imap-login: Disconnected: Connection queue full
by Ralf Hildebrandt 16 May '07

16 May '07

I'm getting "imap-login: Disconnected: Connection queue full:" messages like these: May 16 12:17:26 postamt dovecot: imap-login: Disconnected: Connection queue full: rip=160.45.172.202, lip=141.42.4.250 May 16 12:17:26 postamt dovecot: imap-login: Disconnected: Connection queue full: rip=141.42.165.160, lip=141.42.4.250, TLS May 16 12:18:23 postamt dovecot: imap-login: Disconnected: Connection queue full: rip=193.175.70.61, lip=141.42.4.250 Should I worry about these messages or are they of informational character only? Does it mean that the imap-login encountered more than "login_max_connections" and thus a new process had to be spawned? Is there a parameter I should be changing (config below) # /usr/local/sbin/dovecot --version 1.0.0 ---- snip --- # /usr/local/etc/dovecot.conf protocols: imap imaps pop3s ssl_cert_file: /etc/ssl/certs/postamt.pem ssl_key_file: /etc/ssl/private/postamt.key disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_process_per_connection: no login_process_size: 64 login_max_connections: 32 verbose_proctitle: yes mail_location: maildir:~/Maildir mail_read_mmaped: yes fsync_disable: yes maildir_copy_with_hardlinks: yes maildir_copy_preserve_filename: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): outlook-idle netscape-eoh imap_client_workarounds(imap): outlook-idle netscape-eoh imap_client_workarounds(pop3): outlook-idle pop3_lock_session(default): no pop3_lock_session(imap): no pop3_lock_session(pop3): yes pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %v-%u pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh namespace: type: private separator: . prefix: INBOX. inbox: yes auth default: passdb: driver: pam userdb: driver: passwd plugin: quota: maildir quota: maildir:ignore=Trash ---- snip --- -- Ralf Hildebrandt (i.A. des IT-Zentrums) Ralf.Hildebrandt(a)charite.de Charite - Universitätsmedizin Berlin Tel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-Berlin Fax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to plonk(a)charite.de

2 4

[Dovecot] Login with firstname.lastname instead of loginname
by Ralf Hildebrandt 16 May '07

16 May '07

Some of our users use to login as firstname.lastname or firstname.lastname(a)charite.de instead of using the "correct" "flastname" login name. In order to get this behaviour a long-gone co-worker wrote an authdaemon.pl, which speaks the courier-authdaemon protocol. How can I emulate this behaviour with dovecot? Basically, all I need is a usernamen mapping ala: Ralf.Hildebrandt(a)charite.de rhilde Ralf.Hildebrandt rhilde for all my users -- I can generate this programatically using awk, but how can I make dovecot use that? -- Ralf Hildebrandt (i.A. des IT-Zentrums) Ralf.Hildebrandt(a)charite.de Charite - Universitätsmedizin Berlin Tel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-Berlin Fax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to plonk(a)charite.de

2 6

[Dovecot] Sorting by Received vs Sent
by Bill Boebel 16 May '07

16 May '07

Looks like in Cyrus, sorting by Received date is faster than sorting by the Sent header date because of the way they use the index and cache files... http://www.emaildiscussions.com/showpost.php?p=419246 Is this the case in Dovecot as well? Bill

2 1

[Dovecot] deleted Messages don't go into Trash Folder always
by Rainer Sigl 16 May '07

16 May '07

Hi all, most of the time deleted messages aren't moved into trash folder but go into nirwana. Sometimes it works correctly. But a restart does not guarantee this function. This effect exists with different imap clients. Can anybody help please. Rainer Sigl -- ----------------- Rainer Sigl, | email: sigl(a)mpe.mpg.de MPI f. extraterrestrische Physik, | phone: +49 (89) 30000-3557 Postfach 1312, | fax: +49 (89) 30000-3569 D-85741 Garching, Germany | web: http://www.mpe.mpg.de/~sigl/

3 3

[Dovecot] List problems?
by Charles Marcus 16 May '07

16 May '07

Hi Timo, Sorry to bother you, but I'm used to having at least 10-20 in the morning. This morning there are none... and the last one is from 3:00pm yesterday? So, this is a test, I guess... -- Best regards, Charles

2 1

[Dovecot] Deliver sending bounces from 'MAILER-DAEMON@'
by Erland Nylend 16 May '07

16 May '07

Hello, I'm having a problem with postfix and/or dovecots "deliver". I'm getting these lines in the mail log: | Apr 24 11:42:08 smtp2 postfix/qmgr[6176]: 05BAE3B67E: from=<>, size=3055, nrcpt=1 (queue active) | Apr 24 11:42:08 smtp2 postfix/qmgr[6176]: 05BAE3B67E: to=<MAILER-DAEMON@>, relay=none, delay=0.01, delays=0.01/0.01/0/0, dsn=5.1.3, status=bounced (bad address syntax) After some debugging, it seems that those lines in the log appear if I send mail to an account which is over quota. (I'm using the Maildir++ quota) This is from my dovecot.conf: | protocol lda { | postmaster_address = MAILER-DAEMON(a)my.domain.tld | mail_plugins = quota | auth_socket_path = /var/run/dovecot/auth-master | hostname = my.mail.server | sendmail_path = /usr/sbin/sendmail | } It seems to me that dovecot is sending bounce messages from 'MAILER-DAEMON@' .. Does anyone know why this is happening, or how I can specify the address to be used? I'm using dovecot 1.0.0. -- Erland Nylend

2 5

[Dovecot] assertion failed
by Adrian Stoica 15 May '07

15 May '07

What is this ? dovecot: Apr 24 13:03:29 Error: IMAP(tina.burdujan): file maildir-sync.c: line 1075 (maildir_sync_index): assertion failed: (uid >prev_uid) dovecot: Apr 24 13:03:29 Error: IMAP(tina.burdujan): Raw backtrace: /usr/libexec/dovecot/imap [0x80b8741] -> /usr/libexec/dovecot/imap [0x80b819c] -> /usr/libexec/dovecot/imap(maildir_sync_index+0x898) [0x80695f8] -> /usr/libexec/dovecot/imap [0x80698b3] -> /usr/libexec/dovecot/imap(maildir_ storage_sync_init+0x49) [0x8069aa9] -> /usr/libexec/dovecot/imap(imap_sync_init+0x40) [0x8062620] -> /usr/libexec/dovecot/imap(cmd_sync+0x71) [0x8 062b81] -> /usr/libexec/dovecot/imap(cmd_noop+0x26) [0x8059c76] -> /usr/libexec/dovecot/imap [0x805be7f] -> /usr/libexec/dovecot/imap [0x805bf20] -> /usr/libexec/dovecot/imap(_client_input+0x6c) [0x805c0fc] -> /usr/libexec/dovecot/imap(io_loop_handler_run+0xff) [0x80bef6f] -> /usr/libexec/do vecot/imap(io_loop_run+0x36) [0x80be366] -> /usr/libexec/dovecot/imap(main+0x46c) [0x806448c] -> /lib/libc.so.6(__libc_start_main+0xb9) [0xb7eb4e1 9] -> /usr/libexec/dovecot/imap [0x80568b1] dovecot: Apr 24 13:03:29 Error: child 25748 (imap) killed with signal 6 My conf is: exim + dovecot + mysql exim deliver mail to maildir , because i don't know how to use LDA from dovecot. the maildirs are very large, for one account could be 30000 mails. dovecot is version 1.0.0 dovecot -n shows: # /etc/dovecot.conf base_dir: /var/run/dovecot/login log_path: /var/log/mail.log login_dir: /var/run/dovecot login_executable: /usr/libexec/dovecot/imap-login login_process_per_connection: no login_process_size: 80 login_processes_count: 10 login_max_processes_count: 50 login_max_connections: 80 first_valid_uid: 1001 last_valid_uid: 1001 mail_extra_groups: exim,vmail mail_location: maildir:%Lh/Maildir mail_cache_min_mail_count: 1 dotlock_use_excl: yes fsync_disable: yes maildir_copy_with_hardlinks: yes maildir_copy_preserve_filename: yes mail_drop_priv_before_exec: yes mail_executable: /bin/imap.sh mail_plugins: quota imap_quota auth default: mechanisms: PLAIN CRAM-MD5 default_realm: testing.net cache_size: 256 worker_max_count: 100 passdb: driver: sql args: /etc/dovecot-crammd5.conf userdb: driver: prefetch plugin: quota: maildir

3 12

[Dovecot] Problems with Shared Mailbox
by Gerhard Schmidt 15 May '07

15 May '07

Hi, i've installed dovecot on a new mailserverand try to set up some shared mailboxes. I have everiting up an runnig so far. I have 3 mboxes to be shared. I have use the following setup namespace private { separator = prefix = location = inbox = yes hidden = yes } namespace public { separator = / prefix = zentrale/ location = mbox:/var/mail/shared:CONTROL=/var/mail/shared/.control:INDEX=/var/mail/shared/.index } the problem is with the dovecot.index files [root@mailserv /var/mail/shared/.index]# ls -alR total 6 drwxrwx--- 3 dovecot vhsal 512 May 7 13:49 . drwxrwx--- 4 mailnull vhsal 512 May 7 13:52 .. drwxrwx--- 5 dovecot vhsal 512 May 7 13:49 .imap -rw-rw---- 1 dovecot vhsal 0 May 7 13:49 dovecot-shared ./.imap: total 10 drwxrwx--- 5 dovecot vhsal 512 May 7 13:49 . drwxrwx--- 3 dovecot vhsal 512 May 7 13:49 .. drwxrwx--- 2 dovecot vhsal 512 May 7 13:50 Eingang drwxrwx--- 2 dovecot vhsal 512 May 7 13:49 Erledigt drwxrwx--- 2 dovecot vhsal 512 May 7 13:50 Spam -rw-rw---- 1 dovecot vhsal 0 May 7 13:49 dovecot-shared ./.imap/Eingang: total 38 drwxrwx--- 2 dovecot vhsal 512 May 7 13:50 . drwxrwx--- 5 dovecot vhsal 512 May 7 13:49 .. -rw-rw---- 1 dovecot vhsal 0 May 7 13:50 dovecot-shared -rw-rw---- 1 dovecot vhsal 896 May 7 13:51 dovecot.index -rw-rw---- 1 dovecot vhsal 23552 May 7 13:51 dovecot.index.cache -rw-rw---- 1 dovecot vhsal 6824 May 7 13:51 dovecot.index.log ./.imap/Erledigt: total 30 drwxrwx--- 2 dovecot vhsal 512 May 7 13:49 . drwxrwx--- 5 dovecot vhsal 512 May 7 13:49 .. -rw-rw---- 1 dovecot vhsal 0 May 7 13:49 dovecot-shared -rw-rw---- 1 dovecot vhsal 456 May 7 13:52 dovecot.index -rw-rw---- 1 dovecot vhsal 20480 May 7 13:45 dovecot.index.cache -rw-rw---- 1 dovecot vhsal 3364 May 7 13:52 dovecot.index.log ./.imap/Spam: total 26 drwxrwx--- 2 dovecot vhsal 512 May 7 13:50 . drwxrwx--- 5 dovecot vhsal 512 May 7 13:49 .. -rw-rw---- 1 dovecot vhsal 0 May 7 13:50 dovecot-shared -rw-rw---- 1 dovecot vhsal 240 May 7 13:51 dovecot.index -rw-rw---- 1 dovecot vhsal 17408 May 7 13:45 dovecot.index.cache -rw-rw---- 1 dovecot vhsal 648 May 7 13:51 dovecot.index.log When the directory is setup like this everthing works as planed. But sometimes (havn't quite figured when exactly the dovecot.index file of one of the Mailboxes is regenated with the false permissions set ./.imap/Eingang: total 38 drwxrwx--- 2 dovecot vhsal 512 May 7 13:53 . drwxrwx--- 5 dovecot vhsal 512 May 7 13:49 .. -rw-rw---- 1 dovecot vhsal 0 May 7 13:50 dovecot-shared -rw------- 1 estartu vhsal 376 May 7 13:53 dovecot.index -rw-rw---- 1 dovecot vhsal 23552 May 7 13:53 dovecot.index.cache -rw-rw---- 1 dovecot vhsal 7116 May 7 13:53 dovecot.index.log How can I gate dovecot to set the permissions of this files to rw-rw---- I am using Dovecot v1.0.rc29 Regards Gerhard Schmidt -- ---------------------------------------------------------------------------- Gerhard Schmidt | Nick : estartu IRC : Estartu | Fischbachweg 3 | | PGP Public Key 86856 Hiltenfingen | EMail: estartu(a)augusta.de | on request Germany | |

2 3

[Dovecot] Thunderbird or Dovecot bug? (multiple keywords)
by Troy Engel 15 May '07

15 May '07

Here's a strange one. I have a user who's using Thunderbird 2.0.0 and assigning multiple tags (keywords) to emails, which are getting "lost" (I'll explain) when he leaves the folder and comes back. I can reproduce this on *his* account myself, but cannot reproduce it on *my* account (separate new TBird 2.0.0 profiles on Windows XP). Use the two TBird default tags 'Important' and 'Work' for all these tests, which it refers to as $Label1 and $Label2 in IMAP-keywords land. If I go into my account, label an email with both tags, it sticks -- I can click on Drafts then back to Inbox, and both tags/keywords still show in the client. If I go into his account, add the two tags, then click on Drafts and back on Inbox, only the *second* tag (Work, $Label2) shows. If I remove that tag, then the first tag (Important, $Label1) immediately pops up! On the backend the actual Maildir files match the dovecot-keywords and have the correct letter appended in both cases - so, in his account when the email only shows one tag, the physical mail file has the letters for two tags. So Thunderbird should be showing both tags, like it does in my account where everything is working correctly. This leads me to believe that the problem has something to do with the difference of dovecot-keywords content, and the interaction TBird has with Dovecot. My account, working correctly, looks like: dovecot-keywords: 0 $Forwarded 1 $MDNSent 2 $Label2 3 $Label1 file: Maildir/cur/1178712608.H529732P11686.yak.fluid.com:2,RSdc ...which matches, d=$Label1 (Important), c=$Label2 (Work) and TBird is displaying the email as having both tags - all is well and good. Now, his account looks like: dovecot-keywords: 0 Junk 1 NonJunk 2 $Label4 3 $Label1 4 $Label2 5 $Label3 6 $Label5 file: Maildir/cur/1178728930.P28392Q0M960111.yak.fluid.com:2,RSbde ...again, everything matches on the server; yet, it Thunderbird is only displaying $Label2 (d,3). I also noticed something interesting, even if I have the TB 'Junk Controls' completely disabled on his account, and remove all tags using the menu option, that file still retains the 'b' (NonJunk) tag in the filename: Maildir/cur/1178728930.P28392Q0M960111.yak.fluid.com:2,RSb All this long-winded explanation leads me to believe that somehow the difference in dovecot-keywords is causing this problem, but what I can't tell is who's problem it is -- Dovecot, or Thunderbird? Thoughts welcome, -te PS: all the normal things tried like deleting the dovecot index files, Thunderbird cache files and profiles, etc. -- Troy Engel | Systems Engineer Fluid, Inc | http://www.fluid.com

2 3

[Dovecot] Why is direct invocation of dovecot preferred over inet inclusion?
by Stewart Dean 15 May '07

15 May '07

I'm used to putting things in inetd and, 1) should dovecot crash, I'd think it would get restarted if it was invoked from inet's imap-login 2) it would get started well after the boot ...wouldn't that be preferable. Enlighten me, please -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

2 1

[Dovecot] Refreshing Dovecot
by Stewart Dean 15 May '07

15 May '07

If I've made configuration changes, is there a way to refresh...without killing and restarting....Dovecot? -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

5 5

[Dovecot] maildir_file_do(/var/admhome/user/Maildir) racing
by Ralf Hildebrandt 15 May '07

15 May '07

dovecot version 1.0.0, compile from the sources. --------- snip -------- # /usr/local/etc/dovecot.conf listen: *:10143 ssl_listen: *:10943 ssl_cert_file: /etc/ssl/certs/postamt.pem ssl_key_file: /etc/ssl/private/postamt.key disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login mail_location: maildir:~/Maildir mail_plugins: quota imap_quota namespace: type: private separator: . prefix: INBOX. inbox: yes auth default: passdb: driver: pam userdb: driver: passwd plugin: quota: maildir quota: maildir:ignore=Trash --------- snip -------- We're using these odd ports, because there's still courier-imap on the original ports. One, just one (!) of our users gets: May 14 16:47:17 postamt dovecot: imap-login: Login: user=<username>, method=PLAIN, rip=141.42.x.y, lip=ip.of.the.server May 14 16:47:17 postamt dovecot: imap-login: Login: user=<username>, method=PLAIN, rip=141.42.x.y, lip=ip.of.the.server May 14 16:47:17 postamt dovecot: IMAP(username): maildir_file_do(/var/admhome/username/Maildir) racing May 14 16:47:17 postamt dovecot: IMAP(username): Disconnected: Internal error occurred. Refer to server log for more information. [2007-05-14 16:47:17] Now it's a bit hard for me to see what's going on. /var/admhome/username/Maildir is on /, thus: $ mount /dev/cciss/c0d0p6 on / type ext3 (rw,errors=panic) $ dmesg does not complain about any corruption $ uname -a Linux postamt.charite.de 2.6.21.1 #1 SMP Tue May 1 15:50:11 CEST 2007 i686 GNU/Linux OS: Debian testing -- Ralf Hildebrandt (i.A. des IT-Zentrums) Ralf.Hildebrandt(a)charite.de Charite - Universitätsmedizin Berlin Tel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-Berlin Fax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to plonk(a)charite.de

3 6

[Dovecot] Question: contention with blackberry
by Stewart Dean 15 May '07

15 May '07

My production imap is currently UWIMAP with mbox.. One of the problems commonly observed is mailbox lock loss, which happens when: a) a VIP has multiple secretaries accessing a single mailbox (actually, they are professional enough to have figured the realities of conflicting access and rarely have a problem), b) somebody leaving their machine on at home and coming in and firing up their work computer c) important people with Blackberries....and the BB service polls the mailbox every so often and breaks the lock. In any case, the maillog ends up with a message like this: > May 5 19:45:04 mercury mail:info imapd[2035774]: Logout user=xxxxx host=bda056.bis.na.blackberry.com [216.9.249.56] > May 5 19:46:52 mercury mail:info imapd[2502902]: Killed (lost mailbox lock) user=xxxxx host=cpe-24-161-103-11.hvc.res.rr.com [24.161.103.11] How will this work with Dovecot? I regard what is happening now as OK, working as designed. Although we may eventually move to a different mailbox format, I am only switching from UW to DC in the first step. -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

3 2

[Dovecot] global vs user script
by M1 15 May '07

15 May '07

What is the order of execution if both user and global sieve script exists? Thanks.

4 10

[Dovecot] Mails, work and so on
by Timo Sirainen 14 May '07

14 May '07

You can probably guess from my flood of mails that I'm no longer busy. I still have a couple of exams but since I haven't spent any time at all studying for them or attending the lectures, I can just as easily leave them for next year. I've read and answered most of the "easy" mails in this list and in my INBOX. I'll try to answer the rest of them this weekend, so no need to forward them to me again, at least not yet. :) Now that I'm finally non-busy, it also appears that I haven't worked for a long time and I'm almost broke. :) So now would be a great time for your corporation to buy/sponsor some Dovecot development. Otherwise I'm probably soon busy with non-Dovecot related work. My own high priority TODO contains: - Get the rewritten Squat full text search index working. It probably needs a name change, since it's not all that close to Cyrus Squat anymore. Suggestions? Could of course be just "fts_dovecot". - Shared mailboxes / ACLs - dbox cleanups and possibly partial redesign. I'll write a separate mail about this later. - Index file code cleanups, simplifications and optimizations. Make it work with NFS with attribute cache enabled.

5 7

[Dovecot] How to get rid of locks
by Timo Sirainen 14 May '07

14 May '07

Although Dovecot is already read-lockless and it uses only short- lived write locks, it's be really nice to just get rid of the locking completely. :) I just figured out that O_APPEND is pretty great. If the operating system updates seek position after writing to a file opened with O_APPEND, writes to Dovecot's transaction log file can be made lockless. I see that this works with Linux and Solaris, but not with OS X. Could you BSD people try if it works there? http://dovecot.org/ tmp/append.c and see if it says "offset = 0" (bad) or non-zero (yay). The O_APPEND at least doesn't work with NFS, so it'll have to be optional anyway. Currently Dovecot always updates dovecot.index file after it has done any changes. This isn't really necessary, because the changes are already in transaction log, so the dovecot.index file can be read to memory and the new changes applied on top of it from transaction log (this is pretty much how mmap_disable=yes works). So I'm going to change this to work so that the dovecot.index is updated only if a) there are enough changes in transaction log (eg. 8kB or so) and b) it can be write-locked without waiting. Maildir then. It has this annoying problem that readdir() can skip files if another process is rename()ing them, causing Dovecot to think that the message was expunged. The only way I could avoid this by locking the maildir while synchronizing it. Today I noticed that this doesn't happen with OS X. I'm not sure if I was just lucky or if there really is something special implemented in it, because it doesn't work anywhere else. I'm not sure if this is tied to HFS+, or if it will work with zfs also (Solaris+zfs didn't work). So perhaps the locking could be disabled while running with OS X. More importantly I figured out that it can also be avoided with Linux +inotify. As long as the inotify event buffer doesn't overflow, the full list of files can be read by combining the readdir() output and files listed by inotify events. If the inotify buffer overflows (highly unlikely), the operation can just be retried and it most likely works the next time. So with these changes in place, changing a message flag or expunging a message would usually result in: - lockless write() call to dovecot.index.log - lockless read()ing (or looking into mmaped) dovecot.index.log to see if there's some new data besides what we just wrote that needs to be synchronized to maildir - rename() or unlink() calls to maildir. If a call return ENOENT, the maildir needs to be readdir()ed with inotify enabled to find the new filename. Not a single lock in the operation, assuming that dovecot.index file wasn't updated. Assigning UIDs to newly delivered mails would require locking though. dovecot-uidlist needs to be locked, and the UIDs need to be written to dovecot.index.log file in the correct order, which can also be done with dovecot-uidlist locking. Actually a single write() to dovecot.index.log isn't enough. I think there needs to be some kind of a flag written to the beginning of the transaction which marks the transaction as truly finished. If the flag isn't there, any reader knows to stop and wait until the flag is set. So this means that the writer needs to: 1. Do a single O_APPENDed write() call writing the whole transaction 2. Get the current offset with lseek(fd, 0, SEEK_CUR) (this is what the append.c tester checks) 3. pwrite() the finished-flag to beginning of the transaction Except at least with Linux pwrite() doesn't work if O_APPEND is enabled. There are two ways to work around this: a) fcntl(disable O_APPEND) + pwrite() + fcntl(enable O_APPEND) b) Keep two file descriptors open for the transaction log. First with O_APPEND flag and second without. pwrite() to the second one. a) is probably better because it doesn't waste file descriptors.

8 10

[Dovecot] PATCH: sendmail-like DSNs in Dovecot deliver (EX_TEMPFAIL always)
by Steffen Kaiser 14 May '07

14 May '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I've put together an always tempfail & sendmail-like DSN report back patch. Because I don't know how to transform the rejection reason into sysexit.h codes, it always tempfails. The hooks are so that: a) config file setting: lda_mode = mode b) command line: deliver --mode mode where mode is default or sendmail. When no mode is specified, it defaults to "default", which is the current behaviour. In sendmail mode, mail_send_rejection() simply prints the rejection reason to stdout, logs it and returns EX_TEMPFAIL. Ideally, the return value would be specific to the reason. I haven't poked into this deeply, but it doesn't look straight forward. Bye, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBRkHNQS9SORjhbDpvAQIhdggAq79RHKa1gIUTFwAu7Gd2maIUkDTgbNu6 8+MEQHujOPkV6wcF+5ih/hkht5BnuBUiIbnp2dvKGaUcHY8avzYD6BEc6gIAyJjM YIKDANI5+BVnQWUdiQMlQrSrRIZBqFziL8v/LvICJUsiOqCKT7se37KuUOK14gXO FSghuPta0rorogJ8kh+VGdmnqNVzKb6eKrnFQUggiezTmTcHY6/DRsLbsKV//fyW cybualj+THF9cj+EajwCMsYypc9KOdVg6lhcCD87oskDmMqcG5lwF2HU9nclnMxE 6pOnaLGNfKmWyeAKOLgvMimjhkU74+NBwQ+b4h61JzZ6lbiZKWX7wA== =gE8Z -----END PGP SIGNATURE-----

3 5

[Dovecot] PATCH Deliver forgets sendmail_path if DEBUG is set
by Steffen Kaiser 14 May '07

14 May '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, Dovecot v1.0.0 deliver erases the environment if DEBUG is set, hence, also (probably) erases SENDMAIL_PATH if it has been read from configuration file. This happens with: Debian Etch, libc-2.3.6.so, gcc (GCC) 4.1.2 20061115 (prerelease) (Debian 4.1.1-21). Problem in log: May 10 12:33:07 ux-2s11-9 deliver(dvtest): execv() failed: No such file or directory May 10 12:33:07 ux-2s11-9 deliver(dvtest): Sendmail process terminated abnormally, exit status 75 Note the empty string in the function call execv(). Attached patch just deletes the DEBUG variable. Bye, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBRkL45y9SORjhbDpvAQKeTAgAr6i6XrICqZsTaezUFqXO69cuwOt4iL5u K3PAF0ywAtrRkpWG+G8TUtypUkLp+CGEK3Ery1mWVp2/TeNPv6LxeUWWGxmdlSV3 XFQSV/VRuPtJ/Uc8wFWOBcpAn0H9rnLNkF5vv512t4zs99eF10++US5fZwFOXK8M azgaCEYwOrmZ4U2sCQwVQChXcZQq6MI5IcE3ChpzlUP45bq2dVZrXqAZ/xNo1iuG lQd/43XJu1++LxB8N1Fkbaeme+Ojt/c5fOKApjhnCJuQwi46jnSEeHbO2VUCz+ST mU34QR3zx+h4YW91oKQhFYkbSWEYmuXk2OoZaFUd1Q+E+oXHHuDBng== =CiqO -----END PGP SIGNATURE-----

2 2

[Dovecot] header-lines of subfolders have to be rescanned after each client startup
by Rainer Sigl 14 May '07

14 May '07

Hi all, after each startup of my different mail clients (thunderbird, outlook, ...) the contents of subfolders if I click in has to be renewed. This takes some time for large folders. I just migrated from courier. And there all subfolders were available immediately. Is there something to configure? Another effect regarding subfolders is that the client forgets, which subfolders were opened after shutdown and shows the folders closed. This means, that necessary subfolders have to be reopened after each startup. This was managed as well by my previous courier server. Many thanks for answers Rainer Sigl -- ----------------- Rainer Sigl, | email: sigl(a)mpe.mpg.de MPI f. extraterrestrische Physik, | phone: +49 (89) 30000-3557 Postfach 1312, | fax: +49 (89) 30000-3569 D-85741 Garching, Germany | web: http://www.mpe.mpg.de/~sigl/

2 4

[Dovecot] v1.1 plans
by Timo Sirainen 14 May '07

14 May '07

I think I won't do any actual releases until it's mostly feature complete. Then maybe v1.1.alpha1 or v1.1.beta1. So if you want to test it before then, use CVS or the nightly snapshots. I'm planning on keeping v1.1 almost completely compatible with v1.0. There could be some minor configuration file changes, but for most people v1.0's dovecot.conf should work with v1.1. I want to update index file handling to use less locks and update dovecot.index file less often. The file formats would still stay backwards compatible with v1.0. After this I'm hoping to get index files working well with NFS even with attribute cache enabled. Dovecot v2.0 then brings incompatible index files and more or less rewritten configuration file handling. It could still support old config file format and settings, but the default will be somewhat different. I'm hoping to release the first alphas/betas in 2-3 months, with v1.1.0 maybe even as early as next summer. The good thing here is that index file code hasn't changed much since v1.0, so it should be stable. The bad thing is that I've added a couple of completely new indexes. I'm also quite busy for the next month, but I'm not sure how much it affects my coding. :) The largest already implemented new features are: + Added support for IMAP UIDPLUS extension + IMAP SORT: Sort keys are indexed, which makes SORT commands faster. + IMAP THREAD: Threads are indexed into a dovecot.index.thread file. It can usually be updated incrementally, so this makes THREAD fast. + Added Dovecot-specific X-REFERENCES2 threading algorithm. It's similar to REFERENCES, but it doesn't do base subject merging and it sorts the threads by their newest message. + When saving messages, update cache file immediately with the data that we expect client to fetch later. Maildir-only currently. + Mailbox list indexes. Mailbox metadata is stored there, so STATUS commands can return synchronized mailboxes' metadata simply by reading a single mailbox list index file. - FIXME: Currently works only with Maildir++ layout. + Expire plugin can be used to keep track of oldest messages in specific mailboxes. A nightly run can then quickly expunge old messages from the mailboxes that have them. The tracking is done using lib-dict, so you can use either Berkeley DB or SQL database. + Namespaces are supported everywhere now. - FIXME: except by convert plugin + Full text search indexing support with Lucene and Squat backends. + OTP and S/KEY authentication mechanisms (by Andrey Panin). + mbox and Maildir works with both Maildir++ and FS layouts. You can change these by appending :LAYOUT=maildir++ or :LAYOUT=fs to mail_location. Features that I'm planning on implementing: - Fully supported shared mailboxes and IMAP ACL extension - Replace Squat FTS indexes with my new design - Case-insensitive searches with non-ASCII text as well - Maybe add support for all kinds of IMAP extensions that can be easily supported. LEMONADE extensions especially: CONDSTORE, CATENATE and maybe even URLAUTH if I can figure out how it should work. If a feature can be implemented completely as a plugin, it could still come in v1.1.beta stage, because it won't destabilize the rest of the Dovecot anyway.

17 36

[Dovecot] Feature Request: content-filter / MOVE scripts
by Daniel L. Miller 14 May '07

14 May '07

Since your "1.1 plans" announcement somehow turned into everybody handing in a wish list . . . thought I'd start one by itself - since I expect a few people to have opinions on this matter. I'm aware of a plug-in functionality in Dovecot, and that a plug-in exists for dspam processing - but my review of the plug-ins indicate they require compiling your own Dovecot - the plug-in setup isn't really suitable for packaged distros. As a packaged software user - I really really really don't like compiling my own software, either for features or bugfixes - I want leave that to the experts. On learning of 1.0's official release, I nudged the Debian package maintainers to check - and they were already on it and it updated. Thanx Timo, Jaldhar, and Fabio. I have some thoughts on an interface that would eliminate the need for compile-time plug-ins, but provide some major power to sysadmins. Basically, I want a way of telling an external program the following: 1. A message was moved. 2. The folder is moved from was XXX. 3. The folder it moved to was YYY. 4. The message moved was ZZZ. Armed with this information, just about anybody's spam fighting learn scripts can be called to do their thing. A few different ways have occurred to me: 1. Have a dedicated "content-filter" functionality built-in to Dovecot. Under this model, Dovecot.conf would include at least three new parameters: FILTER-FOLDER-SUFFIX, FILTER-FOLDER-IN-SCRIPT, and FILTER-FOLDER-OUT-SCRIPT. Whenever a message is moved into or out of a folder ending in SUFFIX the appropriate SCRIPT is called, with the arguments above being passed. 2. A bit more generic, less processing for Dovecot. Dovecot.conf parameter ACTION-SCRIPT (hey, feel free to use other names - I'm just brainstorming here). Any time any message is moved anywhere, call SCRIPT with the arguments. Having never looked at Dovecot's code, I'm just guessing, but this probably wouldn't take much to implement - but might be the most performance affecting. 3. Have a definable named-pipe to send the same information to. 4. Have a definable TCP socket to send the same information to. In any case, I figure it's best to prevent any message processing by Dovecot itself - so while it might be nice to define a list of headers to send to the scripts, instead of the whole message, that's probably not appropriate for Dovecot to focus on. On the other hand, any of the above options would probably benefit from a MAXIMUM_FILTER_SIZE parameter to limit the maximum message size. So what's the world got to say about this? (More importantly, how does TIMO feel about this?) ;). -- Daniel

3 2

[Dovecot] Dovecot, Postfix and SMTP AUTH....
by Bartosz Toczek 13 May '07

13 May '07

Hello. I've notice a problem with SMTP AUTH in postfix with dovecot. My configuration is based on Postgresql. I've created a function in postgresql which returns password and username and attached it to password_query. Query looks like this password_query = SELECT username_out as username, password_out as password FROM get_password(lower('%n'),lower('%d')); Problem is when get_password returns something like this... vmail=# SELECT username_out as username, password_out FROM get_password(lower(''),lower('')); LOG: statement: SELECT username_out as username, password_out FROM get_password(lower(''),lower('')); LOG: duration: 2.342 ms statement: SELECT username_out as username, password_out FROM get_password(lower(''),lower('')); username | password_out ----------+-------------- | (1 row) It returns 1 empty row.... When this is attached to postfix with smtp auth with such configuration # SMTP AUTH broken_sasl_auth_clients = yes smtpd_sasl_auth_enable = yes smtpd_sasl_security_options = noanonymous smtpd_sasl_authenticated_header = yes smtpd_sasl_local_domain = smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth my serwer starts to be open relay... I now that it returns empty string for username and password... so where is the password checked... if I dont send password as a parameter to my function. Definition of the function looks like this: CREATE FUNCTION get_password("login" character varying, "domain" character varying, OUT username_out character varying, OUT password_out character varying) RETURNS record Can you help with that... BT ---------------------------------------------------------------------- Zrob numer kumplom >> http://link.interia.pl/f1a5d

4 4

[Dovecot] Public folders using NAMESPACE
by Joakim Ryden 13 May '07

13 May '07

Howdy folks! I've been trying to research how to (or if possible at all) implement public folders using the namespace feature on a server with multiple virtual domains. After about an hour of looking around I'm a little confused. :) I guess there are two questions: 1) Is it possible / does it work? 2) If yes, does anyone have a sample configuration or write-up of How You Did It[TM] to share? I've been mainly focusing on the thread from here: http://www.dovecot.org/list/dovecot/2006-June/013683.html and the wiki ACL documentation: http://wiki.dovecot.org/ACL but I'm having a hard time piecing it all together... Thanks for any and all tips! --Jo

2 5

[Dovecot] mailquota in ldap attribute 'mailQuota'
by Shahmat Dahlan 13 May '07

13 May '07

I've tried having the ldap quota in an ldap attribute, which still doesn't work. /etc/dovecot.conf protocols = imap pop3 mail_location = maildir:/data/mail/%u/Maildir protocol imap { mail_plugins = quota imapquota } plugin { quota = maildir:ignore=Trash } the rest are defaults added an attribute 'mailQuota' with value '10240' kbytes or 10Mbytes as for /etc/dovecot-ldap.conf user_attrs = mail,homeDirectory=home,uidNumber=uid,gidNumber=gid,quotaStorage=mailQuota Would appreciate if anyone could assist on this. I'd prefer to use the above than setting the mail quota manually: quota = maildir:storage=10240:ignore=Trash We are actually in the planning stage of migrating all of current our mailboxes from Netscape to Dovecot, instead of upgrading it to those new Sun.

2 1

[Dovecot] Deferring, instead of rejecting, messages when at quota
by Mike Brudenell 13 May '07

13 May '07

Greetings - I'm having trouble working out where to alter this behaviour (so please forgive me if it turns out to be an Exim thing rather than Dovecot!)... My test service is using Exim as the MTA and Dovecot's "deliver" for the LDA. We are using Maildir mailboxes with filestore quotas. When I send a large test message to myself that cannot be delivered because I don't have sufficient available quota remaining an error message is immediately returned to the sender and the incoming message discarded. The error message says this: Your message was automatically rejected by Dovecot Mail Delivery Agent. The following reason was given: Not enough disk space Instead of Exim rejecting the incoming message and generating the error response because of deliver's failure to, umm, deliver I'd like the message to be retained in Exim's queue so that it can be retried periodically. With our old/live system (Sendmail + UW IMAP's "tmail" LDA) I edited the tmail source code to return a different exit code: one that caused Sendmail to defer (re-queue) the message rather than reject it. How do I achieve this effect with Exim + deliver please? Is it a case of: * Setting something in Dovecot's configuration file (I can't spot what!); * Changing a return code in deliver's source (if so, whereabouts and to what?); * Or is there an Exim directive I need to add to the transport definition in its configuration file? With thanks, Mike B-) -- The Computing Service, University of York, Heslington, York Yo10 5DD, UK Tel:+44-1904-433811 FAX:+44-1904-433740 * Unsolicited commercial e-mail is NOT welcome at this e-mail address. *

3 3

[Dovecot] wierd ssl-parameters.dat regeneration error
by Kyle Wheeler 13 May '07

13 May '07

I just had a strange problem with my Dovecot 1.0 installation. After about two weeks, it logged these messages: dovecot: Error: ssl-build-param: rename(/usr/local/var/lib/dovecot/ssl-parameters.dat.tmp, /usr/local/var/lib/dovecot/ssl-parameters.dat) failed: No such file or directory dovecot: Error: child 30689 (ssl-build-param) returned error 89 And thereafter, all login attempts resulted in this: dovecot: Error: imap-login: read(ssl-parameters.dat) failed: Unexpected EOF dovecot: Error: child 19036 (login) returned error 89 Thankfully, deleting the ssl-parameters.dat file (/var/run/dovecot/memoryhole.net/login/ssl-parameters.dat) and restarting dovecot fixed the problem, but it seems odd to me that dovecot expects /usr/local/var/lib/dovecot to exist (because, of course, it doesn't). I'm not defining that directory in the config file anywhere. Does anyone have any idea what's going on? ~Kyle -- I'm sick of following my dreams. I'm just going to ask them where they're going and hook up with them later. -- Mitch Hedberg

2 10

[Dovecot] Mailbox creation with Spam
by Master Abi 13 May '07

13 May '07

Hi all, I got dovecot working, but I would like to know when and what creates the mailbox (cur, new, trash, etc ). I noticed that when a client connects for the first time that mailbox is created or when a mail arrives for the first time (i think). I would like to give each mailbox a Spam folder, and possibly doing this automatically. Is this possible with some dovecot setting and not via scripting. Thanks master

2 1

[Dovecot] fs quota plugin and NFS
by Nicolas STRANSKY 13 May '07

13 May '07

Hi, I'm trying to use the Dovecot v1 fs quota plugin. The server uses NFS mounted volumes for INBOX and other maildir folders. The /usr/bin/quota command is working seamlessly but I get errors with the quota plugin, which gives the following logs: Apr 19 17:46:15 rouge dovecot: IMAP(xyxyxyx): quotactl(Q_GETQUOTA, nfs.xxx.yyy.org:/home) failed: No such file or directory Apr 19 17:46:18 rouge dovecot: IMAP(yxyxyxy): quotactl(Q_GETQUOTA, nfs.xxx.yyy.org:/home) failed: No such file or directory Is there a way to get it work ? Thanks, -- Nico Il faut s'entraider, c'est la loi de nature. -+- Jean de La Fontaine (1621-1695), L'Âne et le Chien (Fables VIII.17) -+-

2 3

[Dovecot] mailquota in ldap attribute 'mailQuota'
by Shahmat Dahlan 13 May '07

13 May '07

I've tried having the ldap quota in an ldap attribute, which still doesn't work. /etc/dovecot.conf protocols = imap pop3 mail_location = maildir:/data/mail/%u/Maildir protocol imap { mail_plugins = quota imapquota } plugin { quota = maildir:ignore=Trash } the rest are defaults added an attribute 'mailQuota' with value '10240' kbytes or 10Mbytes as for /etc/dovecot-ldap.conf user_attrs = mail,homeDirectory=home,uidNumber=uid,gidNumber=gid,quotaStorage=mailQuota Would appreciate if anyone could assist on this. I'd prefer to use the above than setting the mail quota manually: quota = maildir:storage=10240:ignore=Trash We are actually in the planning stage of migrating all of current our mailboxes from Netscape to Dovecot, instead of upgrading it to those new Sun.

1 0

[Dovecot] Migrating to Maildir -> path
by Wouter de Jong 13 May '07

13 May '07

Hello, I'm in the process of migrating to Maildir, and I wondered what would be an acceptable path. I want to do virtual-accounts only, so $HOME/Maildir/ is not an option. I was thinking of /some/path/username(a)domain.tld/Maildir/ and later perhaps /some/path/(firstletter)/username(a)domain.tld/Maildir/ but perhaps Maildir/ is a bit too redundant here.... Anyone who could advice ? Many thanks, Wouter

3 2

[Dovecot] Mixing MBOX and Maildir?
by Marc Perkel 13 May '07

13 May '07

Is it possible to have some folders be mbox and some be maildir format? Why you might ask? Sometime for diagnostics I have the Exim MTA archive certain messages in MBOX format and then I want to copy them into an imao folder to look at them with Thunderbird. When I used MBOX all I had to do was copy the file into a folder and it worked. So what I'd like to do is have a folder with a special name that is MBOX and the rest be maildir. Ideally have Dovecot be smart so that if the file exists then it is assumed to be MBOX and if the directory exists then it is assumed to be maildir. Has anyone done anything like this?

6 10

[Dovecot] Time adjusting
by Robert McKenzie 13 May '07

13 May '07

Would it be possible to have an option/variable in the config file to allow for easier setting of the maximum time to sleep for rather than having it hard coded or allow for adjustment up to an amount greater than 5 as it is at present but still have an upper limit hard coded. My system is regularly out on boot up by up to 7 seconds and consequently dovecot kills itself, if I restart it is fine and keeps going without a problem until the next reboot. Regards, Robert McKenzie. -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.467 / Virus Database: 269.7.0/801 - Release Date: 12/05/2007 18:40

4 3

[Dovecot] Writing a new mailbox access module
by Tom Alsberg 13 May '07

13 May '07

Having finished a few other projects, I'm contemplating trying to write a new mailbox module which could be useful for us here. I would appreciate any guidance. Basically, I need (or rather, could use) a module that provides a merge of two mailboxes (which are themselves accessed by other modules), cascading them, so that: * The user sees one mailbox M, which contains all the messages in the mailboxes A and B. * A and B are both already accessible by existing Dovecot mailbox access modules, but possibly by different modules (e.g. A is an mbox, B is a Maildir). * Any write operation (creation of a new message, etc.) is eventually performed on B. * As soon as a message that was in A is accessed (either for read or for write), it is transferred to B. I would use such a module to combine the spool file in /var/mail with some INBOX in the user's home directory. The incentive is the following: * Traditionally, users receive their mail in the spool, commonly in /var/spool. Mailers, like mail, elm, pine, mutt, etc. move each read message to some record mailbox (commonly ~/mbox, but with the more advanced mailers it can be configured to be some other mailbox, even a Maildir). * Users keep working this way. IMAP will not substitute the regular mail access when inside the network here. But it should be as convenient as possible to use it from the outside (e.g. at home, or from an Internet Café, or using some Webmail interface). * Mainly for administrative reasons, it is desirable that mail keeps being delivered to the spool, and not directly to the user's home directory. One of the reasons is that mail never fails to be delivered as long as there is space in the spool. When the user is out of quota on his home directory, the mail does not get rejected, and a failure only occurs when the user initiates some operation (like reading the message). Another reason is simply to be compatible with the way traditional mailers and users work. * IMAP, and IMAP clients (e.g. Thunderbird, the most common one here), on the other hand, usually do not recognize the concept of a spool. There is an INBOX, where all mail arrives, and this is where all new messages should arrive, and remain, unless they are deleted moved elsewhere. * It would of course not be desirable to just move messages automatically after the user reads them, because it would confuse users when a message suddenly disappears from a mailbox all by itself. * The best way I can think of to be consistent with both the traditional way mailers work (moving messages from spool to ~/mbox after they are read) and the way IMAP is commonly used (INBOX contains all received messages not deleted or moved, including messages that just arrived), would be using such a module as I suggested, with (using the previous terminology) e.g. M=INBOX, A=spool, and B=~/mbox. I have just skimmed again through the mailbox code (which I last looked at over a year ago, back when it was in alpha releases), not going too much into details. From past experience and current skimming, working with that code doesn't seem too straightforward, though. I can think of how to implement the logic I described on its own (i.e. as a library with a few functions), but not sure how difficult it will be to interface it with Dovecot. Is there any developer/module writer's guide somewhere that explains the mailbox access module interface? I'd appreciate some basic guidance to start with. If I get to working on it seriously, expect lots of questions from me about the code :-) Regards, -- Tom -- Tom Alsberg - hacker (being the best description fitting this space) Web page: http://www.cs.huji.ac.il/~alsbergt/ DISCLAIMER: The above message does not even necessarily represent what my fingers have typed on the keyboard, save anything further.

2 1

[Dovecot] dovecot deliver tries to setuid but why?
by Daniel 13 May '07

13 May '07

Hi! I've set up postfix(2.4.1) + dovecot(1.0-cvs) + dovecot-lda(1.0-cvs). Dovecot's deliver is running as vmail:vmail (according to postfix's master.cf). Now the problem (when receiving mail): deliver(leva): auth input: leva deliver(leva): auth input: uid=8006 deliver(leva): auth input: gid=8000 deliver(leva): auth input: home=/var/mail/virtual/leva deliver(leva): setuid(8006) failed: Operation not permitted Every virtual user has different uids, but the gid is the *same* for everyone. The gid is 8000(vmail) for everybody, and deliver runs as 8000:8000 (vmail:vmail). vmail group has write access to the users' maildirs. So why does deliver try to setuid when it has group write permission to the destination directory? Thanks! Daniel

2 1

[Dovecot] Virtual User Home Directory, and APOP Clear Text Passwords
by imacat 13 May '07

13 May '07

Dear all, Hi. This is imacat from Taiwan. I'm new to this list. I was migrating from Qpopper to Dovecot. (Qpopper copies the mailbox when POP3 logged in, which causes quota problem.) Generally Dovecot is nice. However, I have a few questions: 1. I have a few virtual users, and I'm not using IMAP. Do I still have to give them a writable home directory? I mean, they exists only for me to receive mails from fetchmail. They really have nothing but their inbox. But if I do not give them a writable home directory, I got this error in my syslog all the time: mbox: Can't create root mail directory /home/homeless/mail: Permission denied 2. I would like to use APOP in addition to SSL/TLS. Currently Dovecot saves APOP passwords as clear text. I understand this. But is it possible to have some sort of encoding, for example, Base64? Just to prevent casual reads. I have several users. I do not want to know their passwords just to add them to the APOP database. I do not want other roots to read my passwords, intended or not. Encoded passwords also have the advantage that I can use passwords that contain the colon sign ":". It would be nice if something a little harder than Base64 can be used. Thank you very much in advance. -- imacat ^_*' imacat(a)mail.imacat.idv.tw PGP Key: http://www.imacat.idv.tw/me/pgpkey.txt Tavern IMACAT's http://www.imacat.idv.tw/ Woman's Voice http://www.wov.idv.tw/ TLUG List Manager http://www.linux.org.tw/mailman/listinfo/tlug

2 6

[Dovecot] SASL using different auth database?
by Dave McGuire 13 May '07

13 May '07

Hi folks. Is it possible to configure Dovecot to authenticate against one mechanism (i.e., /etc/passwd) for POP/IMAP connections, while providing a SASL authentication socket that satisfies authentication requests against a different mechanism, say MySQL? The goal here is to allow users to have different passwords for SMTP authentication and POP/IMAP connections. I am converting an existing installation to Dovecot...this installation currently has quite a few users who are configured with SMTP authentication (Cyrus SASL/saslauthdb) using different passwords than are configured for their POP connections (via cucipop, /etc/passwd). If someone can think of any better way to accomplish this goal, I'm all ears. Thanks, -Dave -- Dave McGuire Port Charlotte, FL

3 5

[Dovecot] logging IMAP size?
by Armijn Hemel 12 May '07

12 May '07

hi all, is there a way to somehow log the size of an IMAP session with Dovecot? With POP3 there is this pop3 format string I can set in dovecot.conf, but I don't see an equivalent for IMAP. If so, are there any plans to add this functionality? thanks, armijn -- --------------------------------------------------------------------------- armijn(a)uulug.nl | http://www.uulug.nl/ | UULug: Utrecht Linux Users Group ---------------------------------------------------------------------------

3 3

[Dovecot] dbox redesign
by Timo Sirainen 12 May '07

12 May '07

I don't think anyone uses dbox currently, so the whole format could still be redesigned. So I was thinking about doing two major changes: 1. Rely on index files a lot more. The flags are already stored in index files, so there's no need to waste I/O updating them to dbox files all the time. They could still be updated (if indexes get deleted, the flags aren't all gone), but less often. 2. Require fcntl() locking. Currently dbox uses dotlocks which is slow. Cydir could be a good alternative also once index file code is made a bit more robust. Perhaps I could implement single instance attachments for cydir too.. Locking ======= The current dbox "index" file would be gone. It's pretty useless. Replace it with a whole new index file. Or perhaps it should be called "locks" file or something. The locks file would contain records: <file id> <lock timestamp> <status>. So something like: <header> 1 4645a60f 0 2 00000000 N 3 00000000 D That would mean that the first file is locked by some process, either for appending or expunging. The 2nd and 3rd files aren't locked. New messages can't be appended to 2nd file anymore. 3rd file is already deleted and this record needs to be removed when rewriting the file. Locking a dbox file for either appends or expunges is done like: 1. See if timestamp is zero - If not, see if it's older than .. let's say a day or so .. a) Yes: Continue to 2. b) No: Assume the file is locked 2. Do fcntl() byte range lock over the record line in the locks file. - If it failed, the record is locked 3. Write the timestamp. 4. Compare stat() and fstat() inodes to see if the file was rebuilt - If yes, reopen the file and goto 1 5. File is now locked. Do the append/expunge. 6. Write timestamp to zero. 7. Unlock the byte range. If a file is locked, append will try another file and expunge will mark the message as expunged instead of actually expunging it yet. Note that the locks file is read without locking. This is safe because data is never moved within the file, and it doesn't matter if the timestamp isn't read correctly always. The timestamp check is only an optimization. Actually I'm not sure if it would be better not to have the timestamp at all. Deleted records will stay in the file until the file is rebuilt. If a deleted record is noticed in the file, the process tries to lock the whole locks file. If it succeeds, it proceeds with writing the non-deleted records to a temporary file and rename()ing it over the locks file. Appending ========= 1. Find the first file in the locks file that has appendable=0 - If no such file was found, go to "create a new file" logic as described below 2. Lock the file record 3. Verify from the file's headers that this file can actually be appended to - If messages have been expunged from a dbox file, it can't be safely appended to anymore. - Other reasons include eg. configurable max. file size and daily rotations 4. Write the mail 5. Lock locks file's header 6. Get the UID from "next uid" field and update it 7. Unlock the header 8. Unlock the file record 9. Update index file Create a new file logic: 1. Create a temporary file 2. Write the messages there 3. Lock locks file's header (including fstat() / stat() rebuild check) 4. See what the latest file ID is in the file 5. rename() temp fail to msg.<latest file id+1> 6. Lock locks file for the range of the to-be-written record below 7. Write the new record to locks file 8. Go to step 6 in the original append logic Syncing / expunging =================== If locks file's header's "next uid" doesn't match the one currently in index file, the appending crashed between steps 6 and 9. Find the new message(s) and append them to index file. If the locks file is completely gone , rebuild it by going through all the msg.* files in the directory. If "expunge counter" (see below) doesn't match in locks file's header vs. index file header, go through all the msg.* files to see if a message exists in multiple files. If found, remove the duplicates. Typically neither of the above happens, so the only thing to do here is to write changes from index file to dbox files. This may mean flag changes once in a while, but most importantly expunges will always be synced. Initially figure out what files require expunging. Try to create a single lock range that includes all of them. If there are non-zero lock timestamps in that range, create multiple ranges. If a file couldn't be locked, the expunge is done by updating expunge-flag in the file. This can be done without locking (see below for flag updates). If a file was successfully locked, the expunging is done by: 1. Update "expunge offset" in file header to the offset of the first expunged message. If expunge offset is non-zero, the file is treated as non-appendable. Also when rebuilding and finding the same message from multiple files, this field is used to figure out which file should be truncated. 2. Copy the rest of the non-expunged messages to a new temporary file and add the file to locks file using the "Create a new file" logic described for appends. Instead of updating "next uid" field, update "expunge counter" field. 3. ftruncate() the old file. 4. Update "expunge counter" in index file. Sync locking ============ If there is one big "sync lock", then flags can be updated in any file with relying only on that lock. Some files may be locked, but they're locked for appends so flag updates (and other record updates as well) are safe. It would be interesting to make it work without that sync lock though, so that multiple processes could be syncing dbox at the same time. But there probably isn't much point. If the sync is locked, there's no real requirement to do the syncing at all then, it's just left to be done later. If multiple processes were syncing at the same time, the only problem would come from flag updates. Either the files would have to be locked for flag updates (with waiting locks, bad bad), or it would need to be able to handle the situation when a flag was written just when another process expunged messages from the file and truncated it. That could be done by checking (one way or another) after the flag write if a truncation had happened, and if so do the truncation again. Preventing out of sync disconnects ================================== Reading messages from dbox files requires no locking, so it's possible that while one session is reading a message another session goes and expunges the message by truncating the file. The only way to handle this situation is to disconnect the client. Also even if the message wasn't in the middle of being read, this kind of a out-of-sync could happen if a session hasn't synced itself yet (no NOOP/IDLE/etc. for a while) and tries to begin reading an expunged message. These could be avoided if the expunging process knew that there are other processes that still know about the message, so it could just mark the message as expunged instead of actually doing it. I think this could be done with yet another file that tracks what messages are expunged. The file would contain "dovecot.index.log file sequence + offset" records. Whenever message(s) are expunged, a new seq +offset is written containing the position in the log file for that transaction. All the processes accessing the mailbox would then read lock the file from eof to infinity. The lock is updated whenever mailbox is synced (and being careful not to have race conditions there). So syncing process would then try if it can write lock the file from "last real expunge" log position to end of file. If not, then using some binary search find the position how far it can be locked. If it managed to update the write lock position at least some, the messages up to that far in the transaction log can be expunged safely. One problem with this is that the file needs to be rotated once in a while so that it won't grow infinitely. This can be done only if the write lock can include the whole file (including infinity). And that can be done only if there's a single process having the mailbox open, which may never happen with shared mailboxes. I think I'll leave this feature to be implemented later. It's extra overhead that's probably rarely useful. Single instance attachments =========================== I'll change the dbox messages to have variable sized headers. The header could then contain information such as "at offset 5000 insert 11241242 bytes from file AB123427852". Fast copying ============ Would be nice if copying a message from one mailbox to another wouldn't require actually reading+writing the whole message contents. But I can't really figure out how to implement this without requiring that there is only a single dbox storage which contains the mails for all the mailboxes, and the mailboxes themselves are just Dovecot's index files containing pointers to the dbox storage. The problem with having everything in one storage is that if the index files are broken, the messages can't be placed into correct mailboxes anymore. Although one possibility would be treat mailboxes a bit similarly than keywords. So that when a message is copied to another mailbox, the message in dbox file is updated to contain information that it exists in such and such mailboxes. Hmm. Perhaps that would be good enough, yes.

1 0

[Dovecot] Problems with BEFORE searches.
by Trever L. Adams 12 May '07

12 May '07

Ok, I am trying to modify some code given to me by the author of the dspam plugin for dovecot (sorry the name eludes me). I am modifying it to handle UNSEEN differently than SEEN. Below is the python code. I am not a python programmer, but I get the basic idea. ok, uids = conn.search(None, 'BEFORE', unreadsentbefore, 'SEEN') "11-May-2007 06:18:29 -0600" is the value of unreadsentbefore. However, this doesn't match any emails even though they are all dated as 5/10 and they have all been read for several hours (the time was the current to figure out why it isn't working). Is there a problem with BEFORE and SEEN together? Is there a BEFORE bug in the system? Some of the messages are -500 and others, I am not sure. Thanks, Trever Adams

4 6

[Dovecot] read only maildir subscriptions
by Nagyon Almos 11 May '07

11 May '07

Hello, I have some (possibly very simple) questions about subscriptions: I store my old mails in /home/oldmails/ in one Maildir where I have only read-only permissions (I cannot delete, create or modify any files). Under thunderbird, I can successfully log in and read my new mails, but I cannot subscribe (?) within thunderbird to oldmails (it is grey not black as other folders). What did I do wrong? What other permissions does dovecot need? Here's the relevant part of dovecot.conf: namespace private { separator = / prefix = oldmails/ location = maildir:/home/oldmails/:CONTROL=~/Maildir/control-oldmails:INDEX=~/Maildir/index-oldmails } and when I try to subscribe to it, dovecot says: dovecot: 2007-04-30 17:58:53 Info: IMAP(xxx): Effective uid=7001, gid=1000 dovecot: 2007-04-30 17:58:53 Info: IMAP(xxx): Namespace: type=private, prefix=regi/, sep=/, inbox=no, hidden=no, subscriptions=no dovecot: 2007-04-30 17:58:53 Info: IMAP(xxx): maildir: data=/home/oldmails/:CONTROL=~/Maildir/control-oldmails:INDEX=~/Maildir/index-oldmails dovecot: 2007-04-30 17:58:53 Info: IMAP(xxx): maildir: root=/home/oldmails, index=~/Maildir/index-oldmails, control=~/Maildir/control-oldmails, inbox= Thanks for any help in advance. Regards, A. <br><br>_______________________________________________________________<br> <a href="http://cthandler.adverticum.net/?cturl=http%3A%2F%2Fwww.klikkbank.hu%2Flako… " target="new">INTEZZE PÉNZÜGYEIT AZ INTERNETEN!</a> Lakossági számlacsomag havi 199 Ft-ért! Bankkártya éves kártyadíj nélkül! <a href="http://cthandler.adverticum.net/?cturl=http%3A%2F%2Fwww.klikkbank.hu%2Flako… " target="new">www.klikkbank.hu</a>

2 2

[Dovecot] Dovecot not handling r/o mailboxes completely, and problem with ACL as a workaround
by Adam McDougall 11 May '07

11 May '07

First of all, I think dovecot is really fantastic and I have thanks for all the hard work. I think it will be the best fit for my ~5000 users when I have it setup completely. We normally have approx 500 concurrent IMAP connections during the day. I am trying to convert from courier-imap to dovecot, but I have an issue with public namespace folders that are not writable by certain users. Please let me know if I need to provide more information or how I can help solve this issue. In courier-imap, we were able to take advantage of the maildir structure and standard unix users/groups to allow 'decsstaff' members to have full write access while 'decsall' members only have r/o unless also a member of 'decsstaff': -rw-rw-r-- 1 postlocal decsstaff 37597 May 5 23:37 /egr/mail/shared/decs/.support.In/cur/1178422658.M533373P54269.ice drwxrwxr-x 2 postlocal decsstaff 24576 May 5 23:37 /egr/mail/shared/decs/.support.In/cur drwxrws--- 6 postlocal decsall 4096 Apr 22 18:08 /egr/mail/shared/decs/.support.In drwxrwsr-x 34 postlocal wheel 4096 May 1 07:23 /egr/mail/shared/decs In short, upper directories are used to limit world access to just one group 'decsall', and once inside, r/o world access could be used as an anonymous substitution for 'decsall' and the group permissions would allow writing by 'decsstaff'. I don't know how courier stores and checks mail directory permissions, but it was aware when a user would not be able to delete or change messages and would return a READ-ONLY imap error when an attempt to change a message occurred (courier returns this in the IMAP response to update mail flags to reflect that the client wants to move to delete a mail). I understand that imap clients will usually only set status as read or deleted first and only try to delete an email for real on expunge, but it seems dovecot does not try to detect if a message is modifyable before it is too late for the user to find out. What happens is a user appears to be able to mark messages read, move them to another folder, or delete them (another way of moving to another folder eg. Trash). The user is clueless that the changes will not occur, and only finds out later when they reload the folder to find the messages back, or tries to expunge and get an unhelpful 'internal error' from dovecot (I can help trace this situation if it helps, but I think that stage should not be reached if things were working right). My configuration has the public folder control and indexes inside a user's home directory, so it will always be possible for dovecot to record message status changes, however I do not think dovecot should update the control and indexes to reflect an IMAP operation that is not allowed to complete due to restricted permissions on the actual email file. I suppose dovecot would have to check the permissions on mail message files. As a workaround, I wondered if I could apply dovecot ACLs to the public folders to reinforce my intentions of only allowing readonly access to certain users. If ACLs worked, I could even use it as a viable alternative to the unix permissions on the maildir contents and avoid using more unix groups than necessary. For most of our shared mailboxes, there will only be a few persons with write access, and up to a dozen people with read access, so even if I have to list every user seperately I could. However, I have not been able to get ACLs to do anything useful for me, and I hesitate to use the feature to work around might be a configuration error or bug. It is also more convenient for my migration procedure if I do not have to modify file permissions or structure during downtime to switch to dovecot. I am still not sure how dovecot ACLs affect the actual permissons of dovecot processes. I have mostly tried placing a dovecot-acl file in the maildir directory (alongside cur, tmp, new) and dovecot seems to be reading it according to the log, however I am not getting expected results from the ACLs. If the unix permissions allow a client to enter 'cur' and read mails, the mail client thinks it can delete or move them (until expunge) no matter even if I put acl entries with only 'r' permission. ACL questions (which might help others understand better as well): Is a 'user=foo rl' entry supposed to remove any possible write permissions in a maildir covered by such an ACL for user foo? If not, shouldn't it at least enforce restrictions on the available mail metadata which is more likely to be writable by the user? Is it even possible for an ACL to grant additional permissions above what is granted to a user by standard unix permissions? Does an empty ACL equate to the exact permissions granted by unix, and should an admin try to design an ACL to modify as little as possible, or should the admin try to use enough acl entries to form a complete description of the desired resulting permissions? I get the impression that broad ACLs should be listed first, and more specific ACLS listed below can add or remove ACL permissions applied earlier in the file as a 'last match' case. Should the acl plugin be able to print a summary of the resulting permissions in the log (with mail_debug=yes) when accessing a folder with an ACL? A snip from logs, I generated alot today and I'm not sure which portions would be most useful so I'll start with this: May 6 15:20:08 gribble dovecot: IMAP(mcdouga9): acl: initializing backend with data: vfile:/usr/local/etc/dovecot-acls May 6 15:20:08 gribble dovecot: IMAP(mcdouga9): acl: acl username = mcdouga9 May 6 15:20:08 gribble dovecot: IMAP(mcdouga9): acl: owner username = May 6 15:20:08 gribble dovecot: IMAP(mcdouga9): acl vfile: Global ACL directory: /usr/local/etc/dovecot-acls May 6 15:20:08 gribble dovecot: IMAP(mcdouga9): Namespace: type=public, prefix=#shared/decs/, sep=/, inbox=no, hidden=no, subscriptions=no May 6 15:20:08 gribble dovecot: IMAP(mcdouga9): maildir: data=/egr/mail/shared-dovecot2/decs:CONTROL=/home/mcdouga9/Maildir/dovecot/public/control/decs:INDEX=/home/mcdouga9/Maildir/dovecot/public/indexes/decs May 6 15:20:08 gribble dovecot: IMAP(mcdouga9): maildir: root=/egr/mail/shared-dovecot2/decs, index=/home/mcdouga9/Maildir/dovecot/public/indexes/decs, control=/home/mcdouga9/Maildir/dovecot/public/control/decs, inbox= May 6 15:20:08 gribble dovecot: IMAP(mcdouga9): opendir(/egr/mail/shared-dovecot2/decs/tmp) failed: Permission denied # dovecot --version 1.0.0 The reason I have so many public spaces below, is to match the existing directory structure we setup for courier, and also to help us keep the directory listing more tidy since otherwise we would end up with many folders all under one directory. Some of them have monthly rotation and it could get out of hand if we did not split them up. I understand it makes things more difficult for the global acl list at present, if I were to use it, but I may not have any conflicting folder names at this time. # dovecot -n # /usr/local/etc/dovecot.conf ssl_cert_file: /usr/local/etc/apache2/ssl/mail.egr.msu.edu.pem ssl_key_file: /usr/local/etc/apache2/ssl/mail.egr.msu.edu.pem login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login verbose_proctitle: yes first_valid_uid: 1000 first_valid_gid: 0 mail_location: maildir:~/Maildir:CONTROL=%h/Maildir/dovecot/private/control:INDEX=%h/Maildir/dovecot/private/indexes mail_debug: yes mmap_disable: yes maildir_copy_with_hardlinks: yes mail_plugins: acl mail_log_max_lines_per_sec: 0 imap_client_workarounds: delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep namespace: type: public separator: / prefix: #shared/be/ location: maildir:/egr/mail/shared-dovecot2/be:CONTROL=%h/Maildir/dovecot/public/control/be:INDEX=%h/Maildir/dovecot/public/indexes/be namespace: type: public separator: / prefix: #shared/cee/ location: maildir:/egr/mail/shared-dovecot2/cee:CONTROL=%h/Maildir/dovecot/public/control/cee:INDEX=%h/Maildir/dovecot/public/indexes/cee namespace: type: public separator: / prefix: #shared/chems/ location: maildir:/egr/mail/shared-dovecot2/chems:CONTROL=%h/Maildir/dovecot/public/control/chems:INDEX=%h/Maildir/dovecot/public/indexes/chems namespace: type: public separator: / prefix: #shared/decs/ location: maildir:/egr/mail/shared-dovecot2/decs:CONTROL=%h/Maildir/dovecot/public/control/decs:INDEX=%h/Maildir/dovecot/public/indexes/decs namespace: type: public separator: / prefix: #shared/egr/ location: maildir:/egr/mail/shared-dovecot2/egr:CONTROL=%h/Maildir/dovecot/public/control/egr:INDEX=%h/Maildir/dovecot/public/indexes/egr namespace: type: public separator: / prefix: #shared/me/ location: maildir:/egr/mail/shared-dovecot2/me:CONTROL=%h/Maildir/dovecot/public/control/me:INDEX=%h/Maildir/dovecot/public/indexes/me namespace: type: public separator: / prefix: #shared/org/ location: maildir:/egr/mail/shared-dovecot2/org:CONTROL=%h/Maildir/dovecot/public/control/org:INDEX=%h/Maildir/dovecot/public/indexes/org namespace: type: public separator: / prefix: #shared/toptest/ location: maildir:/egr/mail/shared-dovecot2/toptest:CONTROL=%h/Maildir/dovecot/public/control/toptest:INDEX=%h/Maildir/dovecot/public/indexes/toptest namespace: type: public separator: / prefix: #shared/ugs/ location: maildir:/egr/mail/shared-dovecot2/ugs:CONTROL=%h/Maildir/dovecot/public/control/ugs:INDEX=%h/Maildir/dovecot/public/indexes/ugs namespace: type: public separator: / prefix: #shared/vprgs/ location: maildir:/egr/mail/shared-dovecot2/vprgs:CONTROL=%h/Maildir/dovecot/public/control/vprgs:INDEX=%h/Maildir/dovecot/public/indexes/vprgs namespace: type: private separator: / prefix: mail/ hidden: yes namespace: type: private separator: / location: maildir:~/Maildir:CONTROL=%h/Maildir/dovecot/private/control:INDEX=%h/Maildir/dovecot/private/indexes inbox: yes auth default: mechanisms: plain login passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth user: postfix group: postfix master: plugin: acl: vfile:/usr/local/etc/dovecot-acls Thanks.

6 13