February 2017 - dovecot

Setting up replication - First steps...
by SH Development 16 Oct '17

16 Oct '17

Just had my first (non-Dovecot) server failure due to dried out caps on the motherboard. Got me to thinking about my single-point-of-failure mail server. Currently running Dovecot and Postfix with no issues, but want to start taking steps just to be safe. I currently run a filesystem backup every 24 hours to a tar file over NFS to another server in our rack. I am backing up: /home/vmail /etc/dovecot /etc/postfix Unfortunately, the vmail directory has grown to 27GB and takes around 7 hours now to backup as described above. Which leads me to start thinking about how quickly I could restore the server from a backup if need be, and that time is at least 7 hours just to copy and untar the files onto another hard drive. I’m sure I could hook up a HD up directly to the backup server, then I could considerably reduce the time, but I’m making the assumption that I won’t always have quick physical access to the location. So I believe my first step is to set up another server, on another IP, different hostname, with Dovecot and Postfix, and simply use the files from the /etc directories of the existing server to configure it (changing the IP and hostname of course). Am I on the right track so far? Next steps involve setting up replication with dsync? If I have successfully setup replication between the two servers, does this mean users can then actually log into either server and have their “stuff” intact? So I could set up DNS failover in case the primary server fails? Would this make the setup acceptable for secondary MX as everything should sync to the primary server when it comes back online? Sorry for thinking out loud, but I want to make sure I’m understanding the bigger picture here. Jeff

4 3

Quota-status service on Director
by Michael Kliewe 27 Sep '17

27 Sep '17

Hello, I'm trying to configure the quota-status service, but it seems I'm not successful with my director setup (2.2.9). I activate the quota-status service like this on my director server: $ cat 91-quota-status.conf ## ## Quota-Status configuration. ## # Load Module quota-status and listen on TCP/IP Port for connections. service quota-status { executable = quota-status -p postfix inet_listener { address = 10.0.1.44 port = 12340 } client_limit = 1 } # Plugin configuration. # Return messages for requests by quota status: success, nouser and overquota. plugin { quota_status_success = DUNNO quota_status_nouser = DUNNO quota_status_overquota = "552 5.2.2 Mailbox is over quota" } After restarting the director service I try to query the quota status service: printf "recipient=user(a)domain.de\nsize=100000\n\n" | nc 10.0.1.44 12340 The output is: action=DEFER_IF_PERMIT Invalid user settings. Refer to server log for more information. In the debug log of the director I see this: Feb 23 03:03:09 director01 dovecot: auth: Debug: userdb out: USER 1 user(a)domain.de mail=mdbox:/mnt/data01/domain.de/user/maildir home=/mnt/data01/domain.de/user proxy=Y master=<hidden> pass=<hidden> uid=5000 gid=1 quota_rule=*:storage=60593 quota_rule2=*:messages=100000 Feb 23 03:03:09 director01 dovecot: quota-status(user(a)domain.de): Error: user user(a)domain.de: Initialization failed: Namespace '': mkdir(/mnt/data01/domain.de/user/maildir/mailboxes) failed: Permission denied (euid=5000(vmail) egid=1(daemon) missing +w perm: /mnt, dir owned by 0:0 mode=0755) So the quota status service tries to access the mailbox of the user ON THE DIRECTOR. But the director has not mounted the mailboxes of the users, that's what the backend dovecots are for (proxy=Y). So the quota-status query is not proxied to the dovecot backend server I would assume. Does that mean I have to start the quota-status service on the dovecot backend servers and access it from the Postfix server directly? Currently the Postfixes can only reach the directors, not the backend servers. Is it possible to use the quota-status service on the director? Thanks for any hints and help Michael

3 4

[Dovecot] [PATCH, RFC] add APOP authentication mechanism
by Andrey Panin 14 Aug '17

14 Aug '17

Hello all, this patch add APOP authentication mechanism to dovecot 1.0-test23. Please take a look. Best regards. -- Andrey Panin | Linux and UNIX system administrator pazke(a)donpac.ru | PGP key: wwwkeys.pgp.net

3 2

Pacaging/build issues with AIX and vac (dovecot-2.2.25)
by Michael Felt 10 Jun '17

10 Jun '17

