- dovecot - dovecot.org

Escape comma in the LDAP passdb subquery configuration
by Francesco Fiore 10 Sep '14

10 Sep '14

Hi I have to configure the LDAP passdb to execute a subquery defining dinamically the new DN to use. For example: pass_attrs = @mail=mail=%{login_user},dc=%{login_domain},dc=example,dc=com,\ =proxy=y,\ =host=%{ldap:mailHost@mail} In the previous example, the problem is the use of "," for DN representation, which is also the separator for the attribute template in the pass_attr parameter value. I tried to escape it with '\' or '%' but it doesn't work. Dovecot version is 2.2.13. How can I resolve this issue? Thanks in advance

3 3

"§"-sign in passwords
by InterNetworX | Pascal Heverhagen 10 Sep '14

10 Sep '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hey users, I've got a constellation with dovecot, postfix, froxlor and roundcube. My problem is, when a user has got a paragraph sign in his password, every mail client tells him, that he entered a wrong password. The log says as usually "password mismatch". did anyone else fixed this problem already? Hope you can help me :) Pascal -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJUD+SHAAoJEA3oZzzqW4iVobwH/0r/g9eP2inhqCNLqBBN3Ret gU9L9dXM8iqOBl3ylgTK1Fvf/7rhnPHhM43oS+KAoaOcrG4u9PI83hfKYqMGuZPB +1/PhMcEmydUl98mjT76tC/SuGAgRnWlnc6eA+LB1Zp8EgN0h4l8zLXvw2mv6nA5 dyEHUq6cW9oIg38jMe0rXAb5mqNROAGtKTaM7182Xxk5dnJAfb5ZdNPZ8Vbn0A3d ENE9hzdndNeQPkDIVmdD6Fv1kWVwCf7shAPgQ3yJoJxOUaEq9sl4BQRI/GcLU6RF lpQFsMQTjwDa9RWPYvOT33SHDiwYLAr9l65C5A1ReLNROSaTW5rE+lL9NiUWcD8= =jP+Y -----END PGP SIGNATURE-----

3 2

Creating a backup of incoming mail
by LuKreme 10 Sep '14

10 Sep '14

This is my master.cf line for dovecot virtual users: dovecot unix - n n - - pipe flags=DRhu user=vpopmail:vchkpw argv=/usr/local/libexec/dovecot/dovecot-lda -f ${sender} -d ${user}@${nexthop} -m ${extension} I would like to also write every mail, before delivery to the user, to a backup location like /backup/imap/mm/dd Possible? -- 'On whose authority?' demanded Wert. Trymon turned his grey eyes on him. 'Mine. I need no other.' --The Light Fantastic

5 11

Re: vsz_limit is 18,447 PB
by Joseph Tam 10 Sep '14

10 Sep '14

On Tue, 9 Sep 2014, dovecot-request(a)dovecot.org wrote: > vsz_limit = 18446744073709551615 B > } > > Still the same value? why not 265MB? I guess this is Dovecot's approximation of infinity. It's the largest value that fits into a 64-bit signed integer (2^64-1). Joseph Tam <jtam.home(a)gmail.com>

1 0

ACL with Public Namespace
by Bruno Galindro da Costa 10 Sep '14

10 Sep '14

I've configured a namespace like this: namespace avisos { type = public list = yes location = maildir:/var/mail.avisos:INDEXPVT=~/Maildir/avisos subscriptions = yes prefix = "AVISOS." mailbox DIVULGA { auto = subscribe } } This is the namespace representation in filesystem: root@imap:~# ls -lha /var/mail.avisos/ total 44K drwxr-xr-x 7 vmail mail 4,0K Set 9 18:21 . drwxr-xr-x 16 root root 4,0K Set 9 17:08 .. drwxr-xr-x 5 vmail mail 4,0K Set 9 16:49 .DIVULGA -rw-r--r-- 1 root root 17 Set 9 18:21 dovecot-acl -rw-r--r-- 1 vmail mail 0 Set 9 18:11 dovecot-acl-list -rw-r--r-- 1 vmail mail 360 Set 9 18:11 dovecot.mailbox.log -rw-r--r-- 1 vmail mail 8 Set 9 18:02 dovecot-uidvalidity -r--r--r-- 1 vmail mail 0 Set 9 14:57 dovecot-uidvalidity.540f3f88 -rw-r--r-- 1 vmail mail 249 Set 9 18:11 subscriptions This is the content of dovecot-acl file located at namespace's root level: root@imap:~# cat /var/mail.avisos/dovecot-acl authenticated rs After reload dovecot service, it trows this error message in log: Sep 9 18:14:13 imap dovecot: imap(user@mydomain): Error: Failed to autocreate mailbox AVISOS.DIVULGA: Permission denied So, I've changed the dovecot-acl file to this one and the problem was solved. root@imap:~# cat /var/mail.avisos/dovecot-acl authenticated rsk But that change created another problem: dovecot-acl file is copied into AVISOS.DIVULGA. So, the user can create a maildir inside it. This behaviour is bad because "invalid" maildirs are created under the filesystem. My intention is to don't permit the user to create any maildir inside any location of that namespace. But, I want to make possible to the administrator to edit the dovecot.conf, insert a new mailbox into namespace avisos and reload dovecot service to create new maildirs automatically. How can I solve this problem? -- Att. Bruno Galindro da Costa

