- dovecot - dovecot.org

New mail notification
by Matthew Allen 07 Feb '18

07 Feb '18

Hi, So I'm running dovecot 1.2.17 on Mac OSX using maildir in ~/Mail. After using getmail for a while to download my POP3 email and store it in the right place it started not working so I replaced it with a python script that I wrote. All was good for a while and then I stopped getting new mail notifications in my IMAP client. If I close the connection and restart the new mail shows up as !seen but no amount of re-selecting the folder will show the new mail while the connection is active. There is no untagged responses about new mail while the client is IDLEing. The client is InScribe (http://memecode.com/inscribe.php) but I doubt it's client specific. Seems to be server related. Now the python script in question just puts the .eml file in ~/Mail/tmp and then renames it to the ~/Mail/new folder. Does it need to do something else as well to make the notifications work? There aren't any error messages in the log. Just normal login history. If you can point me in the right direction that'd be appreciated. Regards Matthew Allen

1 0

Dovecot on GlusterFS via NFS is... strange.
by Frank Wall 07 Feb '18

07 Feb '18

Hi, I've discovered some interesting behaviour when running Dovecot on a GlusterFS volume (3.10) that is mounted via NFS 4.1 (ganesha NFS). First of all, using the usual settings for NFS storage seemed like an obvious choice for my setup (Dovecot 2.2.33.2, CentOS 7.4): mail_nfs_storage = yes mail_nfs_index = yes mail_fsync = always maildir_copy_with_hardlinks = yes mmap_disable = yes lock_method = dotlock (FWIW, I've been using these settings for many years on different NFS storages without any issues. Another instance of Dovecot 2.2.33 on FreeBSD 11.1 with a more traditional NFS storage is rock-solid.) SPOILER: These settings caused terrible issues. For example, when trying to clone a mailbox from an old server to this new Dovecot-on-GlusterFS setup (using imapsync), the following errors would show up frequently: Feb 6 16:44:53 dovecot: IMAP(user(a)example.com): Panic: file maildir-uidlist.c: line 1262 (maildir_uidlist_write_fd): assertion failed: (first_idx == 0) Feb 6 16:44:53 dovecot: IMAP(user(a)example.com): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x9f3de) [0x7f7b6b44f3de] -> /usr/lib64/dovecot/libdovecot.so.0(+0x9f4be) [0x7f7b6b44f4be] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7f7b6b3e077c] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x79605) [0x7f7b6b75b605] -> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_uidlist_sync_finish+0x1ac) [0x7f7b6b75d61c] -> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_uidlist_sync_deinit+0x98) [0x7f7b6b75da48] -> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_transaction_save_commit_pre+0x41f) [0x7f7b6b75483f] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xcccd0) [0x7f7b6b7aecd0] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_transaction_commit_full+0x9d) [0x7f7b6b7cb3cd] -> /usr/lib64/dovecot/libdovecot-storage.so.0(index_transaction_commit+0x107) [0x7f7b6b7af217] -> /usr/lib64/dovecot/lib10_quota_plugin.so(+0xe17c) [0x7f7b6a9ca17c] -> /usr/lib64/dovecot/lib01_acl_plugin.so(+0xda0a) [0x7f7b6abe0a0a] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_transaction_commit_get_changes+0x51) [0x7f7b6b72c161] -> dovecot/imap [user(a)example.com 10.0.0.1 APPEND](+0xf255) [0x55ca8238f255] -> dovecot/imap [user(a)example.com 10.0.0.1 APPEND](command_exec+0x5c) [0x55ca8239cf0c] -> dovecot/imap [user(a)example.com 10.0.0.1 APPEND](+0xe771) [0x55ca8238e771] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x7f7b6b464cd2] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x10f) [0x7f7b6b4663bf] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x3c) [0x7f7b6b464d6c] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f7b6b464f28] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f7b6b3eafa3] -> dovecot/imap [user(a)example.com 10.0.0.1 APPEND](main+0x333) [0x55ca8238e2e3] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f7b6b00ec05] -> dovecot/imap [user(a)example.com 10.0.0.1 APPEND](+0xe476) [0x55ca8238e476] Feb 6 16:44:53 dovecot: IMAP(user(a)example.com): Fatal: master: service(imap): child 84782 killed with signal 6 (core dumps disabled) Feb 6 16:44:56 dovecot: IMAP(user(a)example.com): Error: readdir(/data/mail/abc/default/.Foldername 01_ Foo 1234/new) failed: Unknown error 523 Yes, the folder name is "special" in this example. (I'm not sure if this readdir() error is actually related to the other issue.) So, this caused the imap process to die repeatedly and the user got disconnected many many times. In this state the mail services were not really usable. Side note: The NFS share was mounted by using the most conservative moint options I could think of: vers=4.1,rsize=131072,wsize=131072,nosharecache,noac,nordirplus,proto=tcp And if you're wondering: Yes, I'm using Dovecot director for IMAP and LMTP (currently running 3 VMs for Dovecot director and 3 VMs for Dovecot IMAP). Then the fun began... I've decided to change the following settings: mail_nfs_storage = no mail_nfs_index = no Re-created the maildir and restarted the imapsync copy process. Out of sudden the errors are gone! Now Dovecot is performing pretty well on my GlusterFS volume. Does this make any sense to anyone? Ciao - Frank

1 0

"make check" test-hash-method bus error (Sparc alignment)
by Rainer Jung 06 Feb '18

06 Feb '18

Hi there, when doing "make check" for a 2.3.0 build on Solaris Sparc I get a bus error due to an alignment issue. It seems the error is only happening during testing, because in the official API it was fixed in https://github.com/dovecot/core/commit/d8361cc8576d9ede93a037f9b96f2a3f9b7e… But the tests use hand written test vectors, that are not correctly aligned: ... hash method md4 (test vectors) ....................................... : ok hash method md5 (test vectors) ....................................... : ok /bin/ksh[2]: 24287 Bus Error(coredump) make[4]: *** [Makefile:2655: check-local] Error 1 gdb output: Program terminated with signal SIGBUS, Bus error. #0 sha1_loop (ctxt=0xffbff724, input=0x83908, len=3) at sha1.c:224 224 ctxt->c.b64[0] += copysiz * 8; (gdb) print &ctxt->c.b64[0] $1 = (uint64_t *) 0xffbff73c So the address of the 8 byte type is not divisible by 8 (Sparc alignment requirement). Full stack: (gdb) bt full #0 sha1_loop (ctxt=0xffbff724, input=0x83908, len=3) at sha1.c:224 input_c = 0x83908 "abc" gaplen = <optimized out> gapstart = <optimized out> off = 0 copysiz = 3 #1 0x00024eb0 in test_hash_methods_fips () at test-hash-method.c:338 n = 0 method = 0xc4e68 <hash_method_sha1> context = 0xffbff724 "gE#\001▒ͫ\211\230▒▒▒\020\062Tv▒▒▒▒" result = "▒9▒▒^kK\r2U▒▒\225`\030\220▒▒\a\t" i = 7 last_method = 0x839d0 "sha1" test_vectors = {{method = 0x838e0 "md4", input = 0x838e8, ilen = 0, rounds = 1, output = 0x838f0, olen = 16}, {method = 0x838e0 "md4", input = 0x83908, ilen = 3, rounds = 1, output = 0x83910, olen = 16}, {method = 0x838e0 "md4", input = 0x83928, ilen = 62, rounds = 1, output = 0x83968, olen = 16}, {method = 0x83980 "md5", input = 0x838e8, ilen = 0, rounds = 1, output = 0x83988, olen = 16}, {method = 0x83980 "md5", input = 0x83908, ilen = 3, rounds = 1, output = 0x839a0, olen = 16}, { method = 0x83980 "md5", input = 0x83928, ilen = 62, rounds = 1, output = 0x839b8, olen = 16}, {method = 0x839d0 "sha1", input = 0x838e8, ilen = 0, rounds = 1, output = 0x839d8, olen = 20}, {method = 0x839d0 "sha1", input = 0x83908, ilen = 3, rounds = 1, output = 0x839f0, olen = 20}, {method = 0x839d0 "sha1", input = 0x83a08, ilen = 56, rounds = 1, output = 0x83a48, olen = 20}, {method = 0x83a60 "sha3-256", input = 0x838e8, ilen = 0, rounds = 1, output = 0x83a70, olen = 32}, {method = 0x83a60 "sha3-256", input = 0x83a98, ilen = 135, rounds = 1, output = 0x83b20, olen = 32}, {method = 0x83a60 "sha3-256", input = 0x83b48, ilen = 200, rounds = 1, output = 0x83c18, olen = 32}, {method = 0x83a60 "sha3-256", input = 0x83c40, ilen = 1, rounds = 200, output = 0x83c18, olen = 32}, { method = 0x83c48 "sha3-512", input = 0x838e8, ilen = 0, rounds = 1, output = 0x83c58, olen = 64}, {method = 0x83c48 "sha3-512", input = 0x83a98, ilen = 135, rounds = 1, output = 0x83ca0, olen = 64}, {method = 0x83c48 "sha3-512", input = 0x83b48, ilen = 200, rounds = 1, output = 0x83ce8, olen = 64}, { method = 0x83c48 "sha3-512", input = 0x83c40, ilen = 1, rounds = 200, output = 0x83ce8, olen = 64}} #2 0x0003e3e0 in test_run_named_funcs (tests=tests@entry=0x80434 <test_functions>, match=match@entry=0x7fd40 "") at test-common.c:255 _data_stack_cur_id = 2 i = <optimized out> #3 0x0003f1e4 in test_run_named_with_fatals (match=0x7fd40 "", tests=0x80434 <test_functions>, fatals=0x7fde8 <fatal_functions>) at test-common.c:337 No locals. #4 0x0001e024 in _start () Unaligned data comes from file src/lib/test-hash-method.c: ... 53 static void test_hash_methods_fips() { 54 const char *last_method = NULL; 55 56 struct { 57 const char *method; 58 const void *input; 59 size_t ilen; 60 size_t rounds; 61 const void *output; 62 size_t olen; 63 } test_vectors[] = 64 { ... 115 { "sha1", 116 "", 117 0, 118 1, 119 "\xda\x39\xa3\xee\x5e\x6b\x4b\x0d" 120 "\x32\x55\xbf\xef\x95\x60\x18\x90" 121 "\xaf\xd8\x07\x09", 122 160 / 8 123 }, ... etc. The input data needs to be 8 byte aligned but is just a void *. Thanks and regards, Rainer

1 0

Dovecot and /dev/rand
by Michael A. Peters 06 Feb '18

06 Feb '18

There's a (2014 I think) patch in dovecot rpm for Red Hat / Fedora ecosystem that was last update with 2.2.9 (patch last updated for that release) I want to know if the problem it solves still exists in 2.3.x branch. The patch is called "dovecot-2.2.9-nodevrand.patch" and is attached. It allegedly addresses an issue with installation in chroot that does not have /dev/random Red Hat bugzilla 1026790 I am apparently not authorized to see that bug so I don't know much about it, but with many code changes in 2.3.0 from 2.2.x I am wondering if the alleged issue was solved a different way or if the patch should be ported to 2.3.0 when packaged for people who might trigger it. Thanks.

1 0

Does Dovecot LDAP auth support LDAP referral
by Xuan Jia 06 Feb '18

06 Feb '18

We using Dovecot with LDAP. From the beginning, we using GC LDAP query with port 3268 for email accounts. For example, user1(a)our-organization.org (in the USA) with "base = dc=our-organization, dc=org" works fine. But refer to this document: https://wiki2.dovecot.org/AuthDatabase/LDAP When we change the LDAP from 3268 to 389 and with TLS, the base should be changed like this: "base = ou=usa, dc=our-organization, dc=org" But if the user (user2) located in United Kingdom (ou=gbr), the user can not login. When we debug with ldapsearch: ldapsearch -ZZ -v -h dc.our-organization.org -p 389 -D 'cn=auth_user,ou=usa,dc=our-organization,dc=org' -W -b 'dc=our-organization, dc=org' '(userPrincipalName=user2(a)our-organization.org)' It can return user2 information with some "numReferences". But in Dovecot, if "base = dc=our-organization, dc=org" it only reported auth error with timeout. Here are the config: # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 3.16.0-4-amd64 x86_64 Debian 9.3 auth_verbose = yes dsync_remote_cmd = ssh -l%{login} %{host} doveadm dsync-server -u%u -l%{lock_timeout} -n%{namespace} imap_id_send = imapc_user = %u import_environment = TZ listen = * login_log_format_elements = user=u> method=%m rip=%r lip=%l mpid=%e %c mail_shared_explicit_inbox = yes 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 mime foreverypart extracttext namespace inbox { 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-ldap-userdb.conf.ext driver = ldap } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = " imap sieve" service managesieve-login { inet_listener sieve { port = 4190 } service_count = 0 } ssl_ca = /etc/ssl/certs/ca.pem ssl_cert = </etc/ssl/gameloft/our-organization.org.crt ssl_key = # hidden, use -P to show it ssl_parameters_regenerate = 1 weeks userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } So my question is: does Dovecot LDAP auth support LDAP referral? If Dovecot relies on OpenLDAP, it should be support. If not, why and what is the walkthrough? Xuan Jia

2 2

Dovecot 2.3.0, Panic: file mailbox-attribute.c: line 362 (mailbox_attribute_get_stream): assertion failed: (value_r->value != NULL || value_r->value_stream != NULL)
by Marco Giunta 05 Feb '18

05 Feb '18

Hi at all, I have a RHEL7 server with Dovecot 2.3.0 (new installation). I've a problem when trying to dsync from a Dovecot 2.2.24 server. If I try to sync any user with a folder with ACL, dsycn crash with panic: Source server: dsync-local(USERNAME): Debug: sieve: file storage: sync: Synchronization active dovecot: dsync-local(USERNAME): Debug: acl vfile: reading file /var/spool/mail/U/USERNAME/dovecot-acl dsync-local(USERNAME): Error: read(DEST_SERVER.example.com) failed: EOF (last sent=mail_change (EOL), last recv=mailbox) Destination server: Feb 2 14:15:23 DEST_SERVER dovecot: dsync-server(USERNAME): Panic: file mailbox-attribute.c: line 362 (mailbox_attribute_get_stream): assertion failed: (value_r->value != NULL || value_r->value_stream != NULL) Feb 2 14:15:23 DEST_SERVER dovecot: dsync-server(USERNAME): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xc8cc4) [0x7fa861bc0cc4] -> /usr/lib64/dovecot/libdovecot.so.0(+0xc8d7e) [0x7fa861bc0d7e] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7fa861b34190] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x55cbc) [0x7fa861ec1cbc] -> dovecot/doveadm-server [10.0.11.137 USERNAME INBOX send:mail_requests recv:attributes](dsync_mailbox_import_attribute+0x4d) [0x55b9d4ce215d] -> dovecot/doveadm-server [10.0.11.137 USERNAME INBOX send:mail_requests recv:attributes](dsync_brain_sync_mails+0x2ef) [0x55b9d4cddbdf] -> dovecot/doveadm-server [10.0.11.137 USERNAME INBOX send:mail_requests recv:attributes](dsync_brain_run+0x2b0) [0x55b9d4cd93e0] -> dovecot/doveadm-server [10.0.11.137 USERNAME INBOX send:mail_requests recv:attributes](+0x43a10) [0x55b9d4cd9a10] -> dovecot/doveadm-server [10.0.11.137 USERNAME INBOX send:mail_requests recv:attributes](+0x5837f) [0x55b9d4cee37f] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x65) [0x7fa861bd82b5] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x10f) [0x7fa861bd9b5f] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x52) [0x7fa861bd83b2] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fa861bd85d8] -> dovecot/doveadm-server [10.0.11.137 USERNAME INBOX send:mail_requests recv:attributes](+0x28369) [0x55b9d4cbe369] -> dovecot/doveadm-server [10.0.11.137 USERNAME INBOX send:mail_requests recv:attributes](+0x29c07) [0x55b9d4cbfc07] -> dovecot/doveadm-server [10.0.11.137 USERNAME INBOX send:mail_requests recv:attributes](+0x3f969) [0x55b9d4cd5969] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x65) [0x7fa861bd82b5] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x10f) [0x7fa861bd9b5f] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x52) [0x7fa861bd83b2] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fa861bd85d8] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fa861b56b23] -> dovecot/doveadm-server [10.0.11.137 USERNAME INBOX send:mail_requests recv:attributes](main+0x1b6) [0x55b9d4cb0536] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7fa861756c05] -> dovecot/doveadm-server [10.0.11.137 USERNAME INBOX send:mail_requests recv:attributes](+0x1a5f5) [0x55b9d4cb05f5] Feb 2 14:15:23 DEST_SERVER dovecot: dsync-server(USERNAME): Fatal: master: service(doveadm): child 2149 killed with signal 6 (core dumped) Coredump and configuration attached. On source server I run this command: # doveadm -D backup -f -u USERNAME -x 'Archives*' tcp:DEST_SERVER.example.com but same panic if try to sync from destination server: # doveadm -D backup -fR -u USERNAME -x 'Archives*' tcp:SOURCE_SERVER.example.com Same panic also syncing any user with acl and using different acl_shared_dict (file or fs:posix) in dovecot configuration. Thanks, Marco -- Marco Giunta - ITCS SysAdmin Via Bonomea, 265 34136 - Trieste, Italy Tel: +39-040-3787-503 Fax: +39-040-3787-244

1 1

Re: How to grant user access to his .dovecot.sieve.log?
by Sergey Ivanov 04 Feb '18

04 Feb '18

Hi Gabriel, I'm trying to implement what you suggested using apache mod_userdir with === UserDir /srv/dovecot <DirectoryMatch "^/srv/dovecot/(?<WHICHUSER>[^/]+)"> Require user %{env:MATCH_WHICHUSER} DirectoryIndex .dovecot.sieve.log ... </DirectoryMatch> === I still need to find how to set up right permissions for these logs without too much brute force. It looks like this way I can get what I want, but I really hoped to find some better way: my Roundcube installation is on the load-balanced web farm and there is no and should not be a file access to these logs. I think such a feature as Sieve compiler must have some standard way to say what is wrong to the author of the Sieve script. -- Sergey. On Fri, Feb 2, 2018 at 2:29 PM, Gabriel Kaufmann <mailings(a)typoworx.com> wrote: > Alternatively use a web-interface with read-only access to the log? > > best regards > > Gabriel Kaufmann > >

1 0

Dual Dovecot setup
by dovecot.dirk＠o.banes.ch 03 Feb '18

03 Feb '18

Hi all, I´m using dovecot successfully since some years. My current setup is postfix and dovecot on one vserver. This works great so far. +--------------------+ eMail in | VSERVER1 | +---------->+ MX 1 (Master) | | POSTFIX MTA | | DOVECOT ALL Folders| +-----^--------------+ | |eMail Backup | | +------+---------+ | VSERVER2 | eMail in | MX 2 (Backup) | Backup | POSTFIX MTA | +---------> | +----------------+ However now I want to change this setup to have on box in my home which holds all eMails and Folders which are not in the Inbox. This is due to disk space and privacy concerns. Even if the home connection is very very stable for the case something fails while on vacation the content of the inbox of every user should always stay on the VSERVER1 as well - until it is moved to one subfolder. +---------------+ +-------------+ eMail in | VSERVER1 | | HOMEBOX | +---------->+ MX 1 (Master) | ?SYNC? | DOVECOT | | POSTFIX MTA +--------------> ALL FOLDERS | | DOVECOT INBOX | | | +-----^---------+ +-------------+ | |eMail Backup | | +------+---------+ | VSERVER2 | eMail in | MX 2 (Backup) | Backup | POSTFIX MTA | +---------> | +----------------+ I read into documentation and also did a fair share of googeling but I could only identify possible solutions which I´m not sure they will work. a) dsync - Can dsync only sync the Inbox ? b) fetchmail - Unsure how an eMail moved from Inbox (Homebox) to another folder would get removed from the inbox of the vserver1 Therefore I hope maybe someone of you has an idea how this can be archived. Thank you best regards Dirk