Hi. I finally decided it was really time to stop being lazy and really move away from gmail. After I have a server in my basement using power, etc. So I turned on the imap provided - and did not quite cry - it will have to do for now, but imap2 is wanting. A real server yes, but not Linux. (Using linux would require another server AND I would feel I am being lazy again). So, I downloaded dovecot-2.2.25 and tried to build. Configure (messages to stderr) xlc is /usr/vacpp/bin/xlc + CPPFLAGS="-I/opt/include -I/opt/buildaix/include" CFLAGS="-I/opt/include -O2 -qmaxmem=-1 -qarch=pwr5 -I/opt/buildaix/includes ./configure\ --prefix=/opt \ --sysconfdir=/var/dovecot/etc\ --sharedstatedir=/var/dovecot/com\ --localstatedir=/var/dovecot\ --mandir=/usr/share/man\ --infodir=/opt/share/info/dovecot \ > .buildaix/configure.out xlc_r: 1501-216 (W) command option -dM is not recognized - passed to ld xlc_r: 1501-228 (W) input file c not found 1506-297 (S) Unable to open input file null. No such file or directory. ./configure[25617]: rpcgen: not found messages to stderr by make: + make > .buildaix/make.out ./update-version.sh[42]: git: not found. "askpass.c", line 59.18: 1506-359 (I) Automatic variable str contains a const member and is not initialized. It will be initia "guid.c", line 113.18: 1506-359 (I) Automatic variable buf contains a const member and is not initialized. It will be initiali "iostream-rawlog.c", line 28.18: 1506-359 (I) Automatic variable buf contains a const member and is not initialized. It will b "istream-base64-decoder.c", line 42.18: 1506-359 (I) Automatic variable buf contains a const member and is not initialized. It "istream-base64-encoder.c", line 47.18: 1506-359 (I) Automatic variable buf contains a const member and is not initialized. It "istream-jsonstr.c", line 70.26: 1506-359 (I) Automatic variable buf contains a const member and is not initialized. It will b "mountpoint.c", line 222.39: 1506-068 (W) Operation between types "char*" and "const char*" is not allowed. "istream-decrypt.c", line 68.18: 1506-359 (I) Automatic variable ephemeral_key contains a const member and is not initialized. "istream-decrypt.c", line 276.18: 1506-359 (I) Automatic variable buf contains a const member and is not initialized. It will "istream-decrypt.c", line 369.26: 1506-359 (I) Automatic variable peer_key contains a const member and is not initialized. It "istream-decrypt.c", line 745.42: 1506-359 (I) Automatic variable db contains a const member and is not initialized. It will b "ostream-encrypt.c", line 135.65: 1506-359 (I) Automatic variable buf contains a const member and is not initialized. It will "ostream-encrypt.c", line 454.18: 1506-359 (I) Automatic variable buf contains a const member and is not initialized. It will "dcrypt-openssl.c", line 787.36: 1506-359 (I) Automatic variable key contains a const member and is not initialized. It will b "dcrypt-openssl.c", line 1099.33: 1506-359 (I) Automatic variable secret contains a const member and is not initialized. It wi "dcrypt-openssl.c", line 1295.18: 1506-359 (I) Automatic variable tmp contains a const member and is not initialized. It will "dcrypt-openssl.c", line 1365.18: 1506-359 (I) Automatic variable saltbuf contains a const member and is not initialized. It w "istream-decrypt.c", line 68.18: 1506-359 (I) Automatic variable ephemeral_key contains a const member and is not initialized. "istream-decrypt.c", line 276.18: 1506-359 (I) Automatic variable buf contains a const member and is not initialized. It will "istream-decrypt.c", line 369.26: 1506-359 (I) Automatic variable peer_key contains a const member and is not initialized. It "istream-decrypt.c", line 745.42: 1506-359 (I) Automatic variable db contains a const member and is not initialized. It will b "ostream-encrypt.c", line 135.65: 1506-359 (I) Automatic variable buf contains a const member and is not initialized. It will "ostream-encrypt.c", line 454.18: 1506-359 (I) Automatic variable buf contains a const member and is not initialized. It will "istream-decrypt.c", line 68.18: 1506-359 (I) Automatic variable ephemeral_key contains a const member and is not initialized. "istream-decrypt.c", line 276.18: 1506-359 (I) Automatic variable buf contains a const member and is not initialized. It will "istream-decrypt.c", line 369.26: 1506-359 (I) Automatic variable peer_key contains a const member and is not initialized. It "istream-decrypt.c", line 745.42: 1506-359 (I) Automatic variable db contains a const member and is not initialized. It will b "ostream-encrypt.c", line 135.65: 1506-359 (I) Automatic variable buf contains a const member and is not initialized. It will "ostream-encrypt.c", line 454.18: 1506-359 (I) Automatic variable buf contains a const member and is not initialized. It will "test-http-auth.c", line 27.27: 1506-022 (S) "scheme" is not a member of "const struct http_auth_challenges_test". "test-http-auth.c", line 27.37: 1506-196 (W) Initialization between types "struct http_auth_challenge_test* const" and "char*" "test-http-auth.c", line 28.33: 1506-022 (S) "data" is not a member of "const struct http_auth_challenges_test". "test-http-auth.c", line 28.41: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 29.33: 1506-022 (S) "params" is not a member of "const struct http_auth_challenges_test". "test-http-auth.c", line 30.43: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 30.52: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 30.70: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 30.76: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 33.33: 1506-022 (S) "scheme" is not a member of "const struct http_auth_challenges_test". "test-http-auth.c", line 33.43: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 43.27: 1506-022 (S) "scheme" is not a member of "const struct http_auth_challenges_test". "test-http-auth.c", line 43.37: 1506-196 (W) Initialization between types "struct http_auth_challenge_test* const" and "char*" "test-http-auth.c", line 44.33: 1506-022 (S) "data" is not a member of "const struct http_auth_challenges_test". "test-http-auth.c", line 44.41: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 45.33: 1506-022 (S) "params" is not a member of "const struct http_auth_challenges_test". "test-http-auth.c", line 46.43: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 46.52: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 47.43: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 47.50: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 48.43: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 48.52: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 49.43: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 49.53: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 50.43: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 50.49: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 53.33: 1506-022 (S) "scheme" is not a member of "const struct http_auth_challenges_test". "test-http-auth.c", line 53.43: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 60.27: 1506-022 (S) "scheme" is not a member of "const struct http_auth_challenges_test". "test-http-auth.c", line 60.37: 1506-196 (W) Initialization between types "struct http_auth_challenge_test* const" and "char*" "test-http-auth.c", line 61.33: 1506-022 (S) "data" is not a member of "const struct http_auth_challenges_test". "test-http-auth.c", line 61.41: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 62.33: 1506-022 (S) "params" is not a member of "const struct http_auth_challenges_test". "test-http-auth.c", line 63.43: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 63.52: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 64.43: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 64.51: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 65.43: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 65.52: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 66.43: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 66.49: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 69.33: 1506-022 (S) "scheme" is not a member of "const struct http_auth_challenges_test". "test-http-auth.c", line 69.43: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 70.33: 1506-022 (S) "data" is not a member of "const struct http_auth_challenges_test". "test-http-auth.c", line 70.41: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 71.33: 1506-022 (S) "params" is not a member of "const struct http_auth_challenges_test". "test-http-auth.c", line 72.43: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 72.52: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 73.43: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 73.49: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 76.33: 1506-022 (S) "scheme" is not a member of "const struct http_auth_challenges_test". "test-http-auth.c", line 76.43: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 187.27: 1506-196 (W) Initialization between types "struct http_auth_param* const" and "char*" is not a "test-http-auth.c", line 187.39: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 188.27: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 188.36: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 189.27: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 189.36: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 190.27: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 190.34: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 191.27: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 191.34: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 192.27: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 192.33: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 193.27: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 193.37: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 194.27: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 194.39: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 195.27: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 195.37: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 196.27: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. "test-http-auth.c", line 196.33: 1506-026 (S) Number of initializers cannot be greater than the number of aggregate members. make: 1254-004 The error code from the last command is 1. I am quite willing to dig and dig - but I want to be know if there will be any interest and/or support for dovecot on AIX. Sincerely, Michael