1 0

Dovecot + Postfix postmulti SASL
by Nerijus Kislauskas 09 Sep '14

09 Sep '14

Hello, Our Postfix setup uses multi-instance feature. I would like to enable dovecot SASL mechanisms in postfix. Open two unix sockets is not a problem for us: service auth { unix_listener /var/spool/postfix-instance1/private/auth { mode = 0660 user = postfix group = postfix } unix_listener /var/spool/postfix-instance2/private/auth { mode = 0660 user = postfix group = postfix } } Lets assume, that postfix-instance1 uses LDAP1, and postfix-instance2 uses LDAP2. How can I use different userdb and passdb databases for those sockets? -- Sincerely, Nerijus Kislauskas

1 1

d.iskandarov
by d.iskandarov 08 Sep '14

08 Sep '14

http://shop2.vashare.sg/zhbyes/oevhtkx.aknikio

1 0

Panic/backtrace in dovecot 2.2.13
by Ed W 07 Sep '14

07 Sep '14

Hi I'm running into regular problems with dovecot choking on "corrupted" index files. The main problem is that it doesn't sort itself out and recover. This message below is repeated regularly in the log files (until I delete the index files) I *think* the trigger to get into this situation might be a files being delivered with incorrect S= values in the filename? Which is to say I am using maildrop to deliver messages and occasionally maildrop seems to write files with incorrect S= names (anyone know why or how to fix it?). The error logged regarding incorrect S= values is obviously completely different, but I speculate that it could be the earlier cause that gets the index file out of shape as shown in the problem here Thanks for any help? (note it's not easy to remove maildrop at present) Ed W Sep 1 07:32:51 mail1 dovecot: imap(xxxxxxx(a)mailasail.com): Panic: file mail-index-transaction-export.c: line 203 (log_append_ext_hdr_update): assertion failed: (u32.offset + u32.size <= ext_hdr_size) Sep 1 07:32:51 mail1 dovecot: imap(xxxxxxx(a)mailasail.com): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x69a9e) [0xedee5a9e] -> /usr/lib/dovecot/libdovecot.so.0(+0x69b21) [0xedee5b21] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0xede97a69] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_transaction_export+0xa36) [0xedfff706] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xa9f50) [0xedffdf50] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_transaction_commit_full+0xc4) [0xedffe454] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_transaction_commit+0x23) [0xedffe513] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_commit+0xef) [0xee0078ef] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x52e05) [0xedfa6e05] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x52040) [0xedfa6040] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x5251a) [0xedfa651a] -> /usr/lib/dovecot/libdovecot-storage.so.0(maildir_storage_sync_init+0xf4) [0xedfa68d4] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x3b) [0xedfb786b] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x3f) [0xedfb79af] -> dovecot/imap [xxxxxxx(a)mailasail.com 80.189.197.148 SELECT](cmd_select_full+0x187) [0x80594d7] -> dovecot/imap [xxxxxxx(a)mailasail.com 80.189.197.148 SELECT](cmd_select+0x17) [0x8059f37] -> dovecot/imap [xxxxxxx(a)mailasail.com 80.189.197.148 SELECT](command_exec+0x32) [0x805f1a2] -> dovecot/imap [xxxxxxx(a)mailasail.com 80.189.197.148 SELECT]() [0x805e197] -> dovecot/imap [xxxxxxx(a)mailasail.com 80.189.197.148 SELECT]() [0x805e2d9] -> dovecot/imap [xxxxxxx(a)mailasail.com 80.189.197.148 SELECT](client_handle_input+0x115) [0x805e515] -> dovecot/imap [xxxxxxx(a)mailasail.com 80.189.197.148 SELECT](client_input+0x72) [0x805e8c2] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x59) [0xedef8e89] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xee) [0xedefa05e] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x1c) [0xedef8f1c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x48) [0xedef8fa8] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x2e) [0xede9d76e] -> dovecot/imap [xxxxxxx(a)mailasail.com 80.189.197.148 SELECT](main+0x2bd) [0x80520ed] -> /lib/libc.so.6(__libc_start_main+0xf5) [0xedce9f25] Sep 1 07:32:51 mail1 dovecot: imap(xxxxxxx(a)mailasail.com): Fatal: master: service(imap): child 31315 killed with signal 6 (core dumps disabled)

2 1

lmtp memory usage problem - Fatal: pool_system_realloc(268435456): Out of memory
by Arkadiusz Miśkiewicz 05 Sep '14

05 Sep '14

Hi. In my setup exim delivers mails to dovecot using LMTP. In one LMTP session exim can deliver up to 200 recipients (batch_max set to that value). Now the problem is that sometimes 256MB is not enoug for dovecot lmtp to handle incoming emails. My questions: - how big memory limit should be for lmtp? I was thinking that lmtp (more or less) simply reads from one descriptor and writes to file, then does rename() (maildir used here) and that's all. That shouldn't require big number of memory. So how to determine correct memory limit and what affects this limit? - is number of recipients in one LMTP session important here? Not sure, maybe dovecot stores email in memory first and then writes to the user maildirs? Setting (batch) limit to 1 could reduce memory usage then (since no need to store anything in memory) ? Thanks, Log: Sep 4 16:10:30 mail dovecot: lmtp(21383, user): Fatal: pool_system_realloc(268435456): Out of memory Sep 4 16:10:30 mail dovecot: lmtp(21383, user): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x682a0) [0x7fe327e632a0] -> /usr/lib64/dovecot/libd ovecot.so.0(+0x6837e) [0x7fe327e6337e] -> /usr/lib64/dovecot/libdovecot.so.0(i_error+0) [0x7fe327e1dbf8] -> /usr/lib64/dovecot/libdovecot.so.0(+0x7d6a3) [0x7fe327e786a3] -> /usr/lib64/dovecot/libdovecot.so.0(i_stream_grow_buffer+0x8f) [0x7fe327e6c4cf] -> /usr/lib64/dovecot/libdovecot.so.0(i_stream_try_alloc+0x82) [0x7fe327e6c592] -> /usr/lib6 4/dovecot/libdovecot.so.0(+0x73b9b) [0x7fe327e6eb9b] -> /usr/lib64/dovecot/libdovecot.so.0(+0x73c36) [0x7fe327e6ec36] -> /usr/lib64/dovecot/libdovecot.so.0(i_stream_read+0x 53) [0x7fe327e6bad3] -> /usr/lib64/dovecot/libdovecot.so.0(+0x77391) [0x7fe327e72391] -> /usr/lib64/dovecot/libdovecot.so.0(i_stream_read+0x53) [0x7fe327e6bad3] -> /usr/lib 64/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) [0x7fe327e6c2fd] -> /usr/lib64/dovecot/libdovecot.so.0(io_stream_copy+0x7f) [0x7fe327e7cacf] -> /usr/lib64/dovecot/libdo vecot.so.0(+0x83310) [0x7fe327e7e310] -> /usr/lib64/dovecot/libdovecot.so.0(o_stream_send_istream+0x4d) [0x7fe327e7c92d] -> /usr/lib64/dovecot/libdovecot-storage.so.0(maild ir_save_continue+0x5a) [0x7fe32811b14a] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_storage_copy+0x88) [0x7fe328145328] -> /usr/lib64/dovecot/libdovecot-storage.so.0 (maildir_copy+0x42) [0x7fe3281179c2] -> /usr/lib64/dovecot/plugins/lib10_quota_plugin.so(+0xb52b) [0x7fe32764352b] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_cop y+0x6d) [0x7fe32814d29d] -> /usr/lib64/dovecot/libdovecot-lda.so.0(mail_deliver_save+0x185) [0x7fe3283f1765] -> /usr/lib64/dovecot/libdovecot-lda.so.0(mail_deliver+0xeb) [0 x7fe3283f1b6b] -> dovecot/lmtp() [0x405d80] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x3f) [0x7fe327e7398f] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handl er_run_internal+0xd7) [0x7fe327e74897] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x9) [0x7fe327e739f9] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x3 8) [0x7fe327e73a78] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fe327e22ca3] Sep 4 16:10:30 mail dovecot: lmtp(21383, user): Fatal: master: service(lmtp): child 21383 returned error 83 (Out of memory (service lmtp { vsz_limit=256 MB }, you may need to increase it) - set CORE_OUTOFMEM=1 environment to get core dump) -- Arkadiusz Miśkiewicz, arekm / maven.pl

1 0

stemmer or no-stemmer..
by Akash 05 Sep '14

05 Sep '14

Hi, In the documentation of FTS lucene, I need little more clarification about this section: -------------------------------------------------- --with-lucene --with-stemmer The second switch is only required if you have compiled libstemmer yourself or if it's included in the CLucene you are using. -------------------------------------------------- I am totally unsure but as I understand, on Debian testing, the stemmer support for libclucene comes as part of libclucene-contribs1 package (which isn't a required dependency and doesn't get installed if I install dovecot from repos). Please correct me if I am wrong. When I install dovecot-lucene from repos, libclucene-core1 and libstemmer install with it (but no libclucene-contribs1). Does that mean dovecot search has stemmer support? Now I am compiling dovecot and libclucene for Debian stable (which doesn't have latest libs in repos). If I don't compile the contribs part in clucene package but compile dovecot with --with-stemmer, do I get the stemmer support? If I totally opt of this stemmer thing, do I lose anything on search performance? And when you have a no_snowball option, what is the need of libstemmer altogether? Please help me through these confusions.. -Regards, Akash

1 0