- dovecot - dovecot.org

Problem with envelope from in Pigeonhole after upgrade
by David Dodd 17 Sep '18

17 Sep '18

On our FreeBSD 11.2 servers, we recently upgraded from: dovecot2-2.2.26.0_1 dovecot-pigeonhole-0.4.16_1 to: dovecot-2.3.2.1 dovecot-pigeonhole-0.5.2_3 Prior to the upgrade the envelope sender was as expected. After the upgrade, the envelope sender for a user with a sieve script configured is now being set to: >From MAILER-DAEMON Tue Sep 04 13:31:39 2018 The same user without a sieve script in place gets: >From someone(a)gmail.com Tue Sep 04 11:06:04 2018 This happens when manually testing by directly executing: /usr/local/libexec/dovecot/dovecot-lda -d dgdtst -f someone(a)gmail.com It happens with an empty sieve script i.e. just using the implicit keep functionality. I have groped around looking for a configuration setting that might fix the behaviour but nothing I have tried helps. Can anyone suggest what to set to correct the problem ? -- Dave

2 7

Quotas not working with roundcube
by Mik J 17 Sep '18

17 Sep '18

Hello, I'm trying to have quotas working with roundcube. When I'm logged into roundcube I see 0% quota which seems to correspond to disabled. However I did everything that I could to enable quotas https://wiki.dovecot.org/Quota # doveconf -n auth_mechanisms = cram-md5 loginauth_verbose = yes debug_log_path = /tmp/dovecot.log first_valid_uid = 1000 log_path = /var/log/dovecot.log mail_gid = vmail mail_location = maildir:/home/mail/%d/%n/Maildir mail_plugins = notify replication quota mail_uid = vmail mbox_write_locks = fcntl mmap_disable = yes 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 { driver = bsdauth } passdb { args = /etc/dovecot/dovecot.passwd driver = passwd-file } plugin { quota_grace = 10%% quota_rule = *:storage=2G quota_rule2 = Trash:storage=+200M quota_rule3 = SPAM:ignore quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u } ssl_ca = /etc/ssl/certs/CA_Intermed_Lets_Encrypt.crt ssl_cert = </etc/ssl/certs/imap.mydomain.org.crt ssl_key = # hidden, use -P to show it ssl_key_password = # hidden, use -P to show it userdb { driver = passwd } userdb { driver = static } protocol lda { mail_plugins = notify replication quota } protocol imap { mail_plugins = notify replication quota imap_quota }

3 5

Dsync deleting mailboxes due to duplicate UIDs
by Andreas Thienemann 16 Sep '18

16 Sep '18

Hi, I am attempting to migrate a mailspool from a cyrus server to a dovecot server using the dsync backup approach as described in the wiki at <https://wiki.dovecot.org/Migration/Dsync>. The first attempt works great. Everything copies over and a quick glance over the spool looks good. Running doveadm backup again though results in the following error: dsync(eggs): Warning: Deleting mailbox 'INBOX.MailRestore': UID=39 already exists locally for a different mail: Headers hashes don't match (18d567fc7e258a67e47b629c8bb16500 vs 230354b2d5cad21ebbb4a7440b977adb) As promised, the folder MailRestore is gone after dsync finishes. Running doveadm backup again for the third time copies the folder again. Running it a fourth time gives the same error and the folder is gone. Trying to figure this out I initially had a few mails where the header hashes were 68b329da9893e34099c7d8ad5cb9c940, the md5sum of an empty string. Turns out that the source mailspool had a few broken emails and cleaning these out fixed most my issues. But in this case, I am stumped. UID 39 on the server is a valid mail with correct headers and everything. Is there a good way of identifying the two mails that seem to clash? I had a quick look at the dovecot code but did not see how the header_stream gets hashed into the hdr_hash used for comparing mails. Thanks, Andreas

3 5

dovecot_deleted_to_trash no longer compiles with dovecot 2.3.2.1
by Robert S 16 Sep '18

16 Sep '18

I have just upgraded to the latest version of dovecot (Gentoo amd64). When I try to compile the dovecot_deleted_to_trash plugin it won't compile. Is this plugin going to be updated (from https://github.com/lexbrugman/dovecot_deleted_to_trash - same error from https://github.com/NethServer/dovecot-deleted-to-trash)? # make cc \ -fPIC -shared -Wall \ -I/usr/include/dovecot \ -I/usr/include/dovecot/src \ -I/usr/include/dovecot/src/lib \ -I/usr/include/dovecot/src/lib-storage \ -I/usr/include/dovecot/src/lib-mail \ -I/usr/include/dovecot/src/lib-imap \ -I/usr/include/dovecot/src/lib-index \ -DHAVE_CONFIG_H \ src/deleted-to-trash-plugin.c -o lib_deleted_to_trash_plugin.so src/deleted-to-trash-plugin.c: In function ‘copy_deleted_mail_to_trash’: src/deleted-to-trash-plugin.c:117:16: error: too few arguments to function ‘mail box_transaction_begin’ dest_trans = mailbox_transaction_begin(trash_box, MAILBOX_TRANSACTION_FLAG_EX TERNAL); ^~~~~~~~~~~~~~~~~~~~~~~~~ In file included from /usr/include/dovecot/mail-storage-private.h:7:0, from src/deleted-to-trash-plugin.h:5, from src/deleted-to-trash-plugin.c:4: /usr/include/dovecot/mail-storage.h:656:1: note: declared here mailbox_transaction_begin(struct mailbox *box, ^~~~~~~~~~~~~~~~~~~~~~~~~ make: *** [Makefile:32: lib_deleted_to_trash_plugin.so] Error 1 Some further info: # dovecot -n # 2.3.2.1 (0719df592): /etc/dovecot/dovecot.conf # OS: Linux 4.14.8-gentoo-r1 x86_64 Gentoo Base System release 2.4.1 # Hostname: basement-vm.schmidli.com.au doveconf: Warning: please set ssl_dh=</etc/dovecot/dh.pem doveconf: Warning: You can generate it with: dd if=/var/lib/dovecot/ssl-parameters.dat bs=1 skip=88 | openssl dhparam -inform der > /etc/dovecot/dh.pem dict { expire = db:/var/lib/dovecot/expire.db } disable_plaintext_auth = no listen = * mail_location = maildir:~/.maildir mail_plugins = deleted_to_trash mailbox_alias 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 = * driver = pam } plugin { deleted_to_trash_folder = Trash expire = Trash 7 Spam 30 expire_dict = proxy::expire

1 0

Re: auth_policy in a non-authenticating proxy chain
by Peter Mogensen 15 Sep '18

15 Sep '18

On 09/15/2018 10:41 AM, Aki Tuomi wrote: > Point of sending the success ones is to maintain whitelist as well as > blacklist so you know which ones you should not tarpit anymore. We > know it does scale as we have very large deployments using the whole > three request per login model. > > "Success" in a proxy which is not it self authenticating is only whether it know where to proxy the requested username to. I'm not sure whether this would be input to a whitelist. I'm not doubting that 3 req/login scales. /Peter

2 1

auth_policy in a non-authenticating proxy chain
by Peter Mogensen 15 Sep '18

15 Sep '18

Hi, I was looking into the new Authentication Policy feature: https://wiki2.dovecot.org/Authentication/Policy I had kinda hoped that I would be able to enfore this in a proxy running in front of several backends. This proxy does not authenticate. It use "nopassword". But I realize that the "succes" reported in the final authpolicy req. (command=report) is not what is actaully happening on the IMAP protocol level, but rather the result of the passdb chain in the proxy. (I should probably have predicted this, it's kinda reasonable). However... since the proxy use "nopassword", ALL passdb lookups result in "success", so the proxy will never report an authentication failure to the authpolicy server. This, of course, forces me to do the authpolicy check on the backend with a shared state, but It would still have been nice to have the proxy being able to do the first "command=allow" req. and reject attemps already there even though the backend does "command=report". /Peter

3 4

encryption issue in outlook 2016
by ChandranManikandan 14 Sep '18

14 Sep '18

Hi Friends, Am facing the serious issue in outlook 2016. When i tried to configure the email in outlook 2016 it's asking encrypted connection and checked automatically and if not available then it showing unencrypted. but finally unable to configure the email account in outlook 2016 and not permitted. Do i need to update any in the server. Am using COS 6 32 and 64 bit servers with qmailtoaster + dovecot 2.2.7. Currently configured in outlook 2010 it's working without any issue. And always showing in outlook 2010 when i open the account. Do you want to continue yes or no for the certification. Because i have configured in advanced selected Auto in outlook 2010. If i select none it was not working the email. Anyone facing the same issue. How do i rectify it in outlook 2016 and how can i stop the certificate warning message in outlook. If possible to use without encryption and what's the configuration. Please advice and let me know the process. Am seriously cannot access the email from outlook. I have attached the message while open outlook. If i click yes then it will open Is the certificate expired. How do renew it or reload it with the fresh certificate. -- *Thanks & Best Regards,Manikandan.C*

4 4

Occasional crash in db-auth.c (Valgrind: Invalid read of size 4 et al.), Dovecot 2.2.27+
by Jonas Wielicki 14 Sep '18

14 Sep '18

