- dovecot - dovecot.org

passdb {driver = shadow args = override_username=%variable}
by UNIX admin 12 Jul '16

12 Jul '16

Hello list I want to implement override_username = %variable for the "shadow" driver, so that the following works: passdb { driver = shadow args = override_username=%Ln } by "%variable", I mean "Variables" at http://wiki.dovecot.org/Variables. I've hacked up a solution with strtok(3C), but that's a hack and a possible security hole, and I'd rather not implement it. What I really want is to be able to leverage Dovecot's var_expand() call, which, looking at the code, appears to be the function responsible for %variable expansion and formatting. The relevant piece of code seems to be this excerpt in auth/passdb-shadow.c: static enum passdb_result shadow_lookup(struct auth_request *request, struct spwd **spw_r) { auth_request_log_debug(request, AUTH_SUBSYS_DB, "lookup"); *spw_r = getspnam(request->user); if (*spw_r == NULL) { auth_request_log_unknown_user(request, AUTH_SUBSYS_DB); return PASSDB_RESULT_USER_UNKNOWN; } when request->user contains 'user(a)domain.tld', I want the code to be able to process "override_username", determine that the format is %Ln so that request->user is lowercased, and everything after the "@" sign is stripped. Therefore, if this user happens to exist in the shadow file, authentication will succeed. Currently, the "shadow" driver only appears to support "args = blocking=no". Please advise.

3 4

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

12 Jul '16

>> I've reduced the problem to this: >> >> void foo(int X[static 20]); >> >> will compile but if you remove "X", it won't. > > The change was to replace "int" with "unsigned char" in the above test > program, and the test started failing then in CentOS 5's gcc. I'd > expect the same to happen for you also. No, it will fail with both "int" and "unsigned char" without the dummy argument "X", and works for both if one is inserted. I don't know why -- perhaps a bug with my version of gcc. Joseph Tam <jtam.home(a)gmail.com>

1 1

dovecot master password without "auth_master_user_separator"
by Miguel C 12 Jul '16

12 Jul '16

Looking at the doc its sugest we can either use auth_master_user_separator to login with a master user (i.e user(a)email.com*master and the master password defined in a file or db) I'm able to use this method with a password file and works just fine, however we need to sync some imap users to another destrination that does not allow us to use this format in the "email address source" (shame) But the doc also sugests if I don't use this flag I should be able to just use the same login used in the SASL mecahnisms which is not working (testing with plain text ). Is there anything more to this? I have tried to add a username to the password file with the same master password but still doens't work :| What am I missing? Melhores Cumprimentos // Best Regards ----------------------------------------------- *Miguel Clara* *IT - Sys Admin & Developer*

1 0

Feature Request
by Doug Hardie 12 Jul '16

12 Jul '16

I would like to request an additional optional argument for queue-id to dovecot-lda. The intended use for this argument is to include in the logging. From what I can tell, the queue-id size is not consistent between the various MTAs and so would need to be allocated dynamically when read during initialization. This element in the log messages would make it easier to find the trace of a received email. Generally I can easily get the queue-id generated by postfix (or sendmail - I use both). One grep would then give me the whole picture rather than having to dig out the message-id and doing a secondary grep to obtain the lda log messages. — Doug I find it interesting that every submission to this list results in a quick response that says moderation is required since I "am not a member". However, I am a member...

2 1

is it possible to run a post-login script in a dovecot proxy with local auth?
by Luca Lesinigo 12 Jul '16

12 Jul '16

We’re using dovecot v2.2.22, authenticating on a local database (passdb with sql driver), and then proxying the connections to the backend server returned by passdb (proxy=y and backend in “host” column). To support some legacy clients we should keep POP/IMAP-before-SMTP running for some time, but right know I don’t know how to hook up a successful authentication in the dovecot proxy. I did read from http://wiki2.dovecot.org/PostLoginScripting: “...it's not currently possible to run post-login scripts in proxies, because they're not actually logging in to the local Dovecot” Does that also holds true even if the proxy is authenticating users locally before proxying them? Failing that, any idea on how to get successful logins, other than parsing the log file? thank you, -- Luca Lesinigo

2 1

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

12 Jul '16

Aki Tuomi wrote: >>> 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. > > It still happened even with > https://github.com/dovecot/core/commit/d9c865ce774aae9f2f17b89e7e94c3cfca29… > > You need to rerun autotools on this before it can do anything. I don't grok autotools, but I don't think this will solve the problem. If I understand the patch correctly, it modifies the small program used by configure to test a C99 feature. Manually compiling the small test program (with and without the changes made by the patch) will result in a successful compile, but if you compile sha1.h (line 80,81), it will fail. I've reduced the problem to this: void foo(int X[static 20]); will compile but if you remove "X", it won't. Joseph Tam <jtam.home(a)gmail.com>

2 1

a question about dovecot-sieve
by 刘莹莹 11 Jul '16

11 Jul '16

question discribe: example: > vim .dovecot.sieve require ["fileinto"]; # rule:[filter1] if anyof (header :contains "Subject" "测试邮件") { fileinto "sieve"; } when i write a mail ,give subject "这是一封测试邮件" , then server convert this subject to " SUBJECT: =?UTF-8?Q?=E8=BF=99=E6=98=AF=E4=B8=80=E5=B0=81=E6=B5=8B=E8=AF=95=E9=82=AE?= =?UTF-8?Q?=E4=BB=B6?= " the essential question is when the mail go through dovecot-sieve plugin, the sieve plugin get mail subject is "这是一封测试邮件" not "这是一封测试邮件"，there is a extra space added(which as segmentation between "=?UTF-8?Q?"). SIMPLY SAY：edit subject"这是一封测试邮件" ——>server convert "SUBJECT: =?UTF-8?Q?=E8=BF=99=E6=98=AF=E4=B8=80=E5=B0=81=E6=B5=8B=E8=AF=95=E9=82=AE?= =?UTF-8?Q?=E4=BB=B6?="——>sieve plugin get "这是一封测试邮件" The result is filter failure. is this a bug ? How can I avoid it？ thanks

2 1

"anvil: Error: connect limit: disconnection for unknown pid 17659 + ident lmtp/backup@backup.invalid"
by Ralf Hildebrandt 11 Jul '16

11 Jul '16

I updated to 2.3.0 today, and now I'm getting these entries in my log: Jul 7 14:26:20 mail-cbf dovecot: anvil: Error: connect limit: disconnection for unknown pid 17687 + ident lmtp/backup(a)backup.invalid Jul 7 14:26:20 mail-cbf dovecot: anvil: Error: connect limit: disconnection for unknown pid 17659 + ident lmtp/backup(a)backup.invalid Jul 7 14:26:21 mail-cbf dovecot: anvil: Error: connect limit: disconnection for unknown pid 17654 + ident lmtp/backup(a)backup.invalid Jul 7 14:26:22 mail-cbf dovecot: anvil: Error: connect limit: disconnection for unknown pid 17659 + ident lmtp/backup(a)backup.invalid Jul 7 14:26:22 mail-cbf dovecot: anvil: Error: connect limit: disconnection for unknown pid 17687 + ident lmtp/backup(a)backup.invalid Jul 7 14:26:23 mail-cbf dovecot: anvil: Error: connect limit: disconnection for unknown pid 17659 + ident lmtp/backup(a)backup.invalid lmtp on the other seems to be working ok -- I'm not seeing any mails queueing up... Jul 7 14:28:01 mail-cbf dovecot: lmtp(17659): Connect from local Jul 7 14:28:01 mail-cbf dovecot: anvil: Error: connect limit: disconnection for unknown pid 17659 + ident lmtp/backup(a)backup.invalid Jul 7 14:28:01 mail-cbf dovecot: lmtp(17659): Disconnect from local: Successful quit -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG, 80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein

4 3

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

Re: Compile error Dovecot2-pigeonhole
by Мунголин Максим 07 Jul '16

07 Jul '16

