June 2011 - dovecot - dovecot.org

[Dovecot] [dovecot] Getting duplicates when using snarf plugin with mbox backend
by Jonathan SIegle 09 Feb '12

09 Feb '12

Running dovecot version 2.0.11. To reproduce, open two imap sessions and issue a check command from each at the same time with new mail in the queue. 0 login testuser testpw 1 select inbox -- Deliver mail -- 2 check Thanks, Jonathan

2 1

[Dovecot] compressed mboxes very slow
by kjonca＠o2.pl 29 Jan '12

29 Jan '12

I have some archive mails in gzipped mboxes. I could use them with dovecot 1.x without problems. But recently I have installed dovecot 2.0.12, and they are slow. very slow. Creating index files takes about 10 minutes for ~20M file with 560 messages for bzipped mbox, for gzipped is little better but still unusable :( Stracing dovecot process shows that every ~ 20 messages it rereads complete mbox file. Am I doing something wrong? KJ -- http://modnebzdury.wordpress.com/2009/10/01/niewiarygodny-list-prof-majewsk…

4 13

[Dovecot] Managing public folder ACL files
by Keith Edmunds 14 Nov '11

14 Nov '11

We have a customer with a large public folder hierarchy. They occasionally make requests to have the public folder ACLs changed; for example: "please give user X access to all public folders" (that's nearly 1700 folders). Worse: "please give user Y access to all sales folders" (there are 1450 sales folders). The problem is that there are (naturally) spaces in the folder names, which makes command line manipulation challenging. We've ended up with some astonishingly hacky Python scripts that enter each folder starting with (for example) ".sales" and replacing the dovecot-acl file to try to fulfil the above requests. One day our script are going to get it wrong, or requests will become more complex ("give X access all sales/CustA folders, Y access to all sales/CustB folders, and Z access to all sales folders). There must be a Better Way. How do others manage divergent ACLs within large public folder hierarchies? Thanks, Keith

5 4

[Dovecot] LDAP expired password
by roberto palmarin 10 Nov '11

10 Nov '11

hi all, I'm using postfix, LDAP, dovecot and horde for webmail. user and password information is stored in LDAP. I'm attempting to get password aging working properly and am not having much luck. even if password has expired user can login, can i tell dovecot to control the LDAP field shadowexpired? or is there some other way to check properly that the password is expired before allowing the user log in? thank's /roby

4 5

[Dovecot] dovecot evaluation on a 30 gb mailbox
by Rajesh M 04 Nov '11

04 Nov '11

hi all i use qmail toaster. i recently changed over to dovecot. posting below my evaluation on the same my machine dual core dual xeon 5140 processor, with 4 gb ram, centos linux with qmailtoaster i had setup a qmail tap account which backups up data for a client of mine mailbox size over 30 gb setup dovecot with squirrelmail and logged in it had over one hundred and thirty nine thousand emails 139019 emails in the 30 gb mailbox Reports 1) first login : took 7 minutes to parse 139019 mails but never timed out. this was simply impossible with courier 2) the next login it took 5 seconds by which time the mail numbers increased to 139045 3) next i changed squirrelmail display preference to list 500 mails per page and then clicked on inbox ... expecting dovecot to take atleast around 1-2 mins to show the mails ... the mails were displayed in just 8 seconds .. awesome performance qmailtoaster is simply waiting for a dovecot integration i am evaluating the stability of dovecot now in the next 2-3 weeks i post stability report rajesh

19 43

[Dovecot] sieve vacation reply
by Wojciech Giel 04 Oct '11

04 Oct '11