Dear list, We are encountering troubles with dovecot using LDAP userdbs on Debian stretch (but if I’m reading valgrind correctly, we can reproduce this with vanilla dovecot master). Minimal reproducer below. While testing an upgrade to Debian stretch (dovecot-core=1:2.2.27-3+deb9u1), auth-worker has stopped working. We are using two LDAP user databases; one which is iterable, and one which is not (for reasons; I think this is not relevant; if it is, we’re happy to elaborate). The issue seems to be present in any LDAP userdb iteration handling, but it only seems to cause a crash in certain conditions which seem to be reproducibly caused by our setup for some reason. We’re seeing one of two errors. Variant A: Jan 27 13:40:05 up2 dovecot: auth-worker: Error: *** Error in `dovecot/auth': free(): corrupted unsorted chunks: 0x000056553f0fcfa0 *** Jan 27 13:40:05 up2 dovecot: auth-worker: Error: ======= Backtrace: ========= Jan 27 13:40:05 up2 dovecot: auth-worker: Error: /lib/x86_64-linux-gnu/ libc.so.6(+0x70bcb)[0x7f78426adbcb] Jan 27 13:40:05 up2 dovecot: auth-worker: Error: /lib/x86_64-linux-gnu/ libc.so.6(+0x76f96)[0x7f78426b3f96] Jan 27 13:40:05 up2 dovecot: auth-worker: Error: /lib/x86_64-linux-gnu/ libc.so.6(+0x777de)[0x7f78426b47de] Jan 27 13:40:05 up2 dovecot: auth-worker: Error: /usr/lib/dovecot/modules/ auth/libauthdb_ldap.so(+0x5bde)[0x7f7842008bde] Jan 27 13:40:05 up2 dovecot: auth-worker: Error: /usr/lib/dovecot/ libdovecot.so.0(io_loop_call_io+0x52)[0x7f78430cfdd2] Jan 27 13:40:05 up2 dovecot: auth-worker: Error: /usr/lib/dovecot/ libdovecot.so.0(io_loop_handler_run_internal+0x109)[0x7f78430d1409] Jan 27 13:40:05 up2 dovecot: auth-worker: Error: /usr/lib/dovecot/ libdovecot.so.0(io_loop_handler_run+0x3c)[0x7f78430cfe6c] Jan 27 13:40:05 up2 dovecot: auth-worker: Error: /usr/lib/dovecot/ libdovecot.so.0(io_loop_run+0x38)[0x7f78430d0018] Jan 27 13:40:05 up2 dovecot: auth-worker: Error: /usr/lib/dovecot/ libdovecot.so.0(master_service_run+0x13)[0x7f7843057e93] Jan 27 13:40:05 up2 dovecot: auth-worker: Error: dovecot/auth(main+0x398) [0x56553da45f98] Jan 27 13:40:05 up2 dovecot: auth-worker: Error: /lib/x86_64-linux-gnu/ libc.so.6(__libc_start_main+0xf1)[0x7f784265d2b1] Jan 27 13:40:05 up2 dovecot: auth-worker: Error: dovecot/auth(_start+0x2a) [0x56553da461aa] Variant B: Jan 27 13:06:56 up2 dovecot: auth-worker(27495): Panic: file db-ldap.c: line 840 (db_ldap_result_unref): assertion failed: (res->refcount > 0) Jan 27 13:06:56 up2 dovecot: auth-worker(27495): Error: Raw backtrace: /usr/ lib/dovecot/libdovecot.so.0(+0x95272) [0x7f027a4fc272] -> /usr/lib/dovecot/ libdovecot.so.0(+0x9536d) [0x7f027a4fc36d] -> /usr/lib/dovecot/libdovecot.so. 0(i_fatal+0) [0x7f027a492951] -> /usr/lib/dovecot/modules/auth/ libauthdb_ldap.so(+0x3868) [0x7f0279447868] -> /usr/lib/dovecot/modules/auth/ libauthdb_ldap.so(+0x5d7c) [0x7f0279449d7c] -> /usr/lib/dovecot/libdovecot.so. 0(io_loop_call_io+0x52) [0x7f027a510dd2] -> /usr/lib/dovecot/libdovecot.so. 0(io_loop_handler_run_internal+0x109) [0x7f027a512409] -> /usr/lib/dovecot/ libdovecot.so.0(io_loop_handler_run+0x3c) [0x7f027a510e6c] -> /usr/lib/ dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f027a511018] -> /usr/lib/ dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f027a498e93] -> dovecot/ auth(main+0x398) [0x55b981cd2f98] -> /lib/x86_64-linux-gnu/libc.so. 6(__libc_start_main+0xf1) [0x7f0279a9e2b1] -> dovecot/auth(_start+0x2a) [0x55b981cd31aa] When running auth-worker within valgrind, we get more information (valgrind extract from mail.log attached for two versions of dovecot). We have attached mail.log contents for the respective valgrind runs. This seems to affect at least 2.2.27 onwards. We can reproduce the crash with our production data 100% of the time. The valgrind error is present even with very minimal setups (see below). Unfortunately, I haven’t been able so far to create an LDAP database which produces the crash as reliable as our production database does (which we cannot share for obvious reasons). Minimal Reproducer of Valgrind error: - Install dovecot 2.2.27 from debian stretch, or compile from master. - Install valgrind - In conf.d/10-auth.conf, disable auth-system.conf.ext - In conf.d/10-auth.conf, enable auth-ldap.conf.ext - Set contents of dovecot-ldap.conf.ext to: hosts = localhost base = dc=nodomain - In conf.d/10-master.conf, in section "service auth-worker", set executable = /usr/bin/valgrind /usr/lib/dovecot/auth -w (path may differ on your system) - Install an LDAP server with a database for dc=nodomain; this is trivial to do with debian: Simply install slapd and systemctl start slapd. - Start dovecot - Run doveadm user '*' - You should find the error in the mail.log. I hope this is somehow useful to fix our crash issue. We’ll be happy to provide more information as needed. kind regards, Jonas

4 4

Status of SMTPUTF8?
by Noah Tilton 14 Sep '18

14 Sep '18

I was wondering whether there is a roadmap for adding SMTPUTF8 support to Dovecot? My delivery pattern is Postfix -> Dovecot LMTP and it is choking on utf8 messages. I might be able to volunteer some of my time as a developer. Another thread about this seemed to go unanswered: http://dovecot.org/list/dovecot/2016-September/105474.html http://unix.stackexchange.com/questions/320091/configure-postfix-and-doveco… -Noah

4 3

LMTP tcp listener with auth?
by Andreas Thienemann 14 Sep '18

14 Sep '18

I am wondering if it's possible to have a tcp listener for LMTP do authentication and not accept any unauthenticated mail. My configuration looks like the following: service lmtp { inet_listener lmtp { address = 192.168.0.1 127.0.0.1 port = 24 } } This gives me a network reachable lmtp socket, but of course no autentication. When reading the docs, it seems though that only userdb lookup and no actual authentication is supported? Is that understanding correct? cheers, Andreas

4 3

Server certificate verification error with Dovecot 2.3.2.1
by Robert Gill 13 Sep '18

13 Sep '18

I'm attempting to upgrade my Dovecot installation to 2.3.2.1. My SSL certificate authority provides a bundle containing their CA, plus intermediate CAs, which I configure using the 'ssl_ca' option. The comments in the configuration file say to only set this when you're requiring client certificates, which I'm not, but fetchmail complains with a "Server certificate verification error, Broken certificate chain" error if that setting is not set. This works fine with Dovecot 2.2.34. After upgrading to 2.3.2.1, fetchmail throws that error whether 'ssl_ca' is set or not. Dovecot 2.3.2.1 reports the error SSL routines:ssl3_read_bytes:tlsv1 alert unknown ca: SSL alert number 48 in the logs when attempting the TLS handshake. The permissions on the CA bundle haven't changed and should still be readable by Dovecot. I'm running Gentoo Linux on x86_64 and mail is stored on an ext4 file system. I'm attaching my config files for both Dovecot 2.2.34 and Dovecot 2.3.2.1.

3 3

dovecot + centos 7 + internal ca + hostname change
by Matt Bryant 13 Sep '18

13 Sep '18

Not sure if this is dovecot or not but can find very little ie no info around on this ... and added the pem file into /etc/pki/ca-trust/source/anchors and run udpate-ca-trust .. all works ok .. (this is on centos 7 btw) So wanted to change the hostname away from ip-x-x-x-x to something a little bit more descriptive .. but then kaboom .. doesnt work any more and the following errors are seen. Have created and internal CA for domain and added it to Sep 13 10:42:04 ip-10-0-40-230 dovecot: master: Dovecot v2.2.33.2 (d6601f4ec) starting up for imap, pop3, lmtp, sieve (core dumps disabled) Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: 'attr->pValue != NULL' not true at attrs_build Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: 'lexer->tok.field.name && lexer->tok.field.value' not true at p11_lexer_next Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: 'attrs != NULL' not true at attrs_build Sep 13 10:42:04 ip-10-0-40-230 dovecot: message repeated 16 times: [ auth: Error: p11-kit: 'attrs != NULL' not true at attrs_build] Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: 'new_memory != NULL' not true at maybe_expand_array Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: shouldn't be reached at p11_array_push Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: shouldn't be reached at sink_object Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: 'attrs != NULL' not true at attrs_build Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: 'new_memory != NULL' not true at maybe_expand_array Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: shouldn't be reached at p11_array_push Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: shouldn't be reached at sink_object ... ... Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: 'new_memory != NULL' not true at maybe_expand_array Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: shouldn't be reached at p11_array_push Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: shouldn't be reached at sink_object Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: 'attr->pValue != NULL' not true at attrs_build Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: 'new_memory != NULL' not true at maybe_expand_array Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: shouldn't be reached at p11_array_push Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: shouldn't be reached at sink_object Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: no CKA_CLASS attribute found Sep 13 10:42:04 ip-10-0-40-230 dovecot: auth: Error: p11-kit: couldn't load file into objects: /usr/share/pki/ca-trust-source/ca-bundle.trust.p11-kit Sep 13 10:42:05 ip-10-0-40-230 dovecot: auth-worker: Error: p11-kit: 'attrs != NULL' not true at attrs_build Sep 13 10:42:05 ip-10-0-40-230 dovecot: auth-worker: Fatal: master: service(auth-worker): child 14389 killed with signal 11 (core dumps disabled) Sep 13 10:42:05 ip-10-0-40-230 dovecot: auth-worker: Error: p11-kit: 'attrs != NULL' not true at attrs_build Sep 13 10:42:05 ip-10-0-40-230 dovecot: auth-worker: Fatal: master: service(auth-worker): child 14391 killed with signal 11 (core dumps disabled) Sep 13 10:42:05 ip-10-0-40-230 dovecot: auth-worker: Error: p11-kit: 'attrs != NULL' not true at attrs_build Sep 13 10:42:05 ip-10-0-40-230 dovecot: auth-worker: Fatal: master: service(auth-worker): child 14393 killed with signal 11 (core dumps disabled) why would a hostname change make any difference here .. the certs specified in dovecot config are all complete in their chain so not sure what its trying to do ... set hostname back to original works find .. so something is obviously tied or keyed to hostname though cant find anything specific anyone seen anything like this at all ?? rgds Matt

1 1

Re: make check (pigeonhole)
by Eric Broch 12 Sep '18

12 Sep '18

Must be non root user as well On 9/12/2018 1:05 PM, Aki Tuomi wrote: > Ok. We have that fix as well but for other reasons. Good to know this. > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Eric Broch <ebroch(a)whitehorsetc.com> > Date: 12/09/2018 21:36 (GMT+02:00) > To: Aki Tuomi <aki.tuomi(a)dovecot.fi>, dovecot(a)dovecot.org > Subject: Re: make check (pigeonhole) > > Hi Aki, > > I needed this patch > <https://src.fedoraproject.org/cgit/rpms/dovecot.git/tree/dovecot-2.3.0.1-li…> > (fedora): > > |diff -up dovecot-2.3.0.1/src/auth/mycrypt.c.libxcrypt > dovecot-2.3.0.1/src/auth/mycrypt.c --- > dovecot-2.3.0.1/src/auth/mycrypt.c.libxcrypt 2018-02-28 > 15:28:58.000000000 +0100 +++ dovecot-2.3.0.1/src/auth/mycrypt.c > 2018-03-27 10:57:38.447769201 +0200 @@ -14,6 +14,7 @@ # define _XPG6 > /* Some Solaris versions require this, some break with this */ #endif > #include <unistd.h> +#include <crypt.h> #include "mycrypt.h" All works > well now. Thanks for your help Eric | > > On 9/12/2018 12:35 AM, Aki Tuomi wrote: >> >> I tried reproducing your problem and I only can make it happen if I >> run the test suite as root, which is not supported. >> >> Aki >> >> >> On 12.09.2018 06:49, Eric Broch wrote: >>> >>> I'll give those a look and make change accordingly. >>> >>> >>> On 9/11/2018 9:26 PM, Aki Tuomi wrote: >>>> You know we have rpm packages for 2.3.2.1 available at >>>> https://repo.dovecot.org if you are in a hurry? >>>> >>>> >>>> >>>> --- >>>> Aki Tuomi >>>> Dovecot oy >>>> >>>> -------- Original message -------- >>>> From: Eric Broch <ebroch(a)whitehorsetc.com> >>>> Date: 12/09/2018 00:35 (GMT+02:00) >>>> To: dovecot(a)dovecot.org >>>> Subject: Re: make check (pigeonhole) >>>> >>>> Any news on this error on CentOS 7 ? >>>> >>>> Help! >>>> >>>> >>>> On 9/10/2018 9:32 AM, Eric Broch wrote: >>>>> >>>>> I attempted as non-root user and got the exact same error. >>>>> >>>>> >>>>> On 9/10/2018 9:10 AM, Aki Tuomi wrote: >>>>>> Have you attempted this as non-root user? >>>>>> >>>>>> >>>>>> >>>>>> --- >>>>>> Aki Tuomi >>>>>> Dovecot oy >>>>> >>>>> -- >>>>> Eric Broch >>>>> White Horse Technical Consulting (WHTC) >>>> >>>> -- >>>> Eric Broch >>>> White Horse Technical Consulting (WHTC) >>> >>> -- >>> Eric Broch >>> White Horse Technical Consulting (WHTC) >> > > -- > Eric Broch > White Horse Technical Consulting (WHTC) -- Eric Broch White Horse Technical Consulting (WHTC)

1 0

Re: make check (pigeonhole)
by Eric Broch 12 Sep '18

12 Sep '18

I'll give those a look and make change accordingly. On 9/11/2018 9:26 PM, Aki Tuomi wrote: > You know we have rpm packages for 2.3.2.1 available at > https://repo.dovecot.org if you are in a hurry? > > > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Eric Broch <ebroch(a)whitehorsetc.com> > Date: 12/09/2018 00:35 (GMT+02:00) > To: dovecot(a)dovecot.org > Subject: Re: make check (pigeonhole) > > Any news on this error on CentOS 7 ? > > Help! > > > On 9/10/2018 9:32 AM, Eric Broch wrote: >> >> I attempted as non-root user and got the exact same error. >> >> >> On 9/10/2018 9:10 AM, Aki Tuomi wrote: >>> Have you attempted this as non-root user? >>> >>> >>> >>> --- >>> Aki Tuomi >>> Dovecot oy >> >> -- >> Eric Broch >> White Horse Technical Consulting (WHTC) > > -- > Eric Broch > White Horse Technical Consulting (WHTC) -- Eric Broch White Horse Technical Consulting (WHTC)

2 3

Adding namespace alias_for causes index resync?
by Tom Sommer 12 Sep '18

12 Sep '18

I just added a new namespace-alias with alias_for. Apparently this causes all mailbox indexes to be resynced? Is this intentional and/or is there some way to avoid this? My NFS storage pretty much kills its elf when hundreds of thausands of users needs to resync indexes :) Thanks -- Tom

1 1

Re: LMTP tcp listener with auth?
by Andreas Thienemann 12 Sep '18

12 Sep '18

Hi Stephan, On Wed, 12 Sep 2018, Stephan Bosch wrote: > LMTP currently does not support AUTH. Bummer. Thought so. > What is your use case? Most people hide LMTP behind a firewall, or don't > expose it through TCP/IP in the first place. The port is currently only available to a few trusted machines, but having auth available would have been a nice benefit in case the firewall gets misconfigured. Cyrus for example will expose the LMTP port via TCP if configured, but expects valid user credentials. The larger use-case is a migration from cyrus to dovecot. As it's not just the MDA but also the MTA installation that is being migrated I need a way to deliver mail from the old MTA to the new MDA. LMTP comes in handy. https://github.com/ixs/lmtp_proxy/blob/master/README.md#minmal-downtime-mig… has a rough invocation of the steps needed for that. As I said, LMTP auth isn't critical for this, but would have been a nice addition. cheers, Andreas

1 0

Letsencrypt certificate for repo.dovecot.org expired May 14th..
by B. Reino 12 Sep '18

12 Sep '18

Dear all, Just in case you've missed it, the certificate for repo.dovecot.org just expired yesterday. This causes errors in e.g. apt-get update. Thanks in advance for fixing it, -- B. Reino

2 6

Re: make check (pigeonhole)
by Eric Broch 12 Sep '18

12 Sep '18

I attempted as non-root user and got the exact same error. On 9/10/2018 9:10 AM, Aki Tuomi wrote: > Have you attempted this as non-root user? > > > > --- > Aki Tuomi > Dovecot oy -- Eric Broch White Horse Technical Consulting (WHTC)

2 2

Log sync error
by Jakobus Schürz 11 Sep '18

11 Sep '18

Hi there! I get a lot of errormessages. My dovecot is: dovecot-core 2:2.3.2.1-1~stretch from Debian stable. I found this: https://www.dovecot.org/list/dovecot/2013-July/091648.html So the bug came back... The Log is attached Thanks Jakob

1 0

Re: make check (pigeonhole)
by Eric Broch 10 Sep '18

10 Sep '18

I did so as non-root user and got the same error. On 9/10/2018 9:10 AM, Aki Tuomi wrote: > Have you attempted this as non-root user? > > > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Eric Broch <ebroch(a)whitehorsetc.com> > Date: 10/09/2018 18:03 (GMT+02:00) > To: dovecot(a)dovecot.org > Subject: Re: make check (pigeonhole) > > Dovecot list, > > 1) I downloaded latest dovecot and pigeonhole tar balls and extracted on > latest updated CentOS 7 : dovecot-2.3.2.1.tar.gz and > dovecot-2.3-pigeonhole-0.5.2.tar.gz > > 2) I moved pigeonhole (dovecot-2.3-pigeonhole-0.5.2) directory into > dovecot (dovecot-2.3.2.1) directory > > 3) built dovecot with following config and paramerters: > > patch -p1 < ../../SOURCES/dovecot-2.0-defaultconfig.patch > patch -p1 < ../../SOURCES/dovecot-1.0.beta2-mkcert-permissions.patch > patch -p1 < ../../SOURCES/dovecot-2.2.27-mkcert-paths.patch > > sed -i '/DEFAULT_INCLUDES *=/s|$| '"$(pkg-config --cflags > libclucene-core)|" src/plugins/fts-lucene/Makefile.in > > #export CFLAGS="-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions > -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches > -fno-strict-aliasing" > #export LDFLAGS="-Wl,-z,now -Wl,-z,relro -Wl,-z,relro" > aclocal --install -I m4 > autoreconf -I . -fiv > > ./configure \ > INSTALL_DATA="install -c -p -m644" \ > --docdir=/usr/share/doc/dovecot-2.3.2.1 \ > --disable-static \ > --disable-rpath \ > --with-nss \ > --with-shadow \ > --with-pam \ > --with-gssapi=plugin \ > --with-ldap=plugin \ > --with-sql=plugin \ > --with-lua=plugin \ > --with-pgsql \ > --with-mysql \ > --with-sqlite \ > --with-vpopmail=/etc/libvpopmail \ > --with-zlib \ > --with-libcap \ > --with-libwrap \ > --with-lucene \ > --with-ssl=openssl \ > --with-ssldir=/etc/pki/dovecot \ > --with-solr \ > --with-systemdsystemunitdir=/usr/lib/systemd/system \ > --with-docs > > sed -i 's|/etc/ssl|/etc/pki/dovecot|' doc/mkcert.sh > doc/example-config/conf.d/10-ssl.conf > > make -j3 > > 4) built pigeon hole with the following paramters: > > # required for snapshot > [ -f configure ] || autoreconf -fiv > [ -f ChangeLog ] || echo "Pigeonhole ChangeLog is not available, yet" > >ChangeLog > > ./configure \ > INSTALL_DATA="install -c -p -m644" \ > --disable-static \ > --with-dovecot=../ \ > --with-ldap=plugin \ > --without-unfinished-features > > make -j3 > > 5) during 'make check' of pigeonhole got the following error: > > make[3]: Entering directory > `/root/rpmbuild/SRPMS/dovecot-2.3.2.1/dovecot-2.3-pigeonhole-0.5.2/src/lib-sieve/util' > for bin in test-edit-mail; do \ > if ! /bin/sh ../../../run-test.sh ../../.. ./$bin; then exit 1; fi; \ > done > test-edit-header(root): Error: Cannot lookup test user: Mail access for > users with UID 89 not permitted (see first_valid_uid in config file, uid > from mail_uid setting). > ../../../run-test.sh: line 27: 29930 Segmentation fault (core > dumped) valgrind -q --trace-children=yes --leak-check=full > --log-file=test.out.$$ $noundef $* > ==29930== Invalid read of size 8 > ==29930== at 0x404699: mail_raw_user_create (mail-raw.c:142) > ==29930== by 0x40325B: test_init (test-edit-mail.c:105) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== by 0x524E280: test_run (test-common.c:315) > ==29930== by 0x402FE5: main (test-edit-mail.c:765) > ==29930== Address 0xb8 is not stack'd, malloc'd or (recently) free'd > ==29930== > ==29930== > ==29930== Process terminating with default action of signal 11 (SIGSEGV) > ==29930== Access not within mapped region at address 0xB8 > ==29930== at 0x404699: mail_raw_user_create (mail-raw.c:142) > ==29930== by 0x40325B: test_init (test-edit-mail.c:105) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== by 0x524E280: test_run (test-common.c:315) > ==29930== by 0x402FE5: main (test-edit-mail.c:765) > ==29930== If you believe this happened as a result of a stack > ==29930== overflow in your program's main thread (unlikely but > ==29930== possible), you can try to increase the size of the > ==29930== main thread stack using the --main-stacksize= flag. > ==29930== The main thread stack size used in this run was 8388608. > ==29930== 64 bytes in 1 blocks are possibly lost in loss record 35 of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277AB5: pool_system_malloc (mempool-system.c:75) > ==29930== by 0x525D2FD: p_malloc (mempool.h:99) > ==29930== by 0x525D2FD: hash_table_create (hash.c:70) > ==29930== by 0x51F377C: settings_parser_init_list > (settings-parser.c:215) > ==29930== by 0x51ED102: master_service_settings_read > (master-service-settings.c:595) > ==29930== by 0x51EE3A9: master_service_settings_cache_read > (master-service-settings-cache.c:387) > ==29930== by 0x4E874BF: mail_storage_service_read_settings > (mail-storage-service.c:1085) > ==29930== by 0x4E87745: mail_storage_service_lookup_real > (mail-storage-service.c:1249) > ==29930== by 0x4E88795: mail_storage_service_lookup > (mail-storage-service.c:1441) > ==29930== by 0x403223: test_init_mail_user (test-edit-mail.c:71) > ==29930== by 0x403223: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== > ==29930== 64 bytes in 1 blocks are possibly lost in loss record 36 of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277AB5: pool_system_malloc (mempool-system.c:75) > ==29930== by 0x525D2FD: p_malloc (mempool.h:99) > ==29930== by 0x525D2FD: hash_table_create (hash.c:70) > ==29930== by 0x51F2EA3: settings_parser_dup (settings-parser.c:1957) > ==29930== by 0x51EE844: cache_add (master-service-settings-cache.c:291) > ==29930== by 0x51EE844: master_service_settings_cache_read > (master-service-settings-cache.c:409) > ==29930== by 0x4E874BF: mail_storage_service_read_settings > (mail-storage-service.c:1085) > ==29930== by 0x4E87745: mail_storage_service_lookup_real > (mail-storage-service.c:1249) > ==29930== by 0x4E88795: mail_storage_service_lookup > (mail-storage-service.c:1441) > ==29930== by 0x403223: test_init_mail_user (test-edit-mail.c:71) > ==29930== by 0x403223: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== by 0x524E280: test_run (test-common.c:315) > ==29930== > ==29930== 64 bytes in 1 blocks are possibly lost in loss record 37 of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277AB5: pool_system_malloc (mempool-system.c:75) > ==29930== by 0x525D2FD: p_malloc (mempool.h:99) > ==29930== by 0x525D2FD: hash_table_create (hash.c:70) > ==29930== by 0x51F2EA3: settings_parser_dup (settings-parser.c:1957) > ==29930== by 0x4E8792F: mail_storage_service_lookup_real > (mail-storage-service.c:1324) > ==29930== by 0x4E88795: mail_storage_service_lookup > (mail-storage-service.c:1441) > ==29930== by 0x403223: test_init_mail_user (test-edit-mail.c:71) > ==29930== by 0x403223: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== by 0x524E280: test_run (test-common.c:315) > ==29930== by 0x402FE5: main (test-edit-mail.c:765) > ==29930== > ==29930== 128 bytes in 1 blocks are possibly lost in loss record 48 of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277456: block_alloc.isra.1 (mempool-alloconly.c:254) > ==29930== by 0x527768C: pool_alloconly_create (mempool-alloconly.c:138) > ==29930== by 0x403159: test_init (test-edit-mail.c:101) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== by 0x524E280: test_run (test-common.c:315) > ==29930== by 0x402FE5: main (test-edit-mail.c:765) > ==29930== > ==29930== 256 bytes in 1 blocks are possibly lost in loss record 52 of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277456: block_alloc.isra.1 (mempool-alloconly.c:254) > ==29930== by 0x527751D: pool_alloconly_malloc (mempool-alloconly.c:283) > ==29930== by 0x528A74E: p_malloc (mempool.h:99) > ==29930== by 0x528A74E: p_strdup_vprintf (strfuncs.c:167) > ==29930== by 0x528A833: p_strdup_printf (strfuncs.c:111) > ==29930== by 0x40318E: test_init_mail_user (test-edit-mail.c:52) > ==29930== by 0x40318E: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== by 0x524E280: test_run (test-common.c:315) > ==29930== by 0x402FE5: main (test-edit-mail.c:765) > ==29930== > ==29930== 256 bytes in 1 blocks are possibly lost in loss record 53 of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277456: block_alloc.isra.1 (mempool-alloconly.c:254) > ==29930== by 0x527768C: pool_alloconly_create (mempool-alloconly.c:138) > ==29930== by 0x5272941: event_create (lib-event.c:54) > ==29930== by 0x4E8797C: mail_storage_service_lookup_real > (mail-storage-service.c:1334) > ==29930== by 0x4E88795: mail_storage_service_lookup > (mail-storage-service.c:1441) > ==29930== by 0x403223: test_init_mail_user (test-edit-mail.c:71) > ==29930== by 0x403223: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== by 0x524E280: test_run (test-common.c:315) > ==29930== by 0x402FE5: main (test-edit-mail.c:765) > ==29930== > ==29930== 512 bytes in 1 blocks are possibly lost in loss record 56 of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277456: block_alloc.isra.1 (mempool-alloconly.c:254) > ==29930== by 0x527751D: pool_alloconly_malloc (mempool-alloconly.c:283) > ==29930== by 0x5272952: p_malloc (mempool.h:99) > ==29930== by 0x5272952: event_create (lib-event.c:56) > ==29930== by 0x4E8797C: mail_storage_service_lookup_real > (mail-storage-service.c:1334) > ==29930== by 0x4E88795: mail_storage_service_lookup > (mail-storage-service.c:1441) > ==29930== by 0x403223: test_init_mail_user (test-edit-mail.c:71) > ==29930== by 0x403223: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== by 0x524E280: test_run (test-common.c:315) > ==29930== by 0x402FE5: main (test-edit-mail.c:765) > ==29930== > ==29930== 1,024 bytes in 1 blocks are possibly lost in loss record 59 > of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277456: block_alloc.isra.1 (mempool-alloconly.c:254) > ==29930== by 0x527768C: pool_alloconly_create (mempool-alloconly.c:138) > ==29930== by 0x51F3741: settings_parser_init_list > (settings-parser.c:204) > ==29930== by 0x51ED102: master_service_settings_read > (master-service-settings.c:595) > ==29930== by 0x51EE3A9: master_service_settings_cache_read > (master-service-settings-cache.c:387) > ==29930== by 0x4E874BF: mail_storage_service_read_settings > (mail-storage-service.c:1085) > ==29930== by 0x4E87745: mail_storage_service_lookup_real > (mail-storage-service.c:1249) > ==29930== by 0x4E88795: mail_storage_service_lookup > (mail-storage-service.c:1441) > ==29930== by 0x403223: test_init_mail_user (test-edit-mail.c:71) > ==29930== by 0x403223: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== > ==29930== 1,024 bytes in 1 blocks are possibly lost in loss record 60 > of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277456: block_alloc.isra.1 (mempool-alloconly.c:254) > ==29930== by 0x527768C: pool_alloconly_create (mempool-alloconly.c:138) > ==29930== by 0x51F2D14: settings_parser_dup (settings-parser.c:1924) > ==29930== by 0x51EE844: cache_add (master-service-settings-cache.c:291) > ==29930== by 0x51EE844: master_service_settings_cache_read > (master-service-settings-cache.c:409) > ==29930== by 0x4E874BF: mail_storage_service_read_settings > (mail-storage-service.c:1085) > ==29930== by 0x4E87745: mail_storage_service_lookup_real > (mail-storage-service.c:1249) > ==29930== by 0x4E88795: mail_storage_service_lookup > (mail-storage-service.c:1441) > ==29930== by 0x403223: test_init_mail_user (test-edit-mail.c:71) > ==29930== by 0x403223: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== by 0x524E280: test_run (test-common.c:315) > ==29930== > ==29930== 1,024 bytes in 1 blocks are possibly lost in loss record 61 > of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277456: block_alloc.isra.1 (mempool-alloconly.c:254) > ==29930== by 0x527768C: pool_alloconly_create (mempool-alloconly.c:138) > ==29930== by 0x51F2D14: settings_parser_dup (settings-parser.c:1924) > ==29930== by 0x4E8792F: mail_storage_service_lookup_real > (mail-storage-service.c:1324) > ==29930== by 0x4E88795: mail_storage_service_lookup > (mail-storage-service.c:1441) > ==29930== by 0x403223: test_init_mail_user (test-edit-mail.c:71) > ==29930== by 0x403223: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== by 0x524E280: test_run (test-common.c:315) > ==29930== by 0x402FE5: main (test-edit-mail.c:765) > ==29930== > ==29930== 1,024 bytes in 1 blocks are possibly lost in loss record 62 > of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277456: block_alloc.isra.1 (mempool-alloconly.c:254) > ==29930== by 0x527751D: pool_alloconly_malloc (mempool-alloconly.c:283) > ==29930== by 0x5250ED5: p_malloc (mempool.h:99) > ==29930== by 0x5250ED5: buffer_alloc (buffer.c:34) > ==29930== by 0x525110C: buffer_create_dynamic (buffer.c:143) > ==29930== by 0x5272805: array_create_i (array.h:129) > ==29930== by 0x5272805: event_get_field (lib-event.c:383) > ==29930== by 0x5273283: event_add_str (lib-event.c:400) > ==29930== by 0x5273437: event_add_fields (lib-event.c:438) > ==29930== by 0x4E879FD: mail_storage_service_lookup_real > (mail-storage-service.c:1335) > ==29930== by 0x4E88795: mail_storage_service_lookup > (mail-storage-service.c:1441) > ==29930== by 0x403223: test_init_mail_user (test-edit-mail.c:71) > ==29930== by 0x403223: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== > ==29930== 1,608 bytes in 1 blocks are possibly lost in loss record 67 > of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277AB5: pool_system_malloc (mempool-system.c:75) > ==29930== by 0x525D33D: p_malloc (mempool.h:99) > ==29930== by 0x525D33D: hash_table_create (hash.c:79) > ==29930== by 0x51F377C: settings_parser_init_list > (settings-parser.c:215) > ==29930== by 0x51ED102: master_service_settings_read > (master-service-settings.c:595) > ==29930== by 0x51EE3A9: master_service_settings_cache_read > (master-service-settings-cache.c:387) > ==29930== by 0x4E874BF: mail_storage_service_read_settings > (mail-storage-service.c:1085) > ==29930== by 0x4E87745: mail_storage_service_lookup_real > (mail-storage-service.c:1249) > ==29930== by 0x4E88795: mail_storage_service_lookup > (mail-storage-service.c:1441) > ==29930== by 0x403223: test_init_mail_user (test-edit-mail.c:71) > ==29930== by 0x403223: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== > ==29930== 1,608 bytes in 1 blocks are possibly lost in loss record 68 > of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277AB5: pool_system_malloc (mempool-system.c:75) > ==29930== by 0x525D33D: p_malloc (mempool.h:99) > ==29930== by 0x525D33D: hash_table_create (hash.c:79) > ==29930== by 0x51F2EA3: settings_parser_dup (settings-parser.c:1957) > ==29930== by 0x51EE844: cache_add (master-service-settings-cache.c:291) > ==29930== by 0x51EE844: master_service_settings_cache_read > (master-service-settings-cache.c:409) > ==29930== by 0x4E874BF: mail_storage_service_read_settings > (mail-storage-service.c:1085) > ==29930== by 0x4E87745: mail_storage_service_lookup_real > (mail-storage-service.c:1249) > ==29930== by 0x4E88795: mail_storage_service_lookup > (mail-storage-service.c:1441) > ==29930== by 0x403223: test_init_mail_user (test-edit-mail.c:71) > ==29930== by 0x403223: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== by 0x524E280: test_run (test-common.c:315) > ==29930== > ==29930== 1,608 bytes in 1 blocks are possibly lost in loss record 69 > of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277AB5: pool_system_malloc (mempool-system.c:75) > ==29930== by 0x525D33D: p_malloc (mempool.h:99) > ==29930== by 0x525D33D: hash_table_create (hash.c:79) > ==29930== by 0x51F2EA3: settings_parser_dup (settings-parser.c:1957) > ==29930== by 0x4E8792F: mail_storage_service_lookup_real > (mail-storage-service.c:1324) > ==29930== by 0x4E88795: mail_storage_service_lookup > (mail-storage-service.c:1441) > ==29930== by 0x403223: test_init_mail_user (test-edit-mail.c:71) > ==29930== by 0x403223: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== by 0x524E280: test_run (test-common.c:315) > ==29930== by 0x402FE5: main (test-edit-mail.c:765) > ==29930== > ==29930== 2,048 bytes in 1 blocks are possibly lost in loss record 70 > of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277456: block_alloc.isra.1 (mempool-alloconly.c:254) > ==29930== by 0x527768C: pool_alloconly_create (mempool-alloconly.c:138) > ==29930== by 0x4E8C454: mailbox_attributes_init > (mailbox-attribute.c:17) > ==29930== by 0x4E7F2F5: mail_storage_init (mail-storage.c:70) > ==29930== by 0x4E87139: mail_storage_service_init > (mail-storage-service.c:975) > ==29930== by 0x403205: test_init_mail_user (test-edit-mail.c:66) > ==29930== by 0x403205: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== by 0x524E280: test_run (test-common.c:315) > ==29930== by 0x402FE5: main (test-edit-mail.c:765) > ==29930== > ==29930== 2,048 bytes in 1 blocks are possibly lost in loss record 71 > of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277456: block_alloc.isra.1 (mempool-alloconly.c:254) > ==29930== by 0x527768C: pool_alloconly_create (mempool-alloconly.c:138) > ==29930== by 0x4E8714A: mail_storage_service_init > (mail-storage-service.c:977) > ==29930== by 0x403205: test_init_mail_user (test-edit-mail.c:66) > ==29930== by 0x403205: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== by 0x524E280: test_run (test-common.c:315) > ==29930== by 0x402FE5: main (test-edit-mail.c:765) > ==29930== > ==29930== 2,048 bytes in 1 blocks are possibly lost in loss record 72 > of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277456: block_alloc.isra.1 (mempool-alloconly.c:254) > ==29930== by 0x527751D: pool_alloconly_malloc (mempool-alloconly.c:283) > ==29930== by 0x528AA66: p_malloc (mempool.h:99) > ==29930== by 0x528AA66: p_strconcat (strfuncs.c:223) > ==29930== by 0x51F40ED: settings_parse_keyvalue (settings-parser.c:845) > ==29930== by 0x51F50E0: settings_parse_environ (settings-parser.c:1103) > ==29930== by 0x51ED247: master_service_settings_read > (master-service-settings.c:648) > ==29930== by 0x51EE3A9: master_service_settings_cache_read > (master-service-settings-cache.c:387) > ==29930== by 0x4E874BF: mail_storage_service_read_settings > (mail-storage-service.c:1085) > ==29930== by 0x4E87745: mail_storage_service_lookup_real > (mail-storage-service.c:1249) > ==29930== by 0x4E88795: mail_storage_service_lookup > (mail-storage-service.c:1441) > ==29930== by 0x403223: test_init_mail_user (test-edit-mail.c:71) > ==29930== by 0x403223: test_init (test-edit-mail.c:103) > ==29930== > ==29930== 6,144 bytes in 1 blocks are possibly lost in loss record 74 > of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277456: block_alloc.isra.1 (mempool-alloconly.c:254) > ==29930== by 0x527768C: pool_alloconly_create (mempool-alloconly.c:138) > ==29930== by 0x4E876FA: mail_storage_service_lookup_real > (mail-storage-service.c:1238) > ==29930== by 0x4E88795: mail_storage_service_lookup > (mail-storage-service.c:1441) > ==29930== by 0x403223: test_init_mail_user (test-edit-mail.c:71) > ==29930== by 0x403223: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== by 0x524E280: test_run (test-common.c:315) > ==29930== by 0x402FE5: main (test-edit-mail.c:765) > ==29930== > ==29930== 12,288 bytes in 1 blocks are possibly lost in loss record 75 > of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277456: block_alloc.isra.1 (mempool-alloconly.c:254) > ==29930== by 0x527768C: pool_alloconly_create (mempool-alloconly.c:138) > ==29930== by 0x51EDD31: master_service_settings_cache_init > (master-service-settings-cache.c:75) > ==29930== by 0x4E87541: mail_storage_service_read_settings > (mail-storage-service.c:1073) > ==29930== by 0x4E87745: mail_storage_service_lookup_real > (mail-storage-service.c:1249) > ==29930== by 0x4E88795: mail_storage_service_lookup > (mail-storage-service.c:1441) > ==29930== by 0x403223: test_init_mail_user (test-edit-mail.c:71) > ==29930== by 0x403223: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== by 0x524E280: test_run (test-common.c:315) > ==29930== by 0x402FE5: main (test-edit-mail.c:765) > ==29930== > ==29930== 16,384 bytes in 1 blocks are possibly lost in loss record 76 > of 77 > ==29930== at 0x4C2B9B5: calloc (vg_replace_malloc.c:711) > ==29930== by 0x5277456: block_alloc.isra.1 (mempool-alloconly.c:254) > ==29930== by 0x527768C: pool_alloconly_create (mempool-alloconly.c:138) > ==29930== by 0x51ED84C: master_service_settings_read > (master-service-settings.c:580) > ==29930== by 0x51EE3A9: master_service_settings_cache_read > (master-service-settings-cache.c:387) > ==29930== by 0x4E874BF: mail_storage_service_read_settings > (mail-storage-service.c:1085) > ==29930== by 0x4E87745: mail_storage_service_lookup_real > (mail-storage-service.c:1249) > ==29930== by 0x4E88795: mail_storage_service_lookup > (mail-storage-service.c:1441) > ==29930== by 0x403223: test_init_mail_user (test-edit-mail.c:71) > ==29930== by 0x403223: test_init (test-edit-mail.c:103) > ==29930== by 0x4036DA: test_edit_mail_concatenated > (test-edit-mail.c:187) > ==29930== by 0x524D8B1: test_run_funcs (test-common.c:244) > ==29930== by 0x524E280: test_run (test-common.c:315) > ==29930== > Failed to run: ./test-edit-mail > > *Note: Previous versions of pigeonhole did a 'make check' successfully > even the first version of 2.3 (CE). Pigeonhole v0.5.1 and v0.5.2 fail on > CentOS 7 > > Help would be appreciated. > > > On 9/9/2018 3:11 PM, Eric Broch wrote: > > Anyone? > > > > > > On 9/8/2018 7:36 PM, Eric Broch wrote: > >> Hello list, > >> > >> During the 'make check' (pigeonhole) portion of a building (rpmbuild) > >> a dovecot.spec file I'm getting the following error: > >> > >> testsuite(root): Fatal: Couldn't drop privileges: User is missing UID > >> (see mail_uid setting) > >> > >> I'm not sure how to resolve this, and any help would be appreciated > >> to help me finish the creating the rpm > >> > > > > -- > Eric Broch > White Horse Technical Consulting (WHTC) > -- Eric Broch White Horse Technical Consulting (WHTC)

1 0

make check (pigeonhole)
by Eric Broch 10 Sep '18

10 Sep '18

Hello list, During the 'make check' (pigeonhole) portion of a building (rpmbuild) a dovecot.spec file I'm getting the following error: testsuite(root): Fatal: Couldn't drop privileges: User is missing UID (see mail_uid setting) I'm not sure how to resolve this, and any help would be appreciated to help me finish the creating the rpm -- Eric Broch White Horse Technical Consulting (WHTC)

2 4

dsync mail from a remote server
by Kai Schaetzl 10 Sep '18

10 Sep '18

I would like to transfer mail for some users from an old dovecot (with no doveadm) to a modern dovecot (2.3.2). I've read up on https://wiki2.dovecot.org/Tools/Doveadm/Sync https://wiki2.dovecot.org/Migration/Dsync and I'm not sure if I can use doveadm for this purpose. I need doveadm to login to the remote server (source) with a username/password via IMAP, fetch all mail and deliver it to a local user (target), preferrably with the same folder structure that exists on the source account. Is this possible? I don't understand this page completely: https://wiki2.dovecot.org/Migration/Dsync For some testing (that's why I used pop3, to keep it simple) I put a file for pop3c in conf.d (mostly identical with the file shown on that page) and restarted dovecot. Then I tried a command line like this: doveadm -o pop3c_user=user -o pop3c_password=password backup -R -u user@domain pop3c: This creates an error: dsync(user@domain): Error: Mail locations must use the same virtual mailbox hierarchy separator (specify separator for the default namespace) I'm not sure what this exactly means. Does it refer to the account naming structure of user@domain? The source server does not have such usernames, only the target server I run the command on. Or does it refer to structure within the mailbox? (which can't really be the case as it doesn't login to the source and can't know the structure yet). So, if it indeed refers to the user naming structure, can I tell it to use the "simple" account names on the source machine? Am I correct in assuming that I can override any pop3c_ setting in the conf file with -o? For instance also using -o pop3c_host= and that if there is -o pop3c_user=user on the command line I don't need a pop3c_user in the conf file? (no master-user). Thanks for any help on this. (If it doesn't work I can use fetchmail, but that is much less preferrable as it "delivers" all mail, so it's all "new" and in the INBOX. Kai

1 0

Disconnects on Director
by Tom Sommer 10 Sep '18

10 Sep '18

Hi I am seeing a lot of clients time out on my Director. I'm wondering if this is "normal" or there is some opportunity to tweak something? Log line: imap-login: Info: proxy(user(a)example.com): disconnecting 1.2.3.4 (Disconnected by client: read(size=433) failed: Connection timed out(37s idle, in=939, out=3083)): user=<user(a)example.com>, method=CRAM-MD5, rip=1.2.3.4, lip=172.0.0.0, TLS: read(size=433) failed: Connection timed out, session=<P2kq7H91H4dZF/2O> Any hints? Nothing is logged by the kernel. 2.3.2.1 -- Tom

2 1

Dovecot - being dropped
by Maurizio Caloro 10 Sep '18

10 Sep '18

Hello Yesterday, I could not receive an email anymore when I looked in the logs found the following errors: * Sep 7 06:04:44 mail dovecot: master: Warning: service(imap-login): process_limit (100) reached, client connections are being dropped * Sep 7 06:06:41 mail dovecot: master: Warning: service(imap-login): process_limit (100) reached, client connections are being dropped If show the config i dont see any process_limits Dovecot 2.2.13 root@mail:/var/log# dovecot -n # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.16.0-6-amd64 x86_64 Debian 8.11 auth_mechanisms = plain login auth_verbose = yes disable_plaintext_auth = no info_log_path = /var/log/mail.log log_timestamp = %b %d %H:%M:%S Dovecot/ mail_access_groups = vmail mail_location = maildir:~/Maildir 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 vironment 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 = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { sieve = ~/sieve/.dovecot.sieve sieve_dir = ~/sieve } postmaster_address = admin@ protocols = imap pop3 lmtp service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-client { mode = 0660 user = mail } } service lmtp { inet_listener lmtp { address = 127.0.0.1 port = 24 } } ssl_cert = </etc/dovecot/dovecot.pem ssl_key = </etc/dovecot/private/dovecot.pem userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lda { mail_plugins = " quota sieve" } protocol imap { mail_plugins = " quota imap_quota" } root@mail:/var/log#

3 3

Re: Dsync deleting mailboxes due to duplicate UIDs
by Andreas Thienemann 10 Sep '18

10 Sep '18