1 0

dovecot-lda won't cause mail to be filtered by sieve
by Volker Wysk 03 Feb '18

03 Feb '18

Hi I'm changing from fetchmail to getmail, in order to fetch my mail from several mail servers and deliver it to my local dovecot server. Fetchmail supports LMTP, getmail doesn't. So I'm making getmail call dovecot-lda for delivering the mail. But now, the incoming mail doesn't get filtered through sieve any longer. However, this command works: sieve-filter -v -u v ~v/.dovecot.sieve INBOX -e -W expunge Any ideas? Greetings V.W.

2 2

AuthDatabase CheckPassword broken?
by Mark Foley 02 Feb '18

02 Feb '18

I had been using the CheckPassword authentication interface with dovecot 2.2.15, https://wiki2.dovecot.org/AuthDatabase/CheckPassword, and it was working. After upgrading to 2.2.33.2 CheckPassword no longer works. The referenced wiki page says, Checkpassword Interface Read <username> NUL <password> NUL from fd 3. I've checked the information read from fd 3 with 2.2.33.2 and I get <username> followed by 3 nulls. I'm guessing the 2nd null is supposed to be the password. Why is this no longer working? How can I fix it? THX --Mark

3 4

Dovecot 2.3 on CentOS 7.
by Reio Remma 02 Feb '18

