- dovecot - dovecot.org

replication full documentation
by MyWorking 19 Oct '15

19 Oct '15

Hi! I am create replication between two Debian 8.2 servers with dovecot 2.2.13. It work, but wont now more about replication used and i didn't now where i can red it: 1. aggregator - documentation and what he done? 2. replicator - full description or man for him 3. dsync - full description or man for him 4. doveadm replicator status - full description for all his points: * Queued 'sync' requests - when it started and what it is mean? * Queued 'high' requests - when it started and what it is mean? * Queued 'low' requests - when it started and what it is mean? * Queued 'failed' requests - when it started and what it is mean? * Queued 'full resync' requests - when it started and what it is mean? (wherry often i see this point is active on status for all my mail accounts) * Waiting 'failed' requests - i now what is it! * Total number of known users - i now what is it! 5. can dovecot create replication in real-time????

1 0

Doveadm client/server possible?
by Leon Kyneur 19 Oct '15

19 Oct '15

Hi As my mail infrastructure grows I'm now looking at the possibility of running all my doveadm commands from a central location. Wondering if there is a way to configure an inet_listener on doveadm and have a client elsewhere connect to it? Have seen the inet_listener for replication but not sure if it can also be used for general client server communication. Thanks Leon

1 0

Order in which UIDs are assigned..
by Akash 17 Oct '15

17 Oct '15

Hi, I just want some clarification on how Dovecot's IMAP assigns UIDs when it picks files from the "new" directory of a Maildir. What I am observing is that only ctime has a role to play in it. For example if there are two files in "new", a.msg & z.msg. Even when a.msg has lower mtime than z.msg and "a" comes before "z" alphabetically, dovecot will assign z.msg a lower UID if its ctime is lower than a.msg. Is this correct? Secondly, when mails are placed into Maildir through a external mechanism by-passing LDA, by any means is it possible for IMAP to run seive on it when it migrates the files from new to cur and indexes them? I understand that this might not be a valid question as mail is delivered already so there is nothing to filter :-) -Akash

2 4

doveadm-search-query pattern format
by Frank-Ulrich Sommer 17 Oct '15

17 Oct '15

Hello, the doveadm-search-query documentation specifies a 'pattern' for many search keys. Unfortunately it does not mention the format specification of this pattern (special characters, wildcards, ...). I'm using dovecot 2.2.9 but also searched the current documention on dovecot.org. Where can I find further documentation concerning the exact specification of the pattern format?

2 1

Re: doveadm index assertion failed
by Nick Rosier 16 Oct '15

16 Oct '15

Nick Rosier schreef: > > Timo Sirainen wrote: >> On 05 Oct 2015, at 22:05, Nick Rosier<nick+dovecot(a)bunbun.be> wrote: >>> Hi, >>> >>> one of my mailboxes returns following error when I run doveadm index on it: >>> >>> Panic: file charset-iconv.c: line 85 (charset_to_utf8_try): assertion failed: (srcleft<= CHARSET_MAX_PENDING_BUF_SIZE) >>> >>> OS: FreeBSD 10.2 >>> Dovecot: 2.1.19 >>> Tika: 1.10 >>> SOLR: 5.3.1 >> >> I thought this would have definitely been fixed by now.. Can you find some specific email which is triggering this? It's either something strange that I didn't expect, or it's a bug in FreeBSD's iconv(). >> >> Also can you debug this like: >> >> gdb --args doveadm index -u user@domain INBOX >> run >> <it should crash now> >> f 5 >> p src >> p ic_srcbuf >> p *src_size >> p srcleft > I recompiled Dovecot with Debug but I suspect I will have to do it for > all the required libraries as well; I did manage to find the offending > message is in Trash but have not been able to pin-point which message > it is. Just in case, here is the debugging info. I will see if I can > compile all dependencies in debug mode as well. > > GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and > you are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for > details. > This GDB was configured as "amd64-marcel-freebsd"... > (gdb) run > Starting program: /usr/local/bin/doveadm index -u xxxx@xxxx Trash > doveadm(xxxx@xxxx): Panic: file charset-iconv.c: line 85 > (charset_to_utf8_try): assertion failed: (srcleft <= > CHARSET_MAX_PENDING_BUF_SIZE) > > Program received signal SIGABRT, Aborted. > 0x000000080149f64a in thr_kill () from /lib/libc.so.7 > (gdb) f 5 > #5 0x0000000801143cd3 in i_panic (format=0x801191c30 "file %s: line > %d (%s): assertion failed: (%s)") at failures.c:275 > 275 failures.c: No such file or directory. > in failures.c > Current language: auto; currently minimal > (gdb) p src > No symbol "src" in current context. > (gdb) p ic_srcbuf > No symbol "ic_srcbuf" in current context. > (gdb) p *src_size > No symbol "src_size" in current context. > (gdb) p srcleft > No symbol "srcleft" in current context. > recompiled dovecot + all dependencies with debug but I get the same output. anything else I can try?

1 0

quotas configuration a few questions
by niya levi 16 Oct '15

16 Oct '15