Hi Sami, On Sun, 9 Sep 2018, Sami Ketola wrote: > Is it possible to get imapc rawlogs to analyze? create a directory that is > writeable and add -o imapc_rawlog_dir=/path/to/directory to command line. Tried that. Thanks for the suggestion, that is actually really helpful. If anyone wants to play along at home, the files in that directory are created with the permissions of mail_uid/mail_gid. The dir should be world-writable to make it easy. > Also with recent dovecot release you can tell dsync which header fields to > hash when matching mails. Add dsync_hashed_headers=Message-ID to config and > dovecot will only mach mails using Message-ID header fileld. I had seen that parameter but thought it would be prudent to not _just_ rely on the Message-ID but instead keep the default "Date Message-ID". I _think_ I might have found an issue when looking at the log: 1536525811.026071 * 39 FETCH (UID 39 BODY[HEADER.FIELDS (Date Message-ID)] {159} 1536525811.026071 Message-ID: <Pine.LNX.4.30.0207091925420.433-100000(a)trinity.knopfdruck.org> 1536525811.026071 Date: Tue, 9 Jul 2002 19:26:04 +0200 (MEST) 1536525811.026071 Date: Tue, 9 Jul 2002 12:36:13 +0200 1536525811.026071 1536525811.026071 ) A duplicate Date header is certainly unexpected. Having a look at the original mail on disk on the Cyrus server shows the following Mail: >From [redacted] Tue Jul 9 19:26:04 2002 X-Sieve: cmu-sieve 1.3 Return-Path: [redacted] Received: from bender.bawue.de (localhost [127.0.0.1]) by bender.bawue.de (Postfix) with ESMTP id C79CE48CBC; Tue, 9 Jul 2002 19:29:08 +0200 (CEST) Delivered-To: [redacted] Received: from [redacted] by bender.bawue.de (Postfix) with ESMTP id CFA4848CAA for [redacted]; Tue, 9 Jul 2002 19:28:43 +0200 (CEST) From: [redacted] X-Sender: [redacted] To: [redacted] Message-ID: <Pine.LNX.4.30.0207091925420.433-100000(a)trinity.knopfdruck.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Subject: [redacted] Date: Tue, 9 Jul 2002 19:26:04 +0200 (MEST) Status: RO X-Status: X-Keywords: X-UID: 38 ---------- Forwarded message ---------- Date: Tue, 9 Jul 2002 12:36:13 +0200 Subject: Gewinn [redacted] So it looks like the Cyrus imapd is incorrectly parsing the mail and returning the body content as a header. Comparing the content of UID 39 on the remote server will then hash differently than the UID 39 on the local dovecot server, which behaves better and only returns a single date header. Following the robustness principle it feels to me that it would make sense for dsync to disregard a duplicate header from a remote server and only use the first occurence. Would that be a good approach to the problem? Now that I understand the problem I am having, I can just workaround it but it seems to me that dsync should handle this case better. Anyway, thanks a lot for the imapc_rawlog_dir hint, that helped a lot. cheers, Andreas

1 0

Re: Auth process sometimes stop responding after upgrade
by Simone Lazzaris 08 Sep '18

08 Sep '18

In data venerdì 7 settembre 2018 09:39:23 CEST, Aki Tuomi ha scritto: > Do you see anything else in logs? > Just the usual proxy messages, like these: Sep 6 14:45:41 imap-front13 dovecot: imap-login: proxy(alessandro(a)soldinicarrelli.it): disconnecting 5.169.233.224 (Disconnected by server(0s idle, in=451, out=3556)): user=<alessandro(a)soldinicarrelli.it>, method=PLAIN, rip=5.169.233.224, lip=80.76.81.92, TLS, session=<uqVq2TJ1VbkFqeng> Sep 6 14:45:51 imap-front13 dovecot: pop3-login: proxy(prg(a)pedrini.it): started proxying to 192.168.1.144:110: user=<prg(a)pedrini.it>, method=DIGEST- MD5, rip=5.34.191.10, lip=80.76.81.92, TLS, session=<WqhRRDN1qw0FIr8K> The only suspect thing is this: Sep 6 14:45:41 imap-front13 dovecot: director: doveadm: Host 192.168.1.142 vhost count changed from 100 to 0 Sep 6 14:45:41 imap-front13 dovecot: director: doveadm: Host 192.168.1.143 vhost count changed from 100 to 0 Sep 6 14:45:41 imap-front13 dovecot: director: doveadm: Host 192.168.1.219 vhost count changed from 100 to 0 Nothing on the other system logs (e.g. kernel, daemon, syslog, messages ....). -- *Simone Lazzaris* *Qcom S.p.A.*

5 11

Sievescript in database
by Harald Leithner 07 Sep '18

07 Sep '18

Hi, is it possible to save sieve scripts to a mysql database? I know its possible to read them with the dict sql plugin but iirc it wasn't possible to save it with sievemanaged. thx Harald -- Harald Leithner ITronic Wiedner Hauptstraße 120/5.1, 1050 Wien, Austria Tel: +43-1-545 0 604 Mobil: +43-699-123 78 4 78 Mail: leithner(a)itronic.at | itronic.at

1 0

Auth process sometimes stop responding after upgrade
by Simone Lazzaris 07 Sep '18

07 Sep '18

Hi all; I've upgraded a ring of dovecot directors from 2.2.15 to 2.2.36. After the upgrade I've got some instability: a few time per day per server, seemly at random, the auth process stop responding and the clients cannot authenticate any more: Sep 6 14:45:51 imap-front13 dovecot: pop3-login: Warning: Auth process not responding, delayed sending initial response (greeting): user=<>, rip=xx.xx.xx.xx, lip=xx.xx.xx.xx, TLS, session=<1HVqRTN10MNTie+S> I can't figure it out.... Any hints? This is my configuration: # 2.2.36 (1f10bfa63): /usr/local/etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-686-pae i686 Debian 7.11 # Hostname: imap-front13.mailfarm.interac.it auth_mechanisms = plain login digest-md5 cram-md5 apop scram-sha-1 auth_verbose = yes auth_verbose_passwords = plain auth_worker_max_count = 50 base_dir = /var/run/dovecot/ default_login_user = nobody director_doveadm_port = 9091 director_mail_servers = 192.168.1.142 192.168.1.143 192.168.1.144 192.168.1.145 192.168.1.216 192.168.1.217 192.168.1.218 192.168.1.219 director_servers = 212.183.164.157 212.183.164.158 212.183.164.159 212.183.164.160 listen = * passdb { args = /usr/local/etc/dovecot/sql.conf driver = sql } protocols = imap pop3 service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { port = 9090 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service imap-login { executable = imap-login director service_count = 0 vsz_limit = 128 M } service pop3-login { executable = pop3-login director service_count = 0 vsz_limit = 128 M } ssl_cert = </usr/local/etc/dovecot/qcom.wildcard.pem ssl_cipher_list = ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM- SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA- AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128- SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128- SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256- SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS- AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256- SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128- SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:! MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA ssl_dh_parameters_length = 2048 ssl_key = # hidden, use -P to show it ssl_parameters_regenerate = 1 weeks ssl_prefer_server_ciphers = yes ssl_protocols = !SSlv2 !SSLv3 syslog_facility = local5 userdb { driver = prefetch } -- *Simone Lazzaris* *Qcom S.p.A.*

2 1

Virtual Maildir as subfolder
by Duncan Bellamy 07 Sep '18

07 Sep '18

I have a setup where google fetches mail from dovecot with pop3s and deletes mail downloaded, so to do this I currently forward a copy of the email to user-fetch@localhost which is the google login and it downloads from that maildir. But it means creating extra folders and I was looking at better ways of doing it. So I have an entry in my user DB file which ends with userdb_mail=maildir:/var/mail/virtual/adomain.com/user/Maildir/.Gfetch, and if I do a "doveadm auth test user(a)adomain.xn--com-9o0a it shows the correct mail location of the .Gfetch folder. But even though it has 6 messages in the folder a doveadm search and google both see zero messages. I think this is because the index file is only in the root of the maildir, is there a way to have a ‘virtual root’ inside a maildir like this? Thanks, Duncan

1 0

Auth process sometimes stop responding after upgrade
by Simone Lazzaris 06 Sep '18

06 Sep '18

Hi all; I've upgraded a ring of dovecot directors from 2.2.15 to 2.2.36. After the upgrade I've got some instability: a few time per day per server, seemly at random, the auth process stop responding and the clients cannot authenticate any more: Sep 6 14:45:51 imap-front13 dovecot: pop3-login: Warning: Auth process not responding, delayed sending initial response (greeting): user=<>, rip=xx.xx.xx.xx, lip=xx.xx.xx.xx, TLS, session=<1HVqRTN10MNTie+S> I can't figure it out.... Any hints? This is my configuration: # 2.2.36 (1f10bfa63): /usr/local/etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-686-pae i686 Debian 7.11 # Hostname: imap-front13.mailfarm.interac.it auth_mechanisms = plain login digest-md5 cram-md5 apop scram-sha-1 auth_verbose = yes auth_verbose_passwords = plain auth_worker_max_count = 50 base_dir = /var/run/dovecot/ default_login_user = nobody director_doveadm_port = 9091 director_mail_servers = 192.168.1.142 192.168.1.143 192.168.1.144 192.168.1.145 192.168.1.216 192.168.1.217 192.168.1.218 192.168.1.219 director_servers = 212.183.164.157 212.183.164.158 212.183.164.159 212.183.164.160 listen = * passdb { args = /usr/local/etc/dovecot/sql.conf driver = sql } protocols = imap pop3 service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { port = 9090 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service imap-login { executable = imap-login director service_count = 0 vsz_limit = 128 M } service pop3-login { executable = pop3-login director service_count = 0 vsz_limit = 128 M } ssl_cert = </usr/local/etc/dovecot/qcom.wildcard.pem ssl_cipher_list = ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM- SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA- AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128- SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128- SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256- SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS- AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256- SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128- SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:! PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA ssl_dh_parameters_length = 2048 ssl_key = # hidden, use -P to show it ssl_parameters_regenerate = 1 weeks ssl_prefer_server_ciphers = yes ssl_protocols = !SSlv2 !SSLv3 syslog_facility = local5 userdb { driver = prefetch } *Simone Lazzaris* *Qcom S.p.A.* simone.lazzaris(a)qcom.it[1] | www.qcom.it[2] * LinkedIn[3]* | *Facebook[4]* [5] -------- [1] mailto:simone.lazzaris@qcom.it [2] https://www.qcom.it [3] https://www.linkedin.com/company/qcom-spa [4] http://www.facebook.com/qcomspa [5] https://www.qcom.it/includes/email-banner.gif

1 0

Global duplicate filtering via Sieve
by Hanno Stock 06 Sep '18

06 Sep '18

Hi everybody, I have the following problem: Our mail users are receiving mails from externally defined mail forwardings and lists which sometimes leads to duplicate messages. As far as I understand, a single user can use the Sieve duplicate extension for filtering out such duplicate messages. Would it be feasible to add a script with sieve_before that does this for all users? Do scripts that run from sieve_before store persistent data also on a per-user basis, i.e. in the user's home dir? Thanks for your help! Best regards Hanno

2 1

Specifying other mail_attachment_dir for namespace
by Pedro Ribeiro 04 Sep '18

04 Sep '18

Hello, I have a Dovecot setup where I need to allow users to access a snapshot of their messages (when they complain about missing messages/folders deleted by mistake). From time to time the system does a LVM snapshot of the volume holding the mailboxes and sis storage and that messages are available via a "special" namespace. The problem is the messages that references attachments in the single attachment storage cause the file in some cases (when all the references were delete), the attachment itself is missing from the current SIS. Is there any option to reference a specific SIS folder for the namespace like I do for the messages as below? > namespace arquivo { > type = private > separator = / > prefix = "@ARQUIVO/" > subscriptions = yes > list = yes > inbox = no > hidden = no > ignore_on_failure = yes > location = mdbox:/mail-snap/domains/%d/%-2.2n/%n > } TIA. -- Best regards, =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Pedro Ribeiro Politécnico de Lisboa, Serviços da Presidência Departamento de Sistemas de Informação e Comunicações Phone: +351 210 464 700 (general) / VoIP: 80100 Helpdesk: helpdesk(a)net.ipl.pt / https://www.net.ipl.pt =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

1 0

Re: online conversion using replication?
by Daniel Miller 04 Sep '18

04 Sep '18

That works for a one-time migration, or perhaps via a cron-job, but what I want is basically a constant one-way backup and it seems replication could do it more elegantly & efficiently. -- Daniel On 9/1/2018 11:14 PM, Aki Tuomi wrote: > You don't need to setup replication for that. See > https://wiki2.dovecot.org/Migration/MailFormat > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Daniel Miller <dmiller(a)amfes.com> > Date: 02/09/2018 04:14 (GMT+02:00) > To: Dovecot Mailing List <dovecot(a)dovecot.org> > Subject: online conversion using replication? > > With a single server - and no intent to have a second server online at > this time - is it possible to use the replication service to keep a > "live" backup? Or otherwise perform a storage format conversion? > > I'm presently using sdbox - and considering going back to mdbox though > without SIS. My intent now is ONLY a 1-way backup, to be kept current, > and no clients will utilize the converted storage (unless/until I change). > > I've successfully executed: > > doveadm backup -u <username> -n inbox > mdbox:/var/mail/<domain>/<user>/mdbox > > For a few users - but reading the docs leads me to believe I can > automate this. But there's no explicit example for this - so I'm not > sure what to set. > > Initially I'm thinking of: > > dsync_remote_cmd = doveadm backup -u %u -n inbox > mdbox:/var/mail/%d/%n/mdbox > > and if that's right - which other services/listeners do I need to setup? > > -- > Daniel >

5 5

Re: dying on osx
by Mike Makuch 04 Sep '18

04 Sep '18

I found and tried this work around on the man page: https://www.unix.com/man-page/all/5/ngroups_max/ but I still get the same "Too many extra groups" error even when I start dovecot with the above program to limit the # of groups. I suspect that dovecot is adding a number of groups when it starts up. I've hacked a work around to get it working for me on my laptop: diff --git a/src/lib/restrict-access.c b/src/lib/restrict-access.c @@ -224,7 +224,12 @@ static void fix_groups_list(const struct restrict_access_settings *set, - if (setgroups(gid_count, gid_list) < 0) { + if (setgroups(gid_count > NGROUPS_MAX ? 16 : gid_count, gid_list) < 0) { if (errno == EINVAL) { i_fatal("setgroups(%s) failed: Too many extra groups", set->extra_groups == NULL ? "" : and this works. I'm not sure what the right solution is for a PR. Any suggestions? Thanks Mike On 8/10/18 11:04, Aki Tuomi wrote: > Is the user member of mail group? > > > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Mike Makuch <1mikemakuch(a)gmail.com> > Date: 10/08/2018 19:02 (GMT+02:00) > To: Aki Tuomi <aki.tuomi(a)dovecot.fi> > Cc: dovecot(a)dovecot.org > Subject: Re: dying on osx > > Maybe an old problem that has resurfaced??? > > https://bugzilla.samba.org/show_bug.cgi?id=8773 > > Mike > > > > On 8/10/18 10:54, Aki Tuomi wrote: >> I have to see if this is reproducible outside mac. >> >> >> >> --- >> Aki Tuomi >> Dovecot oy >> >> -------- Original message -------- >> From: Mike Makuch <1mikemakuch(a)gmail.com> >> Date: 10/08/2018 18:46 (GMT+02:00) >> To: Aki Tuomi <aki.tuomi(a)dovecot.fi> >> Subject: Re: dying on osx >> >> I did find that page and tried a few things there. My config has all of >> the settings there except 3: >> >> mail_access_groups = mail >> mbox_read_locks = fcntl >> mbox_write_locks = fcntl >> >> I add them to my config, restart and get the same abort >> >> 20180810-103849 imap(mkm)<79213><MkA5ihZzmdh/AAAB>: Fatal: >> setgroups(mail,505) failed: Too many extra groups >> >> I've tried numerous other settings as well. >> >> Thanks for any further advice >> >> Mike >> >> >> On 8/10/18 08:45, Aki Tuomi wrote: >> > Can you try this config and report back? >> > >> > >> https://superuser.com/questions/957272/dotlock-permissions-problems-with-do… >> > >> > Aki >> > >> >> On 10 August 2018 at 16:39 Mike Makuch <1mikemakuch(a)gmail.com> wrote: >> >> >> >> >> >> OSX 10.13.6 High Sierra, dovecot 2.3.2.1 >> >> >> >> dovecot starts up and runs but dies as soon as my mail client makes a >> >> request with log and config below. >> >> >> >> And advice appreciated. >> >> >> >> Thanks >> >> >> >> Mike >> >> >> >> >> >> >> >> 20180810-083730 auth: Debug: auth client connected (pid=77432) >> >> >> >> 20180810-083730 auth: Debug: client in: AUTH 1 PLAIN >> >> service=imap secured session=xo1p2BRzZNd/AAAB lip=127.0.0.1 >> >> rip=127.0.0.1 lport=143 rport=55140 >> >> 20180810-083730 auth: Debug: client passdb out: CONT 1 >> >> 20180810-083730 auth: Debug: client in: CONT 1 AG1rbQBta20xMjM= >> >> (previous base64 data may contain sensitive data) >> >> 20180810-083730 auth: Debug: static(mkm,127.0.0.1,<xo1p2BRzZNd/AAAB>): >> >> lookup >> >> 20180810-083730 auth: Debug: client passdb out: OK 1 user=mkm >> >> host=localhost nopasswd=y >> >> 20180810-083730 auth: Debug: master in: REQUEST 4201906177 77432 >> >> 1 b8126b4b71be2959fc7716888eccc566 session_pid=77433 >> >> request_auth_token >> >> 20180810-083730 auth-worker(77426): Debug: >> >> passwd(mkm,127.0.0.1,<xo1p2BRzZNd/AAAB>): lookup >> >> 20180810-083730 auth: Debug: master userdb out: USER 4201906177 >> >> mkm system_groups_user=mkm uid=503 gid=20 home=/Users/mkm >> >> auth_token=4d2bb44168df3d63e4e1bb352e59de632bc7da49 >> >> 20180810-083730 imap-login: Info: Login: user=<mkm>, method=PLAIN, >> >> rip=127.0.0.1, lip=127.0.0.1, mpid=77433, secured, >> >> session=<xo1p2BRzZNd/AAAB> >> >> 20180810-083730 imap(mkm)<77433><xo1p2BRzZNd/AAAB>: Fatal: >> >> setgroups(505) failed: Too many extra groups >> >> >> >> # doveconf -n >> >> # 2.3.2.1 (0719df592): /usr/local/etc/dovecot/dovecot.conf >> >> # OS: Darwin 17.7.0 x86_64 >> >> # Hostname: pine >> >> auth_debug = yes >> >> auth_debug_passwords = yes >> >> default_internal_user = _dovecot >> >> default_login_user = _dovenull >> >> disable_plaintext_auth = no >> >> listen = 127.0.0.1 >> >> log_path = /var/log/dovecot >> >> log_timestamp = "%Y%m%d-%H%M%S " >> >> mail_debug = yes >> >> mail_gid = staff >> >> mail_location = mbox:~/Mail:INBOX=/var/mail/%u >> >> mail_privileged_group = mail >> >> mail_uid = _dovecot >> >> passdb { >> >> args = password=*** host=localhost nopasswd=y >> >> driver = static >> >> } >> >> passdb { >> >> args = login >> >> driver = pam >> >> } >> >> protocols = imap >> >> service auth { >> >> user = root >> >> } >> >> service imap-login { >> >> inet_listener imap { >> >> address = * >> >> port = 143 >> >> } >> >> } >> >> ssl = no >> >> userdb { >> >> driver = passwd >> >> } >> >> >> >> >> >

2 1

doveadm variables
by Daniel Miller 04 Sep '18

04 Sep '18

Are variables such as %d and %n available to doveadm when executed from the command line? Either when explicitly declaring the user via -u or when using all users with -A? -- Daniel

1 0

Failed to get attribute vendor/vendor.dovecot/pvt/server/sieve/default
by Bob Smith 03 Sep '18

03 Sep '18

Any ideas what this cryptic message means ? Despite what the message says, there is no "more information" to be found in the logs on either server ! mail.debug dovecot: dsync-server(<REMOVED>): Debug: sieve: file storage: Created storage directory /my/dir/structure/.dovecot.sieve/tmp mxd mail.debug dovecot: dsync-server(<REMOVED>): Debug: sieve: file storage: Relative path to sieve storage in active link: .dovecot.sieve/ mxd mail.debug dovecot: dsync-server(<REMOVED>): Debug: sieve: file storage: sync: Synchronization active Error: Mailbox INBOX: Failed to get attribute vendor/vendor.dovecot/pvt/server/sieve/default: Internal error occurred. Refer to server log for more information. [2018-09-03 09:52:46] mail.debug dovecot: dsync-server(<REMOVED>): Debug: brain S: Import INBOX: Import attribute vendor/vendor.dovecot/pvt/server/sieve/default: failed mail.debug dovecot: dsync-server(<REMOVED>): Debug: brain S: Import INBOX: Saved UIDs: No errors are reported by "doveadm -v backup my@user tcp:mydest:myport". doveadm-backup returns exit code 75, something which also appears to be documented nowhere !

2 1

Re: Dovecot User Listing Error - getpwent() failed: Invalid Argument
by Aki Tuomi 03 Sep '18

03 Sep '18

Reuben, could you try this: service auth-worker { executable = /usr/bin/strace -o /tmp/out /usr/libexec/dovecot/auth -w } and send the out file to me? I wasn't able to reproduce your problem with glibc-2.28. Aki On 31.08.2018 21:30, Aki Tuomi wrote: > Ah. Thanks for the pointer. > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Michael Marley <michael(a)michaelmarley.com> > Date: 31/08/2018 21:17 (GMT+02:00) > To: dovecot(a)dovecot.org > Subject: Re: Dovecot User Listing Error - getpwent() failed: Invalid > Argument > > I think this might be caused by glibc 2.28. I saw a similar error > with the "doveadm purge" command after upgrading my system to that > version. > > Michael Marley > > On 2018-08-31 13:10, Aki Tuomi wrote: > >> I'll see if this is reproducible >> >> >> >> --- >> Aki Tuomi >> Dovecot oy >> >> -------- Original message -------- >> From: Reuben Farrelly <reuben-dovecot(a)reub.net> >> Date: 31/08/2018 17:41 (GMT+02:00) >> To: Aki Tuomi <aki.tuomi(a)dovecot.fi>, Dovecot Mailing List >> <dovecot(a)dovecot.org> >> Subject: Re: Dovecot User Listing Error - getpwent() failed: Invalid >> Argument >> >> Sure: >> >> https://www.reub.net/files/dovecot/lightning-dovecot.conf >> https://www.reub.net/files/dovecot/thunderstorm-dovecot.conf >> >> Updated nightly. >> >> Reuben >> >> >> On 1/09/2018 12:26 am, Aki Tuomi wrote: >> > Can you provide doveconf -n? >> > >> > >> > >> > --- >> > Aki Tuomi >> > Dovecot oy >> > >> > -------- Original message -------- >> > From: Reuben Farrelly <reuben-dovecot(a)reub.net> >> > Date: 31/08/2018 17:12 (GMT+02:00) >> > To: Aki Tuomi <aki.tuomi(a)dovecot.fi>, Dovecot Mailing List >> > <dovecot(a)dovecot.org> >> > Subject: Re: Dovecot User Listing Error - getpwent() failed: Invalid >> > Argument >> > >> > No. Neither of those are installed on either system. >> > >> > Reuben >> > >> > On 1/09/2018 12:09 am, Aki Tuomi wrote: >> > > Could apparmor or selinux be causing this! >> > > >> > > >> > > >> > > --- >> > > Aki Tuomi >> > > Dovecot oy >> > > >> > > -------- Original message -------- >> > > From: Reuben Farrelly <reuben-dovecot(a)reub.net> >> > > Date: 31/08/2018 16:50 (GMT+02:00) >> > > To: Dovecot Mailing List <dovecot(a)dovecot.org> >> > > Subject: Dovecot User Listing Error - getpwent() failed: Invalid >> Argument >> > > >> > > Hi, >> > > >> > > I'm running dovecot-2.3 git and seeing on 2 of my Dovecot >> installations, >> > > the following message logged quite frequently: >> > > >> > > Aug 31 16:55:53 lightning.reub.net dovecot[7698]: auth-worker(7707): >> > > Error: getpwent() failed: Invalid argument >> > > Aug 31 16:55:53 lightning.reub.net dovecot[7698]: replicator: Error: >> > > User listing returned failure >> > > Aug 31 16:55:53 lightning.reub.net dovecot[7698]: replicator: Error: >> > > listing users failed, can't replicate existing data >> > > >> > > It appears that this could be having an effect on replication, >> but it's >> > > unclear because the secondary/replica doesn't see much traffic. >> > > >> > > Authentication is via PAM and the system is Gentoo Linux x86_64. >> passb >> > > driver = pam, userdb driver = static . >> > > >> > > doveadm user -u '*' shows the system users listed twice like >> this (is >> > > this a problem?) and then prints: >> > > >> > > ---- >> > > reuben >> > > liam >> > > reuben >> > > liam >> > > <some other users> >> > > Error: User listing returned failure >> > > Fatal: user listing failed >> > > ---- >> > > >> > > To me that doesn't look right. >> > > >> > > Can anyone suggest what could be causing this? I don't recall >> seeing >> > > this message some time ago so I suspect it's a recent change in >> either >> > > dovecot, or pam or glibc etc.. >> > > >> > > Thanks, >> > > Reuben > >

1 0

online conversion using replication?
by Daniel Miller 02 Sep '18

02 Sep '18

With a single server - and no intent to have a second server online at this time - is it possible to use the replication service to keep a "live" backup? Or otherwise perform a storage format conversion? I'm presently using sdbox - and considering going back to mdbox though without SIS. My intent now is ONLY a 1-way backup, to be kept current, and no clients will utilize the converted storage (unless/until I change). I've successfully executed: doveadm backup -u <username> -n inbox mdbox:/var/mail/<domain>/<user>/mdbox For a few users - but reading the docs leads me to believe I can automate this. But there's no explicit example for this - so I'm not sure what to set. Initially I'm thinking of: dsync_remote_cmd = doveadm backup -u %u -n inbox mdbox:/var/mail/%d/%n/mdbox and if that's right - which other services/listeners do I need to setup? -- Daniel

2 1

remove non-standard flags
by Daniel Miller 02 Sep '18

02 Sep '18

Having relocated my virtual folders to a new namespace - I'm having some subscription challenges. I'm able to reach them via telnet without issue - and some clients have better luck than others. Some folders have no problems at all - some seem different. In trying to identify what might be the issue - at the moment the only thing I'm seeing is the ones that are completely without issue don't have any "weird" flags. Example: an apparently "clean" virtual folder: . select virtual/Flagged * OK [CLOSED] Previous mailbox closed. * FLAGS (\Answered \Flagged \Deleted \Seen \Draft $Forwarded) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft $Forwarded \*)] Flags permitted. * 12 EXISTS * 0 RECENT * OK [UNSEEN 7] First unseen. * OK [UIDVALIDITY 1535841027] UIDs valid * OK [UIDNEXT 13] Predicted next UID * OK [HIGHESTMODSEQ 3] Highest . OK [READ-WRITE] Select completed (0.316 + 0.000 + 0.315 secs). This folder is recognized by all clients. But this one: . select virtual/INBOX * OK [CLOSED] Previous mailbox closed. * FLAGS (\Answered \Flagged \Deleted \Seen \Draft $Forwarded junk $MDNSent) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft $Forwarded junk $MDNSent \*)] Flags permitted. * 9540 EXISTS * 0 RECENT * OK [UNSEEN 85] First unseen. * OK [UIDVALIDITY 1535841672] UIDs valid * OK [UIDNEXT 9541] Predicted next UID . OK [READ-WRITE] Select completed (44.266 + 0.000 + 44.265 secs). Is a little more troublesome. And then... . select virtual/Archives * FLAGS (\Answered \Flagged \Deleted \Seen \Draft $MDNSent unknown-0 unknown-2 unknown-3 unknown-5 unknown-9 unknown-4 $Forwarded unknown-7 unknown-8 junk $NotJunk $label5) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft $MDNSent unknown-0 unknown-2 unknown-3 unknown-5 unknown-9 unknown-4 $Forwarded unknown-7 unknown-8 junk $NotJunk $label5 \*)] Flags permitted. * 142605 EXISTS * 0 RECENT * OK [UNSEEN 82998] First unseen. * OK [UIDVALIDITY 1535841824] UIDs valid * OK [UIDNEXT 142606] Predicted next UID . OK [READ-WRITE] Select completed (10.217 + 0.000 + 10.217 secs). I can't get Thunderbird to recognize it all (though RoundCube web client works). There very well may be something totally separate from the flags that's causing the problem, but, is there a way to strip the flags off? I tried: doveadm flags remove -u <username> '$MDNSent unknown-0 unknown-2 unknown-3 unknown-5 unknown-9 unknown-4 unknown-7 unknown-8 junk $NotJunk $label5' mailbox 'inbox/Archive/2004' since that's one of the source folders of the virtual folder - no error, but no apparent change. Same for operating on the virtual folder directly. -- Daniel

