- dovecot - dovecot.org

[Dovecot] maildir question
by Tim Bates 22 Aug '07

22 Aug '07

If I copy message files (from a command prompt) will dovecot get upset or confused? Do I need to delete index files or anything like that? I ask because I need to restore some messages from a backup, but not restore the entire maildir. I tried some the other day as a test, but the user is saying that they didn't appear. TB ********************************************************************** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. **********************************************************************

3 3

[Dovecot] Subscriptions - delivering to different folders
by bichumo 21 Aug '07

21 Aug '07

Hi, I am using Postfix and Dovecot. I have set up backup_mailbox(a)domain.tld, which gets mail copies from user1(a)domain.tld user2(a)domain.tld user3(a)domain.tld, the copy option is set in postfix recipient_bcc_maps = path_to_file_recipient_bcc. In recipient_bcc file I have: user1(a)domain.tld backup_mailbox(a)domain.tld user2(a)domain.tld backup_mailbox(a)domain.tld user3(a)domain.tld backup_mailbox(a)domain.tld Postfix does the job and copies user1, user2, user3 emails to backup_mailbox. But I also want to filter mails in backup_mailbox and to put user1 mails to USER1 folder in backup_mailbox, user2 mails to USER2 folder in backup_mailbox and so on. How this is possible? I made an entry in subscriptions file of user1, user2, user3. Now I have folders .user1, .user2, user3 in backup_mailbox folder and I can also see these folders through webmail client (squirrelmail), but how do I put email copy which comes from user1(a)domain.tld to backup_mailbox(a)domain.tld to go not to main folder of backup_mailbox but to USER1 folder in backup_mailbox folder. Thanks for any suggestions.

2 1

[Dovecot] userdb override?
by Leroy van Logchem 21 Aug '07

21 Aug '07

Hi, I used to change the mailbox root for some users using a custom userdb file which contains lines like: doe::20000:200::/u/doe::userdb_mail=mbox:/u/doe/Mail:INBOX=/var/mail/%u The logfiles shows the mail location stays default ( rc15 worked ): --- dovecot: Aug 21 09:43:49 Info: auth(default): master out: USER 250 doe system_user=doe uid=20324 gid=200 home=/u/doe dovecot: Aug 21 09:43:49 Info: imap-login: Login: user=<doe> dovecot: Aug 21 09:43:49 Info: IMAP(doe): Effective uid=20000, gid=200, home=/u/doe dovecot: Aug 21 09:43:49 Info: IMAP(doe): mbox: data=/u/doe/:INBOX=/var/mail/doe dovecot: Aug 21 09:43:49 Info: IMAP(doe): mbox: root=/u/doe, index=/u/doe, inbox=/var/mail/doe --- Configuration: # 1.0.3: etc/dovecot.conf mail_location: mbox:~/:INBOX=/var/mail/%u auth default: mechanisms: plain login digest-md5 cram-md5 ntlm verbose: yes debug: yes passdb: driver: passwd-file args: /etc/userdb_extra passdb: driver: pam userdb: driver: passwd args: /etc/userdb_extra userdb: driver: passwd-file args: /etc/userdb_extra -- Leroy

2 2

Re: [Dovecot] imap memory footprint rather large
by Timo Sirainen 21 Aug '07

21 Aug '07

[back to list] On Tue, 2007-08-14 at 14:50 +0300, Timo Sirainen wrote: > On Tue, 2007-08-14 at 13:47 +0200, martin f krafft wrote: > > also sprach Timo Sirainen <tss(a)iki.fi> [2007.08.14.1250 +0200]: > > > mmap()ing a 200MB file doesn't mean that it immediately uses 200MB > > > of memory. It just reserves that much virtual space. Even if it > > > happens to read the whole 200MB, it shouldn't be much different > > > from simply reading the file in small parts, in which case kernel > > > places the same 200MB to page cache. > > > > I am aware of that. I just wonder why dovecot has to read the entire > > file into memory, via read() or mmap(). > > It doesn't. It mmaps it entirely so it doesn't waste CPU mmaping and > unmapping parts of it. It's then accessed only when and where needed. It probably does access the whole file though. This is because all the cached data for messages are stored next to each others. So now that your client fetches only INTERNALDATE it doesn't really need to read much, but because mmaped pages are read 4kB at a time, it practically reads the whole file. Perhaps this could use some work in future too, so that fields that are accessed together are stored in cache file close together. But then if multiple clients are used, there can be conflicting access patterns, and what's good for one client would be bad for another. Data could also be duplicated to reduce disk reads for different access patterns, but that comes at the cost of disk space..