1) I was trying to compile from ports: make (without any flags) Got an error: cc1: error: unrecognized command line option "-Wno-duplicate-decl-specifier" cc1: error: unrecognized command line option "-Wno-duplicate-decl-specifier" cc1: error: unrecognized command line option "-Wno-duplicate-decl-specifier" cc1: error: unrecognized command line option "-Wno-duplicate-decl-specifier" *** [edit-mail.lo] Error code 1 *** [program-client-local.lo] Error code 1 *** [program-client-remote.lo] Error code 1 *** [rfc2822.lo] Error code 1 4 errors *** [all-recursive] Error code 1 1 error *** [all-recursive] Error code 1 1 error *** [all-recursive] Error code 1 1 error *** [all] Error code 2 1 error ===> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** [do-build] Error code 1 Stop in /usr/ports/mail/dovecot2-pigeonhole. *** [stage] Error code 1 2) When, I was trying to add flag -k (force). Same error. 3) When, I was trying to add flag MAKE_JOBS_UNSAFE. Same error.

1 0

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

07 Jul '16

Please keep replies on-list. If you removed the compiler flag, how can you get error about compiler flag? Perhaps you need to contact package maintainer? Aki On 07.07.2016 10:23, Maximus wrote: > Sure. > Same error. > > -----Original Message----- > From: dovecot [mailto:dovecot-bounces@dovecot.org] On Behalf Of Aki Tuomi > Sent: Thursday, July 07, 2016 9:24 AM > To: dovecot(a)dovecot.org > Subject: Re: Compile error Dovecot2-pigeonhole > > > > On 07.07.2016 08:35, Maximus wrote: >> 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: >> >> > Hi! > > Try removing that superfluous compiler flag? > > Aki

1 0

Configure Dovecot for GSSAPI [formerly: Looking for GSSAPI config]
by Mark Foley 06 Jul '16

06 Jul '16

After a over a year and a half struggling to get Dovecot to do either NTLM or GSSAPI authentication with Samba4 AD/DC, I believe I've finally got it! Thanks to all those in this list who helped: Jan Jurkus, Edgar Pettijohn, Gregory Sloop, Tom Talpey especially Aki Tuomi; and infinite thanks to Achim Gottinger on the SambaList for his patience in working this through with me. Although my purpose was for Dovecot to authenticate mail clients, the configuration settings needed were on the Samba side. I hope a variation of these instructions can eventually make it into: http://wiki2.dovecot.org/Authentication/Kerberos What is essentially missing from the wiki is how to set up the proper Service Principal Names and the subsequent creation of a dovecot useable kerberos keytab file. The wiki comment on "k5principals passdb" was not helpful and largely unintelligble to me. Perhaps like many of you, I have switched from Microsoft SBS and Exchange to Samaba4 and Dovecot/IMAP. The transition was completely transparent to my users, except they needed a separate password for email authentication in the absence of NTLM or GSSAPI working with Dovecot. A mild inconvenience, but I have been on a "quest" to fill that gap. This solution finally takes care of that last piece. The following describes how to create the SPNs and krb5 keytab files using Samba4 which has its own built-in (Heimdal) kerberos. The procedures are probably similar for other facilities such as setspn for Windows, but I've not used those so I won't attempt to discuss those mechanism here. You do need kerberos as the Samba built-in kerberos does not have needed commands like `klist`. My distro (Slackware 14.1) does not come with kerberos (nor, I think, does Ubuntu), but is easily found at: https://slackbuilds.org/repository/14.1/network/krb5/ Ubuntu/Debian: apt-get install krb5-config libpam-krb5 krb5-user ssh-krb5 (perhaps more) After provisioning Samba4, copy the krb5.conf template to /etc/krb5.conf. (Note: the actual docs advise symlinking: ln -sf /usr/local/samba/private/krb5.conf /etc/krb5.conf but I prefer making a copy in case I need to modify things). I've set The /etc/krb5.conf file to world readable. It's default contents are (and these do not need to be changed): [libdefaults] default_realm = HPRS.LOCAL dns_lookup_realm = false dns_lookup_kdc = true where HPRS.LOCAL is my realm, of course use your own. Now, we need a samba user in order to create the necessary SPNs (Server Principal Names): $ samba-tool user create dovecot New Password: Retype Password: User 'dovecot' created successfully Next, add the SPN(s), and create the keytab: $ samba-tool spn add imap/mail.hprs.local dovecot $ samba-tool domain exportkeytab --principal imap/mail.hprs.local /etc/dovecot/dovecot.keytab Dovecot does not do my (outgoing) SMTP serving, only (incoming) IMAP, but if it did I'd have to create another SPN for smtp: $ samba-tool spn add smtp/mail.hprs.local dovecot $ samba-tool domain exportkeytab --principal smtp/mail.hprs.local /etc/dovecot/dovecot.keytab Dovecot needs to be able to read the keytab file: $ chgrp dovecot /etc/dovecot/dovecot.keytab $ chmod g+r /etc/dovecot/dovecot.keytab my new keytab: $ klist -Kek /etc/dovecot/dovecot.keytab Keytab name: FILE:/etc/dovecot/dovecot.keytab KVNO Principal ---- -------------------------------------------------------------------------- 1 imap/mail.hprs.local(a)HPRS.LOCAL (des-cbc-crc) (0x232616c2a4fd08f7) 1 imap/mail.hprs.local(a)HPRS.LOCAL (des-cbc-md5) (0x232616c2a4fd08f7) 1 imap/mail.hprs.local(a)HPRS.LOCAL (arcfour-hmac) (0x9dae89a221dc374a39f560833352f60f) (and if I also created the spn for smtp I would also have these:) 1 smtp/mail.hprs.local(a)HPRS.LOCAL (des-cbc-crc) (0x232616c2a4fd08f7) 1 smtp/mail.hprs.local(a)HPRS.LOCAL (des-cbc-md5) (0x232616c2a4fd08f7) 1 smtp/mail.hprs.local(a)HPRS.LOCAL (arcfour-hmac) (0x9dae89a221dc374a39f560833352f60f) DOVECOT SETTINGS: My version: 2.2.15 Of crucial importance is to build dovecot with GSSAPI! That is NOT one of the default settings. In the dovecot build directory: ./configure --with-gssapi=yes Other than that serious build gotcha, settings are pretty simple. Add the following 3 settings to 10-auth.conf: auth_gssapi_hostname = "$ALL" auth_krb5_keytab = /etc/dovecot/dovecot.keytab auth_mechanisms = plain login gssapi The auth_gssapi_hostname is supposedly not required according to some of the above-listed commentors, but my 10-auth.conf template implies differently, so it can't hurt. gssapi does not require a passdb. Use whatever userdb you want. The dovecot wiki doc has some suggestions, not of which I've tried. I use the 'driver = passwd' for my userdb for unrelated reasons. I couldn't get any of this working until I rebooted the Samba AD/DC-Dovecot server, but that just may have been me not stopping/starting Samba and Dovecot in the right sequence (or, everything happened to start working with a concurrent upgrade to Samba 4.2!). In my WIN7 and Ubuntu Thunderbird clients I selected gssapi/kerberos for the IMAP authenticate method and it works! I've even changed the test user's AD password, just to make sure. Someone please put at least the required info on creating the SPNs and krb keytab file for other poor schmucks like me. Now, if I can get NTLM figured out for the remaining Outlook users ... ! --Mark

4 9

Compile error v2.2.25 MacOS X
by James Brown 06 Jul '16

06 Jul '16

Tried to update from 2.2.24 to 2.2.25 using same configure command as previously. make ends with: 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[3]: *** [all] Error 2 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Mac OS X 10.7.5 Configure statement was: ./configure --with-mysql --with-ssl=openssl Any suggestions? Thanks, James.

3 3

Dovecot2-pigeonhole
by Maximus 06 Jul '16

06 Jul '16

Got an error then I'm trying to upgrade to version 0.4.14: cc1: error: unrecognized command line option "-Wno-duplicate-decl-specifier"

1 0

Postfix/dovecot: user unrecognized, file permissions being misread
by C. Andrews Lavarre 06 Jul '16

06 Jul '16