1 0

Does domain quota work and how?
by Kai Schaetzl 01 Sep '18

01 Sep '18

Hello, I'm in the process of moving users from an old dovecot setup with system users to a modern virtual user setup. I can't find good documentation on domain quota. It is mentioned in the docs as quota2 = dict:domain:%d:proxy::quota_domain but not much more. Searching the mailing list or Google doesn't reveal much more info. Searching the German mailing list at jpberlin finds mostly information where they say that it doesn't work. So, does it or does it not? And if it works, does it work like I'm used to? e.g. with system users and aquota the filesystem quota kicks in whenever either the user or the domain quota is reached. That makes sense. It prohibits that single users can "fill" the whole domain (group) quota. I found one particular example where they say the dict quota works different, e.g. it's an either/or. They give this example for the user_query (the relevant part): CONCAT('*:bytes=', \ IF(mailbox.quota = 0, domain.maxquota*1024000, mailbox.quota)) \ as quota_rule So, this works as a default domain quota that is overridden on a user by user basis. But this means that a user quota that is set cannot honor the domain quota. So, in theory all users together can reach a maximum quota that is way over the domain quota. Not desirable. Concluding from the example in 90-quota.conf I want to set up this user_query (relevant part): concat('*:bytes=', m.quota) AS quota_rule, concat('*:bytes=', (s.quota*1024*1024)) AS quota2_rule (with m and s being the two tables for user and domain quota and s holding the domain quota in MB) Does this work together with this quota plugin setup and would provide both a user and domain quota? quota = dict:user::proxy::quota quota2 = dict:domain:%d:proxy::quota_domain quota_rule = *:storage=100M # default quota2_rule = *:storage=1000M # default I would like to know if this is supposed to work (and how) before I start testing in vain. One thing that I can confirm from several statements on the mailing lists is that the recalc option of doveadm doesn't work correctly. A doveadm quota recalc -A sets the used domain quota to the user used quota that it handles last for the domain (and a recalc -u sets the whole domain used quota to the one of that user). Which sets the domain quota completely wrong. I tried iterating thru the various users but got the same result as with -A. So, this is clearly broken, at least from my point of view. I'm using dovecot 2.3 from this repo: deb https://repo.dovecot.org/ce-2.3-latest/ubuntu/xenial xenial main I installed it because of the native blowfish encryption support. So far, it seems to be running great. Except for this particular aspect. Thanks! Kai

2 5

Do encrypted user keys self generate?
by eaerhaerhaehae aehraerhaeha 01 Sep '18

01 Sep '18

2 1

Re: Dovecot User Listing Error - getpwent() failed: Invalid Argument
by Michael Marley 31 Aug '18

31 Aug '18

I think this might be caused by glibc 2.28. I saw a similar error with the "doveadm purge" command after upgrading my system to that version. Michael Marley On 2018-08-31 13:10, Aki Tuomi wrote: > I'll see if this is reproducible > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Reuben Farrelly <reuben-dovecot(a)reub.net> > Date: 31/08/2018 17:41 (GMT+02:00) > To: Aki Tuomi <aki.tuomi(a)dovecot.fi>, Dovecot Mailing List <dovecot(a)dovecot.org> > Subject: Re: Dovecot User Listing Error - getpwent() failed: Invalid Argument > Sure: > > https://www.reub.net/files/dovecot/lightning-dovecot.conf > https://www.reub.net/files/dovecot/thunderstorm-dovecot.conf > > Updated nightly. > > Reuben > > On 1/09/2018 12:26 am, Aki Tuomi wrote: >> Can you provide doveconf -n? >> >> >> >> --- >> Aki Tuomi >> Dovecot oy >> >> -------- Original message -------- >> From: Reuben Farrelly <reuben-dovecot(a)reub.net> >> Date: 31/08/2018 17:12 (GMT+02:00) >> To: Aki Tuomi <aki.tuomi(a)dovecot.fi>, Dovecot Mailing List >> <dovecot(a)dovecot.org> >> Subject: Re: Dovecot User Listing Error - getpwent() failed: Invalid >> Argument >> >> No. Neither of those are installed on either system. >> >> Reuben >> >> On 1/09/2018 12:09 am, Aki Tuomi wrote: >>> Could apparmor or selinux be causing this! >>> >>> >>> >>> --- >>> Aki Tuomi >>> Dovecot oy >>> >>> -------- Original message -------- >>> From: Reuben Farrelly <reuben-dovecot(a)reub.net> >>> Date: 31/08/2018 16:50 (GMT+02:00) >>> To: Dovecot Mailing List <dovecot(a)dovecot.org> >>> Subject: Dovecot User Listing Error - getpwent() failed: Invalid Argument >>> >>> Hi, >>> >>> I'm running dovecot-2.3 git and seeing on 2 of my Dovecot installations, >>> the following message logged quite frequently: >>> >>> Aug 31 16:55:53 lightning.reub.net dovecot[7698]: auth-worker(7707): >>> Error: getpwent() failed: Invalid argument >>> Aug 31 16:55:53 lightning.reub.net dovecot[7698]: replicator: Error: >>> User listing returned failure >>> Aug 31 16:55:53 lightning.reub.net dovecot[7698]: replicator: Error: >>> listing users failed, can't replicate existing data >>> >>> It appears that this could be having an effect on replication, but it's >>> unclear because the secondary/replica doesn't see much traffic. >>> >>> Authentication is via PAM and the system is Gentoo Linux x86_64. passb >>> driver = pam, userdb driver = static . >>> >>> doveadm user -u '*' shows the system users listed twice like this (is >>> this a problem?) and then prints: >>> >>> ---- >>> reuben >>> liam >>> reuben >>> liam >>> <some other users> >>> Error: User listing returned failure >>> Fatal: user listing failed >>> ---- >>> >>> To me that doesn't look right. >>> >>> Can anyone suggest what could be causing this? I don't recall seeing >>> this message some time ago so I suspect it's a recent change in either >>> dovecot, or pam or glibc etc.. >>> >>> Thanks, >>> Reuben

2 1

Re: Dovecot User Listing Error - getpwent() failed: Invalid Argument
by Reuben Farrelly 31 Aug '18

31 Aug '18

No. Neither of those are installed on either system. Reuben On 1/09/2018 12:09 am, Aki Tuomi wrote: > Could apparmor or selinux be causing this! > > > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Reuben Farrelly <reuben-dovecot(a)reub.net> > Date: 31/08/2018 16:50 (GMT+02:00) > To: Dovecot Mailing List <dovecot(a)dovecot.org> > Subject: Dovecot User Listing Error - getpwent() failed: Invalid Argument > > Hi, > > I'm running dovecot-2.3 git and seeing on 2 of my Dovecot installations, > the following message logged quite frequently: > > Aug 31 16:55:53 lightning.reub.net dovecot[7698]: auth-worker(7707): > Error: getpwent() failed: Invalid argument > Aug 31 16:55:53 lightning.reub.net dovecot[7698]: replicator: Error: > User listing returned failure > Aug 31 16:55:53 lightning.reub.net dovecot[7698]: replicator: Error: > listing users failed, can't replicate existing data > > It appears that this could be having an effect on replication, but it's > unclear because the secondary/replica doesn't see much traffic. > > Authentication is via PAM and the system is Gentoo Linux x86_64. passb > driver = pam, userdb driver = static . > > doveadm user -u '*' shows the system users listed twice like this (is > this a problem?) and then prints: > > ---- > reuben > liam > reuben > liam > <some other users> > Error: User listing returned failure > Fatal: user listing failed > ---- > > To me that doesn't look right. > > Can anyone suggest what could be causing this? I don't recall seeing > this message some time ago so I suspect it's a recent change in either > dovecot, or pam or glibc etc.. > > Thanks, > Reuben

2 1

Dovecot User Listing Error - getpwent() failed: Invalid Argument
by Reuben Farrelly 31 Aug '18

31 Aug '18

Hi, I'm running dovecot-2.3 git and seeing on 2 of my Dovecot installations, the following message logged quite frequently: Aug 31 16:55:53 lightning.reub.net dovecot[7698]: auth-worker(7707): Error: getpwent() failed: Invalid argument Aug 31 16:55:53 lightning.reub.net dovecot[7698]: replicator: Error: User listing returned failure Aug 31 16:55:53 lightning.reub.net dovecot[7698]: replicator: Error: listing users failed, can't replicate existing data It appears that this could be having an effect on replication, but it's unclear because the secondary/replica doesn't see much traffic. Authentication is via PAM and the system is Gentoo Linux x86_64. passb driver = pam, userdb driver = static . doveadm user -u '*' shows the system users listed twice like this (is this a problem?) and then prints: ---- reuben liam reuben liam <some other users> Error: User listing returned failure Fatal: user listing failed ---- To me that doesn't look right. Can anyone suggest what could be causing this? I don't recall seeing this message some time ago so I suspect it's a recent change in either dovecot, or pam or glibc etc.. Thanks, Reuben

2 1

Shared mailbox name
by Kacper 31 Aug '18

31 Aug '18

Hello, Is it possible to have a custom name on a shared inbox? Currently prefix = shared/%%u/ makes the shared inbox have the name of the user whos sharing the inbox. I would like to set a custom name on the shared inbox such as "My Recipes" (spaces included). Background: I've implemented shared inboxes by using groups in Active Directory. Each group is a user with a mailbox and has it's mailbox shared using a namespace. A post login script fetches all groups a user is member of and includes them into the ACL_GROUPS environment variable. namespace { type = shared separator = / prefix = Shared/%%u/ location = maildir:/var/mail/maildir/%%u:INDEXPVT=/var/mail/maildir/shared/%u/%%u subscriptions = no list = children } I've tried using groups which contain spaces and mixing lower/upper case letters. "doveadm acl set -u "My Recipes" inbox group="My Recipes" create expunge insert lookup read write write-deleted write-seen" works and creates "/var/mail/maildir/My Recepies", but for some reason when refreshing the imap subscriptions in Thunderbird dovecot creates "/var/mail/maildir/my recepies" and "/var/mail/maildir/myrecepies". Thanks, Kacper

1 0

SNI Dovecot
by Nicolas 31 Aug '18

31 Aug '18

Hi all, I'm testing the SNI configuration from dovecot's wiki page, to have multiple domains. I'm using letsencrypt certificates. On the 10-ssl.conf, when I only use one domain, like this, it works : ssl_ca = </etc/letsencrypt/live/mail.mydomain.fr/chain.pem ssl_cert = </etc/letsencrypt/live/mail.mydomain.fr/cert.pem ssl_key = </etc/letsencrypt/live/mail.mydomain.fr/privkey.pem I got a warning of course when using my second domain, mydomain2.fr. If I do the config : local_name mail.mydomain.fr { ssl_ca = </etc/letsencrypt/live/mail.mydomain.fr/chain.pem ssl_cert = </etc/letsencrypt/live/mail.mydomain.fr/cert.pem ssl_key = </etc/letsencrypt/live/mail.mydomain.fr/privkey.pem } local_name mail.mydomain2.fr { ssl_ca = </etc/letsencrypt/live/mail.mydomain2.fr/chain.pem ssl_cert = </etc/letsencrypt/live/mail.mydomain2.fr/cert.pem ssl_key = </etc/letsencrypt/live/mail.mydomain2.fr/privkey.pem } I got this on dovecot's start : dovecot[930]: master: Error: service(imap-login): command startup failed, throttling for 8 secs dovecot[932]: imap-login: Fatal: Couldn't parse private ssl_key: error:0906D06C:PEM routines:PEM_read_bio:no start line: Expecting: ANY PRIVATE KEY It's working without local_name, so why it can be a certificate issue? Any idea? I'm using dovecot 2.2.27-3+deb9u2 from debian. Thanks, Nicolas

3 3

Userdb by directory lookup
by Miloslav Hůla 30 Aug '18

30 Aug '18

Hi, I have the Dovecot (2.2.27-3+deb9u2) with LMTP and Postfix. Static userdb: userdb { driver = static args = uid=vmail gid=vmail home=/data/vmail/user/%n allow_all_users=yes } and passdb by LDAP, only to verify IMAP user password by bind. Problem is, when someone sends email to non-existent(a)mydomain.tld, Dovecot automatically creates its home directory and Maildir. Is there any way how deliver only when /data/vmail/user/%n directory already exists, and reject otherwise? When I remove allow_all_users=yes, LMTP stops to deliver at all with 550 code. I probably understand why, but I cannot figure how to solve it. I cannot use LDAP to user lookup. Milo

2 3

Re: where are stored attachments
by Aki Tuomi 29 Aug '18

29 Aug '18

Based on this you are not using SIS, so I wonder if those are some old emails when you were using SIS? Can you provide an example corpus of such mail? You can use e.g. https://www.dovecot.org/tools/dbox-anonymize.pl https://www.dovecot.org/tools/maildir-obfuscate.pl https://www.dovecot.org/tools/mbox-anonymize.pl https://www.dovecot.org/tools/mdbox-obfuscate.pl to obfuscate the mail. Aki On 29.08.2018 08:39, Poliman - Serwis wrote: > Sure, here it is: > root@s1:~# doveconf -n > # 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf > # Pigeonhole version 0.4.13 (7b14904) > # OS: Linux 4.4.0-134-generic x86_64 Ubuntu 16.04.5 LTS > auth_mechanisms = plain login > disable_plaintext_auth = no > listen = *,[::] > log_timestamp = "%Y-%m-%d %H:%M:%S " > mail_max_userip_connections = 100 > mail_plugins = " quota" > mail_privileged_group = vmail > passdb { > args = /etc/dovecot/dovecot-sql.conf > driver = sql > } > plugin { > quota = dict:user::file:/var/vmail/%d/%n/.quotausage > sieve = /var/vmail/%d/%n/.sieve > sieve_max_redirects = 25 > } > postmaster_address = postmaster(a)s1.poliman.net > <mailto:postmaster@s1.poliman.net> > protocols = imap pop3 > service auth { > unix_listener /var/spool/postfix/private/auth { > group = postfix > mode = 0660 > user = postfix > } > unix_listener auth-userdb { > group = vmail > mode = 0600 > user = vmail > } > user = root > } > service imap-login { > client_limit = 1000 > process_limit = 512 > } > service lmtp { > unix_listener /var/spool/postfix/private/dovecot-lmtp { > group = postfix > mode = 0600 > user = postfix > } > } > ssl_cert = </etc/postfix/smtpd.cert > ssl_key = </etc/postfix/smtpd.key > ssl_protocols = !SSLv3 > userdb { > driver = prefetch > } > userdb { > args = /etc/dovecot/dovecot-sql.conf > driver = sql > } > protocol imap { > mail_plugins = quota imap_quota > } > protocol pop3 { > mail_plugins = quota > pop3_uidl_format = %08Xu%08Xv > } > protocol lda { > mail_plugins = sieve quota > postmaster_address = postmaster(a)s1.poliman.net > <mailto:postmaster@s1.poliman.net> > } > protocol lmtp { > mail_plugins = quota sieve > postmaster_address = postmaster(a)s1.poliman.net > <mailto:postmaster@s1.poliman.net> > } > > > 2018-08-29 7:37 GMT+02:00 Aki Tuomi <aki.tuomi(a)dovecot.fi > <mailto:aki.tuomi@dovecot.fi>>: > > Can you provide output of doveconf -n? > > > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Poliman - Serwis <serwis(a)poliman.pl <mailto:serwis@poliman.pl>> > Date: 29/08/2018 08:20 (GMT+02:00) > To: Aki Tuomi <aki.tuomi(a)dovecot.fi <mailto:aki.tuomi@dovecot.fi>> > Cc: dovecot <dovecot(a)dovecot.org <mailto:dovecot@dovecot.org>> > Subject: Re: where are stored attachments > > Sorry, I have checked before I wrote first post. Based on docs - > the path should be in /etc/dovecot/dovecot.conf or > /etc/dovecot/conf.d/10-mail.conf (I have Ubuntu 16.04 LTS). I have > some familiar lines in 10-mail.conf: > #mail_attachment_dir = > #mail_attachment_min_size = 128k > #mail_attachment_fs = sis posix > #mail_attachment_hash = %{sha1} > > but all these lines are commented out. So - in theory - dovecot > does not store attachments anywhere but when I log into i.e. > Roundcube, I have there mails with attachments. In Maildir/cur I > see formatted files related with specific emails. These with > attachments have specific hash at the bottom of content. As we > could suppose they are hashed by sha1. But still no idea where are > real files, which I can download after login to mailbox. > > > 2018-08-28 18:38 GMT+02:00 Aki Tuomi <aki.tuomi(a)dovecot.fi > <mailto:aki.tuomi@dovecot.fi>>: > > Check your configuration > > > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Poliman - Serwis <serwis(a)poliman.pl > <mailto:serwis@poliman.pl>> > Date: 28/08/2018 16:40 (GMT+02:00) > To: dovecot <dovecot(a)dovecot.org <mailto:dovecot@dovecot.org>> > Subject: where are stored attachments > > Hi! I would like to know where are stored attachments for > mails stored in /var/vmail/domain.com/user/Maildir > <http://domain.com/user/Maildir> ? Specific email has only > hash included at the bottom of message. > > -- > /Pozdrawiam / Best Regards > / > /Piotr Bracha/ > > > > > -- > /Pozdrawiam / Best Regards > / > /Piotr Bracha/ > > > > > -- > /Pozdrawiam / Best Regards > / > /Piotr Bracha/

2 2

Re: where are stored attachments
by Poliman - Serwis 29 Aug '18

29 Aug '18

Sorry, I have checked before I wrote first post. Based on docs - the path should be in /etc/dovecot/dovecot.conf or /etc/dovecot/conf.d/10-mail.conf (I have Ubuntu 16.04 LTS). I have some familiar lines in 10-mail.conf: #mail_attachment_dir = #mail_attachment_min_size = 128k #mail_attachment_fs = sis posix #mail_attachment_hash = %{sha1} but all these lines are commented out. So - in theory - dovecot does not store attachments anywhere but when I log into i.e. Roundcube, I have there mails with attachments. In Maildir/cur I see formatted files related with specific emails. These with attachments have specific hash at the bottom of content. As we could suppose they are hashed by sha1. But still no idea where are real files, which I can download after login to mailbox. 2018-08-28 18:38 GMT+02:00 Aki Tuomi <aki.tuomi(a)dovecot.fi>: > Check your configuration > > > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Poliman - Serwis <serwis(a)poliman.pl> > Date: 28/08/2018 16:40 (GMT+02:00) > To: dovecot <dovecot(a)dovecot.org> > Subject: where are stored attachments > > Hi! I would like to know where are stored attachments for mails stored in > /var/vmail/domain.com/user/Maildir ? Specific email has only hash > included at the bottom of message. > > -- > > *Pozdrawiam / Best Regards* > *Piotr Bracha* > -- *Pozdrawiam / Best Regards* *Piotr Bracha*

2 1

Perl Net::Doveadm
by Felipe Gasper 28 Aug '18

28 Aug '18

Hi all, In response to a discussion last week about API access--and notwithstanding Aki’s encouragement that integrators prefer the HTTP-based API--I’ve released a Perl module that facilitates access to Dovecot via the Doveadm protocol: https://metacpan.org/pod/Net::Doveadm I hope it’s useful. -Felipe Gasper Mississauga, ON

1 0

Update both virtual indexes & FTS indexes
by Daniel Miller 28 Aug '18

28 Aug '18

Will the following command: doveadm index -A '*' Ensure all Dovecot indexes are current (including virtual mailboxes) and also update FTS? Other than the time/resources needed to parse all users/mailboxes - is there a reason not to schedule this to run on a regular (hourly?) basis? My goal is to have my server constantly working...so my client isn't waiting for either virtual mailbox or Solr FTS updates. -- Daniel

2 1

where are stored attachments
by Poliman - Serwis 28 Aug '18

28 Aug '18

Hi! I would like to know where are stored attachments for mails stored in /var/vmail/domain.com/user/Maildir ? Specific email has only hash included at the bottom of message. -- *Pozdrawiam / Best Regards* *Piotr Bracha*

2 1

Re: Issue sharing folders with Thunderbird
by Jason Perry 28 Aug '18

28 Aug '18

Hi Aki, they are. > 3. The permissions for the file are: > root@dal-notify-01 Maildir]# ls -la /var/lib/dovecot/db/shared-mailboxes.db > -rw-rw-r--. 1 operations sharedusers 197 Aug 26 20:33 /var/lib/dovecot/db/shared-mailboxes.db > 4. Users I'm testing with are part of the sharedusers group in /etc/group The dir /var/lib/dovecot/db has this for permissions: drwsrwsrwx. 2 root sharedusers 33 Aug 27 21:12 db the user operations is a member of “sharedusers” in /etc/group. I even chmod’ed the permissions after to rw for global and I get the same error/result. The file does appear to get written to. For example, lets say user u2.name creates a folder called “starbucks” and uses the IMAP commands to share it out to user operations. It seems to write to the acl_shared_dict file in /var/lib/dovecot/db/shared-mailboxes.db with an entry like > shared/shared-boxes/user/u2.name/operations > 1 And it writes to the ~/Maildir/.starbucks/dovecot-acl file for u2.user with an entry like: user=operations lrw So it appears to be working. However, if I log into Thunderbird with the user operations account and go to subscribe, I do not see “starbucks” in the list of available folders. And I still get the nfs_flush_chown error. Is there anything else I can be doing with the file/dir permissions? Thanks. > On Aug 27, 2018, at 10:50 AM, Aki Tuomi <aki.tuomi(a)dovecot.fi> wrote: > > acl_shared_dict file & folder must be readwritable by user performing the sharing as stated in wiki. > > https://wiki.dovecot.org/SharedMailboxes/Shared > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Jason Perry <jason.perry(a)dtainc.us> > Date: 27/08/2018 17:01 (GMT+02:00) > To: dovecot(a)dovecot.org > Subject: Issue sharing folders with Thunderbird > > Trying to share folder "JasonAlerts" within mailbox operations to user u1.name > > Issues: > 1. Shared mailboxes do not appear under subscriptions in Thunderbird for another user > 2. When I try to set permissions via IMAP commands I get in /var/log/dovecot.log > Aug 26 20:33:24 imap(operations): Error: nfs_flush_chown_uid: chown(/var/lib/dovecot/db) failed: Permission denied > 3. The permissions for the file are: > root@dal-notify-01 Maildir]# ls -la /var/lib/dovecot/db/shared-mailboxes.db > -rw-rw-r--. 1 operations sharedusers 197 Aug 26 20:33 /var/lib/dovecot/db/shared-mailboxes.db > 4. Users I'm testing with are part of the sharedusers group in /etc/group > 5. IMAP commands DO write to the file: > [root@dal-notify-01 Maildir]# cat /var/lib/dovecot/db/shared-mailboxes.db > shared/shared-boxes/user/u1.name/u2.name > 1 > shared/shared-boxes/user/operations/u2.name > 1 > shared/shared-boxes/user/u1.name/operations > 1 > shared/shared-boxes/user/u1.name/operations > 1 > 6. It will also write to the user's /home/operations/Maildir/.JasonAlert/dovecot-acl file > user=u1.name ilrw > > However if I got into Thunderbird and try to subscribe, none of the shared folders are listed. Can anyone help?? Thanks!! > > Dovecot version = 2.2.10 > > dovecot -n > [root@server]# dovecot -n > # 2.2.10: /etc/dovecot/dovecot.conf > # OS: Linux 3.10.0-693.17.1.el7.x86_64 x86_64 CentOS Linux release 7.4.1708 (Core) > first_valid_uid = 100 > listen = * > log_path = /var/log/dovecot.log > mail_debug = yes > mail_location = maildir:~/Maildir > mail_plugins = acl > mail_privileged_group = mail > mbox_write_locks = fcntl > namespace Private { > hidden = no > inbox = no > list = no > location = > prefix = Private/ > separator = / > type = private > } > namespace Public { > hidden = no > inbox = no > list = no > location = maildir:/var/mail/public > prefix = Public/ > separator = / > subscriptions = yes > type = public > } > namespace Shared { > hidden = no > inbox = no > list = yes > location = maildir:/var/mail/%u:INDEXPVT=~/Maildir/%u > prefix = shared/%u/ > separator = / > subscriptions = yes > type = shared > } > 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 = > separator = / > } > passdb { > driver = pam > } > passdb { > driver = pam > } > plugin { > acl = vfile > acl_shared_dict = file:/var/lib/dovecot/db/shared-mailboxes.db <file:///var/lib/dovecot/db/shared-mailboxes.db> > } > protocols = imap > ssl_cert = </etc/pki/dovecot/certs/dovecot.pem > ssl_key = </etc/pki/dovecot/private/dovecot.pem > syslog_facility = local2 > userdb { > driver = passwd > } > userdb { > driver = passwd > } > protocol imap { > mail_plugins = acl imap_acl > }

2 1

mail-migration with dovadm sync/backup and mail_attachment_dir
by Ralf Becker 27 Aug '18

27 Aug '18

I need to run a mail-migration from a Dovecot with mail_attachment_dir / single instance storage enabled. As mailboxes and mail_attachment_dir are rsynced I would normally run a doveadm backup -u <user> -R -d dbox:<path to rsynced mailbox>/dbox How can I tell it the mail_attachment_dir the rsynced source / (reverse) destination uses? Or do I have to start a Dovecot process and use imapc for the migration? Ralf -- Ralf Becker EGroupware GmbH [www.egroupware.org] Handelsregister HRB Kaiserslautern 3587 Geschäftsführer Birgit und Ralf Becker Leibnizstr. 17, 67663 Kaiserslautern, Germany Telefon +49 631 31657-0

1 1

Issue sharing folders with Thunderbird
by Jason Perry 27 Aug '18

27 Aug '18