hi everyone need a few questions answering if possible before i can complete some modifications on my mailserver 1 how do i modify my user_query line in dovecot-sql.conf for quotas 2 is my iterate_query line ok 3 should i use lmtp or lda to deliver the quota warnings in quota-warning.sh my server is using lmtp but i've only seen examples using lda 4 how do i break long lines in dovecot.conf, is it the same as postgresql where you leave a space on the next line before continuing the txt. i would like to break the cipher line in dovecot.conf over multiple lines 5 have i configured my namespace section correctly so that i can substitute for the autocreate plugin also could you give the files a quick look over to make sure there isn't any unnecessary additions that shouldn't be there or omissions that should be there thanks shadrock ============ /etc/dovecot/dovecot.conf disable_plaintext_auth = no mail_privileged_group = vmail log_timestamp = "%Y-%m-%d %H:%M:%S " log_path = /var/log/dovecot.log auth_debug_passwords=yes mail_debug=yes verbose_ssl=yes ssl_prefer_server_ciphers = yes ssl_dh_parameters_length = 2048 ssl_cert = </etc/ssl/certs/postfix.crt ssl_key = </etc/ssl/private/postfix.key ssl_ca = </etc/ssl/ca.crt ssl_protocols = !SSLv2 !SSLv3 ssl_cipher_list = ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH: auth_mechanisms = plain login passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } #namespace inbox { # separator = / # type = private # inbox = yes # location = maildir:/home/mailboxes/Maildir # list = yes # prefix = INBOX. #mailbox Drafts { # auto = subscribe # special_use = \Drafts #} #mailbox Junk { # auto = subscribe # special_use = \Junk #} #mailbox Sent { # auto = subscribe # special_use = \Sent #} #mailbox Trash { # auto = subscribe # special_use = \Trash #} #} mail_plugins = quota # protocols = "pop3 imap lmtp" protocols = pop3 imap lmtp sieve plugin { autocreate = Trash autocreate2 = Sent autosubscribe = Trash autosubscribe2 = Sent sieve = ~/.dovecot.sieve sieve_global_path = /etc/dovecot/sieve/default.sieve sieve_dir = ~/sieve sieve_global_dir = /etc/dovecot/sieve/global/ quota = dict:User quota::proxy::quotadict quota_rule2 = Trash:storage=+10%% quota_warning = storage=100%% quota-warning +100 %u quota_warning2 = storage=95%% quota-warning +95 %u quota_warning3 = storage=80%% quota-warning +80 %u quota_warning4 = -storage=100%% quota-warning -100 %u # user is no longer over quota } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } } service managesieve { } service dict { unix_listener dict { group = vmail mode = 0660 user = vmail } user = root } service quota-warning { executable = script /usr/local/bin/quota-warning.sh user = vmail unix_listener quota-warning { group = vmail mode = 0660 user = vmail } } protocol imap { mail_plugins = $mail_plugins autocreate imap_quota } protocol sieve { managesieve_max_line_length = 65536 managesieve_implementation_string = dovecot log_path = /var/log/dovecot-sieve-errors.log info_log_path = /var/log/dovecot-sieve.log } protocol lmtp { postmaster_address=postmaster(a)thisdomain.co.uk hostname=testy.thisdomain.co.uk mail_plugins = $mail_plugins sieve quota info_log_path = /var/log/dovecot-lmtp.log } dict { quotadict = pgsql:/etc/dovecot/dovecot-dict-sql.conf } protocol pop3 { mail_plugins = quota pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv } --(postgresql stuff)-- CREATE DATABASE mail WITH OWNER mailreader; CREATE TABLE aliases ( alias text NOT NULL, email text NOT NULL ); CREATE TABLE users ( email text NOT NULL, password text NOT NULL, maildir text NOT NULL, created timestamp with time zone DEFAULT now() ); CREATE TABLE vdomain ( domain text NOT NULL ); CREATE TABLE quota ( username varchar(100) not null, bytes bigint not null default 0, messages integer not null default 0, primary key (username) ); CREATE OR REPLACE FUNCTION merge_quota() RETURNS TRIGGER AS $$ BEGIN IF NEW.messages < 0 OR NEW.messages IS NULL THEN -- ugly kludge: we came here from this function, really do try to insert IF NEW.messages IS NULL THEN NEW.messages = 0; ELSE NEW.messages = -NEW.messages; END IF; return NEW; END IF; LOOP UPDATE quota SET bytes = bytes + NEW.bytes, messages = messages + NEW.messages WHERE username = NEW.username; IF found THEN RETURN NULL; END IF; BEGIN IF NEW.messages = 0 THEN INSERT INTO quota (bytes, messages, username) VALUES (NEW.bytes, NULL, NEW.username); ELSE INSERT INTO quota (bytes, messages, username) VALUES (NEW.bytes, -NEW.messages, NEW.username); END IF; return NULL; EXCEPTION WHEN unique_violation THEN -- someone just inserted the record, update it END; END LOOP; END; $$ LANGUAGE plpgsql; DROP TRIGGER IF EXISTS mergequota ON quota; CREATE TRIGGER mergequota BEFORE INSERT ON quota FOR EACH ROW EXECUTE PROCEDURE merge_quota(); --(postgresql stuff)-- ============ /etc/dovecot/dovecot-dict-sql.conf connect = host=/run/postgresql dbname=mail user=mailreader map { pattern = priv/quota/storage table = quota2 username_field = username value_field = bytes } map { pattern = priv/quota/messages table = quota2 username_field = username value_field = messages } ============ /etc/dovecot/dovecot-sql.conf driver = pgsql connect = host=/run/postgresql dbname=mail user=mailreader default_pass_scheme = SHA512 password_query = SELECT email as user, password FROM users WHERE email = '%u' user_query = SELECT email as user, 'maildir:/home/mailboxes/maildir/'||maildir as mail, '/home/mailboxes/maildir/'||maildir as home, 500 as uid, 500 as gid FROM users WHERE email = '%u' iterate_query = SELECT email AS user FROM users ============ /usr/local/bin/quota-warning.sh #!/bin/sh BOUNDARY="$1" USER="$2" MSG="" if [[ "$BOUNDARY" = "+100" ]]; then MSG="Your mailbox is now overfull (>100%). In order for your account to continue functioning properly, you need to remove some emails NOW." elif [[ "$BOUNDARY" = "+95" ]]; then MSG="Your mailbox is now over 95% full. Please remove some emails ASAP." elif [[ "$BOUNDARY" = "+80" ]]; then MSG="Your mailbox is now over 80% full. Please consider removing some emails to save space." elif [[ "$BOUNDARY" = "-100" ]]; then MSG="Your mailbox is now back to normal (<100%)." fi cat << EOF | /usr/lib/dovecot/lmtp -d $USER -o "plugin/quota=maildir:User quota:noenforcing" From: postmaster(a)yourdomain.com Subject: Email Account Quota Warning Dear User, $MSG Best regards, Your Mail System EOF

1 0

Strange indexing behavior on HTML emails ..
by Akash 16 Oct '15

16 Oct '15

Hi, In continuation to the issue I had posted about long back: http://www.dovecot.org/list/dovecot/2014-August/097362.html I did further testing today on a fresh new Debian & latest Dovecot and observed a undesired behavior. I am using fts_lucene & following sequence of commands on a empty test account me(a)myself.com: doveadm expunge -u 'my(a)myself.com' mailbox 'INBOX' all cat test.eml | /usr/lib/dovecot/dovecot-lda -e -f you(a)yourself.com -d me(a)myself.com doveadm search -u 'akash(a)mailjol.in' mailbox 'INBOX' text ABCD Search command does or doesn't find the email with slight variation in the content of test.eml. Here are the results: test.eml content: ----------------------------- From: you(a)yourself.com To: me(a)myself.com Subject: Test Message Content-Type: text/html <div id="mydiv">ABCD 1234</div> ----------------------------- RESULT: OK. The email is found. test.eml content (double quotes inside div tag replaced with single): ----------------------------- From: you(a)yourself.com To: me(a)myself.com Subject: Test Message Content-Type: text/html <div id='mydiv'>ABCD 1234</div> ----------------------------- RESULT: None. The email isn't found. test.eml content (single quotes in div but content/type header removed): ----------------------------- From: you(a)yourself.com To: me(a)myself.com Subject: Test Message <div id='mydiv'>ABCD 1234</div> ----------------------------- RESULT: OK. The email is found. What could be the reason for this? -Akash