Hello all. Have spent several days following the excellent tutorial: http://www.binarytides.com/install-postfix-dovecot-debian/ but still fail to have the user recognized and am getting log entries that the mail directories are 0755 when I can clearly see that they are 0774. Very puzzling, any help would be deeply appreciated. Best regards, Andy =========== Details =========== • I can add directories under IMAP, so my IMAP login and permissions must be correct. • I can create an outgoing message under IMAP, but clicking SEND just hangs. Logs do not indicate problem. • I clearly can send it a message with smtp. The message is delivered to postfix, but then dovecot fails to deliver it to a mailbox. ------------------------------------ Log Entries --------------------- --------------- # tail /var/log/mail postfix/qmgr[16390]: 9D6E8C1A77: from=<alavarre(a)gmail.com>, size=2794, nrcpt=1 (queue active) Message has been received postfix/lmtp[16770]: C218DC197D: to=<alavarre(a)privustech.com>, relay=mail.privustech.com[private/lmtp], delay=2560, delays=2260/0.01/300/0, dsn=4.4.2, status=deferred (conversation with mail.privustech.com[private/lmtp] timed out while receiving the initial server greeting) lmtp is not working ------------------------------------ # tail /var/log/dovecot.log auth-worker(16612): Info: pam(alavarre(a)privustech.com,98.179.190.111): unknown user imap-login: Info: Login: user=<alavarre(a)privustech.com>, method=PLAIN, rip=98.179.190.111, lip=70.186.159.22, mpid=16615, TLS, session=<ad;slfj;asfa;> imap(alavarre(a)privustech.com): Error: mkdir(/var/mail/vhosts/privustech.com/alavarre/cur) failed: Permission denied (euid=5000(vmail) egid=5000(vmail) missing +w perm: /var/mail/vhosts/privustech.com/alavarre, dir owned by 0:0 mode=0755) However, the mail directory /var/mail/vhosts/privustech.com/alavarre is -rwxrwxr-- vmail:vmail and I have restarted both postfix and dovecot. ========================= System is openSUSE Leap 42.1 (64). postfix and dovecot with SASL authentication, connecting through a Unix socket: /etc/postfix/main.cf: virtual_transport = lmtp:unix:private/lmtp /etc/dovecot/conf.d/10-master.cf: service lmtp { unix_listener /var/spool/postfix/private/lmtp { mode = 0600 user = postfix group = postfix } The lmtp socket is owned by postfix, while the mail system is owned by vmail, per the tutorial. ------------------------------ I am using virtual users (not system users) defined in /etc/dovecot/dovecot-users: alavarre@privustech.com:{plain}ksaj;flkasjd;ds;f Thanks in advance, Andy

2 6

Dovecot delete and expunge loop
by Il Neofita 06 Jul '16

06 Jul '16

Hi I am using dovecot 2.0.9 with redhat 6.8 One client with Outlook 2013 is deleting and expunging and email over and over changing the uid. I am not able to understand how to solve it.

2 1

kqueue crash on FreeBSD with 2.2.25
by Adam Weinberger 05 Jul '16

05 Jul '16

