- dovecot - dovecot.org

Raw backtrace multiple passwords not allowed
by Leon Kyneur 10 Jul '16

10 Jul '16

Hi Recently enabled support for encrypted passwords on my proxies - CRAM-MD5, DIGEST-MD5, NTLM and APOP to support some new users. Most users are working perfectly though every so often I see this happening in the logs: Jul 09 06:32:51 auth: Error: ldap(user(a)domain.com,192.168.10.90,<mOWiFi431eDKOsBS>): Multiple password values not supported Jul 09 06:32:51 auth: Panic: file passdb-ldap.c: line 99 (ldap_lookup_finish): assertion failed: (password == NULL || scheme != NULL) Jul 09 06:32:51 auth: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x86aae) [0x7ff4db08faae] -> /usr/lib64/dovecot/libdovecot.so.0(+0x86b8e) [0x7ff4db08fb8e] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7ff4db033b5d] -> /usr/lib64/dovecot/auth/libauthdb_ldap.so(+0x720b) [0x7ff4d967a20b] -> /usr/lib64/dovecot/auth/libauthdb_ldap.so(+0x5e2f) [0x7ff4d9678e2f] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x4c) [0x7ff4db0a338c] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xff) [0x7ff4db0a47ef] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7ff4db0a3415] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7ff4db0a35c8] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7ff4db03a033] -> dovecot/auth [13 wait, 1 passdb, 0 userdb](main+0x39c) [0x7ff4db5454ac] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7ff4da61fb15] -> dovecot/auth [13 wait, 1 passdb, 0 userdb](+0xf6a1) [0x7ff4db5456a1] Jul 09 06:32:51 imap-login: Warning: Auth connection closed with 1 pending requests (max 0 secs, pid=8759, EOF) Jul 09 06:32:51 imap-login: Warning: Auth connection closed with 1 pending requests (max 1 secs, pid=8764, EOF) Password debug shows: Jul 09 06:38:25 auth: Debug: ldap(user(a)domain.com,192.168.10.90,<xSSOKi438ODKOsBS>): Credentials: 4b616e6761733138 Jul 09 06:38:27 auth: Debug: client passdb out: FAIL 2541 user=user(a)domain.com pass=NotPassword original_user=user Jul 09 06:38:37 auth: Debug: passwd-file(tassiedevil,192.168.10.90,<weQKKy438eDKOsBS>): username changed user -> user(a)domain.com Jul 09 06:38:37 auth: Debug: passwd-file(user(a)domain.com,192.168.10.90,<weQKKy438eDKOsBS>): Allowing any password Jul 09 06:38:37 auth: Debug: ldap(user(a)domain.com,192.168.10.90,<weQKKy438eDKOsBS>): pass search: base=o=domains,dc=mail,dc=com scope=subtree filter=(&(objectClass=mail)(status=active)(|(|(mail=user@domain.com)(&(uid=user@domain.com)))(&(enabledService=shadowaddress)(shadowAddress user(a)domain.com)))) fields=mail,userPlaintextPassword,userPlaintextPassword,mailstoreHost Jul 09 06:38:37 auth: Debug: ldap(user(a)domain.com,192.168.10.90,<weQKKy438eDKOsBS>): result: mail=user(a)domain.com userPlaintextPassword=NotPassword; mail,userPlaintextPassword unused Jul 09 06:38:37 auth: Debug: ldap(user(a)domain.com,192.168.10.90,<weQKKy438eDKOsBS>): result: mail=user(a)domain.com userPlaintextPassword=NotPassword; mailstoreHost missing Jul 09 06:38:37 auth: Debug: ldap(user(a)domain.com,192.168.10.90,<weQKKy438eDKOsBS>): PLAIN( Jenni) != 'NotPassword' Jul 09 06:38:39 auth: Debug: client passdb out: FAIL 2826 user=user(a)domain.com original_user=user This particular user has a space in their password.. some other users do not when seeing this error. I run multiple passdb and config is: passdb { args = /etc/dovecot/dovecot-ldap-proxy-alias.conf.ext default_fields = nopassword=y password= driver = ldap result_failure = continue-fail result_internalfail = continue-fail result_success = continue-ok } passdb { args = scheme=plain username_format=%l@%d /etc/dovecot/passwd.domains default_fields = nopassword=y password= driver = passwd-file result_success = continue-fail } passdb { args = /etc/dovecot/dovecot-ldap-proxy.conf.ext driver = ldap } LDAP passdb specifies 'PLAIN' as default_pass_scheme. [root@S605 dovecot]# dovecot --version 2.2.24 (a82c823) Any ideas what's going on here?

2 3

Dovecot threading implementation
by Gabriele Bulfon 08 Jul '16

08 Jul '16