3 7

Re: Problems sync with mail client MAC and dovecot-2.2.10-4.el7_0.1.el7_0.1.x86_64
by grupo correo 16 Oct '15

16 Oct '15

> Message: 6 > Date: Wed, 14 Oct 2015 11:43:22 +0200 > From: Christian Kivalo <ml+dovecot(a)valo.at> > To: Dovecot Mailing List <dovecot(a)dovecot.org> > Subject: Re: Problems sync with mail client MAC and > dovecot-2.2.10-4.el7_0.1.el7_0.1.x86_64 > Message-ID: <33ba2eacef5dcfcb4c703615e559b094(a)valo.at> > Content-Type: text/plain; charset=US-ASCII; format=flowed > > > > Attached the doveconf -n > > Yes i have mail_debug = yes into file conf.d/10-logging.conf > > I paste the rest of log: > > Oct 13 21:27:17 localhost dovecot: imap: Debug: Loading modules from > > directory: /usr/lib64/dovecot > > Oct 13 21:27:17 localhost dovecot: imap: Debug: Module loaded: > > /usr/lib64/dovecot/lib01_acl_plugin.so > > Oct 13 21:27:17 localhost dovecot: imap: Debug: Module loaded: > > /usr/lib64/dovecot/lib02_imap_acl_plugin.so > > Oct 13 21:27:17 localhost dovecot: imap: Debug: Module loaded: > > /usr/lib64/dovecot/lib10_quota_plugin.so > > Oct 13 21:27:17 localhost dovecot: imap: Debug: Module loaded: > > /usr/lib64/dovecot/lib11_imap_quota_plugin.so > > Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Debug: > > Effective > > uid=56396, gid=55000, home=/VMAIL/xxxxxxxxxxxxxx > > Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Debug: Quota > > root: > > name=User quota backend=maildir args= > > Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Debug: Quota > > grace: root=User quota bytes=0 (10%) > > Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Debug: > > Namespace > > inbox: type=private, prefix=INBOX., sep=., inbox=yes, hidden=no, > > list=children, subscriptions=yes location=maildir:~/Maildir > > Your inbox namespace seems to be ok and is also defined in your doveconf > -n output. > > > Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Debug: > > maildir++: > > root=/VMAIL/xxxxxxxxxxxxxx/Maildir, index=, indexpvt=, control=, > > inbox=/VMAIL/xxxxxxxxxxxxxx/Maildir, alt= > > Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Debug: acl: > > initializing backend with data: vfile > > Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Debug: acl: > > acl > > username = xxxxxxxxxxxxxx > > Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Debug: acl: > > owner > > = 1 > > Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Debug: acl > > vfile: > > Global ACL directory: (none) > > Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Debug: > > Namespace : > > type=private, prefix=, sep=, inbox=no, hidden=yes, list=no, > > subscriptions=no location=fail::LAYOUT=none > > Somehow there seems to be an empty namespace in addition to your inbox > namespace. > > Is there a second namespace in your config somewhere? > > > Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Debug: none: > > root=, index=, indexpvt=, control=, inbox=, alt= > > Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Fatal: master: > > service(imap): child 2464 killed with signal 11 (core dumps disabled) > > Just guessing: > Could it be with Thunderbird that the second namespace is ignored when > there is no subscription to it and the Apple mailprogram behaves > differently? > > regards > christian > > > > Hi, i can reproduce the error, conencting opnessl to port 993:

1 0

Problem with ldap - master user - sogo vacation
by zava.zava＠libero.it 16 Oct '15

16 Oct '15

Hi,I have a problem, i can't get the authentication for the master user using dovecot - ldap authentication, in combination with sogo.There is a script that is used by Sogo to check and disable the vacation messagge: "sogo /usr/sbin/sogo-tool expire-autoreply -p /etc/dovecot/master-users" Insidie this file there is: sogo:{SHA}gkodfgdk6yujkgdklkkdfkgjrg9ugr9p= if I run the script I get: Oct 16 09:59:12 auth: Debug: auth client connected (pid=6528)Oct 16 09:59:12 auth: Debug: client in: AUTH 1 PLAIN service=sieve secured session=aQDV64h65pAB/AAAB lip=127.0.0.1 rip=127.0.0.1 lport=4190 rport=36260 resp=Y2VkQGdyddgPQ== (previous base64 data may contain sensitive data)Oct 16 09:59:12 auth: Debug: passwd-file(sogo,127.0.0.1,master,<aQDVKzQipAB/AAAB>): Master user lookup for login: user(a)domain.comOct 16 09:59:12 auth: Debug: passwd-file(sogo,127.0.0.1,master,<aQDVKzQipAB/AAAB>): lookup: user=sogo file=/etc/dovecot/master-usersOct 16 09:59:12 auth: Info: passwd-file(sogo,127.0.0.1,master,<aQDVKzQipAB/AAAB>): Password mismatch (given password: {SHA}4sdgkfgwe22=)Oct 16 09:59:12 auth: Debug: passwd-file(sogo,127.0.0.1,master,<aQDVKzQipAB/AAAB>): SHA({SHA}kerwkekwrejkewerjrw=) != 'erwrewwweewrerewrwe='Oct 16 09:59:14 auth: Debug: client passdb out: FAIL 1 user=sogoOct 16 09:59:14 managesieve-login: Info: Disconnected (auth failed, 1 attempts in 2 secs): user=<sogo>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, TLS: Disconnected, session=<aQDVKzQipAB/AAAB> In the auth-master.conf.ext file I have: passdb { driver = passwd-file master = yes args = /etc/dovecot/master-users} Thanks in advance for help. # 2.2.13: /etc/dovecot/dovecot.conf# OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.2 ext4auth_debug = yesauth_debug_passwords = yesauth_master_user_separator = *auth_mechanisms = plain auth_verbose = yesauth_verbose_passwords = yesdefault_client_limit = 22000default_process_limit = 5000default_vsz_limit = 1 Gdisable_plaintext_auth = nofirst_valid_gid = 5000first_valid_uid = 5000last_valid_gid = 5000last_valid_uid = 5000log_path = /var/log/dovecot.logmail_debug = yesmail_location = maildir:/var/vmail/xxx/%Ln/Maildirmanagesieve_notify_capability = mailtomanagesieve_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 imapflags notifynamespace 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 = separator = /}passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes}passdb { driver = pam}passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap}passdb { args = /etc/dovecot/dovecot-ldap.conf1.ext driver = ldap}passdb { args = /etc/dovecot/dovecot-ldap.conf2.ext driver = ldap}passdb { args = /etc/dovecot/dovecot-ldap.conf3.ext driver = ldap}passdb { args = /etc/dovecot/dovecot-ldap.conf4.ext driver = ldap}passdb { args = /etc/dovecot/dovecot-ldap.conf5.ext driver = ldap}passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap}plugin { sieve = /var/vmail/xxx/%n/.dovecot.sieve sieve_dir = /var/vmail/xxx/%n/ sieve_extensions = +enotify +vacation +copy +imapflags +notify}protocols = imap sieveservice auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { mode = 0666 }}service imap { process_limit = 5000}service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 0 service_count = 0 vsz_limit = 64 M}service managesieve { process_limit = 1024}ssl_cert = </etc/ssl/certs/xxx.pemssl_dh_parameters_length = 2048ssl_key = </etc/ssl/private/xxx.keyuserdb { args = uid=5000 gid=5000 home=/var/vmail/xxx/%Lu driver = passwd}userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap}userdb { args = /etc/dovecot/dovecot-ldap.conf1.ext driver = ldap}userdb { args = /etc/dovecot/dovecot-ldap.conf2.ext driver = ldap}userdb { args = /etc/dovecot/dovecot-ldap.conf3.ext driver = ldap}userdb { args = /etc/dovecot/dovecot-ldap.conf4.ext driver = ldap}userdb { args = /etc/dovecot/dovecot-ldap.conf5.ext driver = ldap}userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap}protocol imap { mail_max_userip_connections = 100 mail_plugins =}protocol sieve { mail_max_userip_connections = 10 managesieve_max_line_length = 65536}