02 Feb '18

Greetings! I'm having a bit of trouble trying out Dovecot 2.3 on CentOS 7. Dovecot 2.2.33 works fine on the same system (same config as well, minus the SSL changes) but after upgrading to 2.3 I'm getting the following errors: Feb 1 21:30:18 localhost dovecot: imap(reio(a)bwo.mrstuudio.ee)<3566><FoOsnStkXt4KAAgC>: Debug: INBOX.Templates: Mailbox opened because: STATUS Feb 1 21:30:18 localhost dovecot: Error: imap(reio(a)bwo.mrstuudio.ee)<3566><FoOsnStkXt4KAAgC>: open() failed with file /home/dovecot/bwo.mrstuudio.ee/reio/Maildir/.Templates/dovecot.index.log: Read-only file system Feb 1 21:30:18 localhost dovecot: imap(reio(a)bwo.mrstuudio.ee)<3566><FoOsnStkXt4KAAgC>: Error: open(/home/dovecot/bwo.mrstuudio.ee/reio/Maildir/.Templates/dovecot-uidlist.lock) failed: Read-only file system Feb 1 21:30:18 localhost dovecot: Error: imap(reio(a)bwo.mrstuudio.ee)<3566><FoOsnStkXt4KAAgC>: Mailbox INBOX.Templates: file_dotlock_create(/home/dovecot/bwo.mrstuudio.ee/reio/Maildir/.Templates/dovecot-uidlist) failed: Read-only file system Feb 1 21:30:18 localhost dovecot: Error: imap(reio(a)bwo.mrstuudio.ee)<3566><FoOsnStkXt4KAAgC>: Mailbox INBOX.Templates: open(/home/dovecot/bwo.mrstuudio.ee/reio/Maildir/.Templates/dovecot-uidlist) failed: Read-only file system So far I've tried running it with SELinux enforce off and giving the directories 777 permissions to no avail. Is anyone else running 2.3 on CentOS 7? Thanks and good luck! Reio