Hi, I was trying to compare avrious thread refs/references implementation, both server side and client side. While testing dovecot, it looks to me that issuing thread=references or thread=refs I get the same response, while the refs drafts says it should reverse the date ordering inside a branch. Is this correct? Does Dovecot implements references and refs with same sorting? Also, cyrus has subject grouping included in references (which is bad!). What's dovecot doing in references alg? Thanks for any help, Gabriele ---------------------------------------------------------------------------------------- Sonicle S.r.l. : http://www.sonicle.com Music: http://www.gabrielebulfon.com Quantum Mechanics : http://www.cdbaby.com/cd/gabrielebulfon

1 0

Re: Dovecot 2.2.25 compiling error
by Joseph Tam 08 Jul '16

08 Jul '16

> Well, tried with or without patches, but got still same error: > > sha1.h:80: error: static or type qualifiers in abstract declarator For what it's worth, I get the same error compiling on Solaris 10. It may be because I have a rather old gcc (3.4.4). Editing out the "static" keyword from config.h allowed it to finish the compile. Joseph Tam <jtam.home(a)gmail.com>

2 1

Dovecot 2.2.25 compiling error
by Mart Pirita 08 Jul '16

08 Jul '16

Hello. I cant build 2.2.25, but I can build fine version 2.2.24 with same options: RedHat based customized distro, 2.6.28.10 kernel Build options: export CPPFLAGS export LDFLAGS CPPFLAGS=-I/usr/local/ssl/include LDFLAGS=-L/usr/local/ssl/lib ./configure \ --prefix=/usr \ --with-ssl=openssl \ --with-ssldir=/etc/ssl \ --sysconfdir=/etc \ --without-vpopmail \ --with-pam \ --without-bsdauth \ --without-sql \ --without-nss \ --without-ldap \ --without-pgsql \ --without-mysql \ --without-sqlite \ --with-rundir=/var/run/dovecot\ --without-deliver \ --without-gssapi Build error: libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/local/ssl/include -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -MT guid.lo -MD -MP -MF .deps/guid.Tpo -c guid.c -fPIC -DPIC -o .libs/guid.o In file included from guid.c:6: sha1.h:80: error: static or type qualifiers in abstract declarator make[4]: *** [guid.lo] Error 1 make[4]: Leaving directory `/usr/src/redhat/BUILD/dovecot-2.2.25/src/lib' make[3]: *** [all] Error 2 make[3]: Leaving directory `/usr/src/redhat/BUILD/dovecot-2.2.25/src/lib' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/src/redhat/BUILD/dovecot-2.2.25/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/src/redhat/BUILD/dovecot-2.2.25' make: *** [all] Error 2 Please advise? -- Mart

4 8

Deletion of mail from Junk mailbox
by Doug Hardie 08 Jul '16

08 Jul '16

I have a pigeon sive running which directs some of my received mail to the Junk folder. That works just fine. However, a couple minutes later, it is moved to Deleted mailbox and deleted from Junk. At first I thought my client was doing that so I shut down the client and it still happens. Here are the log entries: Jul 2 00:36:31 mail dovecot: imap(doug): copy from INBOX: box=Junk, uid=10842, msgid=<F3C67E609C1A1BC4DB924CEA5FE12C76@ze>, size=3340, from="jnilj" <hr(a)bjwmt.com> Jul 2 00:36:31 mail dovecot: imap(doug): delete: box=INBOX, uid=55719, msgid=<F3C67E609C1A1BC4DB924CEA5FE12C76@ze>, size=3340, from="jnilj" <hr(a)bjwmt.com> Jul 2 00:39:33 mail dovecot: imap(doug): copy from Junk: box=Deleted Messages, uid=31049, msgid=<F3C67E609C1A1BC4DB924CEA5FE12C76@ze>, size=3340, from="jnilj" <hr(a)bjwmt.com> Jul 2 00:39:33 mail dovecot: imap(doug): delete: box=Junk, uid=10842, msgid=<F3C67E609C1A1BC4DB924CEA5FE12C76@ze>, size=3340, from="jnilj" <hr(a)bjwmt.com> Jul 2 00:50:29 mail dovecot: imap(doug): expunge: box=Junk, uid=10842, msgid=<F3C67E609C1A1BC4DB924CEA5FE12C76@ze>, size=3340, from="jnilj" <hr(a)bjwmt.com> Jul 2 00:50:29 mail dovecot: imap(doug): expunge: box=INBOX, uid=55719, msgid=<F3C67E609C1A1BC4DB924CEA5FE12C76@ze>, size=3340, from="jnilj" <hr(a)bjwmt.com> Is this the intended way the Junk maibox is supposed to work? I couldn't find any settings that appear to control (or affect) this behavior. — Doug

3 3

Released Pigeonhole v0.4.15 for Dovecot v2.2.25.
by Stephan Bosch 08 Jul '16

08 Jul '16