Hi, 2.2.25 crashes on FreeBSD with a kqueue-related message. I see references to something similar (http://www.dovecot.org/list/dovecot/2012-February.txt) from a couple years ago. I get: Jul 1 10:07:27 imap dovecot: master: Panic: kevent(EV_ADD, READ, 54) failed: Bad file descriptor It's not dumping core, and I get the message even with "protocols =" Downgrading back to 2.2.24 fixes it. What info would be helpful for me to provide here? # Adam -- Adam Weinberger adamw(a)adamw.org http://www.adamw.org

5 11

duplicate Mails with dsync replication
by Dennis Kuhn 05 Jul '16

05 Jul '16

Hi! We have some strange replication issues. Some mails are duplicated when expunged. This bug is quite hard to reproduce, it just happens occasionally. It seems somehow related to sieve. When i deleted the sieve script i could not reproduce this behavior. Here are some logs, mjm-100010(a)mydomain.com is an alias for mjm(a)mydomain.com: # Master Jun 23 00:51:41 dobby4 dovecot: lmtp(mjm-100010(a)mydomain.com): copy from <lmtp DATA>: box=INBOX, uid=7816, msgid=<20160623005132EE517444BB$3A04DF25DD@ABRAHAM>, size=8933 Jun 23 00:51:41 dobby4 dovecot: lmtp(mjm-100010(a)mydomain.com): 4N23HaMVa1fpmQEAJEBNLA: sieve: msgid=<20160623005132EE517444BB$3A04DF25DD@ABRAHAM>: stored mail into mailbox 'INBOX' Jun 23 04:52:57 dobby4 dovecot: pop3(mjm(a)mydomain.com): expunge: box=INBOX, uid=7816, msgid=<20160623005132EE517444BB$3A04DF25DD@ABRAHAM>, size=8933 Jun 23 04:52:57 dobby4 dovecot: dsync-local(mjm(a)mydomain.com): save: box=INBOX, uid=7817, msgid=<20160623005132EE517444BB$3A04DF25DD@ABRAHAM>, size=8933 Jun 23 04:55:21 dobby4 dovecot: pop3(mjm(a)mydomain.com): expunge: box=INBOX, uid=7817, msgid=<20160623005132EE517444BB$3A04DF25DD@ABRAHAM>, size=8933 # Replica Jun 23 00:51:42 dobby5 dovecot: dsync-server(mjm-100010(a)mydomain.com): save: box=INBOX, uid=7816, msgid=<20160623005132EE517444BB$3A04DF25DD@ABRAHAM>, size=8933 Jun 23 04:52:57 dobby5 dovecot: dsync-server(mjm(a)mydomain.com): copy from INBOX: box=INBOX, uid=7817, msgid=<20160623005132EE517444BB$3A04DF25DD@ABRAHAM>, size=8933 Jun 23 04:52:57 dobby5 dovecot: dsync-server(mjm(a)mydomain.com): expunge: box=INBOX, uid=7816, msgid=<20160623005132EE517444BB$3A04DF25DD@ABRAHAM>, size=8933 Jun 23 04:55:22 dobby5 dovecot: dsync-server(mjm(a)mydomain.com): expunge: box=INBOX, uid=7817, msgid=<20160623005132EE517444BB$3A04DF25DD@ABRAHAM>, size=8933 The problem is the "dsync-server(mjm(a)mydomain.com): copy from INBOX: box=INBOX, uid=7817" on dobby5 at 04:52:57. This creates a new uid 7817 and the new mail is replicated back to dobby4. But i have no idea what triggers this copy. Any ideas? The dovecot version is 2.2.24. Thanks Dennis

1 0

many imap connections issue
by Бауыржан Сахариев 05 Jul '16

05 Jul '16

I'm using dovecot 2.1.7 I'm trying to connect to dovecot by imap via Java mail api. My approach described here <http://stackoverflow.com/questions/37991025/why-iterating-over-all-java-mai…>. Bill Shannon, author of the Java Mail api recommended me to check carefully my server side (I have dovecot at server side). Actually, imap login in loop works but very slow. Each store.connect(login,password) takes about 1 minute. I tried to increase mail_max_userip_connections client_limit and process limit but it didn't help. My dovecot sometimes performs query, sometimes not! My logs: Jul 04 18:23:25 auth: Error: pgsql: Query failed, aborting: SELECT email, 'maildir:/home/mailboxes/maildir/'||maildir as mail,'/home/mailboxes/home/'||maildir as home, 500 as uid, 500 as gid FROM users WHERE email = 'test(a)test.domain.com' Jul 04 18:23:25 auth: Error: sql(test(a)test.domain.com,127.0.0.1,<HGiPY842jgB/AAAB>): User query failed: ERROR: permission denied for relation users My user and password queries: 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/home/'||maildir as home, 500 as uid, 500 as gid FROM users WHERE email = '%u' My master conf *Please note, that I'm using same uid!* service imap-login { inet_listener imap { #port = 143 } inet_listener imaps { #port = 993 #ssl = yes } # Number of connections to handle before starting a new process. Typically # the only useful values are 0 (unlimited) or 1. 1 is more secure, but 0 # is faster. <doc/wiki/LoginProcess.txt> #service_count = 1 # Number of processes to always keep waiting for more connections. #process_min_avail = 0 # If you set service_count=0, you probably need to grow this. #vsz_limit = $default_vsz_limit } service imap { # Most of the memory goes to mmap()ing files. You may need to increase this # limit if you have huge mailboxes. #vsz_limit = $default_vsz_limit # Max. number of IMAP processes (connections) #process_limit = 1024 } service auth { unix_listener auth-userdb { #mode = 0666 #user = #group = } # Postfix smtp-auth #unix_listener /var/spool/postfix/private/auth { # mode = 0666 #} # Auth process is run as this user. #user = $default_internal_user } service auth-worker { # Auth worker process is run as root by default, so that it can access # /etc/shadow. If this isn't necessary, the user should be changed to # $default_internal_user. #user = root } I'm sure that long login *reason is poor dovecot config* but some things are not clear to me and I can't improve it. 1. Which service are being used when Java connects to dovecot? imap-login,imap or auth? My assumption - imap-login. Imap user for dealing with folders *after* login, auth is for delivery (my assotioations here are postfix,lmtp,lda) =) Is my assumptions about imap-login and other services correct? 2. Which user are being used when I login? One that specified in connection code(one of 50K users in loop) or uid(500) user? I suggested that only one user and increased mail_max_userip_connections is it correct? 3. May some troubles in connection (which I showed above) caused by mode(0660) bad config in master.cf services? 4. Almost each loop iteration connects to dovecot in 60 seconds and rarely connects in a few milliseconds. Is that fact somehow connected with deafult_idle_kill which equlas to 1 mins?

1 0

v2.2.25 released
by Timo Sirainen 04 Jul '16

04 Jul '16

http://dovecot.org/releases/2.2/dovecot-2.2.25.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.25.tar.gz.sig Some minor fixes and (mainly logging) improvements since rc1. * lmtp: Start tracking lmtp_user_concurrency_limit and reject already at RCPT TO stage. This avoids MTA unnecessarily completing DATA only to get an error. * doveadm: Previously only mail settings were read from protocol doveadm { .. } section. Now all settings are. + quota: Added quota_over_flag_lazy_check setting. It avoids checking quota_over_flag always at startup. Instead it's checked only when quota is being read for some other purpose. + auth: Added a new auth policy service: http://wiki2.dovecot.org/Authentication/Policy + auth: Added PBKDF2 password scheme + auth: Added %{auth_user}, %{auth_username} and %{auth_domain} + auth: Added ":remove" suffix to extra field names to remove them. + auth: Added "delay_until=<timestamp>[+<max random secs>]" passdb extra field. The auth will wait until <timestamp> and optionally some randomness and then return success. + dict proxy: Added idle_msecs=<n> parameter. Support async operations. + Performance improvements for handling large mailboxes. + Added lib-dcrypt API for providing cryptographic functions. + Added "doveadm mailbox update" command + imap commands' output now includes timing spent on the "syncing" stage if it's larger than 0. + cassandra: Added metrics=<path> to connect setting to output internal statistics in JSON format every second to <path>. + doveadm mailbox delete: Added -e parameter to delete only empty mailboxes. Added --unsafe option to quickly delete a mailbox, bypassing lazy_expunge and quota plugins. + doveadm user & auth cache flush are now available via doveadm-server. + doveadm service stop <services> will stop specified services while leaving the rest of Dovecot running. + quota optimization: Avoid reading mail sizes for backends which don't need them (count, fs, dirsize) + Added mailbox { autoexpunge_max_mails=<n> } setting. + Added welcome plugin: http://wiki2.dovecot.org/Plugins/Welcome + fts: Added fts_autoindex_exclude setting. - v2.2.24's MIME parser was assert-crashing on mails having truncated MIME headers. - auth: With multiple userdbs the final success/failure result wasn't always correct. The last userdb's result was always used. - doveadm backup was sometimes deleting entire mailboxes unnecessarily. - doveadm: Command -parameters weren't being sent to doveadm-server. - If dovecot.index read failed e.g. because mmap() reached VSZ limit, an empty index could have been opened instead, corrupting the mailbox state. - imapc: Fixed EXPUNGE handling when imapc_features didn't have modseq. - lazy-expunge: Fixed a crash when copying failed. Various other fixes. - fts-lucene: Fixed crash on index rescan. - auth_stats=yes produced broken output - dict-ldap: Various fixes - dict-sql: NULL values crashed. Now they're treated as "not found".

6 8

Shared mailboxes not showing up in shared namespace
by Marti Markov 04 Jul '16

04 Jul '16

Hi, I think I have configured everything correctly but for some reason I can’t get a list of the shared mailboxes to show up. When I run: doveadm acl debug -u m.markov Shared/d.marteva/INBOX doveadm(root): Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_plugin.so: undefined symbol: fts_backend_rescan (this is usually intentional, so just ignore this message) doveadm(m.markov): Debug: Added userdb setting: plugin/=yes doveadm(m.markov): Debug: Effective uid=1000, gid=1000, home=/home/vmail/domain.com/m.markov doveadm(m.markov): Debug: Namespace inbox: type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/Maildir doveadm(m.markov): Debug: maildir++: root=/home/vmail/domain.com/m.markov/Maildir, index=, indexpvt=, control=, inbox=/home/vmail/domain.com/m.markov/Maildir, alt= doveadm(m.markov): Debug: acl: initializing backend with data: vfile doveadm(m.markov): Debug: acl: acl username = m.markov(a)domain.com doveadm(m.markov): Debug: acl: owner = 1 doveadm(m.markov): Debug: acl vfile: Global ACLs disabled [ Read 8 lines ] doveadm(m.markov): Debug: Namespace : type=public, prefix=Public/, sep=/, inbox=no, hidden=no, list=yes, subscriptions=yes location=maildir:/home/vmail/Public:INDEXPVT=~/Maildir/Publics doveadm(m.markov): Debug: maildir++: root=/home/vmail/Public, index=, indexpvt=/home/vmail/domain.com/m.markov/Maildir/Public, control=, inbox=, alt=ext ^T To Spell doveadm(m.markov): Debug: acl: initializing backend with data: vfile doveadm(m.markov): Debug: acl: acl username = m.markov(a)domain.com doveadm(m.markov): Debug: acl: owner = 0 doveadm(m.markov): Debug: acl vfile: Global ACLs disabled doveadm(m.markov): Debug: Namespace : type=shared, prefix=Shared/%u/, sep=/, inbox=no, hidden=no, list=yes, subscriptions=yes location=maildir:/home/vmail/domain.com/%u/Maildir:INDEXPVT=~/Maildir/share… doveadm(m.markov): Debug: shared: root=/var/run/dovecot, index=, indexpvt=, control=, inbox=, alt= doveadm(m.markov): Debug: acl: initializing backend with data: vfile doveadm(m.markov): Debug: acl: acl username = m.markov(a)domain.com doveadm(m.markov): Debug: acl: owner = 0 doveadm(m.markov): Debug: acl vfile: Global ACLs disabled doveadm(m.markov): Debug: maildir++: root=/home/vmail/domain.com/d.marteva/Maildir, index=, indexpvt=/home/vmail//d.marteva/Maildir/shared/d.marteva, control=, inbox=/home/vmail/domain.com/d.marteva/Maildir, alt= doveadm(m.markov): Debug: acl: initializing backend with data: vfile doveadm(m.markov): Debug: acl: acl username = d.marteva doveadm(m.markov): Debug: acl: owner = 1 doveadm(m.markov): Debug: acl vfile: Global ACLs disabled doveadm(m.markov): Debug: maildir++: root=/home/vmail/domain.com/d.marteva/Maildir, index=, indexpvt=/home/vmail/domain.com/m.markov/Maildir/shared/d.marteva, control=, inbox=/home/vmail/domain.com/d.marteva/Maildir, alt= doveadm(m.markov): Debug: acl: initializing backend with data: vfile doveadm(m.markov): Debug: acl: acl username = m.markov(a)domain.com doveadm(m.markov): Debug: acl: owner = 0 doveadm(m.markov): Debug: acl vfile: Global ACLs disabled doveadm(m.markov): Info: Mailbox 'INBOX' is in namespace 'Shared/d.marteva/' doveadm(m.markov): Info: Mailbox path: /home/vmail/domain.com/d.marteva/Maildir doveadm(m.markov): Info: Per-user private flags in mailbox: \Seen doveadm(m.markov): Debug: acl vfile: reading file /home/vmail/domain.com/d.marteva/Maildir/dovecot-acl doveadm(m.markov): Info: User m.markov(a)domain.com has rights: lookup read write create doveadm(m.markov): Info: Mailbox found from dovecot-acl-list doveadm(m.markov): Info: User d.marteva found from ACL shared dict doveadm(m.markov): Info: Mailbox Shared/d.marteva/INBOX is visible in LIST Here is how I have defined the namespace: namespace { type = shared separator = / prefix = Shared/%%u/ # a) Per-user seen flags. Maildir indexes are shared. (INDEXPVT requires v2.2+) location = maildir:/home/vmail/domain.com/%%u/Maildir:INDEXPVT=~/Maildir/shared/%%u # b) Per-user seen flags. Maildir indexes are not shared. If users have direct filesystem level access to their mails, this is a safer option: #location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u:INDEXPVT=~/Maildir/shared/%%u subscriptions = yes # list = children list=yes } And here is the ACL config: plugin { #acl = vfile:/etc/dovecot/global-acls:cache_secs=300 acl = vfile } # To let users LIST mailboxes shared by other users, Dovecot needs a # shared mailbox dictionary. For example: plugin { #acl_shared_dict = file:/var/lib/dovecot/shared-mailboxes acl_shared_dict = file:/home/vmail/domain.com/shared-mailboxes2 #acl_lookup_dict = file:/home/vmail/domain.com/shared-mailboxes } Any suggestions?

3 7

RE: quota-status service
by Michael Fox 03 Jul '16

03 Jul '16

??? From: Michael Fox [mailto:news@mefox.org] Sent: Thursday, June 30, 2016 1:59 PM To: Dovecot Mailing List (dovecot(a)dovecot.org) <dovecot(a)dovecot.org> Subject: quota-status service I'm trying to understand the quota-status service, but I can't find complete documentation. The quota-status service is mentioned here: http://wiki.dovecot.org/Quota And an example configuration is shown: service quota-status { executable = quota-status -p postfix inet_listener { port = 12340 # You can choose any port you want } client_limit = 1 } But I can't find any information on quota-status. "man quota-status" returns nothing. I am unable to find a "quota-status" file on my machine. Where is the executable located? What does the "-p postfix" option do? Are there any other command line options? The above wiki page shows three quota_status_* options in use: quota_status_success = DUNNO quota_status_nouser = DUNNO quota_status_overquota = "552 5.2.2 Mailbox is full" Where are their meanings documented? What are the allowed values? Are there other quota_status_* options? Thanks in advance. Thanks, Michael

2 3

Re: FW: quota-status service
by Aki Tuomi 03 Jul '16

03 Jul '16

If you need fast and timely support you can contact OX sales for an support agreement . It is somewhat impolite to except such from a public mailing list over weekend. ---Aki TuomiDovecot oy -------- Original message --------From: Michael Fox <news(a)mefox.org> Date: 03/07/2016 09:00 (GMT+02:00) To: Dovecot Mailing List <dovecot(a)dovecot.org> Subject: FW: quota-status service ??? 3rd request -----Original Message----- From: dovecot [mailto:dovecot-bounces@dovecot.org] On Behalf Of Michael Fox Sent: Friday, July 1, 2016 5:56 PM To: Dovecot Mailing List <dovecot(a)dovecot.org> Subject: RE: quota-status service ??? From: Michael Fox [mailto:news@mefox.org] Sent: Thursday, June 30, 2016 1:59 PM To: Dovecot Mailing List (dovecot(a)dovecot.org) <dovecot(a)dovecot.org> Subject: quota-status service I'm trying to understand the quota-status service, but I can't find complete documentation. The quota-status service is mentioned here: http://wiki.dovecot.org/Quota And an example configuration is shown: service quota-status { executable = quota-status -p postfix inet_listener { port = 12340 # You can choose any port you want } client_limit = 1 } But I can't find any information on quota-status. "man quota-status" returns nothing. I am unable to find a "quota-status" file on my machine. Where is the executable located? What does the "-p postfix" option do? Are there any other command line options? The above wiki page shows three quota_status_* options in use: quota_status_success = DUNNO quota_status_nouser = DUNNO quota_status_overquota = "552 5.2.2 Mailbox is full" Where are their meanings documented? What are the allowed values? Are there other quota_status_* options? Thanks in advance. Thanks, Michael

4 4

Error on upgrade to 2.2.25 from 2.2.24
by Goetz R Schultz 02 Jul '16

02 Jul '16

Hi, I have compiled the latest version with those flags: ./configure --with-pgsql --with-sql under FreeBSD/amd64. This worked fine with the previous version. Compilation also works without errors. Yet when I start DC I get this error: Jul 1 22:48:55 section31 dovecot: master: Dovecot v2.2.25 () starting up for imap Jul 1 22:48:55 section31 dovecot: master: Panic: kevent(EV_ADD, READ, 55) failed: Bad file descriptor This does not hapen with the previous version. I could not find any change note that would point in that direction. Any clues? Did I miss something to set? -- Thanks and regards Goetz "I intend to live forever - so far, so good." =============================================== /"\ Get the rootcertificate at www.cacert.org \ / ASCII Ribbon Campaign against HTML e-mail X / \ Verify the cert @ CaCert.Com =============================================== "Si forte in alienas manus oberraverit hec peregrina epistola incertis ventis dimissa, sed Deo commendata, precamur ut ei reddatur cui soli destinata, nec preripiat quisquam non sibi parata."

1 0

Re: Looking for GSSAPI config [was: Looking for NTLM config example]
by Mark Foley 01 Jul '16

01 Jul '16

Aki - made your suggested changes, but no joy :( My /etc/krb5.conf: ------SNIP-------- [libdefaults] default_realm = HPRS.LOCAL dns_lookup_realm = false dns_lookup_kdc = true [libdefaults] default_realm = HPRS.LOCAL dns_lookup_kdc = true kdc_timesync = 1 ccache_type = 4 forwardable = true proxiable = true fcc-mit-ticketflags = true [realms] HPRS.LOCAL = { default_domain = hprs.local auth_to_local_names = { Administrator = root } } [domain_realm] hprs.local = HPRS.LOCAL # this is not a mistake .hprs.local = HPRS.LOCAL ------PINS----------- you wrote: > You can remove the krb4_ stuff I've remove krb4_ stuff from the [libdefaults] and eliminated the [login] section altogether. Question on [realms]Administrator: should that really be root or should it be my AD Administrator? my doveconf -n is exactly the same as posted below, but in particular: auth_krb5_keytab = /etc/krb5.keytab auth_mechanisms = plain login gssapi When I reloaded dovecot no mail was delivered to anyone (even though everyone was still using plain/ssl, no one yet configured for gssapi). In /var/log/maillog I got (repeatedly): Jun 28 09:43:36 mail dovecot: imap-login: Warning: Auth process not responding, delayed sending initial response (greeting): user=<>, rip=192.168.0.54, lip=192.168.0.2, session=<Jy/e0lY2WADAqAA2> Jun 28 09:43:37 mail dovecot: auth: Fatal: Unknown authentication mechanism 'gssapi' Jun 28 09:43:37 mail dovecot: master: Error: service(auth): command startup failed, throttling for 60 secs Jun 28 09:43:37 mail dovecot: imap-login: Warning: Auth process not responding, delayed sending initial response (greeting): user=<>, rip=166.170.27.161, lip=98.102.63.107, TLS, session=</GXn0lY22wCmqhuh> This looks pretty bad right off. Why "Unknown authentication mechanism 'gssapi'"? Do you have any idea from the configs I've posted? I'm rather depressed about this. I thought I'd finally able to get AD authentication going for Dovecot. Not ready to give up though! Suggestions? THX -- Mark -----original Message----- > Subject: Re: Looking for GSSAPI config [was: Looking for NTLM config example] > To: dovecot(a)dovecot.org > From: Aki Tuomi <aki.tuomi(a)dovecot.fi> > Date: Tue, 28 Jun 2016 15:13:11 +0300 > > On 28.06.2016 09:27, Mark Foley wrote: > > Aki, > > > > To review your 5 points: > > > > On Mon, 27 Jun 2016 09:18:54 +0300 Aki Tuomi <aki.tuomi(a)dovecot.fi> wrote: > > > >> 1. Functional AD or Kerberos environment > >> 2. Time synced against your KDC (which is your Domain Controller on Windows) > >> 3. /etc/krb5.conf configured > >> 4. Both forward / reverse DNS names correct for clients and servers. > >> Reverse is only mandatory for servers, but having them right will work > >> wonders. Most kerberos problems are about DNS problems. > >> 5. You need a keytab. This keytab needs to hold entries like > >> IMAP/your.host.name@REALM and IMAP/$HOSTNAME@REALM. You can generate > >> these on any Windows DC server (at least). > > I believe I am good on 1,2 and 4. I downloaded and installed kerberos and tested it with kinit > > and klist according to the instructions at > > https://wiki.samba.org/index.php/Setup_a_Samba_Active_Directory_Domain_Cont… > > > > As to the the keytab (#5) I did the following: > > > > $ samba-tool domain exportkeytab /etc/krb5.keytab > > > > which created the file. I made this owned and readable by group dovecot, per instructions at > > http://wiki2.dovecot.org/Authentication/Kerberos. Running `klist -k /etc/krb5.keytab` shows me > > configuration listing all the users and computers in the domain, mostly in triplicate. A > > partial list: > > > > Keytab name: FILE:/etc/krb5.keytab > > KVNO Principal > > ---- -------------------------------------------------------------------------- > > 18 COMMON$(a)HPRS.LOCAL > > 18 COMMON$(a)HPRS.LOCAL > > 18 COMMON$(a)HPRS.LOCAL > > 1 MAIL$(a)HPRS.LOCAL > > 1 MAIL$(a)HPRS.LOCAL > > 1 MAIL$(a)HPRS.LOCAL > > 1 charmaine(a)HPRS.LOCAL > > 1 charmaine(a)HPRS.LOCAL > > 1 charmaine(a)HPRS.LOCAL > > > > where COMMON and MAIL are hosts and charmaine is a user. I don't really understand the listing, > > but am assuming it is OK. > > Strange that you do not have any host/ entries. Maybe it works without. > > >> setspn -q is helpful here, also setspn command in general. > > I have no such command in my system. Is that a Windows thing? > > > > Yes, but you can do those kind of things in Samba too. > > > As to the /etc/krb5.conf, the default one generated by samba is: > > > > [libdefaults] > > default_realm = HPRS.LOCAL > > dns_lookup_realm = false > > dns_lookup_kdc = true > > > > I'd like to modify that to your suggestions, but I need more help. You have (with my questions): > > > >> Here is a *SAMPLE* configuration: > >> > >> [libdefaults] > >> default_realm = YOUR.REALM > >> dns_lookup_kdc = true > >> krb4_config = /etc/krb.conf > >> krb4_realms = /etc/krb.realms > > Here, you have krb4_*. Do you mean that? My config file is krb5.conf. Should I rather have: > > You can remove the krb4_ stuff > > > krb5_config = /etc/krb5.conf > > > > Also, I have no /etc/krb*.realms file. Do I need this? If so, what should be in there? > You don't necessarely require that. > > >> kdc_timesync = 1 > >> ccache_type = 4 > >> forwardable = true > >> proxiable = true > >> fcc-mit-ticketflags = true > >> > >> [realms] > >> YOUR.REALM = { > >> default_domain = your.domain.name > >> auth_to_local_names = { > >> Administrator = root > >> } > >> } > > I suppose my "YOUR.REALM" is HPRS.LOCAL, right? Is my "your.domain.name" my FQDN for my AD > > server: mail.hprs.local, or is it just hprs.local? (or something else!) > > HPRS.LOCAL is your REALM, hprs.local is your domain name. > > > >> [domain_realm] > >> your.domain.name = YOUR.REALM > >> # this is not a mistake > >> .your.domain.name = YOUR.REALM > >> [login] > >> krb4_convert = true > >> krb4_get_tickets = false > > Likewise here a question on the whole krb4 versus krb5 thing. > > > > Your closing comment: > > > >> Also, note that kerberos can only act as AUTHENTICATION system. It > >> cannot act as USER DATABASE. For that you need to configure LDAP or > >> something else. With Active Directory LDAP is probably a damn good idea. > > I have the following doveconf -n: > > > > # 2.2.15: /usr/local/etc/dovecot/dovecot.conf > > # OS: Linux 3.10.17 x86_64 Slackware 14.1 > > auth_debug_passwords = yes > > auth_krb5_keytab = /etc/krb5.keytab > > auth_mechanisms = plain login gssapi > > auth_verbose = yes > > auth_verbose_passwords = plain > > disable_plaintext_auth = no > > info_log_path = /var/log/dovecot_info > > mail_location = maildir:~/Maildir > > passdb { > > driver = shadow > > } > > protocols = imap > > ssl_cert = </etc/ssl/certs/OHPRS/GoDaddy/Apache/2015-08-14/57aa6ed6ae98b4c7.crt > > ssl_key = </etc/ssl/certs/OHPRS/GoDaddy/mail.ohprs.org.key > > userdb { > > driver = passwd > > } > > verbose_ssl = yes > > > > I assume the passwd driver for the userdb is OK? Seems to me it should work with gssapi, but in > > any case I still have all but this test workstation NOT using gssapi, so I still need to > > accomodate them. > > > > Thanks, --Mark > passwd driver is fine, yes, if you ensure that users can be found. > > Aki >

5 12

Suggestions? Moving maildir to new storage and may be switch to mdbox
by Götz Reinicke - IT Koordinator 01 Jul '16

01 Jul '16

Hi, we got a new storage for our mails and now we think about the best way to use it. Currently about 1TB is stored in maildirs, some mail has been moved to client side local storage temporarily to get space on the old storage. I think of different options, some downtime in mind: a) stay with maildir and just rsync/move all mail to the new storage, mount the new storage at the old mountpoint (or may be new mountpoint and edit the dovecot config). b) "dsync backup" users maildir to mdboxes at a temp mountpoint and change the dovecot config afterwords. c) your suggestions or best practice Thanks for feedback . Götz