Trying to share folder "JasonAlerts" within mailbox operations to user u1.name Issues: 1. Shared mailboxes do not appear under subscriptions in Thunderbird for another user 2. When I try to set permissions via IMAP commands I get in /var/log/dovecot.log Aug 26 20:33:24 imap(operations): Error: nfs_flush_chown_uid: chown(/var/lib/dovecot/db) failed: Permission denied 3. The permissions for the file are: root@dal-notify-01 Maildir]# ls -la /var/lib/dovecot/db/shared-mailboxes.db -rw-rw-r--. 1 operations sharedusers 197 Aug 26 20:33 /var/lib/dovecot/db/shared-mailboxes.db 4. Users I'm testing with are part of the sharedusers group in /etc/group 5. IMAP commands DO write to the file: [root@dal-notify-01 Maildir]# cat /var/lib/dovecot/db/shared-mailboxes.db shared/shared-boxes/user/u1.name/u2.name 1 shared/shared-boxes/user/operations/u2.name 1 shared/shared-boxes/user/u1.name/operations 1 shared/shared-boxes/user/u1.name/operations 1 6. It will also write to the user's /home/operations/Maildir/.JasonAlert/dovecot-acl file user=u1.name ilrw However if I got into Thunderbird and try to subscribe, none of the shared folders are listed. Can anyone help?? Thanks!! Dovecot version = 2.2.10 dovecot -n [root@server]# dovecot -n # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-693.17.1.el7.x86_64 x86_64 CentOS Linux release 7.4.1708 (Core) first_valid_uid = 100 listen = * log_path = /var/log/dovecot.log mail_debug = yes mail_location = maildir:~/Maildir mail_plugins = acl mail_privileged_group = mail mbox_write_locks = fcntl namespace Private { hidden = no inbox = no list = no location = prefix = Private/ separator = / type = private } namespace Public { hidden = no inbox = no list = no location = maildir:/var/mail/public prefix = Public/ separator = / subscriptions = yes type = public } namespace Shared { hidden = no inbox = no list = yes location = maildir:/var/mail/%u:INDEXPVT=~/Maildir/%u prefix = shared/%u/ separator = / subscriptions = yes type = shared } 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 = separator = / } passdb { driver = pam } passdb { driver = pam } plugin { acl = vfile acl_shared_dict = file:/var/lib/dovecot/db/shared-mailboxes.db <file:///var/lib/dovecot/db/shared-mailboxes.db> } protocols = imap ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem syslog_facility = local2 userdb { driver = passwd } userdb { driver = passwd } protocol imap { mail_plugins = acl imap_acl }

2 1

Fatal: setgroups(6) failed: Too many extra groups when authenticating using mysql - macOS 10.13.6
by James Brown 27 Aug '18

27 Aug '18

Using mysql for authentication. Successful username & password gives: Aug 27 15:10:03 master: Info: Dovecot v2.3.2.1 (0719df592) starting up for imap, pop3 (core dumps disabled) Aug 27 15:10:50 imap-login: Info: Login: user=<jlbrown(a)bordo.com.au>, method=PLAIN, rip=::1, lip=::1, mpid=24924, secured, session=<E+DEvWN0xcoAAAAAAAAAAAAAAAAAAAAB> Aug 27 15:10:50 imap(jlbrown)<24924><E+DEvWN0xcoAAAAAAAAAAAAAAAAAAAAB>: Fatal: setgroups(6) failed: Too many extra groups Installed using Homebrew on a Mac running High Sierra. Any idea how to fix this? Thanks, James.

1 0

HTTP API vs. doveadm
by Felipe Gasper 24 Aug '18

24 Aug '18

To follow up on an earlier thread: is there any functional advantage of the new HTTP API over the doveadm API? How does the HTTP API deal with a query like “mailbox list”, which (as best I can tell) could return non-UTF8 text? -FG

2 1

Is the Doveadm HTTP API considered stable for production use?
by James Beck 23 Aug '18

23 Aug '18

Hi, I'm running 2.2.34 in production (installed from Debian stretch backports) and want to rework some scripts. Can the HTTP API be considered stable in 2.2.34 please? The wiki says it is "considered experimental in v2.2.22" so I thought I'd check before writing API calls rather than a wrapper around doveadm! -- James Beck Andrews & Arnold Ltd Tel: 03333 400999

5 8

allow_nets based on RBL
by Tom Sommer 23 Aug '18

23 Aug '18

This was brought up in 2014, and left without conclusion, so I thought it would be time to bump it :) I would love a way to do allow_nets based on an RBL check, could this be added to the feature-list? https://wiki2.dovecot.org/PasswordDatabase/ExtraFields/AllowNets Thanks -- Tom

2 1

lmtp Panic Buffer write out of range
by Gabriele Nencioni 23 Aug '18

23 Aug '18

Hi all, as described here: https://www.dovecot.org/pipermail/dovecot/2018-July/112173.html we are experiencing the same error on dovecot version 2.3.2.1 while it never occurs on an old version as 2.2.15 It followings the error logs: On an upgraded dovecot backend: Aug 21 12:03:51 backend20 dovecot: lmtp(test1(a)internalinboundcm.eu)<SONkAYfje1veGgAAu8+/vw>: Panic: Buffer write out of range (789 + 18446744073709551606) /var/log/dovecot_lmtp_20180821.12.log-Aug 21 12:03:51 monti-backend20 dovecot: lmtp(test1(a)internalinboundcm.eu)<SONkAYfje1veGgAAu8+/vw>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xcb851) [0x7f78e6f0a851] -> /usr/lib/dovecot/libdovecot.so.0(+0xcb8e9) [0x7f78e6f0a8e9] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f78e6e78851] -> /usr/lib/dovecot/libdovecot.so.0(buffer_write+0x131) [0x7f78e6f04871] -> /usr/lib/dovecot/libdovecot-sieve.so.0(rfc2822_header_append+0xcf) [0x7f78e531613f] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x7d35b) [0x7f78e531335b] -> /usr/lib/dovecot/libdovecot-sieve.so.0(edit_mail_header_add+0x1b) [0x7f78e531525b] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x73014) [0x7f78e5309014] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_interpreter_continue+0x81) [0x7f78e52d2a11] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_interpreter_run+0x2b) [0x7f78e52d2c7b] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x51000) [0x7f78e52e7000] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_multiscript_run+0x3a) [0x7f78e52e7eba] -> /usr/lib/dovecot/modules/lib90_sieve_plugin.so(+0x38f0) [0x7f78e554e8f0] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0xf0) [0x7f78e750da30] -> dovecot/lmtp [81.88.49.172 DATA](lmtp_local_data+0x4f1) [0x5582554451d1] -> dovecot/lmtp [81.88.49.172 DATA](cmd_data_continue+0x243) [0x558255443ee3] -> /usr/lib/dovecot/libdovecot.so.0(+0x4c402) [0x7f78e6e8b402] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7f78e6f228a9] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x109) [0x7f78e6f24199] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x52) [0x7f78e6f229b2] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f78e6f22bc8] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f78e6e9cff3] -> dovecot/lmtp [81.88.49.172 DATA](main+0x240) [0x558255442f70] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7f78e6ac02e1] -> dovecot/lmtp [81.88.49.172 DATA](_start+0x2a) [0x5582554430ba] while once the user test1(a)internalinboundcm.eu has been moved on an old dovecot backend, with the "doveadm director move" command the message has been properly delivered at next retry attempt: Aug 21 12:32:31 backend01 dovecot: lmtp(test1(a)internalinboundcm.eu)<Zv32Lzbqe1tSLQAAF5Yx/g>: copy from <lmtp DATA>: box=Spam, uid=1, msgid=<ceb54c05728586392119651424858d85(a)l2.losclientes3.com> Aug 21 12:32:31 backend01 dovecot: lmtp(test1(a)internalinboundcm.eu)<Zv32Lzbqe1tSLQAAF5Yx/g>: Zv32Lzbqe1tSLQAAF5Yx/g: sieve: msgid=<ceb54c05728586392119651424858d85(a)l2.losclientes3.com>: stored mail into mailbox 'Spam' As you can see the message was detected as spam Let me know if you need more info or details (such us the original message or the sieve filter that trigger the problem) Thanks in advance Regards -- Gabriele Nencioni System Administrator eml gabriele.nencioni(a)register.it

2 3

Re: Possible to set quota in size and number of messages
by J Doe 21 Aug '18

21 Aug '18

Hi Reio and list, It appears placing it at the end of the quota rules and then manually recalculating the quotas via doveadm has solved the problem! Configuration: plugin { quota = dict:User quota::file:%h/dovecot-quota quota_rule = *:storage=10G quota_rule1 = INBOX/Inbox:storage=+30M quota_rule2 = INBOX/Trash:storage=+30M quota_rule3 = INBOX/Deleted Messages:storage=+30M quota_rule4 = *:messages=100000 } Recalculate quotas: $ sudo doveadm quota recalc -u <account> Restart Dovecot and Apple Mail. Thanks, - J

1 0

Possible to set quota in size and number of messages
by J Doe 21 Aug '18

21 Aug '18

Hello, I am using Dovecot 2.2.33.2 and am attempting to set quotas on mailboxes. I currently have the following: plugin { quota = dict:User quota::file:%h/dovecot-quota quota_rule = *:storage=10G quota_rule1 = INBOX/Inbox:storage=+30M quota_rule2 = INBOX/Trash:storage=+30M quota_rule3 = INBOX/Deleted Messages:storage=+30M } If I check the quota via Apple Mail version 11.5 (3445.9.1) on Mac OS X 10.13.6 by selecting “Get Account Info” it displays the correct quota size in bytes but also states “0 messages” (in that it states I can store 0 messages). Is there a way to signify to an IMAP client that the quota should be _EITHER_ 10 GB or 100,000 messages, just so a user doesn’t see that they can store a total of 0 messages ? My initial thought was to alter the previous quota settings by adding: quota_rule4 = INBOX:messages=100000 … and restarting Dovecot and Apple Mail, but upon checking the quota’s on the user’s account, I still see that a user can store 10 GB or 0 messages. Thanks, - J

1 0

lazy expunge folder delete bug
by Jan-Pieter Cornet 21 Aug '18

21 Aug '18

There's a bug in "folder delete" for lazy expunge, type "1 namespace", as descibed on https://wiki2.dovecot.org/Plugins/Lazyexpunge When trying to delete a mailbox that still has messages in it, but that has no EXPUNGED/<name> counterpart, the process hangs after the imap "DELETE" command, and the following appears in the log file after a 60s timeout: Jun 22 15:48:15 userimap6 dovecot: imap(xtra30): Error: Couldn't create mailbox list lock /var/mail/.8d1/index/4/03/xtra30/index/mailboxes.lock: file_create_locked(/var/mail/.8d1/index/4/03/xtra30/index/mailboxes.lock) failed: flock(/var/mail/.8d1/index/4/03/xtra30/index/mailboxes.lock, write-lock) failed: Timed out after 60 seconds (BUG: lock is held by our own process) Jun 22 15:48:15 userimap6 dovecot: imap(xtra30): Error: lazy_expunge: Couldn't open expunge mailbox: Failed to create mailbox EXPUNGED/Test: Internal error occurred. Refer to server log for more information. [2018-06-22 15:47:15] Jun 22 15:48:15 userimap6 dovecot: imap(xtra30): Error: Lazy-expunge transaction failed: Internal error occurred. Refer to server log for more information. [2018-06-22 15:47:15] very quick summage of settings: ----8<----- mail_plugins = $mail_plugins lazy_expunge mail_location = mdbox:/var/mail/.8d1/mail/4/03/xtra30:INDEX=/var/mail/.8d1/index/4/03/xtra30/index ### from userdb namespace { inbox = yes list = yes prefix = separator = / } namespace expunged { hidden = yes inbox = no list = no prefix = EXPUNGED/ separator = / location = mdbox:/var/mail/.8d1/mail/4/03/xtra30:INDEX=/var/mail/.8d1/index/4/03/xtra30/index:MAILBOXDIR=expunged:LISTINDEX=expunged.list.index:SUBSCRIPTIONS=expunged.subscriptions ### also from userdb } plugin { lazy_expunge = EXPUNGED/ } ----8<----- (full doveconf available on request) State of the account before delete: mailbox "Test" exists, 20 messages in it: x LIST * * * LIST (\HasNoChildren \UnMarked \Trash) "/" Trash * LIST (\HasNoChildren \Marked) "/" Test * LIST (\HasNoChildren \UnMarked \Junk) "/" Spam * LIST (\HasNoChildren \UnMarked) "/" Sent * LIST (\HasNoChildren \UnMarked) "/" Drafts * LIST (\HasNoChildren) "/" INBOX x OK List completed (0.009 + 0.000 + 0.008 secs). x LIST EXPUNGED/* * x OK List completed (0.001 + 0.000 secs). x DELETE Test x NO [SERVERBUG] Internal error occurred. Refer to server log for more information. [2018-06-22 15:47:15] (60.064 + 0.000 + 60.063 secs). ... resulting in the above log lines. However, if you first delete one message (causing EXPUNGED/Test to be created), and then remove the folder, it works fine: x SELECT Test * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 20 EXISTS * 2 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1352910749] UIDs valid * OK [UIDNEXT 21] Predicted next UID * OK [HIGHESTMODSEQ 21] Highest x OK [READ-WRITE] Select completed (0.010 + 0.000 + 0.009 secs). x FETCH 1:* (FLAGS) * 1 FETCH (FLAGS ()) [...boring...] * 20 FETCH (FLAGS (\Recent)) x OK Fetch completed (0.002 + 0.000 + 0.001 secs). x STORE 1 +FLAGS (\Deleted) * 1 FETCH (FLAGS (\Deleted)) x OK Store completed (0.011 + 0.000 + 0.010 secs). x EXPUNGE * 1 EXPUNGE x OK Expunge completed (0.131 + 0.000 + 0.130 secs). X LIST * * * LIST (\HasNoChildren \UnMarked \Trash) "/" Trash * LIST (\HasNoChildren \UnMarked) "/" Test * LIST (\HasNoChildren \UnMarked \Junk) "/" Spam * LIST (\HasNoChildren \UnMarked) "/" Sent * LIST (\HasNoChildren \UnMarked) "/" Drafts * LIST (\HasNoChildren) "/" INBOX X OK List completed (0.005 + 0.000 + 0.004 secs). x LIST EXPUNGED/* * * LIST (\HasNoChildren \Marked) "/" EXPUNGED/Test x OK List completed (0.002 + 0.000 + 0.001 secs). x SELECT INBOX * OK [CLOSED] Previous mailbox closed. * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) [...INBOX opening msgs...] x OK [READ-WRITE] Select completed (0.005 + 0.000 + 0.004 secs). x DELETE Test x OK Delete completed (0.129 + 0.000 + 0.128 secs). x LIST * * * LIST (\HasNoChildren \UnMarked \Trash) "/" Trash * LIST (\HasNoChildren \UnMarked \Junk) "/" Spam * LIST (\HasNoChildren \UnMarked) "/" Sent * LIST (\HasNoChildren \UnMarked) "/" Drafts * LIST (\HasNoChildren) "/" INBOX x OK List completed (0.005 + 0.000 + 0.004 secs). x LIST EXPUNGED/* * * LIST (\HasNoChildren \Marked) "/" EXPUNGED/Test x OK List completed (0.003 + 0.000 + 0.002 secs). Seems the delete opeation locks the mailbox list, and then the expunge create hits the same lock. Is this something we can fix by changing settings? Eg use another location for the expunge lock? -- Jan-Pieter Cornet <johnpc(a)xs4all.net> Systeembeheer XS4ALL Internet bv www.xs4all.nl

1 1

iOS Mail Client Not Copying to Sent Folder
by Asai 21 Aug '18

21 Aug '18

Greetings, We have many iOS clients, and some report that they’re having problems with iOS mail copying messages to their Sent folder. This happens 2 - 3 times per day, and the phone just says Sending and the client never knows if it sends. Client says apparently email DOES go out, but there is no recording of it. This is usually on our LAN. We’re not sure if this is solved via Postfix or Dovecot, or maybe something else, so I’m posting this message on both forums as a start. Can anyone point us in the right direction here? Running Postfix 2.11.1 and Dovecot ee 2.2.18.2 see doveconf -n below: # 2.2.18.2 (866bffbafde7): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.8 (73d4f6cd676a) # OS: Linux 2.6.32-358.el6.x86_64 x86_64 CentOS release 6.4 (Final) ext4 auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = plain deliver_log_format = msgid=%m: from=%f: %$ lock_method = dotlock mail_home = /vmail/%d/%n/home mail_location = maildir:/vmail/%d/%n mail_plugins = " notify" managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate namespace { inbox = yes location = prefix = separator = / type = private } passdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } plugin { mail_log_events = delete expunge copy mailbox_delete flag_change append mailbox_rename mail_log_fields = box msgid from flags sieve = /vmail/%d/%n/home/.dovecot.sieve sieve_before = /etc/dovecot/sieve/junk-spam.sieve sieve_default = /etc/dovecot/sieve/junk-spam.sieve sieve_dir = /vmail/%d/%n/home/sieve } protocols = imap lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-master { group = vmail mode = 0660 user = vmail } unix_listener auth-userdb { mode = 0660 user = vmail } user = root } service imap-login { process_limit = 200 process_min_avail = 16 service_count = 0 vsz_limit = 0 } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 0 service_count = 1 vsz_limit = 64 M } ssl_cert = </etc/postfix/ssl/triata.pem ssl_key = </etc/postfix/ssl/triata.key userdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } protocol lda { hostname = domain.net mail_plugin_dir = /usr/lib64/dovecot/ mail_plugins = sieve postmaster_address = postmaster(a)domain.net } protocol imap { imap_idle_notify_interval = 24 mins mail_max_userip_connections = 60 } protocol sieve { mail_max_userip_connections = 10 managesieve_implementation_string = Dovecot Pigeonhole managesieve_logout_format = bytes=%i/%o managesieve_max_line_length = 65536 }

1 0

Strange problem on lmtp with dovecot 2.3.2.1
by davide marchi 20 Aug '18

20 Aug '18

Hi to all i have compiled and installed dovecot 2.3.2.1 on debian 6 with success but now i'm facing a strange problem on communication from postfix installed on server A with dovecot installed on server B (which version is 2.3.2.1). All incoming emails delivered from esternal from server A to server B with LMTP is rejected with this message error "smtpgw postfix/lmtp[1772]: 6194CA00B3: to=<xxxxxxxxxxxx(a)mail.cgilfe.it>, relay=192.168.10.50[192.168.10.50]:24, delay=0.02, delays=0/0.01/0.01/0, dsn=5.5.4, status=undeliverable (host 192.168.10.50[192.168.10.50] said: 501 5.5.4 Invalid FROM: Missing domain (in reply to MAIL FROM command))" I cant identify what is the problem , for now i have bypassed lmtp using smtp but my goal is returning to lmtp that i have used since old versions of dovecot.

2 1

systemd also listening on imaps port
by Kai Schaetzl 20 Aug '18

20 Aug '18

I noticed that most of the time with dovecot 2.3 I get this output, showing systemd listening on the port as well: lsof -i TCP:993 systemd 1 root 38u IPv4 3388360574 0t0 TCP *:imaps (LISTEN) systemd 1 root 41u IPv6 3388360575 0t0 TCP *:imaps (LISTEN) dovecot 11607 root 5u IPv4 3388360574 0t0 TCP *:imaps (LISTEN) dovecot 11607 root 6r IPv6 3388360575 0t0 TCP *:imaps (LISTEN) Sometimes I don't get the extra systemd lines, but I can't reproduce it now. It's only for port 143 and 993. Other ports show only two dovecot processes. Operation seems to be normal. Is this how it is supposed to be with dovecot 2.3? This is Ubuntu 16.04.

2 2

Re: creation of ssl-parameters fails
by Kai Schaetzl 20 Aug '18

20 Aug '18

Aki Tuomi wrote on Sun, 19 Aug 2018 18:21:31 +0300: > Just generate new parameters on some machine with good entropy source. So, if it fails to transform (although bigger) the machine hasn't enough entropy (because it's quite new?)? I'm generating now on the original machine from last year which is still going on while a second run on one of the machines where it failed to transform is already finished. So, that would indicate it has less entropy? Can I re-use the ssl-parameters.dat for several machines or should I create a new one for each? For the time being I just copied the dh.pem over, to get going, but I guess this should only be a temporary workaround? Thanks! Kai

3 6

imapsieve: Change message flags on COPY
by Leandro Lucarella 20 Aug '18

20 Aug '18

Hello, I'm trying to do a simple thing using imapsieve, I want messages to be marked as read when moved to certain folders (Trash, Archive, Spam). All the set up to run the imapsieve script works perfectly, but I'm having trouble to make changes effective. As the RFC says, IMAP messages are immutable, but it's not clear to me reading the specs if this applies to IMAP flags too, as one can really change flags in IMAP without having to create a new (modified) message, I guess this is an exception? 3.8. The "setflag", "deleteflag", and "removeflag" Actions Implementations of IMAP events in Sieve MUST also support the imap4flags extension [RFC5232], and the actions associated with it are all applicable to any case that falls under IMAP events in Sieve. It is worth noting also that the "hasflag" test that is defined in the imap4flags extension might be particularly useful in scripts triggered by flag changes ("hasflag" will see the new, changed flags). The flag changes behave as though a client had made the change. As explained above, in order to avoid script loops, flag changes that are made as a result of a script that was itself invoked because of flag changes SHOULD NOT result in another script invocation. In any case, implementations MUST take steps to avoid such loops. https://tools.ietf.org/html/rfc6785 Should changing flags just work for imapsieve? I even tried to use fileinto to explicitly save a new message (as far as I understand if I use fileinto the implicit keep should be cancelled, so the original message should be flagged as \Deleted (this is another hint that changing flags in immutable messages should be fine), and a new message should be created with the changed flags. But this is not happening, after moving the message I see unseen message still not flagged with \Seen. This is my imapsieve script: ---------------------------- require ["variables", "imap4flags", "fileinto", "vnd.dovecot.imapsieve", "vnd.dovecot.environment", "vnd.dovecot.execute", "vnd.dovecot.debug"]; if header :matches "Subject" "*" { set "subject" "${1}"; } if header :matches "From" "*" { set "from" "${1}"; } if environment :matches "imap.mailbox" "*" { set "dst" "${1}"; } debug_log "IMAPSIEVE TEST ---------------------"; debug_log "subject:${subject}"; debug_log "from:${from}"; debug_log "dst:${dst}"; debug_log "END IMAPSIEVE TEST -----------------"; if string :is "${dst}" ["Archive", "Trash", "Spam", "Sent"] { debug_log "Moved to ${dst}, marking as read: '${subject}' <${from>"; setflag "\\Seen"; fileinto "${dst}"; } ---------------------------- This is the log: Aug 16 10:31:51 alerce dovecot: imap(luca): Debug: Archive: Mailbox opened because: UID MOVE Aug 16 10:31:51 alerce dovecot: imap(luca): Debug: Mailbox INBOX: Opened mail UID=13304 because: copying Aug 16 10:31:51 alerce dovecot: imap(luca): Debug: imapsieve: mailbox Archive: MOVE event Aug 16 10:31:51 alerce dovecot: imap(luca): Debug: imapsieve: Matched static mailbox rule [1] Aug 16 10:31:51 alerce dovecot: imap(luca): Debug: sieve: file storage: Using Sieve script path: /home/luca/sieve/imapsieve.sieve Aug 16 10:31:51 alerce dovecot: imap(luca): Debug: sieve: file script: Opened script `imapsieve' from `/home/luca/sieve/imapsieve.sieve' Aug 16 10:31:51 alerce dovecot: imap(luca): Debug: sieve: Opening script 1 of 1 from `/home/luca/sieve/imapsieve.sieve' Aug 16 10:31:51 alerce dovecot: imap(luca): Debug: sieve: Loading script /home/luca/sieve/imapsieve.sieve Aug 16 10:31:51 alerce dovecot: imap(luca): Debug: sieve: Script binary /home/luca/sieve/imapsieve.svbin successfully loaded Aug 16 10:31:51 alerce dovecot: imap(luca): Debug: sieve: binary save: not saving binary /home/luca/sieve/imapsieve.svbin, because it is already stored Aug 16 10:31:51 alerce dovecot: imap(luca): Debug: sieve: Executing script from `/home/luca/sieve/imapsieve.svbin' Aug 16 10:31:51 alerce dovecot: imap(luca): sieve: imapsieve: line 11: DEBUG: IMAPSIEVE TEST --------------------- Aug 16 10:31:51 alerce dovecot: imap(luca): sieve: imapsieve: line 12: DEBUG: subject:Ihr DHL Paket wurde zugestellt. Aug 16 10:31:51 alerce dovecot: imap(luca): sieve: imapsieve: line 13: DEBUG: from:DHL Paket <noreply(a)dhl.de> Aug 16 10:31:51 alerce dovecot: imap(luca): sieve: imapsieve: line 16: DEBUG: dst:Archive Aug 16 10:31:51 alerce dovecot: imap(luca): sieve: imapsieve: line 17: DEBUG: END IMAPSIEVE TEST ----------------- Aug 16 10:31:51 alerce dovecot: imap(luca): sieve: imapsieve: line 23: DEBUG: Moved to Archive, marking as read: 'Ihr DHL Paket wurde zugestellt.' <DHL Paket <noreply(a)dhl.de>> Aug 16 10:31:51 alerce dovecot: imap(luca): Debug: Archive: Mailbox opened because: lib-lda delivery Aug 16 10:31:51 alerce dovecot: imap(luca): sieve: left message in mailbox 'Archive' The last line looks weird, it seems like the message is not being copied, right? I tried adding a stop; too, as suggested in this thread https://www.dovecot.org/list/dovecot/2017-April/107658.html, but the effect is the same, the message in Archive is still not flagged as \Seen. So the main question here is if changing IMAP flags in imapsieve scripts shouldn't just work, without even having to use fileinto, and if not, why isn't even using fileinto working? PS: Please Cc me, I'm not in the list. Thanks! -- Leandro Lucarella (Luca) https://llucax.com

2 4

creation of ssl-parameters fails
by Kai Schaetzl 19 Aug '18

19 Aug '18

I did that the last time one year ago, now on another machine with the same software (Ubuntu 16.04) it fails. openssl dhparam 4096 > /var/lib/dovecot/ssl-parameters.dat dd if=/var/lib/dovecot/ssl-parameters.dat bs=1 skip=88 | openssl dhparam -inform der > /etc/dovecot/dh.pem last command fails with 681+0 records in 681+0 records out 681 bytes copied, 0,00278343 s, 245 kB/s unable to load DH parameters 139858178938624:error:0D0680A8:asn1 encoding routines:asn1_check_tlen:wrong tag:../crypto/asn1/tasn_dec.c:1129: 139858178938624:error:0D07803A:asn1 encoding routines:asn1_item_embed_d2i:nested asn1 error:../crypto/asn1/tasn_dec.c:289:Type=DH ssl-parameters.dat is more than double the size as the one that worked. And that one I can still transform: 272+0 records in 272+0 records out 272 bytes copied, 0,00105017 s, 259 kB/s So, something with openssl dhparam 4096 > /var/lib/dovecot/ssl-parameters.dat must be wrong. But what? https://wiki.dovecot.org/SSL/DovecotConfiguration tells to use this command. Thanks! Kai

3 2

dovecot and postfix, help?
by Christy S 19 Aug '18

19 Aug '18