Hello Dovecot users, I have completed the final release. I found a few more problems while testing this release, so a few more fixes are included. I also added a behavioral change to the vacation extension. Changelog v0.4.15: * vacation extension: The sieve_user_email setting is now used in the check for implicit delivery. - imapsieve plugin: For any mail transaction, the mailbox was opened a second time, even if no mailbox rule matched. This was unintentional, useless and caused problems when the imapsieve plugin was used with other plugins like acl. - extprograms plugin: Significantly improved error handling. No stream errors were logged. - extprograms plugin: Fixed bug in handling of result code from remote program (script service). - extprograms plugin: Connection to remote program service was not retried. - Several small fixes based on static analysis. - Fixed handling of quoted string localparts in email addresses. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.15.ta… http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.15.ta… Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

Re: Compile error Dovecot2-pigeonhole
by Maximus 07 Jul '16

07 Jul '16

Thanks, you've saved my day. ;) Switch to clang and everything looks fine.

1 0

Compile error Dovecot2-pigeonhole
by Maximus 07 Jul '16

07 Jul '16

FreeBSD 9.3 Dovecot 2.25 (7be1766) I'm trying to install Dovecot2-pigeonhole-0.4.14_2 from ports. Get an error: cc1: error: unrecognized command line option "-Wno-duplicate-decl-specifier" With options MAKE_JOBS_UNSAFE=yes: cc1: error: unrecognized command line option "-Wno-duplicate-decl-specifier" *** [edit-mail.lo] Error code 1 Stop in /usr/ports/mail/dovecot2-pigeonhole/work/dovecot-2.2-pigeonhole-0.4.14/src/l ib-sieve/util. *** [all-recursive] Error code 1 Stop in /usr/ports/mail/dovecot2-pigeonhole/work/dovecot-2.2-pigeonhole-0.4.14/src/l ib-sieve. *** [all-recursive] Error code 1 Stop in /usr/ports/mail/dovecot2-pigeonhole/work/dovecot-2.2-pigeonhole-0.4.14/src. *** [all-recursive] Error code 1 Stop in /usr/ports/mail/dovecot2-pigeonhole/work/dovecot-2.2-pigeonhole-0.4.14. *** [all] Error code 1 Stop in /usr/ports/mail/dovecot2-pigeonhole/work/dovecot-2.2-pigeonhole-0.4.14. *** [do-build] Error code 1 Stop in /usr/ports/mail/dovecot2-pigeonhole. *** [stage] Error code 1 I was trying to compile from sources. Same error. Any suggestions?

3 2

LDA autocreate/autosubscribe per namespace?
by Andreas Ntaflos 07 Jul '16

07 Jul '16

Using Dovecot 2.2.25 and Pigeonhole 0.4.14. I can provide the output of doveconf -n if needed. We use a moderately clever global Sieve script to create a read-only (using ACLs) backup/archive of all incoming and outgoing mails. Mail messages filtered this way are filed into folders in a namespace called "Backup", e.g. Backup/sent-backup/${year}/${month} and Backup/received-backup/${year}/${month}. The Sieve script in question can be found at the end of this message for reference. Now obviously we generally want mailboxes to be created automatically, so we set lda_mailbox_autocreate = yes in dovecot.conf. We also want regular mailboxes, created by our users' own Sieve scripts, to be autocreated and autosubscribed, so we also set lda_mailbox_autosubscribe = yes in dovecot.conf. But we *don't* want the Backup mailboxes to be subscribed automatically, because our users usually only need access to those when they want to restore messages accidentally deleted from their INBOX or other folders. So the idea is to keep these Backup mailboxes unsubscribed, which also saves lots of space and network traffic on the user side. When a user then wants to restore a deleted mail message they subscribe to the right Backup folder and copy the message back to their INBOX (and then unsubscribe again). Is there a way to control autocreate/autosubscribe per namespace? Currently it doesn't look that way, and lda_mailbox_autocreate/lda_mailbox_autosubscribe are valid globally. The "Backup" namespace is configured this way: namespace backup { hidden = no list = yes inbox = no location = maildir:~/Maildir-backup prefix = Backup/ separator = / type = private } This is the Sieve script in /etc/dovecot/sieve.d/before/002-backup-mails.sieve: require ["subaddress", "fileinto", "copy", "envelope", "imap4flags", "variables", "date", "mailbox" ]; if currentdate :matches "year" "*" { set "year" "${1}"; } if currentdate :matches "month" "*" { set "month" "${1}"; } # This makes use of sender_bcc_maps in Postfix if envelope :detail "to" "sent-backup" { fileinto :flags "\\Seen" "Backup/sent-backup/${year}/${month}"; stop; } # We only want to backup incoming mail if it is not marked as spam. if header :contains "X-Spam-Flag" ["YES"] { discard; stop; } else { fileinto :copy :flags "\\Seen" "Backup/received-backup/${year}/${month}"; } Thanks, Andreas