1 0

v2.2.25 release candidate released
by Timo Sirainen 01 Jul '16

01 Jul '16

http://dovecot.org/releases/2.2/rc/dovecot-2.2.25.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.25.rc1.tar.gz.sig Quite a lot of changes. Please test out before the final v2.2.25 release, which I'm planning for tomorrow. Especially the new lib-dcrypt might have compiling problems with some OpenSSL versions. * lmtp: Start tracking lmtp_user_concurrency_limit and reject already at RCPT TO stage. This avoids MTA unnecessarily completing DATA only to get an error. * doveadm: Previously only mail settings were read from protocol doveadm { .. } section. Now all settings are. + quota: Added quota_over_flag_lazy_check setting. It avoids checking quota_over_flag always at startup. Instead it's checked only when quota is being read for some other purpose. + auth: Added a new auth policy service: http://wiki2.dovecot.org/Authentication/Policy + auth: Added PBKDF2 password scheme + auth: Added %{auth_user}, %{auth_username} and %{auth_domain} + auth: Added ":remove" suffix to extra field names to remove them. + auth: Added "delay_until=<timestamp>[+<max random secs>]" passdb extra field. The auth will wait until <timestamp> and optionally some randomness and then return success. + dict proxy: Added idle_msecs=<n> parameter. Support async operations. + Performance improvements for handling large mailboxes. + Added lib-dcrypt API for providing cryptographic functions. + Added "doveadm mailbox update" command + imap commands' output now includes timing spent on the "syncing" stage if it's larger than 0. + cassandra: Added metrics=<path> to connect setting to output internal statistics in JSON format every second to <path>. + doveadm mailbox delete: Added -e parameter to delete only empty mailboxes. Added --unsafe option to quickly delete a mailbox, bypassing lazy_expunge and quota plugins. + doveadm user & auth cache flush are now available via doveadm-server. + doveadm service stop <services> will stop specified services while leaving the rest of Dovecot running. + quota optimization: Avoid reading mail sizes for backends which don't need them (count, fs, dirsize) + Added mailbox { autoexpunge_max_mails=<n> } setting. + Added welcome plugin: http://wiki2.dovecot.org/Plugins/Welcome + fts: Added fts_autoindex_exclude setting. - v2.2.24's MIME parser was assert-crashing on mails having truncated MIME headers. - auth: With multiple userdbs the final success/failure result wasn't always correct. The last userdb's result was always used. - doveadm backup was sometimes deleting entire mailboxes unnecessarily. - doveadm: Command -parameters weren't being sent to doveadm-server. - If dovecot.index read failed e.g. because mmap() reached VSZ limit, an empty index could have been opened instead, corrupting the mailbox state. - imapc: Fixed EXPUNGE handling when imapc_features didn't have modseq. - lazy-expunge: Fixed a crash when copying failed. Various other fixes. - fts-lucene: Fixed crash on index rescan. - auth_stats=yes produced broken output - dict-ldap: Various fixes - dict-sql: NULL values crashed. Now they're treated as "not found".

