September 2014 - dovecot

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

Dovecot Enterprize repository access
by Spyros Tsiolis 05 Sep '14

05 Sep '14

Hello all, in regards to the Enterprise repository access : 1. There's no version of v7.x for CentOS 2. There's no download section anywhere Any ideas ? s.

3 4

trouble syncing public folders
by Bjarne Mark Kondrup 05 Sep '14

05 Sep '14

GIF89aÁMæWWWþþþ777ÊÊÊhhhêš©©Û££xyyIIÔŒVVffõõõÑÄhhEEE¶EEoIIÊûóóP55€33œÌÑÑÎÎÎêËËÝDD©##ÔÔÔÃÃÃ$$$§ ¯77ÙÙÙ÷êê°²²êêêÊªªœŸŸæææùøøûîî==ãppÖââÚ88€æŸŸa``ÞßßÑÑÑÇÈÈPOO8íííZHH»hÓûûû>ßdd ÷ÕÕ£ZZÇÌÌÚ---ÒÙÙî¢¢õÌÌþýý«**9))ÌÇÇ°° Ò ºPP¥**§II¯üÿÿýûû¥$$·HH ¶ßÙÒÒðððbbÌÌÌj%%ŠíÒÒÉŒŒÊyyúää ÔÌÌž¶¶ºyyð³³IIIàTTÚÛÛÏÔÔçÁÁÿÿÿ!ù,ÁMÿ,£€¥Š ~§¬®¯©«°Žµ¶²·º»Œ¹œÀÁµ¿ÂÅÆ€ÄÇÊËÉÌÏÐÎÑÔ¢ÈªÕÛHEffEQ£ÓÜæYëYšÚçòNìöïåóü.B÷Øe£/^¿ðŽç€à,XÈ.Š}çÕ£ÏaÆHÔQ· ãÇsE,,Ô#ÅãI.<q¢ÉÜ.%.à=Ä u² %ÚoÏ M3ÈŽ @ŽZáÕ¬[mRí*ï«Ö©K ¥IÁ¶Û·pÿÙ4$®]»i9Á·¯ß¿ù^ ä"°aÃaL ëòÐ#KL2Ak*kÖŒP(GBMº4Ž.Í5±åHÛžsëÞ}{Í Œ@šFÈ+_ÎŒB3>œìRÑ&²-Œ;îËx§8 èÓ«_ÏŸêAd*°OÇuRÙiâ>^øCñý 7yéáPÁ&šà_AH|é-(áqÞ7J~b¥5Xàá â xÛ"Š¢ÃÄ(ã4ÊžÀòqD<FPÂy.ZèYJmèGÿÔd\!8@örV9ä¥!ü U%JÐäQZ2å%²BrÂ ä;Bc`9&%eRÊGeŒ^€QmÃžQQÀ -dQNš%Nf%k"z¢ArCTàV v äËXpjTàë¯Àûk-* ì²Ì..²Ùª^ÒÂéÀ&PÊ yÁ%ú¹kÂ7HšAûÇ íRsÐ:-ÜÀ»À $PÀ1 v`óH¹·y.ºŒ·.pÿôµû ¥Þ»h XìFvè 6 !kp"$ 0ìÃdBq±£Z1}îÕ+-#ÔŒHÀ[lL°è°Â :Ô)ÃqŽÊÛ`û`Òàº¡¹=û¬º°ë.Œæš±ÑŠ4$°*ml±FÔð!Ã4(0³$ððÅDþÃ@ØpÂèÌ3 ¹ Àç .:è\=È€®úêsºñ#¯#,#à°oÎÇVšÀ480st,qÆö,± D0q/f¢kÚ·1 *Åä>7|œÈÿÝ€P²w"8ðÁ8@±E%dàýI8œs 4šŽàÐ\§$ñ©JžmTh÷ŸhÕäc (@~m Ú0-ŒÀ^óð xr\ 'à4be®zžçpcŠíª <9Ÿ"HºH *`àÎ×¹$LaOx ¢Hta'à4€ÜhÏÜcÄ_·&GQ PnÆÀ6ò`¹ÁÂ( ØñÀ@0XÀ?$ IÈBr%Ê ÉÈB& E8&@ÉJZ²ûÑ3Kz²ÿSRµ5úa@ðÇŒÉñ@7$À,mw>ŸPCÖ3%nþ£ËÛ°íìrQÜ!2Êm ÂØ(±Zl Áòî¡<Ä¡`ý±AÿØK?çJR£ÄÚ6ŽÍæLç2agv#ÈE~8wÂÒ7·4R/^þÒ8ò (rè5è4 ÖD`ÏÝH`èQeä$ç@ ãÀ šË?Ø@ ©HGJR`9(©JUªÍAt@©LgJÓ!LkÊSÁ 0ÞÆ. QB P5`388@·ÙQXõªXëÍªV¯Zzõ«]ýªX±J±U`ýº#Ÿ pÍ(02¡RÄMÈÂ! Þ%D@,4ÔLæ±WŸö`¢.E`/5¢±íÅ à?5R=f3ÛGµ?1hÀ$1ZÒöbvÈVwbq®] ðÔ8&DÍÀmnÁ}áŠCÀœUGû\¡F@äEËÜÌ¶¶ºL¹.vq¢Ýí€»ÞÍxÃñ÷ æ=/?Ò«^y°·œæx/|·FÎ×±ÈtïËßþú÷¿G ;

