- dovecot - dovecot.org

can't enable sieve on ubuntu trusty
by Mihai Badici 10 Jun '15

10 Jun '15

I try to create a sieve rule on a Ubuntu server ( managed by i-mscp) For this rule i need the editheader extension. I edited /etc/dovecot/conf.d/90-sieve.conf and added the following: plugin { #sieve_extensions = +notify +imapflags sieve_extensions = +editheader .... Restarted dovecot and didn't work Looks like the content of 90-sieve.conf is ignored. dovecot -n show no rule activated: dovecot -n # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.13.0-53-generic x86_64 Ubuntu 14.04.2 LTS auth_mechanisms = plain login cram-md5 digest-md5 disable_plaintext_auth = no mail_location = maildir:~/ mail_plugins = quota 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 namespace inbox { inbox = yes location = prefix = INBOX. separator = . type = private } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { autocreate = Trash autocreate2 = Spam autocreate3 = Deffered autocreate4 = Whatever autosubscribe = Trash autosubscribe2 = Spam autosubscribe3 = Deffered quota = maildir:User quota quota_rule = *:storage=1GB quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u } protocols = " imap lmtp sieve pop3" service auth { unix_listener auth-master { mode = 0600 user = vmail } } service quota-warning { executable = script /var/www/imscp/engine/quota/imscp-dovecot-quota.sh group = imscp unix_listener quota-warning { mode = 0600 user = vmail } } ssl_cert = </etc/imscp/imscp_services.pem ssl_key = </etc/imscp/imscp_services.pem ssl_protocols = !SSLv2 !SSLv3 userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocol imap { mail_plugins = quota imap_quota } protocol pop3 { pop3_uidl_format = %u-%v } protocol lda { auth_socket_path = /var/run/dovecot/auth-master mail_plugins = quota postmaster_address = postmaster(a)ispcp.sf-hosting.net } Mihai Badici[1] -------- [1] http://mihai.badici.ro

1 0

Dovecot mbox & other programs
by Pali Rohár 09 Jun '15

09 Jun '15

Hello, I want to use dovecot as imap server with mbox storage format (described at [1]) but I also want to access (and modify!) those mbox files which are stored on server (and used by dovecot). What is correct way to read those mboxes? From wiki page [1] I read that I should ignore first message in mbox (which contains X-IMAPbase header) and mbox file is in mboxcl2 format. And what is correct way to modify that mbox file (which is used by dovecot imap)? I would like to configure mutt on server to directly access those mbox mailboxes without need to use imap protocol (over localhost). It is possible without any data/message damage? [1] - http://wiki2.dovecot.org/MailboxFormat/mbox -- Pali Rohár pali.rohar(a)gmail.com

6 15

special_use \Archive not working with some foldernames
by Hajo Locke 09 Jun '15

09 Jun '15

Hello list, i use dovecot 2.2.18 compiled on my own and want to report an odd behaviour when using a folder for special_use \Archive. In my case it is not working when using some special foldernames (mbox). I compared to version 2.2.15 which i found pre-packaged on launchpad.net, same behaviour. All other special_use Folder work like expected. My situation: We authenticate users using mysql-db. also we allow users to store individuell special_use settings in db. this is a way which was recommended by this mailinglist some years ago. we use a password_query like this: password_query = SELECT `inbox` as `user`, `password`, `home` as userdb_home, `uid` AS userdb_uid, `gid` AS userdb_gid, `userdb_import` AS userdb_userdb_import FROM `mail_users` WHERE `login` = '%u' AND `active`='Y' typical column in db looks like this: | username | cryptedpass | path | inboxname | uid | gid | Y | namespace/inbox/mailbox=Sent namespace/inbox/mailbox/Sent/name=Gesendet namespace/inbox/mailbox/Sent/auto=subscribe namespace/inbox/mailbox/Sent/special_use=\Sent namespace/inbox/mailbox=Drafts namespace/inbox/mailbox/Drafts/name=EntwÃ¼rfe namespace/inbox/mailbox/Drafts/auto=subscribe namespace/inbox/mailbox/Drafts/special_use=\Drafts namespace/inbox/mailbox=Trash namespace/inbox/mailbox/Trash/name=Papierkorb namespace/inbox/mailbox/Trash/auto=subscribe namespace/inbox/mailbox/Trash/special_use=\Trash namespace/inbox/mailbox=Junk namespace/inbox/mailbox/Junk/name=Spam namespace/inbox/mailbox/Junk/auto=subscribe namespace/inbox/mailbox/Junk/special_use=\Junk namespace/inbox/mailbox=Archives namespace/inbox/mailbox/Archives/name=Archiv namespace/inbox/mailbox/Archives/auto=subscribe namespace/inbox/mailbox/Archives/special_use=\Archive | Now i noticed that in this case the folder Archiv was not binded to special_use \Archive: * LIST (\NoInferiors \UnMarked \Junk) "/" Spam * LIST (\NoInferiors \UnMarked \Drafts) "/" Entw&APw-rfe * LIST (\NoInferiors \UnMarked \Sent) "/" Gesendet * LIST (\NoInferiors \UnMarked \Trash) "/" Papierkorb * LIST (\NoInferiors \UnMarked) "/" Archiv * LIST (\HasNoChildren) "/" INBOX If i change the name of folder which is binded to special_use \Archive its working again, no other changes: * LIST (\NoInferiors \UnMarked \Archive) "/" Archiviu or a shorter one: * LIST (\HasNoChildren \Archive) "/" Arc It works in most cases, it is not working if i have chosen name "Archiv". It seems also that autocreating of folder is not working if name is "Archiv". I activated the debug settings but was not helpful. Looks the same in all cases: Debug: Added userdb setting: namespace/inbox/mailbox=Archives Debug: Added userdb setting: namespace/inbox/mailbox/Archives/auto=subscribe Debug: Added userdb setting: namespace/inbox/mailbox/Archives/name=Arc Debug: Added userdb setting: namespace/inbox/mailbox/Archives/special_use=\Archive or: Debug: Added userdb setting: namespace/inbox/mailbox=Archives Debug: Added userdb setting: namespace/inbox/mailbox/Archives/auto=subscribe Debug: Added userdb setting: namespace/inbox/mailbox/Archives/name=Archiviu Debug: Added userdb setting: namespace/inbox/mailbox/Archives/special_use=\Archive or the not working one: Debug: Added userdb setting: namespace/inbox/mailbox=Archives Debug: Added userdb setting: namespace/inbox/mailbox/Archives/auto=subscribe Debug: Added userdb setting: namespace/inbox/mailbox/Archives/name=Archiv Debug: Added userdb setting: namespace/inbox/mailbox/Archives/special_use=\Archive I have no idea what is going wrong here. I have no further hints in my logs. What to do now? Any ideas? Thanks, Hajo

1 0

Re: Dovecot mbox & other programs
by Joseph Tam 09 Jun '15

09 Jun '15

Pali Roh?r <pali.rohar(a)gmail.com> writes: > Still I want read/write access to storage and want to use mbox as > storage (also for easier backup and copy)... Backup performance may be another big win for Maildir, especially for incremental backups. Be that as it may ... > And my question was how to properly read and write from/to mbox files > which are used by dovecot. Dovecot mailbox indices are self-healing: indices should be rengenerated automatically when the mailbox is out of sync with regards to the indices. There may be a few complaints in the mail logs about it (e.g. UIDVALIDITY changes), but they are mostly harmless. Joseph Tam <jtam.home(a)gmail.com>

1 0

LMTPs between proxy and backend
by Patrick Westenberg 05 Jun '15

05 Jun '15

Hi @all, I have a 3 server setup (MX ==LMTP==> Proxy ==LMTP==> Backend). After upgrading to 2.2.18 I was able to use LMTPs from MX to the proxy but not from the proxy to the backend: Received: from mf01.example.net ([172.17.1.5]) by mb01.example.net (Dovecot) with LMTP id T+LnDWrvcVWDSwAAJnBBGg for <patrick(a)example.net>; Fri, 05 Jun 2015 20:50:58 +0200 Received: from mx01.example.net ([172.17.1.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) zlib compression) by mf01.example.net (Dovecot) with LMTP id 8uuXJ13vcVW2fgAATr09kg Can anyone help or is Dovecot not able to use LMTPs as client? Regards Patrick Proxy: # 2.2.18: /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.8 (0c4ae064f307+) # OS: Linux 3.16.0-0.bpo.4-amd64 x86_64 Debian 7.8 auth_mechanisms = plain login director_mail_servers = 172.17.1.1 172.17.1.2 director_servers = 172.17.1.3 172.17.1.4 director_user_expire = 5 mins lmtp_proxy = yes log_path = /var/log/dovecot.log 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 index ihave duplicate protocols = imap pop3 lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { user = dovecot } } service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { address = 172.17.1.3 port = 9090 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service imap-login { executable = imap-login director process_min_avail = 1 service_count = 0 } service lmtp { inet_listener lmtp { address = 172.17.1.3 port = 24 } process_min_avail = 20 } service managesieve-login { executable = managesieve-login director inet_listener sieve { port = 4190 } } service pop3-login { executable = pop3-login director } ssl_cert = </etc/ssl/certs/wildcard.pem ssl_cipher_list = <snip> ssl_dh_parameters_length = 2048 ssl_key = </etc/ssl/private/wildcard.key ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv3 !SSLv2 verbose_proctitle = yes protocol !smtp { passdb { args = proxy=y nopassword=y starttls=any-cert driver = static name = } } protocol smtp { passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql name = } userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql name = } } protocol lmtp { auth_socket_path = director-userdb } Backend: # 2.2.18: /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.8 (0c4ae064f307+) # OS: Linux 3.14-0.bpo.1-amd64 x86_64 Debian 7.8 auth_mechanisms = plain login listen = 172.17.1.2 lmtp_save_to_detail_mailbox = yes log_path = /var/log/dovecot.log login_trusted_networks = 172.17.1.3 172.17.1.4 mail_home = /srv/mail/%Ld/%Ln mail_location = maildir:~/Maildir mail_plugins = quota 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 index ihave duplicate namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Spamverdacht { auto = subscribe special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = INBOX/ separator = / type = private } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { mail_replica = tcps:mb01.wk-serv.net quota = dict:User quota::file:%h/Maildir/dovecot-quota quota_rule2 = INBOX/Trash:ignore quota_status_nouser = DUNNO quota_status_success = DUNNO quota_warning = storage=90%% quota-warning 90 %u quota_warning2 = storage=75%% quota-warning 75 %u sieve = ~/.dovecot.sieve sieve_after = /usr/local/etc/dovecot/sieve/sieve_after.sieve sieve_default = /usr/local/etc/dovecot/sieve/default.sieve sieve_dir = ~/sieve } postmaster_address = postmaster(a)wk-serv.de protocols = imap pop3 lmtp sieve service aggregator { fifo_listener replication-notify-fifo { user = vmail } unix_listener replication-notify { user = vmail } } service auth { unix_listener auth-userdb { group = vmail mode = 0666 user = vmail } } service config { unix_listener config { mode = 0600 user = vmail } } service doveadm { inet_listener { port = 12345 ssl = yes } } service imap-login { process_min_avail = 2 service_count = 0 } service lmtp { inet_listener lmtp { address = 172.17.1.2 port = 24 } process_min_avail = 20 } service managesieve-login { inet_listener sieve { port = 4190 } } service quota-status { client_limit = 1 executable = quota-status -p postfix inet_listener { port = 12340 } } service quota-warning { executable = script /usr/local/etc/dovecot/quota_warning.sh unix_listener quota-warning { user = vmail } user = root } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 user = vmail } } ssl = required ssl_cert = </etc/ssl/certs/wildcard.crt ssl_client_ca_file = /etc/ssl/certs/startssl-bundle.pem ssl_key = </etc/ssl/private/wildcard.key ssl_protocols = !SSLv3 !SSLv2 userdb { driver = prefetch } userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } verbose_proctitle = yes protocol lmtp { mail_plugins = quota notify replication sieve } protocol imap { mail_max_userip_connections = 30 mail_plugins = quota notify replication imap_quota }

1 0

Does Dovecot allow different clients to subscribe different subsets of IMAP folders?
by Steve 04 Jun '15

04 Jun '15

I have a working Dovecot IMAP server (v. 2.2.9) where I have a single user but a lot of folders (over 800 in total, hierarchically arranged, about 50 of which are in active use.) I have multiple clients (including k9Mail on Android and Thunderbird on Linux and Windows). These clients all present a consistent subscription to a single subset of the available folders . What I'd like to be able to do is (somehow) allow different devices (different email clients) to subscribe to a different subset of folders. For example, I may want K9mail on my phone to be subscribed only to my "main Inbox" - but for Thunderbird on Windows to also be subscribed to active mailing-list folders. Does Dovecot support such a mode of operation? If so, how do I configure it? If not, what options are there to achieve the desired end result - i.e. different devices/IMAP clients subscribed to different subsets of the universe of folders available to a single user. Mandatory details: Version : 2.2.9 Configuration: See http://paste.ubuntu.com/11564807/

3 4

Testing SHA512-CRYPT password hashes with doveadm pw -t fails
by Felix Zielcke 04 Jun '15

04 Jun '15

Hi, I use Debian jessie with Dovecot 2.2.13-11. While writing a script for Horde to change the passwords in my passwd file I noticed doveadm pw -t fails for SHA512-CRYPT: # doveadm pw -s SHA1 -p test {SHA1}qUqP5cyxm6YcTAhz05Hph5gvu9M= # doveadm pw -t {SHA1}qUqP5cyxm6YcTAhz05Hph5gvu9M= -p test {SHA1}qUqP5cyxm6YcTAhz05Hph5gvu9M= (verified) # doveadm pw -s SHA512-CRYPT -p test {SHA512-CRYPT}$6$8FfoioQWQDR/Vuzu$ynKiO/E6Xf4dMvfx2LsP9KQotqy5cEOEppnEh5Hqe1UpCYAgOwSIJlNb0O65fxdYcRZH3gNFQ7ZOM/2kD/R811 doveadm pw -t {SHA512-CRYPT}$6$8FfoioQWQDR/Vuzu$ynKiO/E6Xf4dMvfx2LsP9KQotqy5cEOEppnEh5Hqe1UpCYAgOwSIJlNb0O65fxdYcRZH3gNFQ7ZOM/2kD/R811 -p test doveadm(root): Fatal: reverse password verification check failed: Password mismatch If this can't work for SHA512-CRYPT then at least the error message should be more helpful. Or am I understanding the -t option wrongly? Then this sohuld be maybe somewhere clarified. I just use now doveadm auth test which works fine. Regards, Felix Zielcke

2 2

Misleading SSL/TLS Log Messages
by Yahooguntu 03 Jun '15

03 Jun '15

Hi all, I think I've found a small bug in how Dovecot logs SSL/TLS info. Basically, if I connect to the server using TLS, the logs have a lot of entries saying I used SSLv3 (which is not allowed). Here's my system info: OSX Yosemite (x86_64, HFS+) Dovecot 2.2.15 (via Homebrew) OpenSSL 0.9.8zd The configuration (see below) disallows SSLv3, and if I try and connect with OpenSSL to test that ("openssl s_client -connect localhost:993 -ssl3") it fails as expected. If I do the same command, but with "-tls1" instead of "-ssl3", I can connect and run IMAP commands. The problem is, if I open up the Dovecot logs and look at the SSL log messages, they all say I used SSLv3. As an example, this is a truncated log from when I connected to the server and immediately did a LOGOUT: 14:50:59 : master: Warning: Killed with signal 15 (by pid=1 uid=0 code=unknown 0) 14:51:03 : master: Dovecot v2.2.15 starting up for imap, lmtp (core dumps disabled) 14:51:13 : imap-login: Debug: SSL: elliptic curve secp384r1 will be used for ECDH and ECDHE key exchanges 14:51:13 --- last message repeated 1 time --- 14:51:13 : imap-login: Debug: SSL: where=0x10, ret=1: before/accept initialization [127.0.0.1] 14:51:13 : imap-login: Debug: SSL: where=0x2001, ret=1: before/accept initialization [127.0.0.1] 14:51:13 : imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read client hello A [127.0.0.1] 14:51:13 : imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write server hello A [127.0.0.1] 14:51:13 : imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write certificate A [127.0.0.1] 14:51:13 : imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write key exchange A [127.0.0.1] 14:51:13 : imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write server done A [127.0.0.1] 14:51:13 : imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 flush data [127.0.0.1] 14:51:13 : imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read client certificate A [127.0.0.1] 14:51:13 : imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv3 read client key exchange A [127.0.0.1] 14:51:13 --- last message repeated 1 time --- 14:51:13 : imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read client key exchange A [127.0.0.1] 14:51:13 : imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read finished A [127.0.0.1] 14:51:13 : imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write session ticket A [127.0.0.1] 14:51:13 : imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write change cipher spec A [127.0.0.1] 14:51:13 : imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write finished A [127.0.0.1] 14:51:13 : imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 flush data [127.0.0.1] 14:51:13 : imap-login: Debug: SSL: where=0x20, ret=1: SSL negotiation finished successfully [127.0.0.1] 14:51:13 : imap-login: Debug: SSL: where=0x2002, ret=1: SSL negotiation finished successfully [127.0.0.1] 14:51:19 : imap-login: Aborted login (no auth attempts in 6 secs): user=<>, rip=127.0.0.1, lip=127.0.0.1, TLS, session=<QdX1YaIXTQB/AAAB> 14:51:19 : imap-login: Debug: SSL alert: close notify [127.0.0.1] The second to last line, which indicates I never tried to log in, correctly states that I used TLS. All the lines for SSL debugging, though, state I used SSL or SSLv3. This is a test setup, so it accepts any mail from @example.com addresses over LMTP and allows any user to connect with the password "staticpassword". Here's the output of "dovecot -n": # 2.2.15: /usr/local/etc/dovecot/dovecot.conf # OS: Darwin 14.3.0 x86_64 hfs default_client_limit = 50 default_internal_user = _dovecot default_login_user = _dovenull default_process_limit = 10 listen = 127.0.0.1 mail_gid = admin mail_location = mbox:/usr/local/etc/dovecot/mailboxes/%n mail_uid = [my username] namespace inbox { inbox = 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 = } passdb { args = password=staticpassword driver = static } postmaster_address = postmaster at example.com protocols = imap lmtp service lmtp { inet_listener lmtp { address = 127.0.0.1 ::1 port = 24 } } ssl = required ssl_cert = </usr/local/etc/dovecot/ssl/cert.pem ssl_key = </usr/local/etc/dovecot/ssl/key.pem ssl_protocols = !SSLv2 !SSLv3 verbose_ssl = yes

2 1

indexer-worker crashes handling mails with big attachments (dovecot 2.2.16/2.2.18 + FTS Apache Solr + Tika)
by Robinson Bomze 03 Jun '15

03 Jun '15

Hi, yesterday i tried to setup Dovecot with Solr (3.6.2) + Tika (1.8) for FTS. i used a fresh Debian 8.0 system in the beginning with Dovecot 2.2.13 from the Debian repository. After i got some issues with Tika/Dovecot and i read on the mailinglist that these problems where fixed in 2.2.14+, so i tried 2.2.18. With 2.2.18 i get panics with big (ok... huge) attachments. Most mailboxes (and their attachments) get index fine, but on some i got panics from the indexer-worker. i was able to isolate the problem. It seems that when Tika (which works flawless) sends a big reply to Dovecot and Dovecot sends this data to Solr, communication crashes between Dovecot and Solr. Eg. indexing an email with a 200k char wordfile results in a panic of the indexer-worker: Jun 02 23:50:57 indexer-worker(username): Warning: I/O leak: 0x7ff65f39f540 (line 120, fd 20) Jun 02 23:50:57 indexer-worker(username): Warning: Timeout leak: 0x7ff65f39f2e0 (line 325) Jun 02 23:50:57 indexer: Error: Indexer worker disconnected, discarding 1 requests for username Jun 02 23:50:57 imap(username): Error: indexer failed to index mailbox INBOX.username Jun 02 23:50:57 indexer-worker(username): Fatal: master: service(indexer-worker): child 11429 killed with signal 11 (core dumped) I got similar issues results with 2.2.16: Jun 02 23:21:12 indexer-worker(username): Warning: I/O leak: 0x7ffff7811cc0 (line 127, fd 20) Jun 02 23:21:12 indexer-worker(username): Panic: file ioloop.c: line 39 (io_add_file): assertion failed: (callback != NULL) Jun 02 23:21:12 indexer-worker(username): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x77130) [0x7ffff7842130] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x7 Jun 02 23:21:12 indexer: Error: Indexer worker disconnected, discarding 1 requests for username Jun 02 23:21:12 imap(username): Error: indexer failed to index mailbox INBOX.username Jun 02 23:21:12 indexer-worker(username): Fatal: master: service(indexer-worker): child 7909 killed with signal 6 (core dumps disabled) The problem was already posted: http://dovecot.org/pipermail/dovecot/2015-May/100901.html I could trigger the same panic running the indexer via 'doveadm index -u username MAILBOX'. Here is a backtrace (bt) of the 2.2.18-crash (on line #8 you see a fragement of the text sent to solr): #0 array_count_i (array=0x8) at array.h:155 #1 array_get_modifiable_i (count_r=<synthetic pointer>, array=0x8) at array.h:228 #2 priorityq_remove_idx (pq=0x0, idx=0) at priorityq.c:121 #3 0x00007ff65f3ef5eb in priorityq_remove (pq=<optimized out>, item=item@entry=0xa26920) at priorityq.c:138 #4 0x00007ff65f3e1e70 in timeout_remove (_timeout=<optimized out>) at ioloop.c:288 #5 0x00007ff65f3e2781 in io_loop_move_timeout (_timeout=_timeout@entry=0xa27f98) at ioloop.c:861 #6 0x00007ff65f39ff37 in http_client_connection_switch_ioloop (conn=conn@entry=0xa27ea0) at http-client-connection.c:1357 #7 0x00007ff65f3a3d68 in http_client_switch_ioloop (client=client@entry=0xa0bf20) at http-client.c:211 #8 0x00007ff65f39c005 in http_client_request_continue_payload (_req=_req@entry=0xa0ee88, data=0xa42fa0 "k for evidence of fluid spill.\nIf the device is mounted on a stand, examine the condition of the mount.\nIf the device moves on casters, check the condition of the casters. Check operation of brakes, i"..., size=55453) at http-client-request.c:566 #9 0x00007ff65f39c22a in http_client_request_send_payload (_req=_req@entry=0xa0ee88, data=<optimized out>, size=<optimized out>) at http-client-request.c:625 #10 0x00007ff65e972429 in solr_connection_post_more (post=0xa0ee80, data=<optimized out>, size=size@entry=55453) at solr-connection.c:504 #11 0x00007ff65e96ea09 in fts_backed_solr_build_commit (ctx=0xa1a880) at fts-backend-solr.c:341 #12 0x00007ff65e96eaad in fts_backend_solr_update_set_mailbox (_ctx=0xa1a880, box=0x0) at fts-backend-solr.c:407 #13 0x00007ff65eb7cfac in fts_backend_set_cur_mailbox (ctx=ctx@entry=0xa1a880) at fts-api.c:129 #14 0x00007ff65eb7cfe3 in fts_backend_update_deinit (_ctx=<optimized out>) at fts-api.c:143 #15 0x00007ff65eb8303c in fts_transaction_end (t=t@entry=0xa11ed0) at fts-storage.c:550 #16 0x00007ff65eb83e91 in fts_transaction_commit (t=0xa11ed0, changes_r=0x7ffdcdca5e30) at fts-storage.c:615 #17 0x00007ff65f688a82 in mailbox_transaction_commit_get_changes (_t=_t@entry=0x7ffdcdca5ee0, changes_r=changes_r@entry=0x7ffdcdca5e30) at mail-storage.c:1837 #18 0x00007ff65f688b2e in mailbox_transaction_commit (t=t@entry=0x7ffdcdca5ee0) at mail-storage.c:1818 "bt full" looks like this: #0 array_count_i (array=0x8) at array.h:155 No locals. #1 array_get_modifiable_i (count_r=<synthetic pointer>, array=0x8) at array.h:228 No locals. #2 priorityq_remove_idx (pq=0x0, idx=0) at priorityq.c:121 count = <optimized out> #3 0x00007ff65f3ef5eb in priorityq_remove (pq=<optimized out>, item=item@entry=0xa26920) at priorityq.c:138 No locals. #4 0x00007ff65f3e1e70 in timeout_remove (_timeout=<optimized out>) at ioloop.c:288 timeout = 0xa26920 #5 0x00007ff65f3e2781 in io_loop_move_timeout (_timeout=_timeout@entry=0xa27f98) at ioloop.c:861 new_to = 0xa1adf0 old_to = <optimized out> #6 0x00007ff65f39ff37 in http_client_connection_switch_ioloop (conn=conn@entry=0xa27ea0) at http-client-connection.c:1357 No locals. #7 0x00007ff65f3a3d68 in http_client_switch_ioloop (client=client@entry=0xa0bf20) at http-client.c:211 conn = 0xa27ea0 _conn = 0xa27ea0 host = <optimized out> peer = <optimized out> #8 0x00007ff65f39c005 in http_client_request_continue_payload (_req=_req@entry=0xa0ee88, data=0xa42fa0 "k for evidence of fluid spill.\nIf the device is mounted on a stand, examine the condition of the mount.\nIf the device moves on casters, check the condition of the casters. Check operation of brakes, i"..., size=55453) at http-client-request.c:566 prev_ioloop = 0x9f4730 req = 0xa36970 conn = 0xa27ea0 client = 0xa0bf20 ret = <optimized out> __FUNCTION__ = "http_client_request_continue_payload" #9 0x00007ff65f39c22a in http_client_request_send_payload (_req=_req@entry=0xa0ee88, data=<optimized out>, size=<optimized out>) at http-client-request.c:625 __FUNCTION__ = "http_client_request_send_payload" #10 0x00007ff65e972429 in solr_connection_post_more (post=0xa0ee80, data=<optimized out>, size=size@entry=55453) at solr-connection.c:504 conn = 0xa0be50 __FUNCTION__ = "solr_connection_post_more" Hope anyone fixes the code... i need this feature :) Thanks a lot in advance!

2 1

multi sync (>2 servers) + selective sync + trigger
by b-dovecot.org＠grmbl.net 03 Jun '15

03 Jun '15

Hi all, I've been researching ways to replicate mail across multiple mailstores and have a few questions. Synching 2 mailstores (M1 & M2) via dsync works fine. I want to add a 3rd and 4th (M3 & M4) server to also be synced. Multi-sync (>2 servers): 1) How do I tell M1 and/or M2 to also sync to M3 and/or M4? Selective sync: 2) How do I sync specific domains to specific servers and not to others? Trigger: 3) Does a normal sync check only check the mailbox being changed or does it get triggered on mailbox changes to check ALL indexes and sync all changed mailboxes accordingly? 4) Can I use an email to trigger a sync for any other mailboxes which might be out of sync? TIA B

3 3