4 4

Live Import of IMAP
by Sergio Belkin 01 Feb '18

01 Feb '18

Hi, I have the mailbox of jon.doe(a)example.com just migrated only with mails after migration, is it ok to run: doveadm -o mail_fsync=never sync -1 -R -u joe(a)example.com imapc: wiil that import all mails missing mails to the new server? I don't want that delete any current mail, is that right the command above? thanks in advance! -- -- Sergio Belkin LPIC-2 Certified - http://www.lpi.org

2 3

lda: Warning: Failed to parse return-path header: Invalid character in localpart
by Christian Authmann 01 Feb '18

01 Feb '18

Hello, Sometimes, when delivering mails, this warning appears in my syslog: > lda(...): Warning: Failed to parse return-path header: Invalid character in localpart dovecot-lda still exits with 0 and the mail is inserted into my inbox. Looking at the mails in question, I determined that the error is caused by a multiline Return-Path header. Here's a testcase: --- snip --- Return-Path: <nowhere(a)example.com> From: "Nowhere" <nowhere(a)example.com> To: redacted(a)example.com Subject: Testcase for lda warnings Date: Wed, 31 Jan 2018 12:00:00 +0000 This is a message body. --- snap --- Copy into a file, with \r\n line endings, then run something like this: > cat testcase.txt | /usr/lib/dovecot/dovecot-lda -e -d '<username>' with a username recognized by your running dovecot installation. The header is 'Return-Path:', \r\n, two spaces, '<...>', \r\n According to rfc2822 folding rules, that should be valid - the Return-Path header allows CFWS at that location. The error message originates in lib-lda/mail-deliver.c in mail_deliver_get_return_address(), while the invalid character message seems to originate from one of several places in lib-lda/mail-deliver.c Ciao, Christian Authmann