1 0

Migrating from 2.0.x to 2.2
by Jens Dueholm Christensen 05 Sep '14

05 Sep '14

Hi I'm about to migrate a setup with <20 IMAP (but with a few million mails in all) accounts that belong to the same system-user on an older machine running Dovecot 2.0.13 to a new machine running Dovecot 2.2.13 (or possibly newer..). Mails are stored in Maildirs with no special or advanced features (like alternate storage etc etc). Filesystems are prepared for the expected amount of inodes required, and for the time beeing a change to mdbox is seen as an added complexity. One requirement of the migration is that messageID is not changed - mails are referenced by other systems that expect to find individual mails by the ID. Since dsync is incompatible between 2.0<->2.1<->2.2 what is the best way to perform this migration? I was hoping of rsync'ing all Maildirs from the old machine to the new one (including indexes etc etc) and power up Dovecot 2.2.x and see what happens, but is that possible or is there another (and better) way short of installing 2.0.x on the new machine, rsync everything and then upgrade to 2.2.x? Regards, Jens Dueholm Christensen

3 4

how to profiling imap process with valgrind
by morrison 05 Sep '14

05 Sep '14

Hi, I want to profile runtime performance of imap and pop3 processes. There processes are forked by dovecot master process. I am wondering if there is a way I can profile these processes with valgrind. I tried "service = /bin/valgrind /bin/imap" but this did not work. Thanks,

2 1

SASL LOGIN : connection to server lost with more than 10 simulatneaous postfix smtps
by Ve (HOME) 04 Sep '14

04 Sep '14

Hi All, I have a problem with SASL authentification from postfix when more than 10 mails is sent from the same user simultaneously Postfix abort connection ( Connection lost to authentication server ). Dovecot log after the postfix error an error about connection lost also ( read EOF ) I don't seem to find a parameter for a maximum of connection for the auth process ( ther's one for imap, pop, .. ) but none for auth. Do you have an idea of a way to solve this problem or to have better information ? result of Docecot -n # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.15.6-gentoo-xxxx-std-ipv6-64 x86_64 Gentoo Base System release 2.2 auth_default_realm = aprogsys.com auth_mechanisms = plain login auth_username_format = %Ln dict { acl = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } disable_plaintext_auth = no dsync_remote_cmd = ssh -l%{login} %{host} doveadm dsync-server -u%u first_valid_uid = 1001 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_access_groups = dovecot mail_location = mdbox:~/mdbox mail_plugins = " acl notify replication" managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave duplicate namespace inbox { inbox = yes list = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = separator = / } passdb { args = * driver = pam } plugin { acl = vfile acl_anyone = allow acl_shared_dict = proxy::acl antispam_backend = DSPAM antispam_debug_target = syslog antispam_dspam_args = --source=error;--signature=%%s;--user;%n antispam_dspam_binary = /usr/bin/dspam antispam_signature = X-DSPAM-Signature antispam_spam = SPAM antispam_trash = Trash antispam_verbose_debug = 1 mail_replica = remote:root@192.168.1.7 replication_dsync_parameters = -d -U sieve = ~/.dovecot.sieve sieve_before = /var/lib/dovecot/sieve sieve_default = /var/lib/dovecot/sieve/spam.sieve sieve_dir = ~/sieve } protocols = imap pop3 lmtp sieve replication_max_conns = 2 service aggregator { fifo_listener replication-notify-fifo { mode = 0666 } unix_listener replication-notify { mode = 0666 } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { mode = 0777 } user = root } service dict { unix_listener dict { mode = 0666 } } service imap-login { process_min_avail = 4 service_count = 0 vsz_limit = 256 M } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 } } ssl_cert = </etc/ssl/dovecot/server.pem ssl_key = </etc/ssl/dovecot/server.pem userdb { driver = passwd } protocol lda { mail_plugins = " acl notify replication sieve" } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags mail_max_userip_connections = 40 mail_plugins = " acl notify replication antispam imap_acl" }

3 2