Hi, I'm configuring postfix with dovecot and roundcube. I'm using flat files as passwdb userdb. Everything works fine except sieve vacation reply. when i send mail from ex. user dennis to tytus I get "discarding vacation response for message implicitly delivered to". What Am i doing wrong? thanks sieve: using sieve path for user's script: /home/tytus/.dovecot.sieve 2011-05-17 16:56:45 deliver(tytus): Info: sieve: opening script /home/tytus/.dovecot.sieve 2011-05-17 16:56:45 deliver(tytus): Info: sieve: executing compiled script /home/tytus/.dovecot.sieve 2011-05-17 16:56:45 deliver(tytus): Info: sieve: msgid=<20110517155641.GA3452(a)badger.example.com>: discarding vacation response for message implicitly delivered to <tytus@badger> /etc/postfix/main.cf ... mailbox_command = /usr/lib/dovecot/deliver -n -m "${EXTENSION}" ... # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.1 log_path: /var/log/dovecot.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps managesieve listen(default): * listen(imap): * listen(managesieve): 127.0.0.1:2000 ssl_ca_file: /etc/postfix/ssl/cacert.pem ssl_cert_file: /etc/postfix/ssl/servercrt.pem ssl_key_file: /etc/postfix/ssl/serverkey.pem ssl_cipher_list: ALL:!LOW:!SSLv2 login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login mail_location: maildir:~/Maildir:INDEX=~/Maildir/indexes mail_debug: yes mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugins(default): quota imap_quota autocreate mail_plugins(imap): quota imap_quota autocreate mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve imap_client_workarounds(default): tb-extra-mailbox-sep netscape-eoh delay-newmail outlook-idle imap_client_workarounds(imap): tb-extra-mailbox-sep netscape-eoh delay-newmail outlook-idle imap_client_workarounds(managesieve): lda: postmaster_address: postmaster mail_plugins: sieve quota autocreate quota_full_tempfail: yes deliver_log_format: msgid=%m: %$ rejection_reason: Your message to <%t> was automatically rejected:%n%r log_path: /var/log/sieve.log auth default: mechanisms: plain login cram-md5 verbose: yes debug: yes debug_passwords: yes passdb: driver: pam passdb: driver: passwd-file args: scheme=cram-md5 /etc/dovecot/passwd userdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/dovecot-auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 plugin: sieve: ~/.dovecot.sieve sieve_dir: ~/sieve autocreate: INBOX autocreate2: Sent autocreate3: Trash autocreate4: Drafts autocreate5: Junk autosubscribe: INBOX autosubscribe2: Sent autosubscribe3: Trash autosubscribe4: Drafts autosubscribe5: Junk quota: maildir:User quota quota_rule: Trash:storage=10M quota_warning: storage=85%% /usr/bin/dovecot-quota-warning.sh 85 quota_warning2: storage=90%% /usr/bin/dovecot-quota-warning.sh 90 quota_warning3: storage=95%% /usr/bin/dovecot-quota-warning.sh 95

5 7

[Dovecot] Dovecot 1.2, problem with SQL quota and mail aliases
by Jacek Osiecki 22 Sep '11

22 Sep '11

Hello, I have a small server running dovecot 1.2 (still not balsy enough to switch to 2.0 - virtual sql accounts, managesieve etc.). There are no local users - only ones defined in the SQL database, and everything else (including quota) is defined in SQL db too. Dovecot is used as IMAP daemon, and dovecot-lda is responsible for delivery (in order to make use of sieve and managesieve). I know that my configuration might be a bit ancient, but this is not referring to any bug (at least I think so) and rather to errors I've made in configuration. Several users have reported, that they are running out of quota even though their mailboxes are empty. I thought these were some single cases, but recently I discovered that this situation occurs when: - user john(a)domain.com has a mail alias, eg. john.smith(a)domain.com - he logs in to the imap account (using MUA or webmail) using his alias (john.smith(a)domain.com) In effect, all incoming emails for john(a)domain.com are increasing the counters (both "bytes" and "messages"), but since user logs in using john.smith(a)domain.com - anything he deletes from the mailbox decreases the records for john.smith(a)domain.com. Finally, John has two records: +---------------------------+-----------+----------+ | username | bytes | messages | +---------------------------+-----------+----------+ | john.smith(a)domain.com | -5488133 | -13 | | john(a)domain.com | 341411029 | 1111 | +---------------------------+-----------+----------+ The record for john(a)domain.com finaly reaches the quota limit - and even removing all emails does not help. My /etc/dovecot/dovecot-dict-quota.conf looks like this: map { pattern = priv/quota/storage table = quota username_field = username value_field = bytes } map { pattern = priv/quota/messages table = quota username_field = username value_field = messages } And my question is: what is used as "username"? Always the username given wher user logs in? Is there a way to provide some dictionary to translate all aliases to the real username? Best regards, -- Jacek Osiecki joshua(a)ceti.pl GG:3828944 I don't want something I need. I want something I want.

3 4

[Dovecot] [PATCH] Indexing mail attachments with Dovecot + Solr
by Antonio Perez-Aranda 31 Aug '11

31 Aug '11