1 0

master user in dovecot 1.2
by Michal Žila 16 Oct '15

16 Oct '15

Hello list, i would like to use master user functionality in dovecot v1.2, but i just cant get it to work: Here’s my configuration: # dovecot -n # 1.2.9: /etc/dovecot.conf # OS: Linux 2.6.18-164.10.1.el5PAE i686 Red Hat Enterprise Linux Server release 5.4 (Tikanga) login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login first_valid_uid: 200 mail_privileged_group: mail mail_location: mbox:~/mail:INBOX=/var/mail/%u mail_executable(default): /root/dovecot-master-postlogin mail_executable(imap): /root/dovecot-master-postlogin mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 lda: postmaster_address: postmaster(a)example.com auth default: master_user_separator: * debug: yes passdb: driver: passwd-file args: /etc/dovecot.passwd.masterusers pass: yes master: yes passdb: driver: pam userdb: driver: passwd # cat /root/dovecot-master-postlogin #!/bin/bash MASTER_USER=$USER export MASTER_USER exec /usr/libexec/dovecot/imap "$@“ # cat /etc/dovecot.passwd.masterusers masteruser:{PLAIN}Heslo42 Trying login as normal user: # telnet localhost imap Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN] Dovecot ready. a1 login jozefkova jozefkova026 a1 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH] Logged in Trying login as master user: # telnet localhost imap Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN] Dovecot ready. a1 login jozefkova*masteruser Heslo42 a1 NO [AUTHORIZATIONFAILED] Authorization failed log sequence of failed auth: Oct 15 13:04:47 linux dovecot: auth(default): client in: AUTH 1 PLAIN service=imap secured lip=127.0.0.1 rip=127.0.0.1 lport=143 rport=34618 resp=<hidden> Oct 15 13:04:47 linux dovecot: auth(default): passwd-file(masteruser,127.0.0.1,master): lookup: user=masteruser file=/etc/dovecot.passwd.masterusers Oct 15 13:04:47 linux dovecot: auth(default): passdb(masteruser,127.0.0.1,master): Master user logging in as jozefkova Oct 15 13:04:47 linux dovecot: auth-worker(default): pam(jozefkova,127.0.0.1): lookup service=dovecot Oct 15 13:04:47 linux dovecot: auth-worker(default): pam(jozefkova,127.0.0.1): #1/1 style=1 msg=Password: Oct 15 13:04:49 linux dovecot: auth-worker(default): pam(jozefkova,127.0.0.1): pam_authenticate() failed: Authentication failure (password mismatch?) Oct 15 13:04:51 linux dovecot: auth(default): client out: FAIL 1 user=jozefkova authz So i can see it’s trying to loggin in using pam mech. Is there something i can configure in dovecot userdb or is it something else? I use pam to authenticate my real users… Thank you in advance… — Michal Zila

4 9

Dovecot top stats
by Kilburn Abrahams 15 Oct '15

15 Oct '15

Hi, I have being try to track down top email users to sometime. When I do a network traffic check I can see there is about 15 times more email traffic pulled from mail server than sent. The problem I am trying to track down is which users are the culprit. I have enabled doevcot stats and I can do a doveadm stats dump user but I get a 0 for disk_input, disk_output, read_bytes and write_bytes. I do get mail_read_bytes numbers but I am not sure these numbers are correct. I there a top utility that works well so I can see email traffic from users mailboxes. The doveadm top does not work well. I also tried the perl scripts and that does not do a much better job. Thanks Kilburn

2 2

Re: iterate users with passwd-file passdb?
by Joseph Tam 15 Oct '15

15 Oct '15

Eric Abrahamsen writes: > Simply: Is it possible to iterate over users if I'm using the > passwd-file passdb driver? Do I need a SQL-based driver if I want to > iterate? What do you mean by "iterate"? If you mean whether you can look up a password entry in a multi-entry file, then yes, definitely. If you mean to sequentially go through it and do a first/last/best match, probably not. Joseph Tam <jtam.home(a)gmail.com>

4 4

Emails with sender MISSING_MAILBOX@missing_domain
by grupo correo 15 Oct '15

15 Oct '15

Hello, we are working in the migration from courier-imap to dovecot 2.2.10-4.el7_0.1.x86_64. Some emails that send a internal application show as sender "MISSING_MAILBOX@missing_domain", i use like email client Horde using dovecot like server. But if i open that email with Horde and courier-imap i can see the correct email sender. I think that the email of the sender is no correct or not accomplish some RFC. Can anyone help me to understand this? Thank you