2 4

Error in virtual mailbox dovecot 2.3-devel maybe in mailcount
by Jakobus Schürz 01 Feb '18

01 Feb '18

Hi there! I splitted my Mailarchiv to an extra namespace. Because i have some Problems with the Archiv. I can open all Folders from Mailarchiv with dovecot. But i want to have a "all archives" Mailbox to search in all messages in only one virtual mailbox. Trying to open this virtual folder from thunderbird, I get in a big archiv this error in logs from dovecot: Jän 12 10:54:41 aldebaran dovecot[839]: imap(jakob)<11302><9ILYQJFipPlcPAkS>: Error: virtual index /var/mail/virtual/ARCHIV: Broken mailbox_count header Jän 12 10:54:41 aldebaran dovecot[839]: imap(jakob)<11302><9ILYQJFipPlcPAkS>: Error: virtual index /var/mail/virtual/ARCHIV: Broken mailbox_count header Jän 12 10:54:41 aldebaran dovecot[839]: imap(jakob)<11302><9ILYQJFipPlcPAkS>: Panic: Leaked view for index /var/lib/dovecot/db/indexes/archiv/jakob/Archiv/2016/Mailinglisten/stvkr-a/dovecot.index: Opened in index-storage.c:336 Jän 12 10:54:41 aldebaran dovecot[839]: imap(jakob)<11302><9ILYQJFipPlcPAkS>: Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0xc6021) [0x7f391bf02021] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xc60ed) [0x7f391bf020ed] -> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f391be74481] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0xf3942) [0x7f391c2a1942] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(index_storage_mailbox_close+0x72) [0x7f391c278ec2] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_close+0x1a) [0x7f391c1f8c0a] -> /usr/local/lib/dovecot/lib20_virtual_plugin.so(+0xa7e0) [0x7f39174637e0] -> /usr/local/lib/dovecot/lib20_virtual_plugin.so(virtual_backend_box_open+0x2b) [0x7f391746397b] -> /usr/local/lib/dovecot/lib20_virtual_plugin.so(virtual_storage_sync_init+0x1026) [0x7f3917466926] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x4d) [0x7f391c1fb05d] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x37) [0x7f391c1fb117] -> dovecot/imap [jakob 92.60.9.18 select](cmd_select_full+0x171) [0x55759e0911a1] -> dovecot/imap [jakob 92.60.9.18 select](command_exec+0x64) [0x55759e098ca4] -> dovecot/imap [jakob 92.60.9.18 select](+0x1b0b2) [0x55759e0970b2] -> dovecot/imap [jakob 92.60.9.18 select](+0x1b13c) [0x55759e09713c] -> dovecot/imap [jakob 92.60.9.18 select](client_handle_input+0x1a5) [0x55759e097565] -> dovecot/imap [jakob 92.60.9.18 select](client_input+0x82) [0x55759e097be2] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7f391bf19c09] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x109) [0x7f391bf1b4a9] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x52) [0x7f391bf19d12] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f391bf19f28] -> /usr/local/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f391be971e3] -> dovecot/imap [jakob 92.60.9.18 select](main+0x328) [0x55759e089768] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7f391babd2b1] -> dovecot/imap [jakob 92.60.9.18 select](_start+0x2a) [0x55759e08994a] Jän 12 10:54:41 aldebaran dovecot[839]: imap(jakob)<11302><9ILYQJFipPlcPAkS>: Fatal: master: service(imap): child 11302 killed with signal 6 (core not dumped) and if i search the virtual mailbox with doveadm i get almost the same error. The "Broken mailbox_count_header" is missing there. The full amount of emails in archiv is about 28000 # ulimit -n 256000 # doveadm search -u jakob mailbox Real/Archiv all doveadm(jakob): Panic: Leaked view for index /var/lib/dovecot/db/indexes/archiv/jakob/Archiv/2016/Diverses/Standard-foren/dovecot.index: Opened in index-storage.c:336 doveadm(jakob): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0xc6021) [0x7f8259fe6021] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xc6079) [0x7f8259fe6079] -> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f8259f58481] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0xf3942) [0x7f825a385942] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(index_storage_mailbox_close+0x72) [0x7f825a35cec2] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_close+0x1a) [0x7f825a2dcc0a] -> /usr/local/lib/dovecot/lib20_virtual_plugin.so(+0xa7e0) [0x7f82559507e0] -> /usr/local/lib/dovecot/lib20_virtual_plugin.so(virtual_backend_box_open+0x2b) [0x7f825595097b] -> /usr/local/lib/dovecot/lib20_virtual_plugin.so(virtual_storage_sync_init+0x1026) [0x7f8255953926] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x4d) [0x7f825a2df05d] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x37) [0x7f825a2df117] -> doveadm(doveadm_mail_iter_init+0x94) [0x56303334be94] -> doveadm(+0x33715) [0x56303334f715] -> doveadm(+0x29a88) [0x563033345a88] -> doveadm(+0x2a702) [0x563033346702] -> doveadm(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x230) [0x563033347570] -> doveadm(doveadm_cmd_run_ver2+0x575) [0x563033357155] -> doveadm(doveadm_cmd_try_run_ver2+0x37) [0x5630333571a7] -> doveadm(main+0x1d2) [0x5630333360c2] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7f8259ba12b1] -> doveadm(_start+0x2a) [0x5630333364ca] Abgebrochen Thanks Jakob