6 9

Fwd: Re: Dictionary quota with Flat file database
by Sam 01 Jul '16

01 Jul '16

Hello Aki, Finally I am using maildir as quota backend and it works! I set the second way like it was write here http://wiki2.dovecot.org/Quota/Maildir With this method The quota can be personalized per user manually. I only have to create the file once for the new users. But I don't know if these following options in 90-quota.ext works again : quota_rule2 = Trash:storage=+100M quota_grace = 10%% I'm going to test that. Thanks a lot! Sam Le 30/06/2016 à 16:13, aki.tuomi(a)dovecot.fi a écrit : >> On June 30, 2016 at 4:41 PM Sam <sr42354(a)gmail.com> wrote: >> >> >> Hello, >> >> I want specific quotas for certain users and I looking for doing that >> with dictionary quota backend and Flat file. >> >> Because I am using "active directory" with PAM for authenticate, I can't >> get per-user quota limits with set/override them by returning >> "quota_rule" extra field from userdb. >> >> I started reading http://wiki1.dovecot.org/Quota/Dict, saw some good >> stuff... >> >> The problem is that I don't understand how to set the limit in the users >> files. >> >> If I open one created file I only see the current number of messages and >> the actual size. Not the quota limits... >> >> vi /home/vmail/john.doe/Maildir/dovecot-quota : >> priv/quota/messages >> 13 >> priv/quota/storage >> 600201 >> >> Here is /etc/dovecot/conf.d/90-quota.conf file details : >> plugin { >> # I think I have to set the default limits here >> quota_rule = *:storage=10G:messages=10000 >> } >> ... >> plugin { >> quota = dict:user::file:%h/Maildir/dovecot-quota >> # same result with : >> # quota = dict:User::file:%h/Maildir/dovecot-quota >> } >> >> my server : CentOS Linux release 7.2.1511 >> dovecot : dovecot-2.2.10-5.el7.x86_64 >> >> Thanks for helping. >> Sam > Hi! > > You can use passwd-file userdb for setting additional attributes. > > Aki

