- dovecot - dovecot.org

[Dovecot] SIS for maildir?
by Mike Abbott 03 Sep '10

03 Sep '10

When might deduplication of attachments work with maildir?

2 2

[Dovecot] Best way to migrate from qmail-ldap's autoreply?
by Attila Nagy 03 Sep '10

03 Sep '10

Hi, qmail-ldap uses four LDAP attributes for handling autoreplies in qmail-local: - deliverymode (to see whether the autoreply should be send) - mailreplytext, which is a base64 encoded multiline string* - mailreplystart and mailreplystop, unix dates I'm wondering how this could be handled with Dovecot (2.0) in the most easier way. All I could find out so far: - patching the code - writing a plugin (it it possible to get these LDAP attributes in the LMTPd with a single userdb-lookup and get it from the plugin during a new mail event? Any examples?) - conditionally provide these values to a sieve script and process them accordingly (the base64 string and maybe the dates seem to be hard for the first glimpse) the mad stuff: - using an LD_PRELOAD library, which emulates per user sieve scripts according to LDAP lookups (gives a lot more flexibility) - an LMTP proxy/server, which does all this and forwards the traffic to the Dovecot LMTPd/deliver process * a sample mailreplytext looks like this: '''%HEADER% Content-type: text/plain; charset="utf-8" távol vagyok''' (of course this is in UTF-8).

3 2

[Dovecot] Maybe wrong quota recalculation behaviour on overquota delivery try
by Luca Palazzo 03 Sep '10

03 Sep '10

Hi all, we are experencing some, may be strange, slowness in our dovecot/postfix mail system. We have three dovecot 2.0.1 server with LMTP, POP3 and IMAP enabled. Three shared OCFS2 filesystem are used for mail storage. We have too a load balancer based on dovecot director in front of these three server. Our SMTP cluster receives mail and send by LMTP to load balancer. Everything work flowless, but sometime, under heavy load, three server slow down a lot. Our mail gateway logs a lot of: status=deferred (host 10.194.1.20[10.194.1.20] said: 451 4.4.0 Remote server not answering (DATA output timeout) IP 10.194.1.20 is dovecot director. Looking at mbox servers log nothing seem to happen, but stracing lmtp process we can see stat system calls to all Maildir files, as if dovecot was recalculating quota and regenerating maildirsize file. It happens always when LMTP tries to deliver a mail to an overquota account. Is this possible and right? How can we look deeper in system to have more information? Best regards Luca PS: dovecot configuration for maildir servers is: # 2.0.1: /etc/dovecot/dovecot.conf # OS: Linux 2.6.26-2-686-bigmem i686 Debian 5.0.5 auth_master_user_separator = * auth_verbose = yes disable_plaintext_auth = no mail_location = maildir:~/Maildir mail_plugins = $mail_plugins notify mail_log quota managesieve_notify_capability = mailto managesieve_sieve_capability = comparator-i;octet comparator-i;ascii-casemap fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date spamtest spamtestplus virustest passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid from size quota = maildir:User quota quota_warning = storage=95%% quota-warning.sh 95 %u quota_warning2 = storage=80%% quota-warning.sh 80 %u sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_global_dir = /etc/dovecot/sieve/global/ sieve_global_path = /etc/dovecot/sieve/default.sieve } protocols = imap pop3 lmtp sieve service auth { unix_listener auth-userdb { group = dovecot mode = 0600 user = dovecot } } service director { inet_listener { port = 8100 } } service lmtp { inet_listener lmtp { address = 10.194.1.31 127.0.0.1 ::1 port = 24 } } service managesieve-login { inet_listener sieve { address = 10.194.1.31 127.0.0.1 ::1 port = 4190 } process_min_avail = 0 service_count = 1 } service quota-warning { executable = script /virtual/shared/quota-warning.sh unix_listener quota-warning { user = vmail } user = dovecot } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } verbose_proctitle = yes protocol lmtp { mail_plugins = $mail_plugins quota sieve } protocol lda { mail_plugins = $mail_plugins quota } protocol imap { mail_plugins = $mail_plugins quota imap_quota } protocol pop3 { mail_plugins = $mail_plugins quota }

2 3

[Dovecot] minor director issues
by Cor Bosman 03 Sep '10

03 Sep '10

I noticed 2 minor things with the director. 1) if I start 2 directors, but in 1 of them I dont add the other as a director_servers, they both start spamming the logfiles really really fast. It seems there is no backoff mechanism in the protocol between directors. 2) user mail server ip expire time cor 194.109.26.171 2010-09-02 14:32:13 <unknown> 194.109.26.172 2010-09-02 14:33:13 Why does it say 'unknown'? That session is active, im manually logged in with telnet, issued a login and a select inbox. The first one is a normal mail client login. Regards, Cor

2 6

[Dovecot] safe_memset
by Len7hir 03 Sep '10

03 Sep '10

samples % lib function 4 0.0525 libdovecot.so.0.0.0 sha1_result_libmysqlcli(..) 7 0.0919 libdovecot.so.0.0.0 io_loop_handler_run 36 0.4729 libdovecot.so.0.0.0 imap_parser_reset 227 2.9817 libdovecot.so.0.0.0 pool_alloconly_unref 7339 96.4009 libdovecot.so.0.0.0 pool_alloconly_clear 7710 3.2463 libdovecot.so.0.0.0 safe_memset 7710 100.000 libdovecot.so.0.0.0 safe_memset [self] ------- 1 0.0148 libdovecot.so.0.0.0 i_stream_limit_read 2 0.0296 libdovecot.so.0.0.0 i_stream_header_filt(..) 6 0.0888 libdovecot.so.0.0.0 imap_parser_destroy 8 0.1184 libdovecot.so.0.0.0 settings_parser_deinit 230 3.4039 libdovecot.so.0.0.0 imap_parser_reset 6510 96.3445 libdovecot.so.0.0.0 pool_alloconly_unref 598 0.2518 libdovecot.so.0.0.0 pool_alloconly_clear 7339 89.8286 libdovecot.so.0.0.0 safe_memset 598 7.3195 libdovecot.so.0.0.0 pool_alloconly_clear [self] 232 2.8397 libc-2.3.6.so (no symbols) 1 0.0122 libdovecot.so.0.0.0 body ------- 4 0.0525 libdovecot.so.0.0.0 sha1_result_libmysqlclient_craps_all_over 7 0.0919 libdovecot.so.0.0.0 io_loop_handler_run 36 0.4729 libdovecot.so.0.0.0 imap_parser_reset 227 2.9817 libdovecot.so.0.0.0 pool_alloconly_unref 7339 96.4009 libdovecot.so.0.0.0 pool_alloconly_clear 7710 3.2463 libdovecot.so.0.0.0 safe_memset 7710 100.000 libdovecot.so.0.0.0 safe_memset [self] Mostly safe_memset is called from pool_alloconly_clear. I attach result from oprofile - functions (with call tree) that have more than 2% of all oprofile samples in libdovecot.so. p_strdup is on the list, but it is lower than before last optimisations. As You see there is no other optimised functions :) -- Len7hir

2 1

[Dovecot] apply sieve filter to old mails
by Giovanni Mancuso 03 Sep '10

03 Sep '10

Hi, i install dovecot 2.0.1 with managesieve support in my test machine. If i create a sieve filter and i send the mail to my user thi filter is applied. Is there a way to apply this filter to old mails too? Thanks

1 0

[Dovecot] Suggested location for single-dbox
by William Blunn 03 Sep '10

03 Sep '10

I've updated http://wiki2.dovecot.org/MailLocation regarding a typical mail_location entry for dbox. Previously it said: mail_location = dbox:~/dbox but of course "dbox" is now the old name for "sdbox", so the example should be updated to say "sdbox" and there might/ought also to be an example for "mdbox". In http://wiki2.dovecot.org/MailboxFormat/dbox the example mail_location for mdbox is given as "mdbox:~/mdbox", so I have followed that for "MailLocation". So I have changed it to say # single-dbox mail_location = sdbox:~/dbox or: # multi-dbox mail_location = mdbox:~/mdbox I didn't know whether to change the directory for sdbox to "~/sdbox" or to leave it as it is. For the time being I have left it at "~/dbox" --- following the example given should allow new installations of Dovecot 2 to be able to read any existing single-dbox data which used the historically-suggested "~/dbox" location, whilst at the same time avoiding using the old mailbox format name of "dbox". Bill

2 1

Re: [Dovecot] Some doubts about quota
by Andre 03 Sep '10

03 Sep '10

Il giorno 03/set/2010, alle ore 10.37, Andre ha scritto: > Hi to all, > we are using quota to collect statistics about usage of mailboxes (thanks to the one who implemented :noenforcing) and we are using “maildir” backend, but we are thinking to migrate to *dbox (as soon as “per-user \Seen flag” would be implemented) and we should need a faster way to collect statistics, so I’ve tried to use Postgresql as a backend. I’ve follwed literally instructions from wiki2 (and part from wiki), but quota is not automatically updated as soon as a messages is delivered to user or deleted from mailbox, we need to perform a “doveadm quota recalc -A” to have it updated. Is it the normal behavior of quota plugin or do I missed something? > > TIA > Andrea Mistrali > am(a)am.cx Solved! I’ve had disabled quota plugin in LDA & LMTP. Now it works, sorry to have bothered you all and wasted your bandwidth Andrea Mistrali am(a)am.cx

1 0

[Dovecot] Some doubts about quota
by Andre 03 Sep '10

03 Sep '10

Hi to all, we are using quota to collect statistics about usage of mailboxes (thanks to the one who implemented :noenforcing) and we are using “maildir” backend, but we are thinking to migrate to *dbox (as soon as “per-user \Seen flag” would be implemented) and we should need a faster way to collect statistics, so I’ve tried to use Postgresql as a backend. I’ve follwed literally instructions from wiki2 (and part from wiki), but quota is not automatically updated as soon as a messages is delivered to user or deleted from mailbox, we need to perform a “doveadm quota recalc -A” to have it updated. Is it the normal behavior of quota plugin or do I missed something? TIA Andrea Mistrali am(a)am.cx

1 0

[Dovecot] bogus fts percentage
by Mike Abbott 03 Sep '10

03 Sep '10

Sometimes dovecot-2.0 sends this untagged response to clients: * OK Indexed -2147483648% of the mailbox, ETA 0:00 I imagine there's a bug in there somewhere.

3 3