1 1

Why does dovecot reject password when authorizing by a certificate?
by yuryb 01 Feb '18

01 Feb '18

We have FreeBSD-server with dovecot installed on it as IMAP-server. My user and password database is a text file with plaintext passwords. Clients connect to imap-server via TLS protocol and plaintext password. All works fine. But I want to configure ability to authorize with a client certificates. I have generated a client certificate and imported it to email-client. Also I have configured dovecot to verify client certificates. But email-client cannot authorize: Password mismatch. Why dovecot reject my password in this case? Please help! My log:dovecot: imap-login: Valid certificate: /C=UA/ST=Kyiv/L=Kyiv/O=Contoso Ltd: user=<>, rip=10.1.1.59, lip=10.1.1.99, TLS handshaking, session=<fp5P5SBkhtMKAQE7> dovecot: imap-login: Valid certificate: /C=UA/ST=Kyiv/O=Contoso Ltd/OU=IT/CN=sysadmin/emailAddress=sysadmin(a)contoso.ua: user=<>, rip=10.1.1.59, lip=10.1.1.99, TLS handshaking, session=<fp5P5SBkhtMKAQE7> dovecot: auth: passwd-file(sysadmin,10.1.1.59,<fp5P5SBkhtMKAQE7>): Password mismatch dovecot: imap-login: Disconnected (auth failed, 1 attempts in 6 secs): user=<sysadmin>, method=EXTERNAL, rip=10.1.1.59, lip=10.1.1.99, TLS, session=<fp5P5SBkhtMKAQE7> My configuration: # 2.2.24 (a82c823): /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 10.2-RELEASE-p20 amd64 ufs auth_debug = yes auth_mechanisms = plain login external auth_ssl_require_client_cert = yes auth_ssl_username_from_cert = yes auth_username_format = %Ln auth_verbose = yes disable_plaintext_auth = no lda_mailbox_autocreate = yes mail_debug = yes mail_gid = 999 mail_location = maildir:/mnt/mail/%n mail_uid = 999 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 = /usr/local/etc/dovecot/users driver = passwd-file } 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 = 0660 user = vmail } } service imap-login { inet_listener imaps { ssl = yes } } ssl_ca = </etc/ssl/cacert.pem ssl_cert = </etc/ssl/certs/dovecot.pem ssl_dh_parameters_length = 2048 ssl_key = </etc/ssl/private/dovecot.pem ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv2 !SSLv3 !TLSv1 ssl_require_crl = no ssl_verify_client_cert = yes userdb { args = /usr/local/etc/dovecot/users driver = passwd-file } verbose_ssl = yes

2 4

test-net.c failure
by Rupert Gallagher 31 Jan '18

31 Jan '18

test-net.c:79: Assert failed: strcmp(net_ip2addr(&ip), "::5") == 0 test-net.c:83: Assert failed: strcmp(net_ip2addr(&ip), "::5") == 0 net_ip2addr() ........................................................ : FAILED Hello, Is it possible to disable DOVECOT_IPV6? We do not use IPv6 (and hope we shall never do on e-mails).

3 3

2.3.0 on 10.13.3 (macos): all testing errors
by Rupert Gallagher 30 Jan '18

30 Jan '18

Enclosed.

1 0

send specific NDR message for users in certain OU
by lists 30 Jan '18

30 Jan '18