3 2

Re: Problems sync with mail client MAC and dovecot-2.2.10-4.el7_0.1.el7_0.1.x86_64
by grupo correo 14 Oct '15

14 Oct '15

> > On 2015-10-13 09:20, grupo correo wrote: > > Hello, > > > > i have installed Centos 7.1.1503 with Dovecot 2.2.10-4.el7_0.1. With > > Thunderbird all works fine, but when i configure the email client of > > Mac > > (Yosemite) with IMAP i can see a error in the log and the client not > > see > > the emails: > > > > Oct 9 14:31:34 localhost dovecot: imap(xxxxxxx@xxxxxxx): Fatal: > > master: > > service(imap): child 18639 killed with signal 11 (core dumps disabled) > > Do you have more logs? > > Have you enabled mail_debug = yes to get more verbose logs? > > > > > I have read the instructions of http://www.dovecot.org/bugreport.html, > > but > > core file is not writing. > > > > Does anyone have this issues? I think that can be a problem in the > > configuration > > Please share your doveconf -n output. > > > Best regards > > regards > christian > Attached the doveconf -n Yes i have mail_debug = yes into file conf.d/10-logging.conf I paste the rest of log: Oct 13 21:27:17 localhost dovecot: imap: Debug: Loading modules from directory: /usr/lib64/dovecot Oct 13 21:27:17 localhost dovecot: imap: Debug: Module loaded: /usr/lib64/dovecot/lib01_acl_plugin.so Oct 13 21:27:17 localhost dovecot: imap: Debug: Module loaded: /usr/lib64/dovecot/lib02_imap_acl_plugin.so Oct 13 21:27:17 localhost dovecot: imap: Debug: Module loaded: /usr/lib64/dovecot/lib10_quota_plugin.so Oct 13 21:27:17 localhost dovecot: imap: Debug: Module loaded: /usr/lib64/dovecot/lib11_imap_quota_plugin.so Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Debug: Effective uid=56396, gid=55000, home=/VMAIL/xxxxxxxxxxxxxx Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Debug: Quota root: name=User quota backend=maildir args= Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Debug: Quota grace: root=User quota bytes=0 (10%) Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Debug: Namespace inbox: type=private, prefix=INBOX., sep=., inbox=yes, hidden=no, list=children, subscriptions=yes location=maildir:~/Maildir Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Debug: maildir++: root=/VMAIL/xxxxxxxxxxxxxx/Maildir, index=, indexpvt=, control=, inbox=/VMAIL/xxxxxxxxxxxxxx/Maildir, alt= Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Debug: acl: initializing backend with data: vfile Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Debug: acl: acl username = xxxxxxxxxxxxxx Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Debug: acl: owner = 1 Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Debug: acl vfile: Global ACL directory: (none) Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Debug: Namespace : type=private, prefix=, sep=, inbox=no, hidden=yes, list=no, subscriptions=no location=fail::LAYOUT=none Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Debug: none: root=, index=, indexpvt=, control=, inbox=, alt= Oct 13 21:27:17 localhost dovecot: imap(xxxxxxxxxxxxxx): Fatal: master: service(imap): child 2464 killed with signal 11 (core dumps disabled)

2 1

Thanks for Dovecot
by Steve Litt 14 Oct '15

14 Oct '15

Hi all, Thanks for making Dovecot. I just transitioned from Debian Wheezy to Void Linux. It was fairly easy to get Dovecot working on my Void box, and having Dovecot makes all of my email activities easier by doing one thing and doing it right. Thank you for such great software. SteveT

6 5

Indexing fails with .. FIELDS_INDEX_EXTENSION).c_str() )' failed
by Akash 14 Oct '15

14 Oct '15