3 22

[Dovecot] Dovecot stops with "Fatal: kevent(): Invalid argument"
by Henrik Larsson 09 Jun '17

09 Jun '17

# 2.0.11: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 8.2-STABLE amd64 Dovecot stops with the following logged: - master: Fatal: kevent(): Invalid argument I have found that a diff was created for "src/lib/ioloop-kqueue.c" for a similar issue: http://dovecot.org/pipermail/dovecot/2010-November/054855.html I have patched my system with this and haven't seen the problem since, but I don't know if this is a coincidence. Could you please explain if the diff should actually fix anything or just add some more logging in case it stops again? Best regards Henrik Larsson

4 9

Panic: file dsync-brain-mailbox.c: line 814 ...
by Sander Lepik 04 Jun '17

04 Jun '17

Hi! We have 2 servers replicating each other and after upgrade to 2.2.26.0 we are seeing this in the logs: Primary server: Nov 17 09:37:39 mailhost01 dovecot: dsync-server(user(a)domain.ee): Panic: file dsync-brain-mailbox.c: line 814 (dsync_brain_slave_recv_mailbox): assertion failed: (memcmp(dsync_box->mailbox_guid, local_dsync_box.mailbox_guid, sizeof(dsync_box->mailbox_guid)) == 0) Nov 17 09:37:39 mailhost01 dovecot: dsync-server(user(a)domain.ee): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x9438e) [0x7f3ccceb238e] -> /usr/lib/dovecot/libdovecot.so.0(+0x9447c) [0x7f3ccceb247c] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f3ccce4ba4e] -> dovecot/doveadm-server(dsync_brain_slave_recv_mailbox+0x3d8) [0x7f3ccd8f66f8] -> dovecot/doveadm-server(dsync_brain_run+0x650) [0x7f3ccd8f4110] -> dovecot/doveadm-server(+0x4143b) [0x7f3ccd8f443b] -> dovecot/doveadm-server(+0x5735f) [0x7f3ccd90a35f] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x4c) [0x7f3cccec6bdc] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x10a) [0x7f3cccec809a] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7f3cccec6c65] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f3cccec6e08] -> dovecot/doveadm-server(+0x26b99) [0x7f3ccd8d9b99] -> dovecot/doveadm-server(+0x28efc) [0x7f3ccd8dbefc] -> dovecot/doveadm-server(+0x3daba) [0x7f3ccd8f0aba] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x4c) [0x7f3cccec6bdc] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x10a) [0x7f3cccec809a] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7f3cccec6c65] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f3cccec6e08] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f3ccce51f53] -> dovecot/doveadm-server(main+0x19f) [0x7f3ccd8ccdef] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f3ccca94b45] -> dovecot/doveadm-server(+0x19ea6) [0x7f3ccd8ccea6] Nov 17 09:37:39 mailhost01 dovecot: dsync-server(user(a)domain.ee): Fatal: master: service(doveadm): child 42621 killed with signal 6 (core dumps disabled) Secondary server: Nov 17 09:37:40 secondarymailhost01 dovecot: dsync-local(user(a)domain.ee): Error: read(mailhost01.domeen.ee) failed: EOF (last sent=mailbox, last recv=mailbox_state) I'm guessing that it happens during automatic full resync, but that's just guessing. OS is Debian 8 (x86_64) and Dovecot is recompiled from Debian's unstable repository. -- Sander