4 4

[Dovecot] Dovecot fails almost every 20 minutes exactly
by Patrick - South Valley Internet 21 Aug '07

21 Aug '07

Hi all, We just set up our new mail servers using Postfix and Dovecot. We have implemented a load balanced solution to where our two mail servers have a common NFS share. Everything is working great. Everything but Dovecot for the most part. In testing, Dovecot was great. Now that we're in the production environment, we've noticed that every 20 minutes, Dovecot will stop running. But it gets even weirder - it appears that Machine A will stop, then 20 mins later after we issue a 'service dovecot restart', Machine B will stop. Then the whole process starts over when we restart Dovecot on Machine B. I can't see anything out of the ordinary in the log files either. I'm at a loss as to what's going on. Here's my dovecot -n: ################################ # 1.0.3: /etc/dovecot.conf listen: * ssl_cert_file: /usr/share/ssl/hermes.garlic.com/hermes.garlic.com.cert.pem ssl_key_file: /usr/share/ssl/hermes.garlic.com/hermes.garlic.com.privatekey.pem 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 first_valid_uid: 200 mail_location: maildir:/home/%u/Maildir:INDEX=MEMORY 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_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 auth default: user: dovecot-auth username_format: %Lu passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix ################################ Any ideas what could be wrong? I don't think that setting up a cron to restart both dovecot servers is an idea solution - I'm hoping this is an easy fix. Thanks in advance. Patrick

2 2

[Dovecot] Dovecot IDLE bandwidth usage
by Fredrik Tolf 20 Aug '07

20 Aug '07

Hi list, I just recently discovered the IMAP IDLE command and tried it out with my Dovecot server. It seems to work fine and all, but it seems to be using quite a deal of bandwidth, because of the "* OK Still here" messages sent by the server at two minute intervals. I would argue that is a bit of a problem when using the IDLE command for "Push mail" on a mobile phone. I don't know exactly what parts of the packets that mobile carriers collect payment for, but the Ethernet bandwidth consumed by one such message is 149 bytes (83 bytes for the message itself, and 66 bytes for the TCP ACK from the client). At two minute intervals, that becomes over 100 KB per day, and over 3 MB per month. At GRPS rates typical here in Sweden, that becomes about 5-7 USD per month. That might not seem tremendously much, but seeing how it is what takes up the vast majority of the IMAP bandwidth, it is still quite annoying. Are those messages really necessary? I mean, Dovecot still times out after half an hour if the client doesn't "finish" the IDLE command and re-issues it, right? (Coincidentally, I would like to argue that it would be better not to time out at all during an IDLE command and just turn on TCP keepalives instead, but that is the minor issue here) I'll apologize in advance if this is already a tunable option, but I haven't found anything about it in the configuration file. Cheers, Fredrik Tolf

5 5

[Dovecot] MANAGESIEVE patch v6 for dovecot 1.0.3
by Stephan Bosch 18 Aug '07

18 Aug '07

Hello dovecot users, I have updated the MANAGESIEVE patch to (hopefully) fix the compilation issues reported by Robin Breathe. This is a patch against the latest stable release 1.0.3. It currently won't compile with 1.1 due to significant changes in the master code. Change Log V6 ------------- - Corked the client output stream while producing the capability greeting and on other some other occasions as well. Some naive client implementations expect to receive this as a single tcp frame and it is a good practice to do so anyway. Using this change the Thunderbird sieve extension (v0.1.1) seemed to work. However, scripts larger than a tcp frame still caused failures. All these issues are fixed in the latest version of the sieve add-on (currently v0.1.4). - Cleaned up the new proxy source. My editor made the indentation a complete mess in terms of TABs vs spaces. - Added TRYLATER response codes to BYE and NO messages where appropriate. - Recopied the libsieve library into this patch to incorporate any changes that were made (only sieve-cmu.c still needs to be compared to the old cmu-sieve.c). This also solves the __attribute__((unused)) GCC dependencies. These were fixed long ago by Timo.... the code duplication beast strikes again. (Will have to do this again for dovecot 1.1) - Removed spurious return value from void function in src/lib-sieve/sieve-implementation.c as reported by Robin Breathe. GCC fails to report these issues. The function involved is currently not used and serves only as an example on how dovecot could support multiple sieve back-ends... This patch still includes (yet another) instance of the CMU Sieve source, as explained in one of my previous e-mails (http://dovecot.org/list/dovecot/2006-July/015016.html) The patch can be downloaded at: http://sinas.rename-it.nl/~sirius/dovecot-1.0.3-MANAGESIEVE-v6.diff.gz The README.managesieve is located in the root of the dovecot source tree after applying the patch. Have fun testing the patch. Don't hesitate to notify me when there are problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl IRC: Freenode, #dovecot, S[r]us