Hi, Mailing list archives suggest that this problem has been fixed in the older versions itself but I am getting the error still while trying to doveadm index a large folder of emails. Sometimes it throws error after 30000, something 40000, the latest it gave up after 111000. But it just never completes. 111000/322080doveadm: /home/stephan/packages/wheezy/i386/clucene-core-2.3.3.4/src/core/CLucene/index/DocumentsWriter.cpp:210: std::string lucene::index::DocumentsWriter::closeDocStore(): Assertion `numDocsInStore*8 == directory->fileLength( (docStoreSegment + "." + IndexFileNames::FIELDS_INDEX_EXTENSION).c_str() )' failed. Aborted I am using dovecot 2:2.2.19-1~auto+7& libclucene-core1:i386 2.3.3.4-4 from debian wheezy backports. Please advice. -Akash

3 2

Re: iterate users with passwd-file passdb?
by Joseph Tam 14 Oct '15

14 Oct '15

Eric Abrahamsen <eric(a)ericabrahamsen.net> writes: >>> Simply: Is it possible to iterate over users if I'm using the >>> passwd-file passdb driver? Do I need a SQL-based driver if I want to >>> iterate? >> >> What do you mean by "iterate"? If you mean whether you can look up a >> password entry in a multi-entry file, then yes, definitely. If you >> mean to sequentially go through it and do a first/last/best match, >> probably not. > > Basically I just mean the -A argument to the doveadm commands. For > example, iterate through all the users and run sa-learn on each user's > learn/spam folder. If it's got to be SQL, it won't kill me... Ah. Yes, you can use -A and iterate through users, subject to any constraints such as first_valid_uid, last_valid_uid, etc. Joseph Tam <jtam.home(a)gmail.com>

1 0

Dovecot - Postfix with HAproxy
by Michael JOIGNY 13 Oct '15

13 Oct '15

Hi Everyone, I wouldlike to set up a postfix-dovecot with HA using HAproxy but im facing issues. I've followed this documentation : http://wiki2.dovecot.org/HAProxy (pour dovecot) http://blog.haproxy.com/2012/06/30/efficient-smtp-relay-infrastructure-with… (pour postfix) Package's version : dovecot : 2:2.2.19 (>= 2.2.19 pour proxy protocol) haproxy : 1.5.14 postfix : 2.11.2-1 (>2.10 pour postscreen) A part of my configuration : ##HAPROXY #postfix listen smtp bind mail.xx.xx:465 balance roundrobin timeout client 1m timeout connect 5s no option http-server-close mode tcp option smtpchk option tcplog server tst tst.xxx:10465 send-proxy server tst2 tst2.xxx:10465 send-proxy server tst3 tst3.xxx:10465 send-proxy #dovecot listen imap bind mail.xxx.xx:993 timeout client 1m no option http-server-close balance leastconn stick store-request src stick-table type ip size 200k expire 30m mode tcp option tcplog server tst tst.xxx:10993 send-proxy-v2 server tst2tst2.xxx:10993 send-proxy-v2 server tst3 tst3.xxx:10993 send-proxy-v2 ##POSTFIX postix main.cf #Haproxy proxy protocol postscreen_upstream_proxy_protocol = haproxy postfix master.cf #haproxy 10465 inet n – n – 1 postscreen smtpd pass – – n – – smtpd S ##DOVECOT # 2.2.19 (719e7f8fd70b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.9 # OS: Linux 2.6.32-41-pve x86_64 Debian 7.9 simfs auth_debug = yes auth_verbose = yes disable_plaintext_auth = no *haproxy_timeout = 5 secs** **haproxy_trusted_networks = x.x.x.x* log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/mailbox/%d/%n mail_max_userip_connections = 0 mail_privileged_group = mail 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 passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_global_path = /mailbox/globalsieverc } protocols = sieve pop3 imap service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-master { mode = 0660 user = mailboxes } unix_listener auth-userdb { group = mail mode = 0666 user = dovecot } user = root } service imap-login { inet_listener imap { port = 0 } inet_listener imap_haproxy { haproxy = yes port = 10993 } inet_listener imaps { address = * port = 993 } process_limit = 450 } service pop3-login { inet_listener pop3 { address = * port = 110 } process_limit = 180 } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/star.key userdb { args = uid=5000 gid=5000 home=/mailbox/%d/%n/ allow_all_users=yes driver = static } protocol imap { imap_client_workarounds = } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } protocol sieve { mail_location = maildir:/mailbox } protocol lda { auth_socket_path = /var/run/dovecot/auth-master hostname = xxx.yyy.com log_path = /var/log/dovecot/deliver.log mail_plugin_dir = /usr/lib/dovecot/modules mail_plugins = sieve postmaster_address = postmaster(a)xxx.yyy rejection_reason = Your message to <%t> was automatically rejected:%n%r rejection_subject = Rejected: %s sendmail_path = /usr/sbin/sendmail } With my mail client : With an IMAP connection, logs below, i don't understand why my login is empty ... dovecot: imap-login: Disconnected: Too many invalid commands (no auth attempts in 0 secs): *user=<>*, rip=mon_ip_publique, lip=ip_publique_haproxy, session= xxx With a SMTP connection, logs below, i have a timeout. postfix/postscreen[16654]: CONNECT from [my public ip]:49942 to [my haproxy public ip]:465 postfix/postscreen[16654]: PREGREET 166 after 0 from [mon ip publique]:49942: \22\3\1\161\1\157\3\3+0E\b\213\131\177\173>\r/\213\177i\223k”FjA#\144\145\153\vP\\\155HL\190 If someone could help me, thanks. Kind regards. --

2 1

Dualstack IPv4/IPv6 setup with directors
by Heiko Schlittermann 13 Oct '15

13 Oct '15

Hi, still using 2.2.9, I've two directors, and these directors use both IPv4/IPv6 addresses. `host directors.<domain>` returns one A and AAA for each of the two directors: directors.<domain> has address 149.x.y.96 (director1) directors.<domain> has address 149.x.y.97 (director2) directors.<domain> has IPv6 address 2001:x:y:f33::5:1 (director1) directors.<domain> has IPv6 address 2001:x:y:f33::5:2 (director2) But connecting the the neighbor director gives: Oct 13 21:23:29 director1 dovecot: director: Warning: Director 2001:x:y:f33::5:2:9090/left disconnected us with reason: Invalid input: ME 149.x.y.96 9090 Oct 13 21:23:29 director1 dovecot: director: Error: director(149.x.y.97:9090/out): connect() failed: Connection refused Oct 13 21:23:29 director1 dovecot: director: Warning: net_connect_ip(): ip->family != my_ip->family Oct 13 21:23:29 director1 dovecot: director: Error: Remote director thinks it's someone else (connected to 2001:x:y:f33::5:1:9090, remote says it's 149.x.y.96:9090) I assume it's because the director uses only one (IPv4 OR IPv6) address for it's own identity, right? Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de ---------------------------- internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} - gnupg encrypted messages are welcome --------------- key ID: F69376CE - ! key id 7CBF764A and 972EAC9F are revoked since 2015-01 ------------ -

2 2

Storage Design (Regligious War, Whatever)
by Kelsey Cummings 13 Oct '15

13 Oct '15

We've been running dovecot director setup using MAILDIR++ spools on NFS served by 4 (aging) Netapp clustered filers and are considering modernizing our storage. There's nothing particularly wrong with the existing storage except the age, density and power consumption don't compare well when against new systems. Refreshing the Netapps is an option but they come at a substantial cost. The last time we were looking one of the recommended hot DIY setups was Linux NFS backed by XFS on N mirrors but this predated the availability of stable ZFS in FreeBSD or Linux as well as products like FreeNAS. A FreeBSD NFS/ZFS filer on commodity hardware with zil/l2arc on a PCIe SSD seems like an attractive, affordable and easily scaled out solution which also would allow us to leverage compression at the filesystem layer. Does anyone have any experience running ZFS spool storage? If so, how do you handle DR/HA for spool storage? Thoughts on how this might compare to using DRBD? Any pitfalls to watch out for or general pointers? Suggestions on pool configuration? -K

1 0

Unknown cache fields?
by Larry Rosenman 13 Oct '15

13 Oct '15

I assume this is expected, but just checking. I do NOT use POP3. Oct 5 09:41:20 thebighonker dovecot: indexer-worker(mrm): Debug: Ignoring unknown cache field: pop3.order Oct 5 09:41:20 thebighonker dovecot: indexer-worker(mrm): Debug: Ignoring unknown cache field: binary.parts Oct 5 09:41:20 thebighonker dovecot: indexer-worker(mrm): Debug: Ignoring unknown cache field: body.snippet -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larryrtx(a)gmail.com US Mail: 7011 W Parmer Ln, Apt 1115, Austin, TX 78729-6961

2 1

doveadm index assertion failed
by Nick Rosier 13 Oct '15

13 Oct '15

Hi, one of my mailboxes returns following error when I run doveadm index on it: Panic: file charset-iconv.c: line 85 (charset_to_utf8_try): assertion failed: (srcleft <= CHARSET_MAX_PENDING_BUF_SIZE) OS: FreeBSD 10.2 Dovecot: 2.1.19 Tika: 1.10 SOLR: 5.3.1 Running doveadm -D index does not show any more information indicating what causes this error (mail/folder/...) How I can find what is causing this error? Rgds, N.

2 1

Re: bug report: dovecot-imapd core dump
by Tamas Papp 13 Oct '15

13 Oct '15

Hi, could not find it -- back to the list, maybe someone can suggest a fix/workaround. Best, Tamas On Wed, Oct 07 2015, Dominik Breu wrote: > Hello, > > yeah this one looks familiar to me can you search the list back in > september there was a somewhat similar bug with thunderbird imho timo > posted a notice about it. > > greetings, > > dominik > > Am Mittwoch, den 07.10.2015, 15:53 +0200 schrieb Tamas Papp: >> Hi Dominik, >> >> Thanks for the help, the backtrace is here (I did not sent it to the >> list since I am not sure if it contains password or message >> information, >> sorry but I am unfamiliar with these things). >> >> Core was generated by `dovecot/imap'. >> Program terminated with signal SIGSEGV, Segmentation fault. >> #0 0x00007f404e58e3b6 in mail_index_keywords_unref >> #(_keywords=_keywords@entry=0x7ffecb8adeb8) at mail-index.c:383 >> 383 mail-index.c: No such file or directory. >> (gdb) bt full >> #0 0x00007f404e58e3b6 in mail_index_keywords_unref >> #(_keywords=_keywords@entry=0x7ffecb8adeb8) at mail-index.c:383 >> keywords = 0x7f404e27066d <buffer_alloc+45> >> __FUNCTION__ = "mail_index_keywords_unref" >> #1 0x00007f404e559975 in mailbox_keywords_unref >> (keywords=keywords@entry=0x7ffecb8adeb8) at mailbox-keywords.c:94 >> No locals. >> #2 0x00007f404ea254ad in cmd_append_handle_args >> (nonsync_r=0x7ffecb8ade8f, >> #args=<optimized out>, cmd=0x7f4050bc3250) at cmd-append.c:602 >> ctx = 0x7f4050bc3348 >> flags_list = 0x7f4050bcc840 >> flags = 9 >> keywords_list = 0x7f4050bc33f0 >> internal_date_str = 0x7f4050bcca00 "17-Sep-2015 14:19:23 >> +0200" >> internal_date = -1 >> timezone_offset = 0 >> keywords = 0x0 >> ret = <optimized out> >> client = 0x7f4050bc2670 >> cat_list = 0x0 >> input = <optimized out> >> valid = <optimized out> >> #3 cmd_append_parse_new_msg (cmd=cmd@entry=0x7f4050bc3250) at >> cmd-append.c:770 >> client = <optimized out> >> ctx = 0x7f4050bc3348 >> args = 0x7f4050bcc488 >> msg = <optimized out> >> arg_min_count = <optimized out> >> fatal = 255 >> nonsync = true >> last_literal = <optimized out> >> ret = <optimized out> >> __FUNCTION__ = "cmd_append_parse_new_msg" >> #4 0x00007f404ea25a17 in cmd_append (cmd=0x7f4050bc3250) at >> cmd-append.c:932 >> client = 0x7f4050bc2670 >> ctx = 0x7f4050bc3348 >> mailbox = 0x7f4050bafb78 "Cemex" >> #5 0x00007f404ea30e4c in command_exec (cmd=cmd@entry=0x7f4050bc3250) >> at >> imap-commands.c:158 >> hook = 0x7f4050bad0d0 >> ret = <optimized out> >> #6 0x00007f404ea2fd62 in client_command_input (cmd=0x7f4050bc3250) >> at >> imap-client.c:780 >> client = 0x7f4050bc2670 >> command = <optimized out> >> __FUNCTION__ = "client_command_input" >> #7 0x00007f404ea2fe16 in client_command_input (cmd=0x7f4050bc3250) >> at >> imap-client.c:841 >> client = 0x7f4050bc2670 >> command = <optimized out> >> __FUNCTION__ = "client_command_input" >> #8 0x00007f404ea3014d in client_handle_next_command >> (remove_io_r=<synthetic >> pointer>, client=0x7f4050bc2670) at imap-client.c:879 >> ---Type <return> to continue, or q <return> to quit--- >> No locals. >> #9 client_handle_input (client=0x7f4050bc2670) at imap-client.c:891 >> _data_stack_cur_id = 3 >> remove_io = false >> handled_commands = false >> client = 0x7f4050bc2670 >> #10 0x00007f404ea304f5 in client_input (client=0x7f4050bc2670) at >> imap-client.c:933 >> cmd = 0xf013c >> output = 0x7f4050bc30a0 >> bytes = 135 >> __FUNCTION__ = "client_input" >> #11 0x00007f404e285247 in io_loop_call_io (io=0x7f4050bc3170) at >> ioloop.c:388 >> ioloop = 0x7f4050bac720 >> t_id = 2 >> #12 0x00007f404e286079 in io_loop_handler_run >> (ioloop=ioloop@entry=0x7f4050bac720) at ioloop-epoll.c:220 >> ctx = 0x7f4050bad3b0 >> io = <optimized out> >> tv = {tv_sec = 1799, tv_usec = 999282} >> events_count = <optimized out> >> msecs = <optimized out> >> ret = 1 >> i = 0 >> j = <optimized out> >> call = <optimized out> >> __FUNCTION__ = "io_loop_handler_run" >> #13 0x00007f404e284d88 in io_loop_run (ioloop=0x7f4050bac720) at >> ioloop.c:412 >> __FUNCTION__ = "io_loop_run" >> #14 0x00007f404e231de3 in master_service_run (service=0x7f4050bac5b0, >> callback=<optimized out>) at master-service.c:566 >> No locals. >> #15 0x00007f404ea2424e in main (argc=1, argv=0x7f4050bac390) at >> main.c:400 >> set_roots = {0x7f404ec489c0 <imap_setting_parser_info>, 0x0} >> login_set = {auth_socket_path = 0x7f4050ba4048 "\001", >> postlogin_socket_path = 0x0, postlogin_timeout_secs = 60, callback = >> 0x7f404ea39f40 <login_client_connected>, >> failure_callback = 0x7f404ea39c20 <login_client_failed>, >> request_auth_token = 1} >> service_flags = <optimized out> >> storage_service_flags = <optimized out> >> username = 0x0 >> c = <optimized out> >> (gdb) quit >> >> Best, >> >> Tamas >> >> On Wed, Oct 07 2015, Dominik Breu wrote: >> >> > Hello >> > >> > Tamas it would be a better backtace when you have installed the >> > dovecot >> > debug symboly mostly located under dovecote-dbg in apt. Further >> > debug >> > help can you find in the wiki. >> > >> > greetings >> > >> > dominik >> > >> > Am Mittwoch, den 07.10.2015, 15:09 +0200 schrieb Tamas Papp: >> > > Typical log message: >> > > >> > > Oct 7 11:39:36 hostname dovecot: imap(username): Fatal: master: >> > > service(imap): child 14864 killed with signal 11 (core dumped) >> > > >> > > What triggers the problem: >> > > >> > > User moving multiple messages to a subfolder via IMAP (from >> > > another >> > > account, on another server, client: Thunderbird). Moving single >> > > messages >> > > either does not trigger the problem, or with much lower >> > > probability >> > > (could not reproduce). >> > > >> > > Version: >> > > $ dpkg -l 'dovecot*' >> > > Desired=Unknown/Install/Remove/Purge/Hold >> > > > Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig >> > > > -aWait/Trig-pend >> > > > / Err?=(none)/Reinst-required (Status,Err: uppercase=bad) >> > > > > / Name Version >> > > > > Architecture Description >> > > +++-=====================================-======================= >> > > -======================= >> > > -================================================================ >> > > ==== >> > > ============ >> > > un dovecot-common <none> >> > > <none> (no description available) >> > > ii dovecot-core 1:2.2.9-1ubuntu5 >> > > amd64 secure POP3/IMAP server - core files >> > > un dovecot-gssapi <none> >> > > <none> (no description available) >> > > ii dovecot-imapd 1:2.2.9-1ubuntu5 >> > > amd64 secure POP3/IMAP server - IMAP daemon >> > > un dovecot-ldap <none> >> > > <none> (no description available) >> > > un dovecot-lmtpd <none> >> > > <none> (no description available) >> > > un dovecot-managesieved <none> >> > > <none> (no description available) >> > > un dovecot-mysql <none> >> > > <none> (no description available) >> > > un dovecot-pgsql <none> >> > > <none> (no description available) >> > > un dovecot-pop3d <none> >> > > <none> (no description available) >> > > un dovecot-sieve <none> >> > > <none> (no description available) >> > > un dovecot-solr <none> >> > > <none> (no description available) >> > > un dovecot-sqlite <none> >> > > <none> (no description available) >> > > tamas@szob:~$ lsb_release -a >> > > No LSB modules are available. >> > > Distributor ID: Ubuntu >> > > Description: Ubuntu 15.04 >> > > Release: 15.04 >> > > Codename: vivid >> > > >> > > Also tried 2.2.18 from Ubuntu wiley, same results. >> > > >> > > Backtrace (I am not sure this is useful, extraced core from >> > > Ubuntu's >> > > Apport): >> > > >> > > (gdb) bt full >> > > #0 0x00007f404e58e3b6 in mail_index_keywords_unref () from >> > > /usr/lib/dovecot/libdovecot-storage.so.0 >> > > No symbol table info available. >> > > #1 0x00007f404ea254ad in _start () >> > > No symbol table info available. >> > > >> > > Any help would be appreciated, I am happy to provide more info if >> > > necessary. >> > > >> > > Tamas