2 2

Fatal error with IMAP MOVE from a shared mailbox to Trash folder
by Daniele Barresi 30 May '17

30 May '17

Hello everyone. I have a problem using Dovecot 2.2.26 with ACL plugin and deleting e-mails from a shared mailbox. My user doesn't have the "expunge" permission on the shared mailbox, but it has the "write-deleted" permission. So, when I delete a message from the shared mailbox using a client that implements the IMAP MOVE command, it tries to move the message to my Trash folder. Then the server closes the connection to the client (process aborted) and I get three lines in the log file with a backtrace and "Fatal" error. In this case the message doesn't get copied or moved from the shared folder and the client complaints. I found the same thing happens whenever I try to move anything between folders of the shared mailbox itself, while logged in with my user. I can move messages inside my own mailbox just fine. If I try the same operation from a client that uses the IMAP COPY + DELETE commands, no errors are logged and the outcome is as expected: the message gets copied from the shared folder to my Trash and gets the flag "\Deleted" set on the shared folder. My setup is as follows: Dovecot: 2.2.26.0 OS: Ubuntu 16.04.1 LTS CPU architecture: x86_64 Filesystem: ext4 The relevant lines from mail.err log: Dec 27 15:21:18 dovecot dovecot: imap(danielebarresi): Panic: file mail-storage.c: line 2143 (mailbox_save_context_reset): assertion failed: (ctx->copying_via_save) Dec 27 15:21:18 dovecot dovecot: imap(danielebarresi): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x9438e) [0x7fbcd478538e] -> /usr/lib/dovecot/libdovecot.so.0(+0x9447c) [0x7fbcd478547c] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fbcd471ea4e] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x41b78) [0x7fbcd4a50b78] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_save_cancel+0x73) [0x7fbcd4a53d73] -> /usr/lib/dovecot/modules/lib01_acl_plugin.so(+0xe142) [0x7fbcd3f1d142] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x4516d) [0x7fbcd4a5416d] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_move+0x23) [0x7fbcd4a54333] -> dovecot/imap(+0xf9c5) [0x557cf98629c5] -> dovecot/imap(command_exec+0xa6) [0x557cf986f196] -> dovecot/imap(+0x1a4c2) [0x557cf986d4c2] -> dovecot/imap(+0x1a550) [0x557cf986d550] -> dovecot/imap(client_handle_input+0x195) [0x557cf986d915] -> dovecot/imap(client_input+0x85) [0x557cf986de25] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x4c) [0x7fbcd4799bdc] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x10a) [0x7fbcd479b09a] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7fbcd4799c65] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fbcd4799e08] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fbcd4724f53] -> dovecot/imap(main+0x322) [0x557cf9860ca2] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7fbcd4348830] -> dovecot/imap(+0xde1f) [0x557cf9860e1f] Dec 27 15:21:18 dovecot dovecot: imap(danielebarresi): Fatal: master: service(imap): child 6907 killed with signal 6 (core dumped) Dovecot configuration (doveadm -n): # 2.2.26.0 (23d1de6): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.4.0-57-generic x86_64 Ubuntu 16.04.1 LTS auth_cache_negative_ttl = 10 mins auth_cache_size = 2 M auth_master_user_separator = * auth_mechanisms = plain login first_valid_uid = 12 last_valid_uid = 12 mail_location = maildir:~/Maildir mail_plugins = acl quota notify mail_log stats lazy_expunge 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 casellecondivise { list = children location = maildir:%%h/Maildir:INDEXPVT=~/Maildir/shared/%%u prefix = Caselle condivise/%%u/ separator = / subscriptions = no type = shared } namespace expunged { hidden = yes list = no location = maildir:/var/expunged/%n/Expunged prefix = EXPUNGED/ separator = / } namespace inbox { inbox = yes location = mailbox Archive { auto = subscribe special_use = \Archive } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / type = private } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile:/etc/dovecot/global-acls:cache_secs=300 acl_shared_dict = file:/etc/dovecot/shared/shared-mailboxes lazy_expunge = EXPUNGED/ lazy_expunge_only_last_instance = yes mail_log_events = delete copy flag_change save undelete expunge mail_log_fields = uid box msgid size quota = maildir:user quota quota_exceeded_message = (Quota exceeded) La casella di posta elettronica del destinatario è piena. quota_rule = *:storage=1G quota_rule2 = Trash:storage=+100M quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=100%% quota-warning 100 %u sieve = file:~/sieve;active=~/.dovecot.sieve stats_command_min_time = 1 mins stats_domain_min_time = 12 hours stats_ip_min_time = 12 hours stats_memory_limit = 32 M stats_refresh = 30 secs stats_session_min_time = 15 mins stats_track_cmds = yes stats_user_min_time = 1 hours } protocols = " imap sieve" service auth { unix_listener /var/spool/postfix/private/auth { group = mail mode = 0666 user = postfix } unix_listener auth-userdb { group = mail user = mail } } service dict { unix_listener dict { group = mail mode = 0600 user = mail } } service imap-login { process_limit = 300 process_min_avail = 2 } service managesieve-login { inet_listener sieve { port = 4190 } } service quota-warning { executable = script /etc/dovecot/scripts/quota-warning.sh unix_listener quota-warning { group = mail user = mail } } service stats { fifo_listener stats-mail { mode = 0600 user = mail } } ssl = required ssl_cert = </etc/ssl/certs/pac.apg23.org.pem ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-sql.conf.ext default_fields = uid=mail gid=mail home=/var/mail/%u master_user=%u driver = sql } userdb { args = /etc/dovecot/dovecot-ldap.conf.ext default_fields = uid=mail gid=mail home=/var/mail/%u master_user=%u driver = ldap } protocol lda { mail_plugins = acl quota notify mail_log stats lazy_expunge sieve } protocol imap { mail_max_userip_connections = 25 mail_plugins = acl quota notify mail_log stats lazy_expunge imap_quota imap_stats } I tested this with different users with the same result. I tested and reproduced the error with Thunderbird and Roundcube. The Apple Mail client uses IMAP COPY + DELETE, instead of IMAP MOVE, and no errors are reported. So I think it's related to the IMAP MOVE implementation on Dovecot server. Has anyone seen the same error? Any suggestions? Is this a Dovecot bug? --- Daniele Barresi