Indexing mail attachments with Dovecot + Solr. This patch has been tested with these versions: * dovecot 2.0.9 * apache-solr 1.4.1 This is a patch for the fts-solr plugin (that indexes mail messages for Dovecot with Solr). In main stream, the plugin does not index attachments; With this patch, you can index mails and their attachments (pdf, docs, openoffice docs...) . You can get others goodies with this patch and the Solr Config provided, like Synonyms and Stemming (Spanish by default). Attachment indexing is provided by Solr Cell and Tika (ExtractingRequestHandler) * http://wiki.apache.org/solr/ExtractingRequestHandler Synonyms and Stemming are provided by SnowballPorterFilterFactory from Solr Language Analysis: * http://wiki.apache.org/solr/LanguageAnalysis We have tested Solr with Tomcat and Jetty. Tomcat is better to handle UTF-8 and bigger POSTS. Attachments file format supported * http://tika.apache.org/0.9/formats.html At present, attachments in attachments (like, for example, attachments in fordwarded "eml" attachments) are not indexed. Also, keep in mind that there are many types of files, and many variants of the same file type. Per Example, some pdf files are "not readable" by solr pdf reader. Config: There are two new options added to fts_solr property: * index-attachments Enable attachments indexing. * manual-update Avoid index on user search. You can trigger indexing using doveadm search or doveadm index commands. There is a new property for the section plugin to filter the mimetypes that you want to index. * fts_solr_mimetype files with this mimetype will be sent to solr. After integrating solr directory in your solr config, and building Dovecot with fts-solr support and with fts-solr-attachments-r885.patch applied, you can update your dovecot config by adding to your dovecot.conf: ... mail_pluings = $mail_plugins fts fts_solr plugin { fts = solr fts_solr = url=http://solrhost:8983/solr/ break-imap-search index-attachments fts_solr_mimetype = application/x-pdf application/vnd.openxmlformats-officedocument.wordprocessingml.document } ... -- Antonio Pérez-Aranda Alcaide aperezaranda(a)yaco.es Yaco Sistemas S.L. http://www.yaco.es/ C/ Rioja 5, 41001 Sevilla Teléfono +34 954 50 00 57 Fax +34 954 50 09 29

3 5

[Dovecot] segfault in dovecot 2.0.9
by Morten P.D. Stevens 18 Aug '11

18 Aug '11

Hi folks, I noticed the following in the dovecot log files: /var/log/maillog Jun 9 00:12:34 mail dovecot: master: Error: service(imap): child 8970 killed with signal 11 (core dumps disabled) Jun 9 00:12:34 mail dovecot: imap-login: Login: user=<username>, method=PLAIN, rip=IP, lip=IP, mpid=8987, TLS Jun 9 00:12:34 mail dovecot: master: Error: service(imap): child 8987 killed with signal 11 (core dumps disabled) /var/log/messages Jun 9 00:12:34 mail kernel: imap[8970]: segfault at 0 ip 00007fe4b2fe432d sp 00007fff29383740 error 4 in libdovecot-storage.so.0.0.0[7fe4b2fb8000+d1000] Jun 9 00:12:34 mail kernel: imap[8987]: segfault at 0 ip 00007f949de1532d sp 00007fff120721b0 error 4 in libdovecot-storage.so.0.0.0[7f949dde9000+d1000] # dovecot -n # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-71.29.1.el6.x86_64 OS: Scientific Linux 6.0 (Red Hat Enterprise Linux 6.0) Filesystem: ext4 I think this is a bug. Any ideas? Best regards, Morten

3 2

[Dovecot] director monitoring?
by Kelsey Cummings 05 Aug '11

05 Aug '11

I'm working the kinks of a new director based setup for the eventual migration away from courier. At this point, with everything basically working I'm trying to ensure that things are properly monitored and I've run into an issue. There doesn't appear to be a way to get dovecot to tell if it is (or is not) connected and properly synced with the other director servers in the ring apart from the logs. It seems like this is an important piece of information -- without it, it isn't apparent how you would be able to tell if your director servers have lost track of each other. I'm also curious what people are doing to health check their director servers when they are running load balancing upstream of them as well. It doesn't seem like it is a good idea to let the load balancers check all the way through to the real servers since a failure on the target real server could end up leading to a director being dropped from the pool (if so, it is most likely that the other directors would be dropped as well.) Otherwise, the health check failure tolerance at the load balancer must be greater than the tolerance for failure of the real servers on the director- a dead director could end up in the pool for longer than desired, or anyway, long enough to be sure that it isn't a transient failure on the real server behind it. A better method would seem to be for the load balancers to query the director for the number of active back-end servers and, so long as it was over a given threshold, to assume that the director is otherwise able to do its job and rely on external monitoring to pickup internal failures where dovecot isn't able to successfully proxy the connection to one of the real servers. So, how are people doing this in the real world? -- Kelsey Cummings - kgc(a)corp.sonic.net sonic.net, inc. System Architect 2260 Apollo Way 707.522.1000 Santa Rosa, CA 95407

3 5