3 5

[Dovecot] Migrating from imapd to dovecot - how to keep user's Mail folders
by Patrick - South Valley Internet 17 Aug '07

17 Aug '07

Hi all, We're migrating off our current mail server with runs postfix and imapd on an AIX machine to Postfix and Dovecot running linux. Our customers have a lot of IMAP folders with folders they configured, which are currently located in their /home directory on the current mail server. The new mail server will have them at the same location. How do I configure Dovecot so that when a customer connects via IMAP using their favorite e-mail client, that the folders will be there? Thanks in advance. Patrick

1 0

[Dovecot] Dovecot 1.0.3: LDA + quota plugin
by Przemek Grądzki 17 Aug '07

17 Aug '07

I have problem with quota limit settings for "deliver" - global plugin settings overrides userdb quota setting !!! imap and pop3 works fine. Quota limit for user is set to "quota=maildir:ignore=Kosz:storage=512". And "maildirsize" file in user's mail_location contains "524288S" line - good. But when I set: ---------------- plugin { quota = maildir:ignore=Kosz:storage=102400 } ---------------- in "/etc/dovecot.conf", quota limit is set to "104857600S" in "maildirsize" file - BAD. Local delivery is configured as in http://wiki.dovecot.org/LDA, quota plugin is set in /etc/dovecot.conf: ---------------- protocol lda { ...... mail_plugins = cmusieve quota #mail_plugin_dir = /usr/lib/dovecot/lda ..... } ---------------- Per-user quota is configured like this (from LDAP): ---------------- user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid,mailQuotaSize=quota=maildir:ignore=Kosz:storage pass_attrs = uid=user,userPassword=password,homeDirectory=userdb_home,uidNumber=userdb_uid,gidNumber=userdb_gid,mailQuotaSize =userdb_quota=maildir:ignore=Kosz:storage ---------------- "mailQuotaSize" attribute contains quota limit in kilobytes. /etc/dovecot.conf: ---------------------------- # 1.0.3: /etc/dovecot.conf log_path: /dev/stderr protocols: imap imaps pop3s managesieve 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_executable(managesieve): /usr/libexec/dovecot/managesieve-login first_valid_uid: 8 first_valid_gid: 12 mail_location: maildir:%h/Maildir mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_executable(managesieve): /usr/libexec/dovecot/managesieve mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 mail_plugin_dir(managesieve): /usr/lib/dovecot/managesieve pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh pop3_client_workarounds(managesieve): auth default: mechanisms: plain login gssapi passdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: prefetch userdb: driver: ldap args: /etc/dovecot-ldap.conf socket: type: listen master: path: /var/run/dovecot/auth-master mode: 438 plugin: quota: maildir:ignore=Kosz:storage=102400 ----------------- PS. Sorry for my english.

1 0

[Dovecot] High CPU utilization on Solaris 10
by Jon Alessandrello 17 Aug '07

17 Aug '07

I've read similar post about such an issue, but have not seen any posted solutions. I have a clean install of Solaris 10 running a Sunfire v440 w/postfix. I am using dovecote solely for SMTP authentication, and it is working just fine except while running top I constantly see: 548 root 1 30 0 5240K 3416K run 522:51 49.45% dovecot-auth The process never crashes, nor are there any errors. I ran a test devel box with an almost identical setup of postfix and dovecot on Solaris 9 (V240) and the functionality is identical, but with no high CPU usage. The following are my configs and system info: dovecot --version 1.0.3 OS Solaris 10 Sparc (Patched) No NFS all local ufs dovecot -n # 1.0.3: /usr/local/etc/dovecot.conf log_path: /var/log/dovecot protocols: none ssl_disable: yes login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login auth default: mechanisms: plain login passdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf userdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf socket: type: listen client: path: /opt/pmx/postfix/var/private/auth mode: 432 user: postfix group: postfix cat dovecot-ldap.conf: hosts = localhost dn = cn=priv-account,ou=container,dc=example,dc=com dnpass = mydnpasswd ldap_version = 3 base = ou=people,dc=example,dc=com scope = subtree pass_attrs = uid=user,userPassword=password pass_filter = (&(objectClass=posixAccount)(uid=%u)) default_pass_scheme = CRYPT Any help would be great!! -Jon

5 6