1 0

duplicated mail in users inbox only
by Tom Priebe 07 Jul '16

07 Jul '16

Hello, one of my users has the issue that some mails seem to get doubled -- but only in their inbox. The mail is bcc'd to them and the original recipient receives one copy as intended. The log shows nothing extraordinary, postfix, dovecot and sieve are certain that they received and delivered one single mail (per user). Further research showed that the doubled mails' mailbox files have the same inode, which seems inexplicable. I'm using dovecot 2.2.13 replicated over two servers (Master-Master). Duplication seems to happen regardless of the receiving server, yet still not all mails they receive with them in bcc are duplicated. Here's doveconf -n > # 2.2.13: /etc/dovecot/dovecot.conf > # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.3 > auth_gssapi_hostname = mail.net.t-labs.tu-berlin.de > auth_mechanisms = login plain gssapi > auth_username_format = %n > auth_verbose = yes > default_client_limit = 1024 > default_process_limit = 1024 > default_vsz_limit = 512 M > doveadm_password = supersecretpassword > listen = *, [::] > log_timestamp = "%Y-%m-%d %H:%M:%S " > login_log_format_elements = user=<%u> method=%m rip=%r lip=%l > %c % > mail_location = maildir:~/Maildir > mail_plugins = " notify replication" > 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 ihave > 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 = failure_show_msg=yes dovecot > driver = pam > } > plugin { > mail_replica = remote:vmail@mail1.inet.tu-berlin.de > sieve = /mail/home/%u/.dovecot.sieve > sieve_dir = /mail/home/%u/sieve > sieve_max_redirects = 20 > } > postmaster_address = postmaster(a)net.t-labs.tu-berlin.de > protocols = imap sieve > service aggregator { > fifo_listener replication-notify-fifo { > user = vmail > } > unix_listener replication-notify { > user = vmail > } > } > service anvil { > chroot = empty > client_limit = 4096 > process_limit = 1 > } > service auth { > client_limit = 4096 > unix_listener /var/spool/postfix/private/auth { > group = postfix > mode = 0660 > user = postfix > } > unix_listener auth-master { > mode = 0600 > user = vmail > } > unix_listener auth-userdb { > mode = 0600 > user = vmail > } > user = root > } > service doveadm { > inet_listener { > port = 12345 > ssl = yes > } > } > service imap-login { > client_limit = 1024 > inet_listener imap { > port = 143 > } > inet_listener imaps { > port = 993 > ssl = yes > } > process_limit = 100 > process_min_avail = 2 > service_count = 50 > } > service imap { > process_limit = 1024 > } > service managesieve-login { > client_limit = 1024 > executable = /usr/lib/dovecot/managesieve-login > inet_listener sieve { > port = 4190 > } > process_limit = 1024 > process_min_avail = 20 > service_count = 1 > } > service managesieve { > process_limit = 1024 > } > service pop3-login { > client_limit = 1024 > inet_listener pop3 { > port = 110 > } > inet_listener pop3s { > port = 995 > ssl = yes > } > process_limit = 100 > process_min_avail = 2 > service_count = 50 > } > service pop3 { > process_limit = 1024 > } > service replicator { > process_min_avail = 1 > unix_listener replicator-doveadm { > group = vmail > mode = 0660 > } > } > ssl = required > ssl_ca = </etc/ssl/certs/TUB-CA.pem > ssl_cert = </etc/ssl/certs/mail.inet.tu-berlin.de.crt > ssl_cipher_list = > EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+SHA384:EECDH+ECDSA+S > HA256:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EECDH+aRSA+RC4:EECDH:EDH+aR > SA:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS:!RC4 > ssl_client_ca_dir = /etc/ssl/certs > ssl_key = </etc/ssl/private/mail.inet.tu-berlin.de.pem > ssl_prefer_server_ciphers = yes > ssl_protocols = !SSLv2 !SSLv3 > userdb { > driver = passwd > override_fields = home=/mail/home/%u uid=vmail gid=vmail > allow_all_users=yes > } > protocol lda { > auth_socket_path = /var/run/dovecot/auth-master > mail_plugins = " notify replication sieve" > } > protocol sieve { > managesieve_logout_format = bytes=%i/%o > managesieve_max_line_length = 65536 > managesieve_notify_capability = mailto > managesieve_sieve_capability = fileinto reject envelope encoded- > character vacation subaddress comparator-i;ascii-num eric relational > regex imap4flags copy include variables body enotify environment > mailbox date ihave > } Has anyone any suggestions what went wrong? Is this a dovecot configuration issue or is something broken? Regards, Tom -- Group "Intelligent Networks" (INET) Technische Universität Berlin Marchstr. 23 MAR4-4 D-10587 Berlin TEL: +49-30-314-78537

1 0