1 0

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

01 Jul '16

Hello Dovecot users, This upcoming release is all about bug fixes, of which only one is really important. It affects the new imapsieve plugin. Changelog v0.4.15: - 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. - Several small fixes based on static analysis. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/rc/dovecot-2.2-pigeonhole-0.4.15… http://pigeonhole.dovecot.org/releases/2.2/rc/dovecot-2.2-pigeonhole-0.4.15… Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this release candidate and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

quota-status service
by Michael Fox 30 Jun '16

30 Jun '16

I'm trying to understand the quota-status service, but I can't find complete documentation. The quota-status service is mentioned here: http://wiki.dovecot.org/Quota And an example configuration is shown: service quota-status { executable = quota-status -p postfix inet_listener { port = 12340 # You can choose any port you want } client_limit = 1 } But I can't find any information on quota-status. "man quota-status" returns nothing. I am unable to find a "quota-status" file on my machine. Where is the executable located? What does the "-p postfix" option do? Are there any other command line options? The above wiki page shows three quota_status_* options in use: quota_status_success = DUNNO quota_status_nouser = DUNNO quota_status_overquota = "552 5.2.2 Mailbox is full" Where are their meanings documented? What are the allowed values? Are there other quota_status_* options? Thanks in advance. Thanks, Michael

1 0

quota_full_tempfail
by Felipe Gasper 30 Jun '16

30 Jun '16

Hi all, What specifically does this flag do? Does it affect what happens: -------------- - when the drive is full? - when the system user’s disk quota is full? - when the mailbox’s quota is full? -------------- Also, does it work with both LDA and LMTP? I don’t see much on this option in the docs. Thank you! -Felipe Gasper Houston, TX

1 0

Re: Error when searching in mailfolders
by Christoph Pleger 30 Jun '16

30 Jun '16

Hello, >>> Lucene library is throwing an error, which crashes Dovecot. Maybe Dovecot >>> should catch the error, but it would still be broken. Try deleting the lucene indexes and rebuilding them? >> Deleting the indexes helped, but after they had been rebuilt, the error occurred again. > Could you enable core dumps and run bt full in gdb? I attached the result. Regards Christoph

2 2

Remove my email id from mailing list
by Mayuri AgarwAl 30 Jun '16

30 Jun '16

Sent from my iPhone

2 1

Dictionary quota with Flat file database
by Sam 30 Jun '16

30 Jun '16

Hello, I want specific quotas for certain users and I looking for doing that with dictionary quota backend and Flat file. Because I am using "active directory" with PAM for authenticate, I can't get per-user quota limits with set/override them by returning "quota_rule" extra field from userdb. I started reading http://wiki1.dovecot.org/Quota/Dict, saw some good stuff... The problem is that I don't understand how to set the limit in the users files. If I open one created file I only see the current number of messages and the actual size. Not the quota limits... vi /home/vmail/john.doe/Maildir/dovecot-quota : priv/quota/messages 13 priv/quota/storage 600201 Here is /etc/dovecot/conf.d/90-quota.conf file details : plugin { # I think I have to set the default limits here quota_rule = *:storage=10G:messages=10000 } ... plugin { quota = dict:user::file:%h/Maildir/dovecot-quota # same result with : # quota = dict:User::file:%h/Maildir/dovecot-quota } my server : CentOS Linux release 7.2.1511 dovecot : dovecot-2.2.10-5.el7.x86_64 Thanks for helping. Sam

2 1

Unread Mail flag being reset frequently with dovecot -git master-2.2
by Reuben Farrelly 30 Jun '16

30 Jun '16

Hi again, I'm experiencing problems with the Dovecot git master-2.2 branch, in which mails that have been previously read are randomly appearing as unread. This happens slowly and affects more and more emails the more changes that occur to a mailbox. I am using Maildir format and on Gentoo Linux x86_64 on local disks. Usually only a few at a time change their status - and it seems to be random which ones lose their read status. Typically though they are the most recent emails that have been delivered in the past few months (I haven't yet seen this occur with any really old emails). This problem is MUA independent, it can be observed with Thunderbird as well as Roundcube. If I go in and mark all mails as read then they will show as read for a short while until they too slowly start become 'unread' again. Currently I'm running git rev from https://github.com/dovecot/core/commits/master-2.2 : f292589f4b85e02d97d974dfe34324c6c0bb9d9f (I can't run anything newer due to an SSL symbol error which I reported earlier). This rev: b1254dfe442639236f881afae85e0739520ab409 Is known to be good, so the problem started happening somewhere between these two. (I know there are a lot of in-between revisions, but bisecting that could take days of time). Dovecot config is up at: http://www.reub.net/files/dovecot/thunderstorm-dovecot.conf Rawlog debug files are at http://www.reub.net/files/dovecot/rawlogs/ Hopefully someone else may have seen this happen before. Are there any other debugs I can gather which will help get to the bottom of this? Reuben

2 2

Re[2]: External mail attachments storage cleanup
by Николай Мананков 30 Jun '16

30 Jun '16