2 2

dovecot as proxy and verification of the backends certificate
by Heiko Schlittermann 13 Oct '15

13 Oct '15

Hello, I'm using a dovecot as proxy, connecting to one or more backends. The backends use X.509 certificates. The proxy's passdb returns extra fields: user=foo proxy host=backend1.<domain> ssl=yes nopassword=y Thus the proxy connects to the backend but can't verify the backends certificate. The following comment suggests using ssl_client_ca_file for that. # Directory and/or file for trusted SSL CA certificates. These are used only # when Dovecot needs to act as an SSL client (e.g. imapc backend). The # directory is usually /etc/ssl/certs in Debian-based systems and the file is # /etc/pki/tls/cert.pem in RedHat-based systems. #ssl_client_ca_dir = #ssl_client_ca_file = ssl_client_ca_file = /tmp/certs/ca-local.pem But that does not work! Instead I've to use ssl_ca # PEM encoded trusted certificate authority. Set this only if you intend to use # ssl_verify_client_cert=yes. The file should contain the CA certificate(s) # followed by the matching CRL(s). (e.g. ssl_ca = </etc/ssl/certs/ca.pem) # ssl_ca = ssl_ca = </tmp/certs/ca-local.pem Bug or feature? Mainly I'm asking because the comments do not indicate that I should have used ssl_ca for this type of operation (dovecot as a SSL client) Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de ---------------------------- internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} - gnupg encrypted messages are welcome --------------- key ID: F69376CE - ! key id 7CBF764A and 972EAC9F are revoked since 2015-01 ------------ -