Hi, The question can perhaps be made more generic like this: Can dovecot generate a *specific* NDR (or an autoreply) for accounts that meet a specific criterium, such as: - user account was found under OU=to-delete,CN=company... contrary to the regular location CN=Users,CN=company... We would like to move to-be-deleted users to this container, before actually deleting them. That gives us an easy way to revert, if the deletion turns out to be erroneous. We could do that with via a sieve config for those accounts, but if dovecot could send a "delivery failure"-type specific for those accounts (with instructions who to contact to revert the situation) it would be very easy: only move the user to the specific OU, and have the system do the rest. Can this be done? (dovecot 2.1.17 on wheezy, yes we know we should upgrade, and we also will, but it runs rock solid...) MJ

2 2

2 panics, 1 segmentation fault in dovecot 2.3.0 (fts)
by Infoomatic 30 Jan '18

30 Jan '18

Hi, While testing our migration to dovecot 2.3.0, we encountered 2 panics, 1 segmentation fault while we wanted to rebuild the solr indizes. Problem [1] was encountered while rebuilding the indizes, and now I don't know how many mails/documents are indexed or where it got stuck. [2] and [3] encountered while just playing around, since I did not know of "tokenize" and did not find a lot of information about it. This is a ubuntu 16.04 machine, dovecot 2.3.0 compiled from source ( + the patch for the recent zlib problem). "doveadm index" runs on a ~ 4GB mdbox-zipped-mailbox for about 3-4 minutes before aborting with the message above, beforehand I did a "/opt/dovecot/bin/doveadm fts rescan -A". When I repeat "doveadm index" it aborts after about 4 seconds, after a "/opt/dovecot/bin/doveadm fts rescan -A" it runs again for 3-4 minutes. Apache tika logs, but those are probably not related to the problem, however, the devs might want investigate the last line: WARN Parse exception Expected ';', got "," determining content disposition javax.mail.internet.ParseException: Expected ';', got "," and org.apache.tika.exception.ZeroByteFileException: InputStream must have > 0 bytes I would be happy if you could have a look at this, please, and of course just tell me what further information you need. Thanks, infoomatic [1] /opt/dovecot/bin/doveadm index -u user1 '*' doveadm(user1): Panic: file unichar.c: line 160 (uni_ucs4_to_utf8_c): assertion failed: (uni_is_valid_ucs4(chr)) doveadm(user1): Error: Raw backtrace: /opt/dovecot/lib/dovecot/libdovecot.so.0(+0xc5eea) [0x7ff27755beea] -> /opt/dovecot/lib/dovecot/libdovecot.so.0(+0xc5f59) [0x7ff27755bf59] -> /opt/dovecot/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7ff2774ce5e1] -> /opt/dovecot/lib/dovecot/libdovecot.so.0(uni_ucs4_to_utf8_c+0xa0) [0x7ff277593300] -> /opt/dovecot/lib/dovecot/libdovecot.so.0(+0xa74f9) [0x7ff27753d4f9] -> /opt/dovecot/lib/dovecot/libdovecot.so.0(mail_html2text_more+0xc5) [0x7ff27753d705] -> /opt/dovecot/lib/dovecot/lib20_fts_plugin.so(+0xcf5c) [0x7ff276460f5c] -> /opt/dovecot/lib/dovecot/lib20_fts_plugin.so(fts_parser_more+0x27) [0x7ff276460c37] -> /opt/dovecot/lib/dovecot/lib20_fts_plugin.so(fts_build_mail+0x511) [0x7ff27645eb51] -> /opt/dovecot/lib/dovecot/lib20_fts_plugin.so(+0x110a6) [0x7ff2764650a6] -> /opt/dovecot/lib/dovecot/libdovecot-storage.so.0(mail_precache+0x2e) [0x7ff27784618e] -> /opt/dovecot/bin/doveadm(+0x2f697) [0x55dd2f912697] -> /opt/dovecot/bin/doveadm(+0x29827) [0x55dd2f90c827] -> /opt/dovecot/bin/doveadm(+0x2a4bb) [0x55dd2f90d4bb] -> /opt/dovecot/bin/doveadm(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x21d) [0x55dd2f90e2cd] -> /opt/dovecot/bin/doveadm(doveadm_cmd_run_ver2+0x575) [0x55dd2f91deb5] -> /opt/dovecot/bin/doveadm(doveadm_cmd_try_run_ver2+0x37) [0x55dd2f91df07] -> /opt/dovecot/bin/doveadm(main+0x1d2) [0x55dd2f8fd032] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7ff2770ec830] -> /opt/dovecot/bin/doveadm(_start+0x29) [0x55dd2f8fd439] Aborted (core dumped) [2] This was just about my curiosity since I haven't used "tokenize" and did not find too much info about it: /opt/dovecot/bin/doveadm fts tokenize -A '*' Panic: file doveadm-print.c: line 142: unreached Error: Raw backtrace: /opt/dovecot/lib/dovecot/libdovecot.so.0(+0xc5eea) [0x7f38ac5c2eea] -> /opt/dovecot/lib/dovecot/libdovecot.so.0(+0xc5f59) [0x7f38ac5c2f59] -> /opt/dovecot/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f38ac5355e1] -> /opt/dovecot/bin/doveadm(+0x3b3d3) [0x55c728e8b3d3] -> /opt/dovecot/bin/doveadm(+0x2a63a) [0x55c728e7a63a] -> /opt/dovecot/bin/doveadm(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x21d) [0x55c728e7b2cd] -> /opt/dovecot/bin/doveadm(doveadm_cmd_run_ver2+0x575) [0x55c728e8aeb5] -> /opt/dovecot/bin/doveadm(doveadm_cmd_try_run_ver2+0x37) [0x55c728e8af07] -> /opt/dovecot/bin/doveadm(main+0x1d2) [0x55c728e6a032] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f38ac153830] -> /opt/dovecot/bin/doveadm(_start+0x29) [0x55c728e6a439] Aborted (core dumped) [3] /opt/dovecot/bin/doveadm fts tokenize -u user1 "@" Segmentation fault (core dumped)