Hi all, First a disclaimer. I have played with linux off and on for years, but this is my first time trying to run a server completely on my own from start to finish, well it's on a vps, but still. I'm pretty techie, but a lot of this stuff is new to me, so I apologize for any *duh!* questions. That said, I've so far installed dovecot, postfix, wordpress, and related programs mostly successfully by following tutorials. I say mostly successfully, because I'm having a really hard time trying to get dovecot and postfix to behave together, and I'm about at the end of what I know how to find on google. If you're still with me and not groaning at yet another newbie asking wtf did I do wrong questions, thank you! My basic setup is running ubuntu 18 with up to date dovecot and postfix. Sasl is installed, and I'm using a custom domain with all records successfully pointing to the VPS. As I mentioned, I've been following tutorials. My goal is to have a mail server which can send and receive emails using this custom domain both from the shell and, much more often, from my primary computer using thunderbird. As there will likely only be two of us using this, I'm completely fine with the setup using mailboxes that actually have linux accounts. I'm also using maildir as the mailbox type. Furthermore, I want to make sure to use ssl on any mail connections.. Normal passwords but ssl being used. So, following one tutorial I set up postfix and dovecot, then went to test it. The result was that while on the shell, I could send email to my gmail account from the domain and receive it just fine. I could also send mail from my gmail account to the domain and receive it on the shel. I even managed to get imap to work, so I could receive domain emails in thunderbird, after playing around with tb's settings. However, if using tb I attempted to send an email using the custom domain, smtp failed to connect. I verified with my VPS provider that no, they do not block port 25, 465 or 587. I also verified that at&t, my home ISP, does not block outgoing smtp traffic, considering I am using google's for my gmail account. After hitting google again, I realized two things. One, for some reason port 25 never got opened on UFW, so I fixed that. Second, for some reason in all the stuff I did, postfix never got configured to use SSL. I found yet another tutorial, and ran through it to set up SSL with postfix. However, in doing this I had to change a path for sasl, only to find out later that doing that broke dovecot! Imap completely and utterly stopped behaving. Back to google again, and this time I found something a bit more up to date which explained how to interconnect postfix and dovecot. It goes through using mysql too, but I don't need that, so I skipped that part. Changed the sasl path back to what it should be, told dovecot and postfix to talk to each other and... Nope, still nothing. I saw a warning that I should not use different certificates for postfix and dovecot, so I told dovecot to look at the smtpd certificate that I made. Not sure if that's what's breaking this or something completely different, as I'm also brand new to the ssl certificate creation process. So, here's the current status of using thunderbird with my domain. mail sent from gmail to new domain, never comes back in thunderbird but doesn't bounce, either. Mail sent via thunderbird to gmail from domain, works, but shows up as from my gmail domain as well, which makes me think it's defaulting to the gmail account even though the domain's smtp info is set up. This could be because just before writing this message, I got the accept this certificate dialog over and over again for the domain and had to cancel out of it. One final point. I looked at /var/log/mail.log and, while at first I found an error in the path to one of the certificates, once I fixed that no error shows up. I restarted both postfix and dovecot, tried refreshing thunderbird and still no emails showed up. I see the connection in the log, but no errors. Anyone have ideas? Even maybe just point me in the right direction for what to check?

3 2

update to my first email
by Christy S 19 Aug '18

19 Aug '18

Alright so after checking logs, rebooting the vps because why not, and removing and re-adding the account in thunderbird... Now nothing is working other than sending mail from gmail to the domain. imap does not pick up the email and trying to send with the domain just plain fails, saying it can't connect to the server. Honestly, tempted to uninstall dovecot, sasl and postfix and start again, but I don't want to run into the same issues with conflicting tutorials. Does anyone know of a good source of how to do this that's fairly recent? I'll keep searching, but all of the outdated info is kind of frustrating. If anyone has replied to me I haven't gotten it yet, so I'm not ignoring anything you may have said. For now going to give this a break. I've been working on it literally all day! :) Christy

4 3

None
by Jarrad 18 Aug '18

18 Aug '18

1 0

Imap special-use with IOS 11
by Federico Bartolucci 17 Aug '18

17 Aug '18

Hello, has anyone experiened any issues with IMAP SPECIAL-USE extension with ios11? After the update to ios11 the Ios mail client seems to not recognize anymore the imap special-use, so that system folders (Sent, Trash etc..) are not authomatically recognized and set during the configuration. Regards Federico

2 1

"nologin" field set leads to internal failure
by postminion＠dicksinmyan.us 17 Aug '18

17 Aug '18

Hi, I've tried to use the "nologin" extra password-db field as specified here: https://wiki.dovecot.org/PasswordDatabase/ExtraFields/NoLogin Due to lack of exact documentation, I've tried to use `nologin`='y' for users that can't login, and setting `nologin`='n' for normal users. Apparently setting it to NULL for normal users would have been correct, as I've found out. Maybe write that on the above website. Anyway, login didn't work for a user with `nologin`='n' set. Trying to debug a normal user being unable to login, the log (mail.log) says: dovecot: imap-login: Disconnected (internal failure, 4 successful auths): user=<test(a)example.com>, method=PLAIN, rip=<ip6>, lip=<ip6>, TLS, session=<session> What I'm expecting it to say would be something like "user not allowed to login". I'm considering this a problem because of "Dovecot always logs a detailed error message if something goes wrong." as written here: https://wiki2.dovecot.org/Logging For the record, setting auth_debug=yes and mail_debug=yes gave the following line in the logs somewhere, from which I was able to figure out that NOLOGIN was the problem: dovecot: auth: Debug: client passdb out: OK#011<id>#011user=test(a)example.com#011nologin Thank you. dovecot -n output: --snip-- # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.9.0-7-amd64 x86_64 Debian 9.5 auth_default_realm = example.com base_dir = ... listen = *,[v6] login_greeting = ... mail_home = .../%d/%n/ mail_location = maildir:~/mail/:INDEX=MEMORY mail_plugins = trees mail_temp_dir = ... namespace inbox { inbox = yes location = prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocols = imap lmtp recipient_delimiter = -+ service auth { unix_listener ... { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 0 } service_count = 1 } service lmtp { unix_listener ... { group = postfix mode = 0600 user = postfix } user = vmail } ssl = required ssl_cert = <... ssl_cipher_list = ... ssl_dh_parameters_length = 4096 ssl_key = # hidden, use -P to show it userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } --snap--

1 0

imap-login: Error: BUG: Authentication server sent unknown id
by Tom Sommer 17 Aug '18

17 Aug '18

I randomly get these errors on my Director Aug 17 10:52:37 imap-login: Error: BUG: Authentication server sent unknown id 98448 Aug 17 10:52:37 imap-login: Warning: Auth connection closed with 2 pending requests (max 2 secs, pid=27036, Received broken input: FAIL 98448 user=user(a)example.com) Aug 17 10:52:37 auth: Warning: auth client 27036 disconnected with 1 pending requests: EOF 2.3.2.1 -- Tom

2 1

None
by Aki Tuomi 17 Aug '18

17 Aug '18

---Aki TuomiDovecot oy

1 0

sdbox filesystem backup potential excludes
by Daniel Miller 17 Aug '18

17 Aug '18

When doing a filesystem backup of an moderate sdbox mailstore (300GB) - are there any files that can be safely excluded from the backup? Like *.log or *.backup? Or are they all "vital" for recovery? I'm already excluding the sdbox/virtual folders as it looks like they get created and updated as needed. -- Daniel

2 4

imapsieve wrong matches on APPEND cause
by Alex Cherevko 17 Aug '18

17 Aug '18

Hello, I'm experiencing some strange problem with imapsieve mailbox rules matching. I have Ubuntu Server 18.04.1 LTS with Postfix 3.3.0, Dovecot 2.2.33.2 and Rspamd 1.7.9. The problem occurs with Microsoft Outlook 2016 mail client. When moving with Outlook, APPEND event is logged instead of MOVE. However, when moving with another client, MOVE event is logged. So without APPEND event in causes in plugin section of dovecot.conf no rule is matched at all. If I add APPEND event into causes in plugin section of dovecot.conf, then for some reason imapsieve matches both rules on move from Inbox to Spam and no rules on move from Spam to Inbox. Matching both rules attempts to run both learn_spam and learn_ham. First one works and second logs error (which is correct). On attempt to move message from Spam to Inbox imapsieve not matching any rule at all and thus learning is not working. Could you please let me know how to fix this? More details. Here is what I have in my plugin section of dovecot.conf: ---------------------------------------- %< ---------------------------------------- plugin { imapsieve_mailbox1_before = file:/var/vmail/sieve/global/learn-spam.sieve imapsieve_mailbox1_causes = COPY APPEND imapsieve_mailbox1_from = Inbox imapsieve_mailbox1_name = Spam imapsieve_mailbox2_before = file:/var/vmail/sieve/global/learn-ham.sieve imapsieve_mailbox2_causes = COPY APPEND imapsieve_mailbox2_from = Spam imapsieve_mailbox2_name = Inbox sieve = file:/var/vmail/sieve/%d/%n/scripts;active=/var/vmail/sieve/%d/%n/active-scr ipt.sieve sieve_before = /var/vmail/sieve/global/spam-global.sieve sieve_global_dir = /var/vmail/sieve/global/ sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.environment +vnd.dovecot.debug sieve_pipe_bin_dir = /usr/bin sieve_plugins = sieve_imapsieve sieve_extprograms } ---------------------------------------- %< ---------------------------------------- I also have Trash, Drafts, Sent and Spam mailboxes defined in dovecot.conf. So when I try to move actual spam message from Inbox to Spam folder, this is what I see in dovecot.log: ---------------------------------------- %< ---------------------------------------- Debug: imapsieve: mailbox Spam: APPEND event ---------------------------------------- %< ---------------------------------------- So before I added "APPEND" into above imapsieve_mailbox1_causes and imapsieve_mailbox2_causes imapsieve was not matching rules at all. But after I added APPEND, here is what happens. In case I move message from Inbox to Spam both rules are matched and dovecot attempts to run both rules: ---------------------------------------- %< ---------------------------------------- Debug: INBOX: Mailbox opened because: SELECT Debug: Spam: Mailbox opened because: SELECT Debug: imapsieve: mailbox Spam: APPEND event Debug: sieve: Pigeonhole version 0.4.21 (92477967) initializing Debug: sieve: Sieve imapsieve plugin for Pigeonhole version 0.4.21 (92477967) loaded Debug: sieve: Sieve Extprograms plugin for Pigeonhole version 0.4.21 (92477967) loaded Debug: imapsieve: Static mailbox rule [1]: mailbox=`Spam' from=`*' causes=(APPEND) => before=`file:/var/vmail/sieve/global/learn-spam.sieve' after=(none) Debug: imapsieve: Static mailbox rule [2]: mailbox=`*' from=`Spam' causes=(APPEND) => before=`file:/var/vmail/sieve/global/learn-ham.sieve' after=(none) Debug: imapsieve: Matched static mailbox rule [2] Debug: imapsieve: Matched static mailbox rule [1] Debug: sieve: file storage: Using Sieve script path: /var/vmail/sieve/global/learn-spam.sieve Debug: sieve: file script: Opened script `learn-spam' from `/var/vmail/sieve/global/learn-spam.sieve' Debug: sieve: file storage: Using Sieve script path: /var/vmail/sieve/global/learn-ham.sieve Debug: sieve: file script: Opened script `learn-ham' from `/var/vmail/sieve/global/learn-ham.sieve' Debug: sieve: Opening script 1 of 2 from `/var/vmail/sieve/global/learn-spam.sieve' Debug: sieve: Loading script /var/vmail/sieve/global/learn-spam.sieve Debug: sieve: Script binary /var/vmail/sieve/global/learn-spam.svbin successfully loaded Debug: sieve: binary save: not saving binary /var/vmail/sieve/global/learn-spam.svbin, because it is already stored Debug: sieve: Executing script from `/var/vmail/sieve/global/learn-spam.svbin' Debug: sieve: action pipe: running program: rspamc Debug: Mailbox Spam: Opened mail UID=12 because: mail stream Debug: waiting for program `/usr/bin/rspamc' to finish after 0 msecs Debug: sieve: Opening script 2 of 2 from `/var/vmail/sieve/global/learn-ham.sieve' Debug: sieve: Loading script /var/vmail/sieve/global/learn-ham.sieve Debug: sieve: Script binary /var/vmail/sieve/global/learn-ham.svbin successfully loaded Debug: sieve: binary save: not saving binary /var/vmail/sieve/global/learn-ham.svbin, because it is already stored Debug: sieve: Executing script from `/var/vmail/sieve/global/learn-ham.svbin' Debug: Spam: Mailbox opened because: lib-lda delivery Debug: Spam: Mailbox opened because: SELECT ---------------------------------------- %< ---------------------------------------- And of course I'm getting the following in the log file: ---------------------------------------- %< ---------------------------------------- Error: sieve: learn-ham: line 2: duplicate pipe "rspamc" action not allowed (previously triggered one was here: learn-spam: line 3) Error: sieve: Execution of script /var/vmail/sieve/global/learn-ham.sieve failed ---------------------------------------- %< ---------------------------------------- In case I move message from Spam to Inbox on rule is matched at all: ---------------------------------------- %< ---------------------------------------- Debug: INBOX: Mailbox opened because: SELECT Debug: imapsieve: mailbox INBOX: APPEND event Debug: sieve: Pigeonhole version 0.4.21 (92477967) initializing Debug: sieve: Sieve imapsieve plugin for Pigeonhole version 0.4.21 (92477967) loaded Debug: sieve: Sieve Extprograms plugin for Pigeonhole version 0.4.21 (92477967) loaded Debug: imapsieve: Static mailbox rule [1]: mailbox=`Spam' from=`*' causes=(APPEND) => before=`file:/var/vmail/sieve/global/learn-spam.sieve' after=(none) Debug: imapsieve: Static mailbox rule [2]: mailbox=`*' from=`Spam' causes=(APPEND) => before=`file:/var/vmail/sieve/global/learn-ham.sieve' after=(none) Debug: INBOX: Mailbox opened because: SELECT ---------------------------------------- %< ---------------------------------------- With best regards, Alex

3 5

Re: Does domain quota work and how?
by Aki Tuomi 16 Aug '18

16 Aug '18

> On 16 August 2018 at 17:47 Kai Schaetzl <maillists(a)conactive.com> wrote: > > > Dovecot-owner(a)dovecot.org wrote on Thu, 16 Aug 2018 17:14:00 +0300: > > > Message rejected by filter rule match > > Hello, > > why was this message rejected by a filter rule ? > (Posting first time to the list, yes, I subscribed.) > > Thanks, > > Kai > > Hi! I'm sorry you got bit by this, it's the spam filter. The way to get by the spam filter is to subscribe and wait about an hour for the subscription list to be updated, then you can post to the list, as we give a high negative score for anyone subscribed. Aki Tuomi ps. Here is the symbols your mail got, if it's any use to you. DMARC_NA(0)[conactive.com] SUBJECT_ENDS_QUESTION Subject ends with a question (1) REPLYTO_EQ_TO_ADDR(5) FROM_HAS_DN(0) IP_SCORE(-0.007259)[country: DE(-0.04)] MV_CASE(0.5) MIME_GOOD(-0.1)[text/plain] R_SPF_ALLOW(-0.2)[+a] R_DKIM_NA(0) GREYLIST(0)[pass,body] RCVD_TLS_LAST(0) ARC_NA(0) ASN(0)[asn:198710, ipnet:185.82.84.0/22, country:DE] PREVIOUSLY_DELIVERED(0)[dovecot(a)dovecot.org] FROM_EQ_ENVFROM(0) TO_DN_NONE(0) RCPT_COUNT_ONE(0)[1] BAYES_HAM(-0.000001)[14.49%] TO_MATCH_ENVRCPT_ALL(0) HAS_REPLYTO(0)[dovecot(a)dovecot.org] RCVD_COUNT_TWO(0)[2]

2 1

Re: [trees-plugin] - Dovecot index gets corrupted,^M when using maildir and recievend and accessing mail at the same time
by Joseph Tam 15 Aug '18

15 Aug '18

On Sat, 11 Aug 2018, Aki Tuomi wrote: > While this is true, it can be useful to encrypt messages in-rest at 3rd > party storage. Sure, in this case, mail operator != storage operator. It's not apparent those who clamour for it know the difference. > For end user, only PGP or similar provides sufficient security against admin. For content. Metadata can also reveal a lot. If the goal is to ensure privacy using a third-party storage provider (and assuming mail handlers are implictly trusted), it seems more productive to invest effort into block/FS level encryption that comprehensively protects all data. Joseph Tam <jtam.home(a)gmail.com>

1 0

doveadm mailbox delete not working
by Ralf Becker 15 Aug '18

15 Aug '18

I have a user who has several folders in his mailbox, which we can not delete, neither via IMAP nor via doveadm: root@ka-nfs-mail:~# doveadm mailbox list -u <username> | grep hbereiche | cat -v INBOX/[Fachbereiche ^M INBOX/Fachbereiche ^M INBOX/hbereiche^M INBOX/hbereiche/LAGen]^M INBOX/hbereiche/LAG^M INBOX/[Fachbereiche^M INBOX/[Fachbereiche/LAGen]^M INBOX/[Fachbereiche]^M INBOX/[Fachbereiche]/LAGen]^M INBOX/[Fachbereiche]/LAGe^M root@ka-nfs-mail:~# doveadm mailbox delete -u <username> 'INBOX/Fachbereiche ' doveadm(<username>): Info: Mailbox deleted: INBOX/Fachbereiche root@ka-nfs-mail:~# doveadm mailbox list -u <username>| grep hbereiche | cat -v INBOX/[Fachbereiche ^M INBOX/Fachbereiche ^M INBOX/hbereiche^M INBOX/hbereiche/LAGen]^M INBOX/hbereiche/LAG^M INBOX/[Fachbereiche^M INBOX/[Fachbereiche/LAGen]^M INBOX/[Fachbereiche]^M INBOX/[Fachbereiche]/LAGen]^M INBOX/[Fachbereiche]/LAGe^M As far as I tried none of these folders can be deleted (I added single quotes for trailing space and tried to delete subfolders first). Mailbox is in mdbox format on a replication pair under Dovecot 2.2.36 and I tried both nodes of the replication with same result. Any ideas? Ralf -- Ralf Becker EGroupware GmbH [www.egroupware.org] Handelsregister HRB Kaiserslautern 3587 Geschäftsführer Birgit und Ralf Becker Leibnizstr. 17, 67663 Kaiserslautern, Germany Telefon +49 631 31657-0

3 6

error while compiling dovecot
by Rajesh M 15 Aug '18

15 Aug '18

hello my server is centos 6 64 bit while installing dovecot i get this error Failed to run: ./test-compression what could be the reason. could someone guide me please Version dovecot-ce-2.3.0-1 0 / 7 tests failed ==21130== Conditional jump or move depends on uninitialised value(s) ==21130== at 0x349B00ACB2: ??? (in /usr/lib64/liblzma.so.0.0.0) ==21130== by 0x349B00AEA9: ??? (in /usr/lib64/liblzma.so.0.0.0) ==21130== by 0x349B003121: ??? (in /usr/lib64/liblzma.so.0.0.0) ==21130== by 0x349B0061A0: ??? (in /usr/lib64/liblzma.so.0.0.0) ==21130== by 0x349B005212: lzma_easy_encoder (in /usr/lib64/liblzma.so.0.0.0) ==21130== by 0x406ACF: o_stream_create_lzma (ostream-lzma.c:206) ==21130== by 0x403D89: test_compression_handler (test-compression.c:36) ==21130== by 0x4040BD: test_compression (test-compression.c:96) ==21130== by 0x408281: test_run_funcs (test-common.c:244) ==21130== by 0x4083E0: test_run (test-common.c:315) ==21130== by 0x40398B: main (test-compression.c:308) ==21130== Failed to run: ./test-compression make[3]: *** [check-local] Error 1 make[3]: Leaving directory `/root/rpmbuild/BUILD/dovecot-ce-2.3.0/src/lib-compression' make[2]: *** [check-am] Error 2 make[2]: Leaving directory `/root/rpmbuild/BUILD/dovecot-ce-2.3.0/src/lib-compression' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/root/rpmbuild/BUILD/dovecot-ce-2.3.0/src' make: *** [check-recursive] Error 1 error: Bad exit status from /var/tmp/rpm-tmp.LCwYD9 (%check) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.LCwYD9 (%check) thanks, rajesh

2 1

Confusing search / caps - non caps different results
by Götz Reinicke 15 Aug '18

15 Aug '18

Hi, I have some troubles with searching and could not find an answer yet. The search term is „istop“ in the subject. The client was SOGo. We run the recent dovecot, with solr backend and milder with zlib compression. Searching for all small letters „istop“ shows up no hit. Searching with a capital „S“ „iStop“ shows all messages back 10 years ago. Sprachig for „istopmotion“ all messages show up, wether the subject contains caps or non caps at all. I did a telnet to our dovecot and searched by hand for all three terms: 8 search Subject istop * SEARCH 8 OK Search completed (0.025 + 0.000 + 0.022 secs). 9 search subject iStop * SEARCH 544 604 654 662 910 1394 1471 1474 5493 9 OK Search completed (0.028 + 0.000 + 0.023 secs). 10 search subject istopmotion * SEARCH 544 604 654 662 910 1471 1472 1474 5493 10 OK Search completed (0.027 + 0.000 + 0.023 secs). Any hints or suggestion is welcome as I m very confused and lost. Thanks and regards . Götz

1 0

Re: doveadm mailbox delete not working
by Ralf Becker 15 Aug '18

15 Aug '18

Hi Aki, thanks for looking into this :) Am 14.08.18 um 15:15 schrieb Aki Tuomi: > can you turn on mail_debug=yes and run doveadm -Dv mailbox delete and > provide output and logs from both servers? root@ka-nfs-mail:~# doveadm -Dv mailbox delete -u h 'INBOX/Fachbereiche ' Debug: Loading modules from directory: /usr/lib/dovecot Debug: Module loaded: /usr/lib/dovecot/lib01_acl_plugin.so Debug: Module loaded: /usr/lib/dovecot/lib10_quota_plugin.so Debug: Module loaded: /usr/lib/dovecot/lib15_notify_plugin.so Debug: Module loaded: /usr/lib/dovecot/lib20_mail_log_plugin.so Debug: Module loaded: /usr/lib/dovecot/lib20_replication_plugin.so Debug: Loading modules from directory: /usr/lib/dovecot/doveadm Debug: Module loaded: /usr/lib/dovecot/doveadm/lib10_doveadm_acl_plugin.so Debug: Skipping module doveadm_expire_plugin, because dlopen() failed: Error relocating /usr/lib/dovecot/doveadm/lib10_doveadm_expire_plugin.so: expire_set_lookup: symbol not found (this is usually intentional, so just ignore this message) Debug: Module loaded: /usr/lib/dovecot/doveadm/lib10_doveadm_quota_plugin.so Debug: Module loaded: /usr/lib/dovecot/doveadm/lib10_doveadm_sieve_plugin.so Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: Error relocating /usr/lib/dovecot/doveadm/lib20_doveadm_fts_plugin.so: fts_backend_rescan: symbol not found (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_mail_crypt_plugin, because dlopen() failed: Error relocating /usr/lib/dovecot/doveadm/libdoveadm_mail_crypt_plugin.so: mail_crypt_box_get_public_key: symbol not found (this is usually intentional, so just ignore this message) doveadm(<username>): Debug: auth PASS input: doveadm(<username> 32679): Debug: auth USER input: <username> userdb_quota_rule=*:bytes=15728640000 master_user=<username> userdb_acl_groups=koakram@<domain>,wahlkampfnetzwerk@<domain>,wahlkalender 2017@<domain>,lgs@<domain> home=/var/dovecot/imap/<domain>/<user> doveadm(<username> 32679): Debug: Added userdb setting: plugin/master_user=<username> doveadm(<username> 32679): Debug: Added userdb setting: plugin/userdb_acl_groups=koakram@<domain>,wahlkampfnetzwerk@<domain>,wahlkalender 2017@<domain>,lgs@<domain> doveadm(<username> 32679): Debug: Added userdb setting: plugin/userdb_quota_rule=*:bytes=15728640000 doveadm(<username>): Debug: Effective uid=90, gid=101, home=/var/dovecot/imap/<domain>/<user> doveadm(<username>): Debug: Quota root: name=User quota backend=dict args=:ns=INBOX/:file:/var/dovecot/imap/<domain>/<user>/dovecot-quota doveadm(<username>): Debug: Quota rule: root=User quota mailbox=* bytes=107374182400 messages=0 doveadm(<username>): Debug: Quota grace: root=User quota bytes=10737418240 (10%) doveadm(<username>): Debug: dict quota: user=<username>, uri=file:/var/dovecot/imap/<domain>/<user>/dovecot-quota, noenforcing=0 doveadm(<username>): Debug: Namespace inboxes: type=private, prefix=INBOX/, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=no location=mdbox:~/mdbox doveadm(<username>): Debug: fs: root=/var/dovecot/imap/<domain>/<user>/mdbox, index=, indexpvt=, control=, inbox=, alt= doveadm(<username>): Debug: acl: initializing backend with data: vfile doveadm(<username>): Debug: acl: acl username = <username> doveadm(<username>): Debug: acl: owner = 1 doveadm(<username>): Debug: acl vfile: Global ACLs disabled doveadm(<username>): Debug: Namespace users: type=shared, prefix=user/%n/, sep=/, inbox=no, hidden=no, list=yes, subscriptions=no location=mdbox:%h/mdbox:INDEXPVT=~/shared/%u doveadm(<username>): Debug: shared: root=/run/dovecot, index=, indexpvt=, control=, inbox=, alt= doveadm(<username>): Debug: acl: initializing backend with data: vfile doveadm(<username>): Debug: acl: acl username = <username> doveadm(<username>): Debug: acl: owner = 0 doveadm(<username>): Debug: acl vfile: Global ACLs disabled doveadm(<username>): Debug: Namespace subs: type=private, prefix=, sep=/, inbox=no, hidden=yes, list=no, subscriptions=yes location=mdbox:~/mdbox doveadm(<username>): Debug: fs: root=/var/dovecot/imap/<domain>/<user>/mdbox, index=, indexpvt=, control=, inbox=, alt= doveadm(<username>): Debug: acl: initializing backend with data: vfile doveadm(<username>): Debug: acl: acl username = <username> doveadm(<username>): Debug: acl: owner = 1 doveadm(<username>): Debug: acl vfile: Global ACLs disabled doveadm(<username>): Debug: quota: quota_over_flag check: quota_over_script unset - skipping doveadm(<username>): Debug: INBOX/Fachbereiche : Mailbox opened because: mailbox delete doveadm(<username>): Debug: acl vfile: file /var/dovecot/imap/<domain>/<user>/mdbox/mailboxes/Fachbereiche /dbox-Mails/dovecot-acl not found doveadm(<username>): Debug: Namespace INBOX/: Using permissions from /var/dovecot/imap/<domain>/<user>/mdbox: mode=0700 gid=default doveadm(<username>): Debug: replication: Replication requested by 'mailbox delete', priority=1 doveadm(<username>): Info: Mailbox deleted: INBOX/Fachbereiche Output and logs are from the (less loaded) standby/backup node. I can get the logs from the active node tonight. I had to remove some folder-names for privacy reasons, but they all have the same output in the logs. Ralf > > > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Ralf Becker <rb(a)egroupware.org> > Date: 14/08/2018 16:13 (GMT+02:00) > To: dovecot(a)dovecot.org > Subject: doveadm mailbox delete not working > > I have a user who has several folders in his mailbox, which we can not > delete, neither via IMAP nor via doveadm: > > root@ka-nfs-mail:~# doveadm mailbox list -u <username> | grep hbereiche > | cat -v > INBOX/[Fachbereiche ^M > INBOX/Fachbereiche ^M > INBOX/hbereiche^M > INBOX/hbereiche/LAGen]^M > INBOX/hbereiche/LAG^M > INBOX/[Fachbereiche^M > INBOX/[Fachbereiche/LAGen]^M > INBOX/[Fachbereiche]^M > INBOX/[Fachbereiche]/LAGen]^M > INBOX/[Fachbereiche]/LAGe^M > root@ka-nfs-mail:~# doveadm mailbox delete -u <username> > 'INBOX/Fachbereiche ' > doveadm(<username>): Info: Mailbox deleted: INBOX/Fachbereiche > root@ka-nfs-mail:~# doveadm mailbox list -u <username>| grep hbereiche | > cat -v > INBOX/[Fachbereiche ^M > INBOX/Fachbereiche ^M > INBOX/hbereiche^M > INBOX/hbereiche/LAGen]^M > INBOX/hbereiche/LAG^M > INBOX/[Fachbereiche^M > INBOX/[Fachbereiche/LAGen]^M > INBOX/[Fachbereiche]^M > INBOX/[Fachbereiche]/LAGen]^M > INBOX/[Fachbereiche]/LAGe^M > > As far as I tried none of these folders can be deleted (I added single > quotes for trailing space and tried to delete subfolders first). > > Mailbox is in mdbox format on a replication pair under Dovecot 2.2.36 > and I tried both nodes of the replication with same result. > > Any ideas? > > Ralf > > -- > Ralf Becker > EGroupware GmbH [www.egroupware.org] > Handelsregister HRB Kaiserslautern 3587 > Geschäftsführer Birgit und Ralf Becker > Leibnizstr. 17, 67663 Kaiserslautern, Germany > Telefon +49 631 31657-0 > > -- Ralf Becker EGroupware GmbH [www.egroupware.org] Handelsregister HRB Kaiserslautern 3587 Geschäftsführer Birgit und Ralf Becker Leibnizstr. 17, 67663 Kaiserslautern, Germany Telefon +49 631 31657-0

