- dovecot - dovecot.org

Re: [Dovecot] Todays Performance Data for 2.0.x
by Timo Sirainen 09 Nov '10

09 Nov '10

Dividing the imap processes's system CPU usage by number of imap processes: imap : 0.478872 of 975 imap : 0.460797 of 1242 imap : 0.409641 of 2482 imap : 0.424035 of 4711 imap : 0.488494 of 6148 imap : 0.56809 of 7031 imap : 0.734864 of 6965 So it's about 0.5 seconds of system CPU per imap login. I also get something like 0.3 seconds of system CPU per imap login on my system. Also setting: service imap { service_count = 0 } (i.e. reuse imap processes) reduced the system CPU usage to almost nothing. But if you use different UIDs for different users you can't do that. So, yeah, looks like the process initialization is wasting time somewhere. I'll look further into it.

2 3

[Dovecot] Can't expand ~ for mail root dir
by Leo Baltus 09 Nov '10

09 Nov '10

Hi, I am not an this list, I hope it gets through: We just moved from dovecot-1.2.12 to dovecot-2.0.6. One of our users wants his mail directly in his homedir which worked fine so far but with 2.0.6: Nov 09 15:19:25 imap(foo.bar(a)example.com): Error: user foo.bar(a)example.com: Initialization failed: Initializing mail storage from mail_location setting failed: No home directory for system user. Can't expand ~ for mail root dir in: ~:INBOX=/e/ml/tech1/home/foo from dovecot.conf: userdb { args = /some/path/to/passwd driver = passwd-file } passwd: foo.bar@example.com::1019:1019:Foo Bar:/e/ml/tech1/home/foo::userdb_mail=maildir:~:INBOX=/e/ml/tech1/home/foo We've changed that for now: foo.bar@example.com::1019:1019:Foo Bar:/e/ml/tech1/home/foo::userdb_mail=maildir:/e/ml/tech1/home/foo:INBOX=/e/ml/tech1/home/foo ~/mail did work but was not desired by the user: foo.bar@example.com::1019:1019:Foo Bar:/e/ml/tech1/home/foo::userdb_mail=maildir:~/mail:INBOX=/e/ml/tech1/home/foo ~/ didn't work either: foo.bar@example.com::1019:1019:Foo Bar:/e/ml/tech1/home/foo::userdb_mail=maildir:~/:INBOX=/e/ml/tech1/home/foo -- Leo Baltus, internetbeheerder /\ NPO ICT Internet Services /NPO/\ Sumatralaan 45, 1217 GP Hilversum, Filmcentrum, west \ /\/ beheer(a)omroep.nl, 035-6773555 \/

2 1

[Dovecot] mdbox & trash
by Daniel L. Miller 09 Nov '10

09 Nov '10

Is there a way I can setup "trash" folders to be stored in a different subdirectory using mdbox? The goal is to provide a way to identify the trash folders for my backup solution (rsync) and avoid copying trash. -- Daniel

2 1

[Dovecot] how can I use different LDAP config for LDA and AUTH?
by Zhou, Yan 09 Nov '10

09 Nov '10

Hi there, I am setting up mail client with DoveCot and, at the same time, use Postfix to deliver message to DoveCot via LDA. I want to support having user name "jsmith" on my mail client, and that gets all messages for email address: dovecotdemo@domain. (The user name is different from what is in the email address). In addition, all user & password look up is handled by LDAP. Here is my problem: 1. my mail client will login as "jsmith", that goes through LDAP to find mail/home/password for this user. (this matches user name) 2. When postfix delivers a message, DoveCot LDA will find a match with email address "dovecotdemo@domain", it goes through the same LDAP configuration. (this matches email address). You can see the two search criteria are different, but by default they use the same passdb and userdb configuration. I want to use a different LDAP config. file for LDA to use, where it will match the email address (so that it is different from the default dovecot-ldap.conf, which is used by authentication). DoveCot Deliver can specify a separate configuration file with "-c", so I tried that. But I cannot get LDA to use a different configuration. Would should be an example of config file used by Deliver? Anyone running into this problem? Thanks, Yan NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. This message has been content scanned by the Axway MailGate. MailGate uses policy enforcement to scan for known viruses, spam, undesirable content and malicious code. For more information on Axway products please visit www.axway.com.

2 1

[Dovecot] dovecot sieve plugin
by maximatt 09 Nov '10

09 Nov '10