2 2

Dovecot 2.2.33.2 doveadm log reopen don't work
by Айхэд 30 Jan '18

30 Jan '18

dovecot -n # 2.2.33.2 (d6601f4ec): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) # OS: FreeBSD 11.1-RELEASE-p1 amd64 zfs from logrotate.conf: /var/log/dovecot/dovecot.log { rotate 180 missingok nomail noolddir compress create 0600 nobody nobody postrotate # /usr/local/bin/doveadm log reopen /usr/sbin/service dovecot reload endscript } After upgrade to 2.2.33.2 (prev version was 2.2.29.1) there are only messages from sieve in /var/log/dovecot/dovecot.log like this: Jan 29 00:00:12 lda(***): Info: sieve: msgid=<20180128210012.3A9A11138B8E@***>: stored mail into mailbox 'INBOX.' (INBOX) Messages from pop3, pop3-login, imap, imap-login are absent. If i replace /usr/local/bin/doveadm log reopen with /usr/sbin/service dovecot reload all works fine. Before upgrade all worked fine.

1 0

Change destination of dsync
by Sergio Belkin 29 Jan '18

29 Jan '18

Hi, I have the following command for retrieving mails from another IMAP mail server dsync -D -v backup -R -u jon.doe imapc: I't ok and works, but I'd want to copy messages outside of /var directory, is there a way to do that? Thanks in advance! -- -- Sergio Belkin LPIC-2 Certified - http://www.lpi.org

2 1

problem with lda
by Infoomatic 27 Jan '18

27 Jan '18

Hello, I am currently testing the upgrade from our dovecot v2.2.23 to 2.3.0. I have a strange problem with lda. We use bounce mails for internal users if they try to send virus/spammails. The exact same config works with 2.2.23, but not with 2.3.0. The relevant postfix/master.cf part: dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/opt/dovecot/libexec/dovecot/deliver -d ${recipient} -f ${sender} On the same machine, with 2.2.23 I get a bounce mail when trying to send a virus, with the subject "VIRUS in message apparently from you (Eicar-Test-Signature)", to both the users inbox as well as to the mailbox of virusalert(a)ourdomain.internal With 2.3.0, in the logs I get an error: relay=dovecot, delay=0.01, delays=0/0/0/0, dsn=5.3.0, status=bounced (command line usage error. Command output: lda: Fatal: Invalid -f parameter: Missing domain and the alert message is only sent to virusalert(a)ourdomain.internal, but not to the user who tried to send the mail. The relevant part of our dovecot.conf: protocol lda { mail_plugins = " quota zlib sieve acl mail_log notify" postmaster_address = postmaster(a)ourdomain.internal } Does anyone know how to solve this problem? Or is there a workaround via postfix/amavis/spamassassin? Any hints are highly appreciated, thanks! Regards, infoomatic

3 6

Send full X.509 client certificate to custom authentication policy server
by Jaime Hablutzel Egoavil 26 Jan '18

26 Jan '18

I'm working with Dovecot 2.3 and I'm wondering if I could send the full X.509 client certificate to my custom authentication policy server. I'm actually aware that I can send the client certificate validity status with something like: auth_policy_request_attributes = ... cert=%{cert} But I want the full X.509 certificate to be able to decide over the basis of certificate extensions, e.g. Certificate Policies extension. Is it currently possible?, what about Lua based authentication?, does Lua currently receive the full client certificate?. -- Jaime Hablutzel - RPC 994690880

2 1

exited on signal 6 (core dumped) when searching folder
by Kristjan Eentsalu 26 Jan '18

26 Jan '18

Hey, I'm getting messages exited on signal 6 (core dumped) when doing imap command "a UID SORT (DATE) UTF-8 BODY someword" message log file Jan 26 13:57:20 mail dovecot: imap(kristjan.eentsalu(a)yyy.yy): Panic: file charset-iconv.c: line 87 (charset_to_utf8_try): assertion failed: (srcleft <= CHARSET_MAX_PENDING_BUF_SIZE) Jan 26 13:57:20 mail dovecot: imap(kristjan.eentsalu(a)yyy.yy): Fatal: master: service(imap): child 6410 killed with signal 6 (core dumped) Problem seems to to be with one old mail. OS: FreeBSD 11.1-RELEASE-p4 Dovecot 2.2.33.2 , pigenhole 0.4.21 trace, conf and email available https://pastebin.com/7X6fZPPd Kristjan

2 1

disable deflate compression in rawlog files
by Daniel Betz 26 Jan '18

26 Jan '18

Hello list, is there an way to disable the deflate compression ( imap_zlib ) in the rawlog files, e.g. via postlogin script when dovecot.rawlog folder exists ? Rawlog shown at the moment like: 1 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE COMPRESS=DEFLATE QUOTA] Logged in * NAMESPACE (("INBOX." ".")) NIL NIL 2 OK Namespace completed (0.001 + 0.000 secs). 3 OK Begin compression (0.001 + 0.000 secs). <D2>R<F0>tQ<D0>P<CA>K<CC>MURPr<C9>/KM<CE>/........ Regards, Daniel Betz System Design Engineer / Senior Systemadministration ___________________________________ domainfactory GmbH Oskar-Messter-Str. 33 85737 Ismaning Germany Telefon: +49 (0)89 / 55266-364 Telefax: +49 (0)89 / 55266-222 E-Mail: dbetz(a)df.eu Internet: www.df.eu Registergericht: Amtsgericht München HRB-Nummer 150294, Geschäftsführer: Dr. Claus Boyens, Tobias Mohr

1 0