2 2

Dovecot auth-ldap ignores tls_* settings when using ldaps://
by Heiko Schlittermann 13 Oct '15

13 Oct '15

Hi, I'm using dovecot 2.2.9 (but after checking src/auth/db-ldap.c in 2.2.13 there seems to be the same bug/feature). The userdb and passdb use LDAP. All further configuration is done in auth-ldap.conf.ext. uri = ldaps://<host>/ # tls = tls_cert_file = /etc/ssl/certs/client-cert.pem tls_key_file = /etc/ssl/certs/client-key.file Dovecot ignores the tls_* options. If I use an ldap:// URI and switch on TLS using tls=yes it works as expected. But I do not see any reason why LDAPS should not read the tls_* settings. This small patch solved it for me --- dovecot-2.2.9/src/auth/db-ldap.c 2013-11-24 14:37:39.000000000 +0100 +++ dovecot-2.2.9.hs12/src/auth/db-ldap.c 2015-10-08 21:24:47.051446465 +0200 @@ -1043,7 +1043,7 @@ static void db_ldap_set_tls_options(struct ldap_connection *conn) { - if (!conn->set.tls) + if (!(conn->set.tls || strncmp(conn->set.uris, "ldaps:", 6) == 0)) return; #ifdef OPENLDAP_TLS_OPTIONS It would be great, if somebody can confirm this and if this or some equivalent patch could make it upstream. Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de ---------------------------- internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} - gnupg encrypted messages are welcome --------------- key ID: F69376CE - ! key id 7CBF764A and 972EAC9F are revoked since 2015-01 ------------ -

2 2