Yes "dovecot purge" is certainly my mistake in the script but it really works completely analogous "doveadm purge" probably why I did not notice the difference before :) It looks like it just launches the doveadm in this case. Adding slashes after asterisks unfortunately they also adds to the variable and the script gives an error like "doveadm(user/(a)example.org/): Error: User doesn't exist" Thanks for the idea , I think it will be now more correctly : === #!/bin/sh cd /backup/MailRoot/dovecot/domains || exit 1 for i in * do if [ -d $i ]; then cd $i for j in * do if [ -d $j ]; then dovecot purge -u $j@$i fi done cd .. fi done === >Четверг, 30 июня 2016, 13:53 +03:00 от Alexander Moisseev <moiseev(a)mezonplus.ru>: > >On 30.06.16 12:51, Николай Мананков wrote: >> -----screenshot begin----- >> >> mail:/etc/cron.daily # cat ./dovepurge.sh >> #!/bin/sh >> >> cd /MailRoot/dovecot/domains >> >> for i in * >> do >> cd $i >> for j in *; do dovecot purge -u $j@$i; done >> cd .. >> done >> >> -----screenshot end ----- >> >It might be worth to add slashes after asterisks to process only directories. >Does "dovecot purge" actually work? > >-----screenshot begin----- > >#!/bin/sh > >cd /MailRoot/dovecot/domains || exit 1 > >for i in */ > do > cd $i > for j in */; do doveadm purge -u $j@$i; done > cd .. >done > >-----screenshot end ----- > >> It is strange that the daemon does not do this automatically, and even setting up autoexpunge option does not help. Also IMHO certainly evident mistake in the documentation about the wildcards processing by purge command.. > >I don't know how the developers themselves use Dovecot, but it lacks some obvious features like automatic purge or SIS cleanup on mailbox deletion. >

1 0

Re[2]: External mail attachments storage cleanup
by Николай Мананков 30 Jun '16

30 Jun '16

Yes "dovecot purge" is certainly my mistake in the script but it really works completely analogous "doveadm purge" probably why I did not notice the difference before :) It looks like it just launches the doveadm in this case. Adding slashes after asterisks unfortunately they also adds to the variable and the script gives an error like "doveadm(user/(a)example.org/): Error: User doesn't exist" Thanks for the idea , I think it will be now more correctly : === #!/bin/sh cd /backup/MailRoot/dovecot/domains || exit 1 for i in * do if [ -d $i ]; then cd $i for j in * do if [ -d $j ]; then dovecot purge -u $j@$i fi done cd .. fi done === >Четверг, 30 июня 2016, 13:53 +03:00 от Alexander Moisseev <moiseev(a)mezonplus.ru>: > >On 30.06.16 12:51, Николай Мананков wrote: >> -----screenshot begin----- >> >> mail:/etc/cron.daily # cat ./dovepurge.sh >> #!/bin/sh >> >> cd /MailRoot/dovecot/domains >> >> for i in * >> do >> cd $i >> for j in *; do dovecot purge -u $j@$i; done >> cd .. >> done >> >> -----screenshot end ----- >> >It might be worth to add slashes after asterisks to process only directories. >Does "dovecot purge" actually work? > >-----screenshot begin----- > >#!/bin/sh > >cd /MailRoot/dovecot/domains || exit 1 > >for i in */ > do > cd $i > for j in */; do doveadm purge -u $j@$i; done > cd .. >done > >-----screenshot end ----- > >> It is strange that the daemon does not do this automatically, and even setting up autoexpunge option does not help. Also IMHO certainly evident mistake in the documentation about the wildcards processing by purge command.. > >I don't know how the developers themselves use Dovecot, but it lacks some obvious features like automatic purge or SIS cleanup on mailbox deletion. >

1 0

[patch] Support redis AUTH
by Dave 30 Jun '16

30 Jun '16

A very minor patch to support redis AUTH (for all that's worth) using an extra password= field. I'm not sure if this will be of any value to anyone here. We're testing it in development and "it works for us" but it's yet to be used in anger. Sorry if I'm going about this the wrong way, I tried emailing this directly but heard nothing back; so I'm reposting to the list as I'm honestly not sure what established protocol is regarding code contribution. -- Dave

2 1

filtering ssl_cert
by Russell Stuart 30 Jun '16

30 Jun '16

In dovecot 1 I was able to do something like this: protocol imap { ssl_cert = cert-imap.pem ssl_key = key-imap.pem } local ww.xx.yy.zz { protocol imap { ssl_cert = cert-imap-ww.xx.yy.zz.pem ssl_key = key-imap-ww.xx.yy.zz.pem } } The intent is ww.xx.yy.zz is an externally routable IP address which has a Cert signed by a real CA, other addresses are internal which have a variety of domain names, signed by a self-signed cert. That worked in dovecot 1, but in dovecot 2 I get the error: "Conflict in setting ssl_cert found from filter". Weirdly, this works in dovecot 2: local 0.0.0.0/0 { ssl_cert = cert-imap.pem ssl_key = key-imap.pem } local ww.xx.yy.zz { ssl_cert = cert-imap-ww.xx.yy.zz.pem ssl_key = key-imap-ww.xx.yy.zz.pem } But this doesn't: local 0.0.0.0/0 { protocol imap { ssl_cert = cert-imap.pem ssl_key = key-imap.pem } } local ww.xx.yy.zz { protocol imap { ssl_cert = cert-imap-ww.xx.yy.zz.pem ssl_key = key-imap-ww.xx.yy.zz.pem } } It smells like a bug. Anyway, does anybody know of a way to port my config to dovecot 2?

1 0

External mail attachments storage cleanup
by Николай Мананков 30 Jun '16

30 Jun '16

Hi, I have set up mdbox backend witch saving mail attachments to external files option. Dovecot store attachments to external files but never delete them. Why?

3 4

ltmp, quota and quota grace
by Sylvain Allemand 30 Jun '16

30 Jun '16

Hi, i try to configure quota in dovecot. 1) I test quota with postfix and quota-status : quota is respected but quota grace is ignored... 2) i test quota with Dovecot LMTP : quota (and quota grace) are ignored i can see in log file : Jun 30 11:36:39 mail1 dovecot: lmtp(24424, sallemantest(a)test.fr) Debug: Quota root: name=User quota sallemantest(a)test.fr backend=count args= Jun 30 11:36:39 mail1 dovecot: lmtp(24424, sallemantest(a)test.fr) Debug: Quota rule: root=User quota sallemantest(a)test.fr mailbox=* bytes=1073741824 messages=0 Jun 30 11:36:39 mail1 dovecot: lmtp(24424, sallemantest(a)test.fr) Debug: Quota rule: root=User quota sallemantest(a)test.fr mailbox=Trash bytes=+104857600 messages=0 Jun 30 11:36:39 mail1 dovecot: lmtp(24424, sallemantest(a)test.fr) Debug: Quota grace: root=User quota sallemantest(a)test.fr bytes=107374182 (10%) Jun 30 11:36:39 mail1 dovecot: lmtp(sallemantest(a)test.fr): Debug: replication: Replication requested by 'transaction commit', priority=2 Jun 30 11:36:39 mail1 dovecot: lmtp(sallemantest(a)test.fr): /z7gBifodFdoXwAAs3/TQA: msgid=<fdf98d16-c557-4e15-42a6-ea019a3bae1e(a)math.u-bordeaux.fr>: saved mail to INBOX Jun 30 11:36:39 mail1 dovecot: lmtp(24424): Disconnect from 127.0.0.1: Successful quit my quota : root@mail1:~# doveadm -v quota get -u sallemantest(a)test.fr Quota name Type Value Limit % User quota sallemantest(a)test.fr STORAGE 29 10 290 User quota sallemantest(a)test.fr MESSAGE 11 - 0 my config for lmtp and quota : protocol lmtp { mail_plugins = " acl notify replication quota sieve" userdb { args = /etc/dovecot/dovecot-lmtp-ldap-userdb.conf.ext default_fields = uid=vmail gid=vmail driver = ldap name = } } plugin { quota = count:User quota %u quota_grace = 10%% quota_rule = *:storage=1G quota_rule2 = Trash:storage=+100M quota_vsizes = yes } root@mail1:/etc/dovecot# dovecot --version 2.2.24 (a82c823) Help please ! Sylvain ps : sorry for my poor english

1 0