3 4

Plugin "mail_crypt" - using folder keys
by Evgeniy Korneechev 26 May '17

26 May '17

Hi, i have two questions about using "folder keys" for encryption: 1. If i use this method how can i decrypt files manually? 2. If move a letter to another folder (or remove it), it will be unreadable. Log: imap(cloud): Error: read() failed: read(/home/cloud/Maildir/.Sent.test/cur/1485528498.M838579P2267....) failed: Decryption error: no private key available (uid=5, box=Sent.test, read reason=) imap(cloud): Info: Internal error occurred. Refer to server log for more information. or: imap(cloud): Error: read() failed: read(/home/cloud/Maildir/.Trash/cur/1485528906.M150750P3081....) failed: Decryption error: no private key available How fix it? Thank you in advance. ------------------------------------------------ # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.4.39-std-def-alt0.M80P.1 x86_64 ALT 8.1 Server ..... mail_attribute_dict = file:%h/Maildir/dovecot-attributes mail_plugins = $mail_plugins mail_crypt plugin { mail_crypt_curve = secp521r1 mail_crypt_save_version = 2 } ..... -- WBR, BaseALT/ALTLinux Team

3 10

[Sieve] Is the way to run external script to get attachment?
by Konstantin Shalygin 22 Mar '17

22 Mar '17