hi... ¿exist some way to extract message body contect to a variable with dovecot sieve plugin? ¿:(? it's needed to do something like these: if address :matches ["From"] ["*"] { set "sender" "${0}"; <extract body content> # i try using something like "if body :raw :contains ["*"]" and use ${1} but i cant make work. set :encodeurl "body" "something more <body content>"; notify :message "Test msg from ${sender}" "mailto:someone@domain.com ?body=${body}"; } thanks in advance! ;) PD: sorry if these message could be off toppic. :( -- *Salu2 ;)*

2 2

[Dovecot] 2.0, hourly performance stats
by Ralf Hildebrandt 08 Nov '10

08 Nov '10

I'm getting constantly high numbers of page reclaims & involuntary context switches for dovecot/auth. page reclaims = minor faults = cpu switching back to system-mode, But why is the auth process doing that so excessively? Same for the large number of involuntary context switches... Attached is my "dovecot -n" output. Date: Sun, 07 Nov 2010 20:40:34 +0100 type real user sys reclaim faults swaps bin bout signals volcs involcs auth 205.93 1.32 2.76 25280 0 0 0 0 0 261 1425 ssl-params 288.71 0.40 0.48 468 0 0 8 0 0 8 1 pop3 0.59 0.80 0.20 651 0 0 48 16 0 12 13 managesieve 0.51 0.00 0.28 576 0 0 416 0 0 13 7 imap 4677.82 0.19 0.89 1480 0 0 488 16 0 23550 136 pop3-login 181.77 0.32 0.28 780 0 0 8 0 0 46 9 Date: Sun, 07 Nov 2010 21:00:02 +0100 type real user sys reclaim faults swaps bin bout signals volcs involcs auth 303.62 1.10 2.20 26208 0 0 0 0 0 235 1362 ssl-params 301.12 0.00 0.12 467 0 0 8 0 0 7 1 pop3 0.26 0.40 0.36 618 0 0 0 8 0 5 18 managesieve 0.53 0.00 0.28 576 0 0 352 0 0 13 7 imap 2856.91 0.12 0.46 655 0 0 0 0 0 13465 105 pop3-login 228.84 0.76 0.24 779 0 0 0 0 0 90 14 Date: Sun, 07 Nov 2010 22:00:02 +0100 type real user sys reclaim faults swaps bin bout signals volcs involcs auth 243.12 0.99 4.56 23762 0 0 0 0 0 222 1419 ssl-params 301.25 0.40 0.80 471 0 0 8 0 0 6 4 pop3 0.43 0.40 0.80 623 0 0 0 8 0 6 4 managesieve 0.43 0.00 0.20 577 0 0 536 0 0 14 7 imap 3.63 0.16 0.36 669 1 0 856 0 0 63 93 pop3-login 181.81 0.60 0.40 782 0 0 0 0 0 52 53 Date: Sun, 07 Nov 2010 23:00:02 +0100 type real user sys reclaim faults swaps bin bout signals volcs involcs auth 232.83 1.72 2.26 25613 0 0 0 0 0 254 1175 ssl-params 149.63 0.00 0.16 469 0 0 40 0 0 10 1 pop3 25.68 0.28 0.12 741 0 0 9696 16 0 109 14 managesieve 0.25 0.40 0.28 576 0 0 8 0 0 11 2 imap 0.32 0.00 0.16 625 0 0 0 0 0 11 11 pop3-login 69.88 0.48 0.24 779 0 0 0 0 0 27 6 Date: Mon, 08 Nov 2010 00:00:02 +0100 type real user sys reclaim faults swaps bin bout signals volcs involcs managesieve 0.29 0.00 0.36 576 0 0 8 0 0 7 16 imap 0.58 0.80 0.36 637 0 0 0 0 0 10 9 Date: Mon, 08 Nov 2010 01:00:01 +0100 type real user sys reclaim faults swaps bin bout signals volcs involcs auth 421.98 1.32 1.66 24216 0 0 0 0 0 267 723 ssl-params 538.47 0.00 0.16 470 0 0 8 0 0 7 1 pop3 0.19 0.80 0.96 671 1 0 760 8 0 22 221 managesieve 0.63 0.40 0.13 578 0 0 192 0 0 9 11 managesieve-lo 18616.9 86.77 32.49 319768 1 0 168 0 0 63448 48838 imap 42.28 0.00 0.52 676 0 0 0 0 0 182 63 pop3-login 361.68 0.76 0.40 780 0 0 0 0 0 52 2 Date: Mon, 08 Nov 2010 02:00:02 +0100 type real user sys reclaim faults swaps bin bout signals volcs involcs auth 592.76 0.97 1.40 23640 8 0 8272 0 0 307 321 ssl-params 676.93 0.00 0.24 468 0 0 136 0 0 18 10 pop3 6.10 0.24 0.44 672 1 0 1688 8 0 35 40 managesieve 0.71 0.12 0.14 572 5 0 1632 0 0 17 38 managesieve-lo 1023.50 1.45 0.46 6066 1 0 184 0 0 1104 317 imap 0.87 0.80 0.44 674 1 0 640 0 0 18 25 pop3-login 361.79 0.72 0.32 780 0 0 112 0 0 56 11 Date: Mon, 08 Nov 2010 03:00:02 +0100 type real user sys reclaim faults swaps bin bout signals volcs involcs auth 600.71 0.96 1.18 22902 0 0 56 0 0 235 212 ssl-params 242.66 0.00 0.16 471 0 0 136 0 0 15 6 pop3 0.20 0.16 0.28 675 1 0 1312 8 0 32 15 managesieve 0.46 0.00 0.36 580 1 0 480 0 0 11 12 managesieve-lo 286.21 0.60 0.44 1048 1 0 184 0 0 50 88 imap 0.34 0.80 0.28 675 0 0 0 0 0 9 20 pop3-login 361.43 0.84 0.32 780 0 0 112 0 0 55 13 Date: Mon, 08 Nov 2010 04:00:01 +0100 type real user sys reclaim faults swaps bin bout signals volcs involcs auth 587.34 0.90 1.52 22075 14 0 14288 0 0 443 375 ssl-params 275.27 0.00 0.12 469 0 0 136 0 0 14 15 pop3 23.90 0.37 0.80 2906 5 0 36856 24 0 3885 136 managesieve 0.45 0.12 0.16 577 1 0 472 0 0 10 20 managesieve-lo 357.38 0.14 0.52 1271 1 0 184 0 0 100 28 imap 0.42 0.00 0.40 671 0 0 0 0 0 9 56 pop3-login 363.16 0.12 0.64 782 0 0 112 0 0 263 23 Date: Mon, 08 Nov 2010 05:00:01 +0100 type real user sys reclaim faults swaps bin bout signals volcs involcs auth 1005.53 0.91 1.60 21583 0 0 0 0 0 238 92 ssl-params 172.31 0.40 0.80 469 0 0 0 0 0 6 3 pop3 0.11 0.16 0.28 667 0 0 0 8 0 11 18 managesieve 0.42 0.80 0.20 577 0 0 520 0 0 13 4 managesieve-lo 84.84 0.80 0.52 1049 0 0 0 0 0 45 11 imap 0.51 0.12 0.76 664 0 0 0 0 0 10 11 pop3-login 361.78 0.64 0.28 773 0 0 0 0 0 13 2 Date: Mon, 08 Nov 2010 06:00:01 +0100 type real user sys reclaim faults swaps bin bout signals volcs involcs auth 467.35 0.16 0.17 797 0 0 0 0 0 8 9 ssl-params 273.33 0.00 0.16 470 0 0 0 0 0 5 3 pop3 0.14 0.12 0.36 667 0 0 0 8 0 14 1 managesieve 0.20 0.00 0.28 576 0 0 0 0 0 10 1 managesieve-lo 640.83 0.13 0.44 1272 0 0 0 0 0 87 17 imap 0.33 0.40 0.32 665 0 0 0 0 0 10 47 pop3-login 362.87 0.60 0.24 774 0 0 0 0 0 13 3 Date: Mon, 08 Nov 2010 07:00:02 +0100 type real user sys reclaim faults swaps bin bout signals volcs involcs auth 468.95 0.96 1.34 21628 0 0 0 0 0 243 218 ssl-params 83.87 0.00 0.12 469 0 0 0 0 0 7 1 pop3 0.11 0.16 0.24 667 0 0 0 8 0 11 6 managesieve 0.83 0.00 0.88 577 0 0 536 0 0 9 12 managesieve-lo 231.47 0.18 0.96 1381 0 0 0 0 0 106 17 imap 0.71 0.12 0.80 665 0 0 0 0 0 10 47 pop3-login 292.13 0.56 0.28 779 0 0 0 0 0 46 7 Date: Mon, 08 Nov 2010 08:00:02 +0100 type real user sys reclaim faults swaps bin bout signals volcs involcs auth 452.63 0.83 1.44 20188 0 0 16 0 0 286 121 ssl-params 289.68 0.00 0.80 470 0 0 136 0 0 14 6 pop3 1.37 0.80 0.17 681 1 0 1936 16 0 55 28 managesieve 0.24 0.40 0.20 580 0 0 256 0 0 14 5 managesieve-lo 1952.41 4.93 1.58 18647 0 0 8 0 0 3673 1339 imap 0.17 0.40 0.19 665 0 0 0 0 0 6 48 pop3-login 96.75 0.60 0.28 777 0 0 112 0 0 41 14 -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | http://www.charite.de

4 9

[Dovecot] Expunge -A cannot find users
by Kilburn Abrahams 08 Nov '10

08 Nov '10

Hi List, If I use doveadm expunge in this format expunge will delete the email doveadm expunge -u test(a)planetseafood.com mailbox Archive ON '8-Nov-2010' But in this format doveadm expunge -A mailbox Archive ON '8-Nov-2010', it will list all the users in the database and display the following and no messages are expunged. doveadm(test@planetseafood.com@planetseafood.com): Info: User no longer exists, skipping. The iterate_query = SELECT username AS username, domain FROM mailbox which is correct for the DB layout. I am not using the expire plugin. Is this a permissions issue? Thanks Kilburn

2 2

[Dovecot] Estimación de horas del cambio a Dovecot 2.0
by Antonio Perez-Aranda 08 Nov '10

08 Nov '10

Actualmente tenemos dovecot 1.2.15 que ha demostrado ser bastante estable, pero con el que podemos tener problemas de corrupción en ficheros de índices de Dovecot (dovecot-uidlist). Este problema, podría llegar a ocasionar la descarga de todos los correos desde el cliente del usuario. En Dovecot 2.0 tenemos una mejor gestión sobre NFS mediante un nuevo sistema llamado director. Con este director se consigue que dovecot haga a su vez de proxy/balanceador e intente direccionar las conexiones de un usuario a un mismo servidor si este permite conexiones. En resumen, conseguimos evitar escrituras "concurrentes" sobre cachés de NFS que podrían ocasionar corrupción en determinados índices de dovecot. Para este cambio básicamente deberíamos repetir ciertas pruebas que hemos realizado para dovecot 1.2 así como ciertas tareas. 1. Actualizar configuración 2. Actualizar plugin TrataSPAM (MarcaSPAM/DesmarcaSPAM) Usando skel creado por Timo durante las sesiones de Málaga. 3. Pruebas de tiempos de indexado con SQUAT 4. Búsquedas concurrentes. 5. Pruebas de IMAP IDLE. 6. Migración { Keywords, suscriptions, flags, status...} 7. Condiciones de estrés. 8. Actualizar Doc. En una primera estimación. El total de estas tareas no debería superar las 45-50 horas. A cambio obtendríamos: 1. Un mejor soporte por parte de Timo. 2. doveadm para realizar búsquedas, gestión del director, pruebas de depuración... 3. Mejoras en el comportamiento ante storage en NFS. 4. Mejoras en la coordinación con SOLR para cuando comencemos con el buscador avanzado con ficheros adjuntos. 5. Mejoras para conexiones concurrentes. La razón por la que no empezamos directamente con dovecot 2.0 es porque no preveíamos que fuera relativamente estable en poco tiempo. Observando la lista de correos y después de la conversación con Timo, la última release de dovecot 2.0 es lo suficientemente estable como para usarse en sistemas de producción. Si lo creéis necesario, podemos organizar una reunión para tomar la decisión, aunque sí que esta reunión debería ser para esta semana o a principios de la siguiente.

2 2

[Dovecot] dovecot + sieve
by maximatt 08 Nov '10

08 Nov '10

Hi, In ower mail system we use postfix and dovecot v1.2.10 with sieve plugin and i think is work fine but..... i need to have access to variables values like in these test script require ["enotify", "variables", "envelope"]; keep; notify :importance "1" :message "TEST SIEVE ${from}: ${subject}" "mailto:i_not_exist@hotmail.com"; but when i receive message, the values for "${from}" and "${subject}" are empty. i don't know the reasons about these (i'm some lost with these issue).. if help ... i put in master.cf (postfix) these value for dovecot delivery: dovecot unix - n n - - pipe flags=DRhu user=mail:mail argv=/etc/dovecot/libexec/deliver -f ${sender} -d ${recipient} ¿is here the problem or what could be? thanks in advance! *Salu2 ;)*

2 1

Re: [Dovecot] dovecot Digest, Vol 91, Issue 18
by Alan Brown 08 Nov '10

08 Nov '10

> From: Timo Sirainen <tss(a)iki.fi> > Subject: Re: [Dovecot] emails getting mangled when dragging from > Exchange account to IMAP shared folders > On Wed, 2010-11-03 at 16:18 -0700, Scott Goodwin wrote: >> FYI, I got rawlog working and it shows the same break in the raw logs as in >> the broken headers. >> Below is a snippet from the rawlog (names and other identifiers redacted). >> The offending sequence is always in the References headers section, and you >> can see the line breaks there that show this. So it sounds like this can't >> be an issue with Dovecot, am I right? > > Yeah, sounds like Outlook breaks with huge headers. That's one huge > References header you have. Summarising mail standards (WRT headers) There is a limit of 4096 characters per line. If Outlook is breaking at less than that it's a bug. If the References: line is longer than that then it should have been truncated by the sending MUA - there's no provision for multiline References headers (which are a non-standardised import from Usenet anyway).

2 2