3 7

Re: doveadm mailbox delete not working
by Ralf Becker 15 Aug '18

15 Aug '18

Hi Aki, Am 15.08.18 um 11:31 schrieb Aki Tuomi: > Such fun folders. Can you try doveadm -Dv mailbox delete -u username > folder and post it to the list? root@ka-nfs-mail:~# doveadm -Dv mailbox delete -u <username> 'INBOX/Fachbereiche ' Debug: Loading modules from directory: /usr/lib/dovecot Debug: Module loaded: /usr/lib/dovecot/lib01_acl_plugin.so Debug: Module loaded: /usr/lib/dovecot/lib10_quota_plugin.so Debug: Module loaded: /usr/lib/dovecot/lib15_notify_plugin.so Debug: Module loaded: /usr/lib/dovecot/lib20_mail_log_plugin.so Debug: Module loaded: /usr/lib/dovecot/lib20_replication_plugin.so Debug: Loading modules from directory: /usr/lib/dovecot/doveadm Debug: Module loaded: /usr/lib/dovecot/doveadm/lib10_doveadm_acl_plugin.so Debug: Skipping module doveadm_expire_plugin, because dlopen() failed: Error relocating /usr/lib/dovecot/doveadm/lib10_doveadm_expire_plugin.so: expire_set_lookup: symbol not found (this is usually intentional, so just ignore this message) Debug: Module loaded: /usr/lib/dovecot/doveadm/lib10_doveadm_quota_plugin.so Debug: Module loaded: /usr/lib/dovecot/doveadm/lib10_doveadm_sieve_plugin.so Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: Error relocating /usr/lib/dovecot/doveadm/lib20_doveadm_fts_plugin.so: fts_backend_rescan: symbol not found (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_mail_crypt_plugin, because dlopen() failed: Error relocating /usr/lib/dovecot/doveadm/libdoveadm_mail_crypt_plugin.so: mail_crypt_box_get_public_key: symbol not found (this is usually intentional, so just ignore this message) doveadm(<username> 46922): Debug: Added userdb setting: plugin/master_user=<username> doveadm(<username> 46922): Debug: Added userdb setting: plugin/userdb_acl_groups=koakram@<domain>,wahlkampfnetzwerk@<domain>,wahlkalender 2017@<domain>,lgs@<domain> doveadm(<username> 46922): Debug: Added userdb setting: plugin/userdb_quota_rule=*:bytes=15728640000 doveadm(<username>): Debug: Effective uid=90, gid=101, home=/var/dovecot/imap/<domain>/<user> doveadm(<username>): Debug: Quota root: name=User quota backend=dict args=:ns=INBOX/:file:/var/dovecot/imap/<domain>/<user>/dovecot-quota doveadm(<username>): Debug: Quota rule: root=User quota mailbox=* bytes=107374182400 messages=0 doveadm(<username>): Debug: Quota grace: root=User quota bytes=10737418240 (10%) doveadm(<username>): Debug: dict quota: user=<username>, uri=file:/var/dovecot/imap/<domain>/<user>/dovecot-quota, noenforcing=0 doveadm(<username>): Debug: Namespace inboxes: type=private, prefix=INBOX/, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=no location=mdbox:~/mdbox doveadm(<username>): Debug: fs: root=/var/dovecot/imap/<domain>/<user>/mdbox, index=, indexpvt=, control=, inbox=, alt= doveadm(<username>): Debug: acl: initializing backend with data: vfile doveadm(<username>): Debug: acl: acl username = <username> doveadm(<username>): Debug: acl: owner = 1 doveadm(<username>): Debug: acl vfile: Global ACLs disabled doveadm(<username>): Debug: Namespace users: type=shared, prefix=user/%n/, sep=/, inbox=no, hidden=no, list=yes, subscriptions=no location=mdbox:%h/mdbox:INDEXPVT=~/shared/%u doveadm(<username>): Debug: shared: root=/run/dovecot, index=, indexpvt=, control=, inbox=, alt= doveadm(<username>): Debug: acl: initializing backend with data: vfile doveadm(<username>): Debug: acl: acl username = <username> doveadm(<username>): Debug: acl: owner = 0 doveadm(<username>): Debug: acl vfile: Global ACLs disabled doveadm(<username>): Debug: Namespace subs: type=private, prefix=, sep=/, inbox=no, hidden=yes, list=no, subscriptions=yes location=mdbox:~/mdbox doveadm(<username>): Debug: fs: root=/var/dovecot/imap/<domain>/<user>/mdbox, index=, indexpvt=, control=, inbox=, alt= doveadm(<username>): Debug: acl: initializing backend with data: vfile doveadm(<username>): Debug: acl: acl username = <username> doveadm(<username>): Debug: acl: owner = 1 doveadm(<username>): Debug: acl vfile: Global ACLs disabled doveadm(<username>): Debug: quota: quota_over_flag check: quota_over_script unset - skipping doveadm(<username>): Debug: INBOX/Fachbereiche : Mailbox opened because: mailbox delete doveadm(<username>): Debug: acl vfile: file /var/dovecot/imap/<domain>/<user>/mdbox/mailboxes/Fachbereiche /dbox-Mails/dovecot-acl not found doveadm(<username>): Debug: Namespace INBOX/: Using permissions from /var/dovecot/imap/<domain>/<user>/mdbox: mode=0700 gid=default doveadm(<username>): Debug: replication: Replication requested by 'mailbox delete', priority=1 doveadm(<username>): Info: Mailbox deleted: INBOX/Fachbereiche Event doveadm reporting the folder is deleted, it is not: root@ka-nfs-mail:~# doveadm mailbox list -u <username> 'INBOX/Fachbereiche ' INBOX/Fachbereiche But it can not get a status of it: root@ka-nfs-mail:~# doveadm mailbox status -u <username> all 'INBOX/Fachbereiche ' doveadm(<username>): Error: Mailbox INBOX/Fachbereiche : Failed to lookup mailbox status: Mailbox doesn't exist: INBOX/Fachbereiche Really wired Ralf > Aki > > On 15.08.2018 11:03, Ralf Becker wrote: >> Hi Aki, >> >> I respond to you only on purpose, as the a dont want to show all folders >> public, please remove them when you reply to the list. >> >> This is the folder my previous examples where about: >> >> "mailbox": "INBOX/[Fachbereiche " <-- trailing space >> >> >> Am 15.08.18 um 08:33 schrieb Aki Tuomi: >>> Can you try >>> >>> doveadm -fjson mailbox list -u user INBOX/* -- Ralf Becker EGroupware GmbH [www.egroupware.org] Handelsregister HRB Kaiserslautern 3587 Geschäftsführer Birgit und Ralf Becker Leibnizstr. 17, 67663 Kaiserslautern, Germany Telefon +49 631 31657-0

1 0

Recommendations for backup methods
by Daniel Miller 14 Aug '18

14 Aug '18

I've been re-thinking my backup strategy - I wanted to see what input others have. At this time - I'm using sdbox as the primary storage format and running on a single server. Previously, all my backups were simple filesystem backups. Either inotify-based or cron-based. The whole mail folder structure would then be copied to a remote storage site. I've changed services - I now use OpenDrive for the remote storage and can access the remote drive as a mounted folder via WebDAV. I also now use a cron-based series of restic jobs for the backup processing. Because I have some large folders - both personal & business letters going back quite some time as well as mailing list archives - some mail folders can be quite sizable. Now I'm wondering, between sdbox's support for alternate locations and the ability to use different storage formats via namespaces - perhaps I should setup archive folders that are stored differently to improve backup performance. Maybe maildir or even mbox for the archive folders - I create one per year? Any comments? Experiences? -- Daniel

2 1

Move messages with doveadm recursively.
by Хлебалов Степан 14 Aug '18

14 Aug '18