Hello. Read all about Extprograms, but have a question. Use case: Every day we have couple messages with attachment (from one sender, this is one-way communication). This attachment is uploads to ownCloud. By hand... need some automation. As I see, pipe cat execute scripts with text data USER/FROM/SUBJECT - and I think with variables it can be any text data, how about attachment? How I see this: script executes and as arg receives from sieve attachment file, or message file and we can parse it for attachment. When we have attachment - upload to ownCloud via RESTapi and purge message. Found some realization for encrypt messages https://github.com/EtiennePerot/gpgit/blob/master/encmaildir.sh but for me more easy just connect to IMAP and do what I want (but I love sieve). Thanks. <http://wiki.dovecot.org/Pigeonhole/Sieve/Plugins/Extprograms>

2 2

Is it possible to use sieve when delivering via pipe to the dovecot deliver command ?
by Thomas Carrié 21 Mar '17

21 Mar '17

Hello, I am using Exim with this delivery configuration: virtual_delivery: driver = pipe command = /usr/lib/dovecot/deliver -d $local_part@$domain -f ... I have enabled manage-sieve and uploaded a simple sieve script that I can see on the server. man page of /usr/lib/dovecot/deliver says it supports sieve. Mail debug is enabled: $ dovecot -n | grep debug mail_debug = yes Delivering a mail shows only this line in dovecot log: Jan 21 17:38:51 myserver dovecot: lda(joe(a)something.com): msgid=<20170121183537.7313f219@homenetwork>: saved mail to INBOX According to page http://wiki2.dovecot.org/Pigeonhole/Sieve/Troubleshooting#Sieve_Scripts_are… I should have a log saying that the sieve plugin is loaded Here is the sieve relevant parts of dovecot -n: # 2.2.13: /etc/dovecot/dovecot.conf ... plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } ... protocols = " imap sieve pop3 sieve" ... protocol lda { mail_plugins = " sieve" } Is there a requirement to use delivery via service (unix socket) so that sieve is enabled? Or is there a configuration thing I forgot ? Thank you for your help Thomas

2 2