Hello. I can move messages with doveadm like this: doveadm move -A Archive mailbox INBOX/* before 2018-02-01 but if inbox has a subfolders then subfolders structure does not move to Archive only messages. Is there a way to move messages to the same folder in new destination? Thanks.

2 1

"For end user, only PGP or similar provides sufficient security against admin." (was: [trees-plugin] - Dovecot index gets corrupted,^M when using maildir and recievend and accessing mail at the same time)
by Steffen Kaiser 13 Aug '18

13 Aug '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, 11 Aug 2018, Aki Tuomi wrote: > While this is true, it can be useful to encrypt messages in-rest at 3rd party storage. > For end user, only PGP or similar provides sufficient security against admin. Nice, short, pinpointed words I will file away for upcoming discussions. And I will file M's response, too, for the management. Thanks both of you. > -------- Original message --------From: "M. Balridge" <dovecot(a)r.paypc.com> Date: 11/08/2018 13:56 (GMT+02:00) To: Dovecot Mailing List <dovecot(a)dovecot.org> Subject: Re: [trees-plugin] - Dovecot index gets corrupted, > when using maildir and recievend and accessing mail at the same time > Quoting Joseph Tam <jtam.home(a)gmail.com>: > >> Another privacy plugin that assumes the server operator is unmotivated or >> respects your privacy anyways, and won't just skim your password right off >> the top to look at your mail. A vault with steel walls and a dirt floor. > > *SIGH* As usual, you're right on the money, Joseph. > > I used to let things like this "slide", but somewhat recently I've had some > clients badgering me to implement something like this. It takes longer than it > should to explain how pointless the exercise is. > > Given that: > > 1) Email transactions, from submission, to delivery, to final reception by a > MUA, are done with plaintext contents. Those who want security, will undergo > the additional steps and hassles with using PGP to encrypt the contents, > providing the only demonstrably secure (against "Evil SysAdmins") means of > cloaking your content. The submission, delivery, and final reception is still > performed as "plaintext", albeit with an attachment that is encrypted, a > process done (and undone) by the ultimate endpoint clients. > > 2) Even if the "Evil SysAdmin" doesn't scribble all of the users' passphrases > into a log, it's trivial for various tools, many of which were hastily cobbled > together during the fad of implementing Sarbanes-Oxley Act (SOX) compliance on > mail servers. Tools like "milter-bcc" and friends which automatically clone > all email submitted to or arriving through SMTP, etc. It doesn't matter if > your SMTP software implements 65,536 Jiggabyte Key Quantum-Computing-Resistant > crypto, when it has the decrypted contents in its spool. > > I imagine this is an exercise in buzzword collection, and to be seen to be > "doing something" to improve security and/or privacy. > > If privacy is desired, there are only end-to-end encryption/signature schemes > to ensure anything at all, and even there we're at the mercy of mathematical > gods greater than we. > > Looking to a "magical" oracle on your server to do it for you, whilst keeping > all of the leaky, plaintext, and promiscuous protocols (DSN, bounces, > intermediate MXer hosts that eruct contents to various envelope addresses, > etc) that will betray you behind your back without a moment's notice is a > Fool's Errand. > > Think it over. > > =M= > > - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBW3ErEMQnQQNheMxiAQJZ+Qf9ECwe0SZXwClaM+wHBVdsOPLPuL6rkSzV TAkPe7bV2jnqUL8J0I7F46MW4yV76ttbWMbZ3wP6Mom2roNOqGoQIxWsQLkgZvib Wdg29L0nsMkHY6A5zCRM/n4rvNi/xDHIUWIinZRUWvFr8J6WWkSaYneX2Xjvf6tF 24nj+tqcuYtFomsY802WySgovLZi5y0s8nSSkQ9nnPA44hpozfbQXXf/pO14D2BL vhsiqvLKnS/3wY83Y05RLCsojfQDG3Vbqgm6qV9qkpOtGN9sLV/ufXc8tui070UW FDmV5S/KnP8Z7ru9Hq83JEhxkaApPhcKqIQcpjUIeWyobIwvYr718A== =cbbG -----END PGP SIGNATURE-----

1 0

[trees-plugin] - Dovecot index gets corrupted, when using maildir and recievend and accessing mail at the same time
by neutron 11 Aug '18

11 Aug '18

Hello dovecot team, at first I want to thank you the awesome dovecot software. I'm currently researching and developing the trees plugin (https://0xacab.org/riseuplabs/trees) In the future I would love to package this software for debian. I run into a problem, which I can not fix by myself, that's why I'm reaching out to you. The plugin is producing a reproducible error, when using dovecots mailbox format maildir, and receiving and accessing mail at the same time. I'm searching for additional information to fix that. I know that it's may not the scope of the mailing list to support external plugins, but since you are the experts, I thought I should ask at least. Trees Plugin: =================== The plugin adds individually encrypted mail storage to the Dovecot IMAP server. It encrypts all (incoming and outgoing) mail on the mail server with a key, which can only be accessed with the users password. So the server operator is not able to see any mail content, if it's saved on the hard disk. Bug Description: =================== I'm using a postfix dovecot setup with the enabled trees plugin with the mailboxformat maildir. When I'm receiving and accessing mail at the same time, the dovecot index gets corrupted. For accessing those mail I use Thunderbird. Example corruption: > ug 4 09:55:15 trees dovecot: imap-login: Login: user=<treesenabled(a)trees.testing>, method=PLAIN, rip=192.168.22.1, lip=192.168.22.77, mpid=4643, TLS, session=<w0OCCplyhLLAqBYB> > Aug 4 09:55:15 trees dovecot: imap(treesenabled(a)trees.testing): Debug: trees plugin initialized > Aug 4 09:55:15 trees dovecot: imap(treesenabled(a)trees.testing): Connection closed in=506 out=495 > Aug 4 09:55:15 trees dovecot: imap(treesenabled(a)trees.testing): Error: Maildir filename has wrong S value, renamed the file from /var/vmail/trees.testing/treesenabled/Maildir/cur/1533376515.M379290P4641.trees,S=1456,W=748:2, to /var/vmail/trees.testing/treesenabled/Maildir/cur/1533376515.M379290P4641.trees,S=783:2, > Aug 4 09:55:15 trees dovecot: imap(treesenabled(a)trees.testing): Error: Corrupted index cache file /var/vmail/trees.testing/treesenabled/Maildir/dovecot.index.cache: Broken physical size for mail UID 1 in mailbox INBOX: read(/var/vmail/trees.testing/treesenabled/Maildir/cur/1533376515.M379290P4641.trees,S=1456,W=748:2,) failed: Cached message size larger than expected (1456 > 728, box=INBOX, UID=1, cached Message-Id=<4ae8ea2c-17ac-37d5-9b9e-b32c6edc777a(a)trees.testing>) > Aug 4 09:55:15 trees dovecot: imap(treesenabled(a)trees.testing): Panic: file istream.c: line 175 (i_stream_read): assertion failed: (old_size <= _stream->pos - _stream->skip) > Aug 4 09:55:15 trees dovecot: imap(treesenabled(a)trees.testing): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x95e92) [0x7fa88e2afe92] -> /usr/lib/dovecot/libdovecot.so.0(+0x95f8d) [0x7fa88e2aff8d] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fa88e245a91] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x290) [0x7fa88e2baf20] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) [0x7fa88e2bb72d] -> /usr/lib/dovecot/libdovecot.so.0(message_get_body_size+0xfd) [0x7fa88e29ab6d] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_init_stream+0x220) [0x7fa88e5eb3d0] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x66fc0) [0x7fa88e5a2fc0] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_get_stream_because+0x5d) [0x7fa88e572e1d] -> /usr/lib/dovecot/libdovecot-storage.so.0(imap_msgpart_open+0x536) [0x7fa88e6264f6] -> dovecot-trees.testing/imap(+0x1ebbc) [0x559b794f1bbc] -> dovecot-trees.testing/imap(+0x1cfb6) [0x559b794effb6] -> dovecot-trees.testing/imap(imap_fetch_more+0x39) [0x559b794f10e9] -> dovecot-trees.testing/imap(cmd_fetch+0x33b) [0x559b794e2d9b] -> dovecot-trees.testing/imap(command_exec+0xa5) [0x559b794ee735] -> dovecot-trees.testing/imap(+0x199c2) [0x559b794ec9c2] -> dovecot-trees.testing/imap(+0x19a4c) [0x559b794eca4c] -> dovecot-trees.testing/imap(client_handle_input+0x1b5) [0x559b794ece55] -> dovecot-trees.testing/imap(client_input+0x86) [0x559b794ed3c6] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x7fa88e2c49f2] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x109) [0x7fa88e2c6029] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x3c) [0x7fa88e2c4a8c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fa88e2c4c38] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fa88e24bfd3] -> dovecot-trees.testing/imap(main+0x328) [0x559b794dfe68] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7fa88de9b2e1] -> dovecot-trees.testing/imap(_start+0x2a) [0x559b794dffea] > Aug 4 09:55:15 trees dovecot: imap(treesenabled(a)trees.testing): Fatal: master: service(imap): child 4633 killed with signal 6 (core dumps disabled) The behavior does not occur, when I'm using maildir and access my mail after receiving it. It also does not occur with other mailbox formats such as mbox, sdbox and mdbox I opened a bug report at the trees repository, which is more detailed ( https://0xacab.org/riseuplabs/trees/issues/24 ). There I described how it's possible to reproduce this error. In the trees repo there is also a vagrant box, with which it's possible to spin up the exact same setup. Questions: =================== 1.) Do you know what could possibly lead to the the larger cached message size, when accessing this mail via imap? 2.) Why does these sizes differ from each other? Mail size from the log is: 'S=1456,W=748:2' or 'renamed to ...S=783:2'. But I do not see where the size of '728' come from? 3.) Do you have a hint what could lead to this behavior and how could I solve this error? Unrelated but also interesting for trees usage: 4.) Is there a tool, with which you can export and import mail to the same inbox? Background: After activation for an existing mail user, only new outgoing and incoming mail is encrypted. So it would be necessary to "re-save" the existing mail again in this mailbox, to pipe all mails through the encryption process. I know that there is dsync, imapsync and several different tools, but I'm not sure what is the best tool for the job, or if I should use dsync to do a 3 way sync? > existing_mailbox(a)server.com > tmp_mailbox(a)server.com > existing_mailbox(a)server.com Thank you: =================== Thank you for time reading this mail :) Dovecot Config: =================== # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.9.0-6-amd64 x86_64 Debian 9.4 ext4 auth_mechanisms = plain login instance_name = trees.testing login_greeting = trees.testing ready. mail_gid = 5000 mail_location = maildir:/var/vmail/%Ld/%Ln/Maildir mail_plugins = " quota trees" mail_uid = 5000 mailbox_list_index = yes namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe autoexpunge = 30 days special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe autoexpunge = 30 days special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocols = " imap pop3" service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } unix_listener auth-userdb { group = vmail mode = 0660 } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_min_avail = 4 } service imap { executable = imap } service pop3 { executable = pop3 } ssl = required ssl_cert = </etc/ssl/certs/ssl-cert-snakeoil.pem ssl_cipher_list = ALL:!LOW:!RC4:!EXP:!aNULL ssl_dh_parameters_length = 2048 ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql }

5 5

dovecot stats-writer socket permissions
by Scott Ruckh 11 Aug '18

11 Aug '18

I have seen this thread about being able to run doveadm as a non-root user, but I don't understand the solution even though I have seen other pages give this link as the solution. http://bit.ly/2MC5oq9 What configuration is necessary so that I can set the permissions on /var/run/dovecot/stats-writer socket-file so when dovecot starts my virtual mail account has read/write access? I saw another page about adding service stats { } Although I set user, group, and permissions, it did not seem to have any effect on the permissions when I restarted dovecot. Thank You.

2 2

Re: dying on osx
by Mike Makuch 10 Aug '18

10 Aug '18

$ grep dove /etc/passwd /etc/group /etc/passwd:_dovecot:*:214:6:Dovecot Administrator:/var/empty:/usr/bin/false /etc/passwd:_dovenull:*:227:227:Dovecot Authentication:/var/empty:/usr/bin/false /etc/group:certusers:*:29:root,_jabber,_postfix,_cyrus,_calendar,_dovecot /etc/group:_dovenull:*:227: I'm trying to build on osx so I can try to do some debugging. The INSTALL.md says to do: $ more INSTALL.md Build Instructions ================== For most people, the usual: ``` ./configure make sudo make install ``` But there is no configure file. How would I generate the configure file? Is it generated? Been a long time since I've done open source C code.. Thanks Mike On 8/10/18 11:04, Aki Tuomi wrote: > Is the user member of mail group? > > > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Mike Makuch <1mikemakuch(a)gmail.com> > Date: 10/08/2018 19:02 (GMT+02:00) > To: Aki Tuomi <aki.tuomi(a)dovecot.fi> > Cc: dovecot(a)dovecot.org > Subject: Re: dying on osx > > Maybe an old problem that has resurfaced??? > > https://bugzilla.samba.org/show_bug.cgi?id=8773 > > Mike > > > > On 8/10/18 10:54, Aki Tuomi wrote: >> I have to see if this is reproducible outside mac. >> >> >> >> --- >> Aki Tuomi >> Dovecot oy >> >> -------- Original message -------- >> From: Mike Makuch <1mikemakuch(a)gmail.com> >> Date: 10/08/2018 18:46 (GMT+02:00) >> To: Aki Tuomi <aki.tuomi(a)dovecot.fi> >> Subject: Re: dying on osx >> >> I did find that page and tried a few things there. My config has all of >> the settings there except 3: >> >> mail_access_groups = mail >> mbox_read_locks = fcntl >> mbox_write_locks = fcntl >> >> I add them to my config, restart and get the same abort >> >> 20180810-103849 imap(mkm)<79213><MkA5ihZzmdh/AAAB>: Fatal: >> setgroups(mail,505) failed: Too many extra groups >> >> I've tried numerous other settings as well. >> >> Thanks for any further advice >> >> Mike >> >> >> On 8/10/18 08:45, Aki Tuomi wrote: >> > Can you try this config and report back? >> > >> > >> https://superuser.com/questions/957272/dotlock-permissions-problems-with-do… >> > >> > Aki >> > >> >> On 10 August 2018 at 16:39 Mike Makuch <1mikemakuch(a)gmail.com> wrote: >> >> >> >> >> >> OSX 10.13.6 High Sierra, dovecot 2.3.2.1 >> >> >> >> dovecot starts up and runs but dies as soon as my mail client makes a >> >> request with log and config below. >> >> >> >> And advice appreciated. >> >> >> >> Thanks >> >> >> >> Mike >> >> >> >> >> >> >> >> 20180810-083730 auth: Debug: auth client connected (pid=77432) >> >> >> >> 20180810-083730 auth: Debug: client in: AUTH 1 PLAIN >> >> service=imap secured session=xo1p2BRzZNd/AAAB lip=127.0.0.1 >> >> rip=127.0.0.1 lport=143 rport=55140 >> >> 20180810-083730 auth: Debug: client passdb out: CONT 1 >> >> 20180810-083730 auth: Debug: client in: CONT 1 AG1rbQBta20xMjM= >> >> (previous base64 data may contain sensitive data) >> >> 20180810-083730 auth: Debug: static(mkm,127.0.0.1,<xo1p2BRzZNd/AAAB>): >> >> lookup >> >> 20180810-083730 auth: Debug: client passdb out: OK 1 user=mkm >> >> host=localhost nopasswd=y >> >> 20180810-083730 auth: Debug: master in: REQUEST 4201906177 77432 >> >> 1 b8126b4b71be2959fc7716888eccc566 session_pid=77433 >> >> request_auth_token >> >> 20180810-083730 auth-worker(77426): Debug: >> >> passwd(mkm,127.0.0.1,<xo1p2BRzZNd/AAAB>): lookup >> >> 20180810-083730 auth: Debug: master userdb out: USER 4201906177 >> >> mkm system_groups_user=mkm uid=503 gid=20 home=/Users/mkm >> >> auth_token=4d2bb44168df3d63e4e1bb352e59de632bc7da49 >> >> 20180810-083730 imap-login: Info: Login: user=<mkm>, method=PLAIN, >> >> rip=127.0.0.1, lip=127.0.0.1, mpid=77433, secured, >> >> session=<xo1p2BRzZNd/AAAB> >> >> 20180810-083730 imap(mkm)<77433><xo1p2BRzZNd/AAAB>: Fatal: >> >> setgroups(505) failed: Too many extra groups >> >> >> >> # doveconf -n >> >> # 2.3.2.1 (0719df592): /usr/local/etc/dovecot/dovecot.conf >> >> # OS: Darwin 17.7.0 x86_64 >> >> # Hostname: pine >> >> auth_debug = yes >> >> auth_debug_passwords = yes >> >> default_internal_user = _dovecot >> >> default_login_user = _dovenull >> >> disable_plaintext_auth = no >> >> listen = 127.0.0.1 >> >> log_path = /var/log/dovecot >> >> log_timestamp = "%Y%m%d-%H%M%S " >> >> mail_debug = yes >> >> mail_gid = staff >> >> mail_location = mbox:~/Mail:INBOX=/var/mail/%u >> >> mail_privileged_group = mail >> >> mail_uid = _dovecot >> >> passdb { >> >> args = password=*** host=localhost nopasswd=y >> >> driver = static >> >> } >> >> passdb { >> >> args = login >> >> driver = pam >> >> } >> >> protocols = imap >> >> service auth { >> >> user = root >> >> } >> >> service imap-login { >> >> inet_listener imap { >> >> address = * >> >> port = 143 >> >> } >> >> } >> >> ssl = no >> >> userdb { >> >> driver = passwd >> >> } >> >> >> >> >> >

1 2

Re: dying on osx
by Mike Makuch 10 Aug '18

10 Aug '18

Maybe an old problem that has resurfaced??? https://bugzilla.samba.org/show_bug.cgi?id=8773 Mike On 8/10/18 10:54, Aki Tuomi wrote: > I have to see if this is reproducible outside mac. > > > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Mike Makuch <1mikemakuch(a)gmail.com> > Date: 10/08/2018 18:46 (GMT+02:00) > To: Aki Tuomi <aki.tuomi(a)dovecot.fi> > Subject: Re: dying on osx > > I did find that page and tried a few things there. My config has all of > the settings there except 3: > > mail_access_groups = mail > mbox_read_locks = fcntl > mbox_write_locks = fcntl > > I add them to my config, restart and get the same abort > > 20180810-103849 imap(mkm)<79213><MkA5ihZzmdh/AAAB>: Fatal: > setgroups(mail,505) failed: Too many extra groups > > I've tried numerous other settings as well. > > Thanks for any further advice > > Mike > > > On 8/10/18 08:45, Aki Tuomi wrote: > > Can you try this config and report back? > > > > > https://superuser.com/questions/957272/dotlock-permissions-problems-with-do… > > > > Aki > > > >> On 10 August 2018 at 16:39 Mike Makuch <1mikemakuch(a)gmail.com> wrote: > >> > >> > >> OSX 10.13.6 High Sierra, dovecot 2.3.2.1 > >> > >> dovecot starts up and runs but dies as soon as my mail client makes a > >> request with log and config below. > >> > >> And advice appreciated. > >> > >> Thanks > >> > >> Mike > >> > >> > >> > >> 20180810-083730 auth: Debug: auth client connected (pid=77432) > >> > >> 20180810-083730 auth: Debug: client in: AUTH 1 PLAIN > >> service=imap secured session=xo1p2BRzZNd/AAAB lip=127.0.0.1 > >> rip=127.0.0.1 lport=143 rport=55140 > >> 20180810-083730 auth: Debug: client passdb out: CONT 1 > >> 20180810-083730 auth: Debug: client in: CONT 1 AG1rbQBta20xMjM= > >> (previous base64 data may contain sensitive data) > >> 20180810-083730 auth: Debug: static(mkm,127.0.0.1,<xo1p2BRzZNd/AAAB>): > >> lookup > >> 20180810-083730 auth: Debug: client passdb out: OK 1 user=mkm > >> host=localhost nopasswd=y > >> 20180810-083730 auth: Debug: master in: REQUEST 4201906177 77432 > >> 1 b8126b4b71be2959fc7716888eccc566 session_pid=77433 > >> request_auth_token > >> 20180810-083730 auth-worker(77426): Debug: > >> passwd(mkm,127.0.0.1,<xo1p2BRzZNd/AAAB>): lookup > >> 20180810-083730 auth: Debug: master userdb out: USER 4201906177 > >> mkm system_groups_user=mkm uid=503 gid=20 home=/Users/mkm > >> auth_token=4d2bb44168df3d63e4e1bb352e59de632bc7da49 > >> 20180810-083730 imap-login: Info: Login: user=<mkm>, method=PLAIN, > >> rip=127.0.0.1, lip=127.0.0.1, mpid=77433, secured, > >> session=<xo1p2BRzZNd/AAAB> > >> 20180810-083730 imap(mkm)<77433><xo1p2BRzZNd/AAAB>: Fatal: > >> setgroups(505) failed: Too many extra groups > >> > >> # doveconf -n > >> # 2.3.2.1 (0719df592): /usr/local/etc/dovecot/dovecot.conf > >> # OS: Darwin 17.7.0 x86_64 > >> # Hostname: pine > >> auth_debug = yes > >> auth_debug_passwords = yes > >> default_internal_user = _dovecot > >> default_login_user = _dovenull > >> disable_plaintext_auth = no > >> listen = 127.0.0.1 > >> log_path = /var/log/dovecot > >> log_timestamp = "%Y%m%d-%H%M%S " > >> mail_debug = yes > >> mail_gid = staff > >> mail_location = mbox:~/Mail:INBOX=/var/mail/%u > >> mail_privileged_group = mail > >> mail_uid = _dovecot > >> passdb { > >> args = password=*** host=localhost nopasswd=y > >> driver = static > >> } > >> passdb { > >> args = login > >> driver = pam > >> } > >> protocols = imap > >> service auth { > >> user = root > >> } > >> service imap-login { > >> inet_listener imap { > >> address = * > >> port = 143 > >> } > >> } > >> ssl = no > >> userdb { > >> driver = passwd > >> } > >> > >> >

2 1

Re: dying on osx
by Aki Tuomi 10 Aug '18

10 Aug '18

I have to see if this is reproducible outside mac. ---Aki TuomiDovecot oy -------- Original message --------From: Mike Makuch <1mikemakuch(a)gmail.com> Date: 10/08/2018 18:46 (GMT+02:00) To: Aki Tuomi <aki.tuomi(a)dovecot.fi> Subject: Re: dying on osx I did find that page and tried a few things there. My config has all of the settings there except 3: mail_access_groups = mail mbox_read_locks = fcntl mbox_write_locks = fcntl I add them to my config, restart and get the same abort 20180810-103849 imap(mkm)<79213><MkA5ihZzmdh/AAAB>: Fatal: setgroups(mail,505) failed: Too many extra groups I've tried numerous other settings as well. Thanks for any further advice Mike On 8/10/18 08:45, Aki Tuomi wrote: > Can you try this config and report back? > > https://superuser.com/questions/957272/dotlock-permissions-problems-with-do… > > Aki > >> On 10 August 2018 at 16:39 Mike Makuch <1mikemakuch(a)gmail.com> wrote: >> >> >> OSX 10.13.6 High Sierra, dovecot 2.3.2.1 >> >> dovecot starts up and runs but dies as soon as my mail client makes a >> request with log and config below. >> >> And advice appreciated. >> >> Thanks >> >> Mike >> >> >> >> 20180810-083730 auth: Debug: auth client connected (pid=77432) >> >> 20180810-083730 auth: Debug: client in: AUTH 1 PLAIN >> service=imap secured session=xo1p2BRzZNd/AAAB lip=127.0.0.1 >> rip=127.0.0.1 lport=143 rport=55140 >> 20180810-083730 auth: Debug: client passdb out: CONT 1 >> 20180810-083730 auth: Debug: client in: CONT 1 AG1rbQBta20xMjM= >> (previous base64 data may contain sensitive data) >> 20180810-083730 auth: Debug: static(mkm,127.0.0.1,<xo1p2BRzZNd/AAAB>): >> lookup >> 20180810-083730 auth: Debug: client passdb out: OK 1 user=mkm >> host=localhost nopasswd=y >> 20180810-083730 auth: Debug: master in: REQUEST 4201906177 77432 >> 1 b8126b4b71be2959fc7716888eccc566 session_pid=77433 >> request_auth_token >> 20180810-083730 auth-worker(77426): Debug: >> passwd(mkm,127.0.0.1,<xo1p2BRzZNd/AAAB>): lookup >> 20180810-083730 auth: Debug: master userdb out: USER 4201906177 >> mkm system_groups_user=mkm uid=503 gid=20 home=/Users/mkm >> auth_token=4d2bb44168df3d63e4e1bb352e59de632bc7da49 >> 20180810-083730 imap-login: Info: Login: user=<mkm>, method=PLAIN, >> rip=127.0.0.1, lip=127.0.0.1, mpid=77433, secured, >> session=<xo1p2BRzZNd/AAAB> >> 20180810-083730 imap(mkm)<77433><xo1p2BRzZNd/AAAB>: Fatal: >> setgroups(505) failed: Too many extra groups >> >> # doveconf -n >> # 2.3.2.1 (0719df592): /usr/local/etc/dovecot/dovecot.conf >> # OS: Darwin 17.7.0 x86_64 >> # Hostname: pine >> auth_debug = yes >> auth_debug_passwords = yes >> default_internal_user = _dovecot >> default_login_user = _dovenull >> disable_plaintext_auth = no >> listen = 127.0.0.1 >> log_path = /var/log/dovecot >> log_timestamp = "%Y%m%d-%H%M%S " >> mail_debug = yes >> mail_gid = staff >> mail_location = mbox:~/Mail:INBOX=/var/mail/%u >> mail_privileged_group = mail >> mail_uid = _dovecot >> passdb { >> args = password=*** host=localhost nopasswd=y >> driver = static >> } >> passdb { >> args = login >> driver = pam >> } >> protocols = imap >> service auth { >> user = root >> } >> service imap-login { >> inet_listener imap { >> address = * >> port = 143 >> } >> } >> ssl = no >> userdb { >> driver = passwd >> } >> >>

1 0

dying on osx
by Mike Makuch 10 Aug '18

10 Aug '18

OSX 10.13.6 High Sierra, dovecot 2.3.2.1 dovecot starts up and runs but dies as soon as my mail client makes a request with log and config below. And advice appreciated. Thanks Mike 20180810-083730 auth: Debug: auth client connected (pid=77432) 20180810-083730 auth: Debug: client in: AUTH 1 PLAIN service=imap secured session=xo1p2BRzZNd/AAAB lip=127.0.0.1 rip=127.0.0.1 lport=143 rport=55140 20180810-083730 auth: Debug: client passdb out: CONT 1 20180810-083730 auth: Debug: client in: CONT 1 AG1rbQBta20xMjM= (previous base64 data may contain sensitive data) 20180810-083730 auth: Debug: static(mkm,127.0.0.1,<xo1p2BRzZNd/AAAB>): lookup 20180810-083730 auth: Debug: client passdb out: OK 1 user=mkm host=localhost nopasswd=y 20180810-083730 auth: Debug: master in: REQUEST 4201906177 77432 1 b8126b4b71be2959fc7716888eccc566 session_pid=77433 request_auth_token 20180810-083730 auth-worker(77426): Debug: passwd(mkm,127.0.0.1,<xo1p2BRzZNd/AAAB>): lookup 20180810-083730 auth: Debug: master userdb out: USER 4201906177 mkm system_groups_user=mkm uid=503 gid=20 home=/Users/mkm auth_token=4d2bb44168df3d63e4e1bb352e59de632bc7da49 20180810-083730 imap-login: Info: Login: user=<mkm>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=77433, secured, session=<xo1p2BRzZNd/AAAB> 20180810-083730 imap(mkm)<77433><xo1p2BRzZNd/AAAB>: Fatal: setgroups(505) failed: Too many extra groups # doveconf -n # 2.3.2.1 (0719df592): /usr/local/etc/dovecot/dovecot.conf # OS: Darwin 17.7.0 x86_64 # Hostname: pine auth_debug = yes auth_debug_passwords = yes default_internal_user = _dovecot default_login_user = _dovenull disable_plaintext_auth = no listen = 127.0.0.1 log_path = /var/log/dovecot log_timestamp = "%Y%m%d-%H%M%S " mail_debug = yes mail_gid = staff mail_location = mbox:~/Mail:INBOX=/var/mail/%u mail_privileged_group = mail mail_uid = _dovecot passdb { args = password=*** host=localhost nopasswd=y driver = static } passdb { args = login driver = pam } protocols = imap service auth { user = root } service imap-login { inet_listener imap { address = * port = 143 } } ssl = no userdb { driver = passwd }

2 1

limit sharing ability to certain users
by Simeon Ott 10 Aug '18

10 Aug '18

Hello Is it possible to limit the ability of sharing it’s own mailboxes to only a few users? We have a few sensitive mailboxes of users where the ability to share via IMAP SETACL should be prevented. I tried the following so far… doveadm acl remove -u test(a)onnet.ch INBOX user=test(a)onnet.ch admin but when doing this the admin rights are still there doveadm acl rights -u test(a)onnet.ch INBOX vmail@buserver:~$ doveadm acl rights -u test(a)onnet.ch INBOX Rights lookup read write write-seen write-deleted insert post expunge create delete admin Thanks in advance for your help Simeon

4 18

Re: Error compiling pigeonhole managesieve 0.4.24
by Aki Tuomi 10 Aug '18

10 Aug '18

Yep On 10.08.2018 11:06, davide marchi wrote: > Thanks Aki for your quick response!! I'm sorry, so i have to compile > and install dovecot version 2.2.36 before compiling and install > pigeonhole 0.4.24? If so sorry for my noob approach > > Il giorno ven 10 ago 2018 alle ore 09:55 Aki Tuomi > <aki.tuomi(a)dovecot.fi <mailto:aki.tuomi@dovecot.fi>> ha scritto: > > Did you remember to install core before compiling pigeonhole? > > Aki > > > On 10.08.2018 10:45, davide marchi wrote: >> Hi i have a problem compiling as mantioned on object of this >> mail: i'm changing dovecot on my debian 6 from version 2.2.32 to >> 2.2.36 and pigeonhole from 0.4.20 to 0.4.24 >> this is output of dovecot -n for listing versions installed >> >> dovecot -n >> # 2.2.32 (dfbe293d4): /usr/local/etc/dovecot/dovecot.conf >> # Pigeonhole version 0.4.20 (7cd71ba) >> # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.10 >> i have downloaded packages from site and compiling from source >> >> so far so good >> for pigeonhole this is the configure command that i always use >> >> ./configure CFLAGS=-O3 >> but when i run make this is the error that i came accross: >> >> /bin/bash ../../libtool --tag=CC --mode=link gcc -std=gnu99 >> -O3 -Wall -W -Wmissing-prototypes -Wmissing-declarations >> -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast >> -fno-builtin-strftime -Wstrict-aliasing=2 -I../.. >> -export-dynamic -o sievec sievec.o >> ../../src/lib-sieve/libdovecot-sieve.la >> <http://libdovecot-sieve.la> >> ../../src/lib-sieve-tool/libsieve-tool.la >> <http://libsieve-tool.la> -ldovecot-storage -ldovecot-lda >> -L/usr/local/lib/dovecot -ldovecot -lrt >> libtool: link: gcc -std=gnu99 -O3 -Wall -W -Wmissing-prototypes >> -Wmissing-declarations -Wpointer-arith -Wchar-subscripts >> -Wformat=2 -Wbad-function-cast -fno-builtin-strftime >> -Wstrict-aliasing=2 -I../.. -o .libs/sievec sievec.o >> -Wl,--export-dynamic >> ../../src/lib-sieve/.libs/libdovecot-sieve.so >> ../../src/lib-sieve-tool/.libs/libsieve-tool.a >> /usr/local/lib/dovecot/libdovecot-storage.so >> /usr/local/lib/dovecot/libdovecot-lda.so -L/usr/local/lib/dovecot >> /usr/local/lib/dovecot/libdovecot.so -lrt -Wl,-rpath >> -Wl,/usr/local/lib/dovecot >> ../../src/lib-sieve/.libs/libdovecot-sieve.so: undefined >> reference to `str_sanitize_utf8' >> collect2: ld returned 1 exit status >> make[3]: *** [sievec] Error 1 >> make[3]: Leaving directory >> `/download/dovecot-2.2-pigeonhole-0.4.24/src/sieve-tools' >> make[2]: *** [all-recursive] Error 1 >> make[2]: Leaving directory >> `/download/dovecot-2.2-pigeonhole-0.4.24/src' >> make[1]: *** [all-recursive] Error 1 >> make[1]: Leaving directory `/download/dovecot-2.2-pigeonhole-0.4.24' >> make: *** [all] Error 2 >> >> What's wrong ? Thanks in advance on helping me >

1 0

Error compiling pigeonhole managesieve 0.4.24
by davide marchi 10 Aug '18

10 Aug '18

Hi i have a problem compiling as mantioned on object of this mail: i'm changing dovecot on my debian 6 from version 2.2.32 to 2.2.36 and pigeonhole from 0.4.20 to 0.4.24 this is output of dovecot -n for listing versions installed dovecot -n # 2.2.32 (dfbe293d4): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.20 (7cd71ba) # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.10 i have downloaded packages from site and compiling from source so far so good for pigeonhole this is the configure command that i always use ./configure CFLAGS=-O3 but when i run make this is the error that i came accross: /bin/bash ../../libtool --tag=CC --mode=link gcc -std=gnu99 -O3 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -I../.. -export-dynamic -o sievec sievec.o ../../src/lib-sieve/libdovecot-sieve.la ../../src/lib-sieve-tool/ libsieve-tool.la -ldovecot-storage -ldovecot-lda -L/usr/local/lib/dovecot -ldovecot -lrt libtool: link: gcc -std=gnu99 -O3 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -I../.. -o .libs/sievec sievec.o -Wl,--export-dynamic ../../src/lib-sieve/.libs/libdovecot-sieve.so ../../src/lib-sieve-tool/.libs/libsieve-tool.a /usr/local/lib/dovecot/libdovecot-storage.so /usr/local/lib/dovecot/libdovecot-lda.so -L/usr/local/lib/dovecot /usr/local/lib/dovecot/libdovecot.so -lrt -Wl,-rpath -Wl,/usr/local/lib/dovecot ../../src/lib-sieve/.libs/libdovecot-sieve.so: undefined reference to `str_sanitize_utf8' collect2: ld returned 1 exit status make[3]: *** [sievec] Error 1 make[3]: Leaving directory `/download/dovecot-2.2-pigeonhole-0.4.24/src/sieve-tools' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/download/dovecot-2.2-pigeonhole-0.4.24/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/download/dovecot-2.2-pigeonhole-0.4.24' make: *** [all] Error 2 What's wrong ? Thanks in advance on helping me

2 1

Best practices for backing up small mailserver to remote location
by Ian Evans 09 Aug '18

09 Aug '18

My webserver also houses our mailserver. There's about six users on that mail system and I'm thinking it would be good to back up the mailboxes to my always on HTPC computer at home, which is reachable via a dynamic IP service. I know (or think) I need to use doveadm-backup for this but rather than reinvent the wheel (or use the wrong wheel altogether) I'm wondering if anyone can recommend a good tutorial or wiki entry that shows the best way to loop through the users and send their backups to a remote server. Thanks.

6 6

Message delivered twice caused by an LMTP error "Got unexpected reply" during upgrade to 2.3
by Gabriele Nencioni 09 Aug '18

09 Aug '18

Hi all, we are upgrading our dovecot platform from: # dovecot --version 2.2.15.14 (39f57c379ded+) to # dovecot --version 2.3.2.1 (0719df592) Our platform is debian based and it is configured as director and backend proxy. We have just upgrade only 4 servers (2 directors and 2 backends) and when the lmtp traffic flow goes through an upgraded director and a not-upgraded backend sometimes the following error has been arised: Aug 6 14:31:28 monti-director07 dovecot: lmtp(13463): Error: eMFVIKA/aFuXNAAAhXvSMA: Failed to send message to <test2(a)internalinboundcm.eu> at 192.168.72.135:24: Got unexpected reply (1/1 at 210 ms) Aug 6 14:31:28 monti-director07 dovecot: lmtp(13463): Error: eMFVIKA/aFuXNAAAhXvSMA: Failed to send message to <test2(a)internalinboundcm.eu> at 192.168.72.135:24: Got unexpected reply (1/1 at 210 ms) where 172.20.44.7 (monti-director07) is a dovecot 2.3.2.1 192.168.72.135 (monti-backend07) is a dovecot 2.2.15.14 When that error occurs an email is delivered twice, as you can see from the following logs. On smtp server you can see the temp fail (by the upgraded director 172.20.44.7), retry and delivered (by a not-upgraded director 172.20.44.3): 20180806 14:31:28.772 core context="Temporary_Delivery_Failure", _fromemail="test1(a)internalinboundcm.eu", _toemail="test2(a)internalinboundcm.eu", _tos="test2(a)internalinboundcm.eu", _size="80294", dip=172.20.44.7 dport=24 type=lmtp msg="4.4.0 Remote server not answering (bad reply)" duration=5 mailfrom=6/6/0/0 rcptto=6/6/0/0 data=6/5/1/0 tls=0/0 20180806 14:32:28.032 core context="Message_Delivered", _fromemail="test1(a)internalinboundcm.eu", _toemail="test2(a)internalinboundcm.eu", _tos="test2(a)internalinboundcm.eu", _size="80294", dip=172.20.44.3 dport=24 type=lmtp msg="2.0.0 <test2(a)internalinboundcm.eu> AS1CJtQ/aFsqMAAAj5cnUg Saved" duration=21457 mailfrom=3586/3586/0/0 rcptto=3586/3586/0/0 data=3586/3584/2/0 tls=0/0 and on backend server there are the related two delivered log entries: Aug 6 14:31:28 monti-backend07 dovecot: lmtp(test2(a)internalinboundcm.eu)<f0WZF5c/aFuPdgAAj5cnUg>: copy from <lmtp DATA>: box=INBOX, uid=2727, msgid=<005b01d42d80$2101fff0$6305ffd0$(a)internalinboundcm.eu> Aug 6 14:31:28 monti-backend07 dovecot: lmtp(test2(a)internalinboundcm.eu)<f0WZF5c/aFuPdgAAj5cnUg>: f0WZF5c/aFuPdgAAj5cnUg: msgid=<005b01d42d80$2101fff0$6305ffd0$(a)internalinboundcm.eu>: saved mail to INBOX Aug 6 14:32:28 monti-backend07 dovecot: lmtp(test2(a)internalinboundcm.eu)<AS1CJtQ/aFsqMAAAj5cnUg>: copy from <lmtp DATA>: box=INBOX, uid=2728, msgid=<005b01d42d80$2101fff0$6305ffd0$(a)internalinboundcm.eu> Aug 6 14:32:28 monti-backend07 dovecot: lmtp(test2(a)internalinboundcm.eu)<AS1CJtQ/aFsqMAAAj5cnUg>: AS1CJtQ/aFsqMAAAj5cnUg: msgid=<005b01d42d80$2101fff0$6305ffd0$(a)internalinboundcm.eu>: saved mail to INBOX This is the strace output of dovecot lmtp director process (13463): 13463 1533558688.759362 read(8, "250 2.0.0 <test2(a)internalinboundcm.eu> f0WZF5c/aFuPdgAAj5cnUg Saved\r\n", 8012) = 71 <0.000028> 13463 1533558688.759493 sendto(14, "<19>Aug 6 14:31:28 dovecot: lmtp(13463): Error: eMFVIKA/aFuXNAAAhXvSMA: Failed to send message to <test2(a)internalinboundcm.eu> at 192.168.72.135:24: Got unexpected reply (1/1 at 210 ms)", 188, MSG_NOSIGNAL, NULL, 0) = 188 <0.000037> So it receives the "Saved" message from backend but it arises the "Got unexpected reply" error anyway. >From tcpdump we have noticed the QUIT response is missed on lmtp trasaction after the "Saved" message from backend at DATA stage: 220 monti-backend07.it.dadainternal Dovecot ready. LHLO monti-director07.it.dadainternal 250-monti-backend07.it.dadainternal 250-8BITMIME 250-ENHANCEDSTATUSCODES 250 PIPELINING MAIL FROM:<test1(a)internalinboundcm.eu> RCPT TO:<test2(a)internalinboundcm.eu> DATA ...truncated message . 250 2.0.0 <test2(a)internalinboundcm.eu> f0WZF5c/aFuPdgAAj5cnUg Saved While it should be something like this: 220 monti-backend07.it.dadainternal Dovecot ready. LHLO monti-director07.it.dadainternal 250-monti-backend07.it.dadainternal 250-8BITMIME 250-ENHANCEDSTATUSCODES 250 PIPELINING MAIL FROM:<test1(a)internalinboundcm.eu> RCPT TO:<test2(a)internalinboundcm.eu> DATA ...truncated message . 250 2.0.0 <test2(a)internalinboundcm.eu> f0WZF5c/aFuPdgAAj5cnUg Saved QUIT 221 2.0.0 OK It follows the both dovecot configurations: # 2.3.2.1 (0719df592): /etc/dovecot/dovecot.conf # OS: Linux 4.9.0-7-amd64 x86_64 Debian 9.5 auth_cache_negative_ttl = 0 auth_verbose = yes auth_worker_max_count = 350 director_mail_servers = 192.168.72.129 192.168.72.130 192.168.72.131 192.168.72.132 192.168.72.133 192.168.72.134 192.168.72.135 192.168.72.136 192.168.72.137 192.168.72.138 192.168.72.139 192.168.72.140 192.168.72.141 192.168.72.142 192.168.72.143 192.168.72.144 192.168.72.145 192.168.72.146 192.168.72.147 192.168.72.148 192.168.72.149 director_servers = 172.20.44.1 172.20.44.2 172.20.44.3 172.20.44.4 172.20.44.5 172.20.44.6 172.20.44.7 172.20.44.8 disable_plaintext_auth = no doveadm_password = # hidden, use -P to show it doveadm_port = 24242 lmtp_proxy = yes log_timestamp = "%Y-%m-%d %H:%M:%S " login_log_format_elements = user=<%Lu> method=%m rip=%r lip=%l mpid=%e %c session=<%{session}> mail_log_prefix = "%s(%Lu)<%{session}>: " mail_max_userip_connections = 500 passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql skip = authenticated } protocols = imap pop3 lmtp service auth-worker { user = dovecot } service auth { client_limit = 0 } service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { port = 9090 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service doveadm { inet_listener { port = 24242 } } service imap-login { client_limit = 12000 executable = imap-login director process_limit = 0 process_min_avail = 4 service_count = 0 } service ipc { unix_listener ipc { user = $default_internal_user } } service lmtp { client_limit = 1 executable = lmtp -L inet_listener lmtp { port = 24 } process_limit = 240 process_min_avail = 20 service_count = 1 } service pop3-login { client_limit = 12000 executable = pop3-login director process_limit = 0 process_min_avail = 4 service_count = 0 } ssl = no userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } verbose_proctitle = yes protocol doveadm { auth_socket_path = director-userdb } protocol lmtp { auth_socket_path = director-userdb mail_plugins = } # 2.2.15.14 (39f57c379ded+): /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.9 auth_cache_negative_ttl = 0 auth_worker_max_count = 500 default_vsz_limit = 1 G disable_plaintext_auth = no doveadm_password = first_valid_uid = 508 last_valid_uid = 508 lda_mailbox_autocreate = yes log_timestamp = "%Y-%m-%d %H:%M:%S " login_log_format_elements = user=<%Lu> method=%m rip=%r lip=%l mpid=%e %c session=<%{session}> login_trusted_networks = 192.168.72.201 192.168.72.202 192.168.72.203 192.168.72.204 192.168.72.205 192.168.72.206 192.168.72.207 192.168.72.208 mail_fsync = always mail_gid = 508 mail_location = maildir:~/Maildir mail_log_prefix = "%s(%Lu)<%{session}>: " mail_max_userip_connections = 30 mail_plugins = notify mail_log quota mail_uid = 508 maildir_very_dirty_syncs = yes mmap_disable = yes namespace { hidden = yes list = no location = prefix = separator = . } namespace inbox { inbox = yes location = mailbox Drafts { auto = create special_use = \Drafts } mailbox Sent { auto = create special_use = \Sent } mailbox Spam { auto = create special_use = \Junk } mailbox Trash { auto = create special_use = \Trash } prefix = INBOX. separator = . } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql skip = authenticated } plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid quota = dict:User quota::file:%h/dovecot-quota quota_exceeded_message = Quota exceeded quota_rule2 = Trash:storage=+100M quota_warning = storage=100%% quota-warning -q 100 -n %n -d %d -e OverQuota quota_warning2 = storage=80%% quota-warning -q 80 -n %n -d %d -e FillQuota quota_warning3 = -storage=99%% quota-warning -q 99 -n %n -d %d -e InQuota sieve = ~/.dovecot.sieve sieve_extensions = +editheader sieve_max_redirects = 15 sieve_vacation_default_period = 1h } quota_full_tempfail = yes service auth-worker { user = dovecot } service auth { client_limit = 15000 } service doveadm { inet_listener { port = 24242 } } service imap-login { process_limit = 0 process_min_avail = 16 service_count = 0 } service imap { executable = imap postlogin process_limit = 7000 service_count = 2300 } service lmtp { client_limit = 1 executable = lmtp -L inet_listener lmtp { address = 192.168.72.129 127.0.0.1 port = 24 } process_limit = 240 process_min_avail = 20 service_count = 10 } service pop3-login { process_limit = 0 process_min_avail = 16 service_count = 0 } service pop3 { executable = pop3 postlogin process_limit = 7000 service_count = 2300 } ssl = no submission_host = userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } verbose_proctitle = yes protocol imap { imap_client_workarounds = delay-newmail mail_plugins = notify mail_log quota imap_quota } protocol pop3 { pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_fast_size_lookups = yes pop3_no_flag_updates = yes pop3_uidl_format = %f } protocol lmtp { mail_plugins = notify mail_log quota sieve passdb { args = /etc/dovecot/dovecot-lmtp.conf driver = sql name = } userdb { args = /etc/dovecot/dovecot-lmtp.conf driver = sql name = result_failure = return-fail skip = never } } Please could someone help me? How can I fix that error, in order to avoid the duplicated email? Thanks in advance Regards, -- Gabriele Nencioni System Administrator eml gabriele.nencioni(a)register.it

2 2

Set X-Original-To based an ORCPT?
by Peer Heinlein 09 Aug '18

09 Aug '18

Since http://dovecot.org/pipermail/dovecot-cvs/2014-November/025241.html Dovecot's LMTP does support ORCPT. Is it possible to set X-Original-To-Header based on that ORCPT? Peer -- Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-42 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin

5 5