- dovecot - dovecot.org

Panic: file-lock.c
by Ricardo Branco 19 Dec '17

19 Dec '17

Today we had an unclean shutdown of our NFS filler and have had lots of issues with mailboxes being re-synced, mostly all the issues are now resolved but we are seeing the following appear for one user on our system. Dec 19 16:15:29 imap(xxx.xxx@xxx.com)(xxx.xxx@xxx.com): Panic: file file-lock.c: line 287: unreached Dec 19 16:15:29 imap(xxx.xxx@xxx.com)(xxx.xxx@xxx.com): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x9ceda) [0x7f2b45209eda] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x9cf46) [0x7f2b45209f46] -> /usr/local/lib/dovecot/libdovecot.so.0(i_error+0) [0x7f2b4519cc5f] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xa150a) [0x7f2b4520e50a] -> /usr/local/lib/dovecot/libdovecot.so.0(file_wait_lock_error+0x39) [0x7f2b4520e789] -> /usr/local/lib/dovecot/libdovecot.so.0(file_try_lock_error+0x13) [0x7f2b4520e873] -> /usr/local/lib/dovecot/libdovecot.so.0(file_create_locked+0x29e) [0x7f2b4520b7de] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_lock_file_create+0x125) [0x7f2b454dc345] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0xba1fd) [0x7f2b4554f1fd] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(index_mailbox_vsize_update_appends+0x63) [0x7f2b4554f363] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(index_mailbox_sync_deinit+0x197) [0x7f2b4555c327] -> /usr/local/lib/dovecot/lib20_fts_plugin.so(+0xebd1) [0x7f2b4416bbd1] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_deinit+0x30) [0x7f2b454de750] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x3b) [0x7f2b454e0b4b] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(index_storage_get_status+0x62) [0x7f2b45558402] -> /usr/local/lib/dovecot/lib20_fts_plugin.so(+0xfbf4) [0x7f2b4416cbf4] -> /usr/local/lib/dovecot/lib01_acl_plugin.so(+0xe564) [0x7f2b445aa564] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_get_status+0x8c) [0x7f2b454e05cc] -> dovecot/imap(imap_status_get+0x7a) [0x42222a] -> dovecot/imap(cmd_status+0x15d) [0x41514d] -> dovecot/imap(command_exec+0x5d) [0x41a7fd] -> dovecot/imap() [0x417fb0] -> dovecot/imap() [0x418046] -> dovecot/imap(client_handle_input+0x165) [0x418385] -> dovecot/imap(client_input+0x6f) [0x41882f] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x61) [0x7f2b4521db71] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xbf) [0x7f2b4521f75f] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x3c) [0x7f2b4521dc2c] Dec 19 16:15:29 imap(xxx.xxx@xxx.com)(xxx.xxx@xxx.com): Fatal: master: service(imap): child 30620 killed with signal 6 (core dumps disabled)

1 0

Released Pigeonhole v0.5.0.rc1 for Dovecot v2.3.0.rc1.
by Stephan Bosch 19 Dec '17

19 Dec '17

Hello Dovecot users, Here is the Pigeonhole release candidate that goes with the Dovecot v2.3 release candidate. Of course, a large part of this release consists of compatibility changes for Dovecot v2.3. Apart from that, not much changed, just a few additions and fixes that accumulated over the last few months. Most of these changes will be back-ported to Pigeonhole v0.4, but that release will happen a little later. Changelog v0.5.0: * editheader extension: The implementation of header modifications is heavily updated. Although the functionality has not changed, the underlying code was updated to address several static analysis warnings, runtime integer arithmetic warnings (Clang), and to match updates in the Dovecot stream API. + variables extension: Made the maximum scope and variable size configurable. + subaddress: Support multiple recipient_delimiters. - enotify extension: mailto method: Fixed parsing of mailto URI with only a header part. - enotify plugin: mailto method: Make sure the "From:" header is set to a usable address and not "(null)". - Fixed writing address headers to outgoing messages. Sometimes headers were MIME-encoded twice, yielding invalid results. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.3/rc/dovecot-2.3-pigeonhole-0.5.0.… http://pigeonhole.dovecot.org/releases/2.3/rc/dovecot-2.3-pigeonhole-0.5.0.… Refer to http://pigeonhole.dovecot.org and the Dovecot wiki for more information. Have fun testing this release candidate and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

3 3

nfs_flush_chown_uid errors over NFS
by Johan Hendriks 18 Dec '17

18 Dec '17

Hello all, We use an older version of dovecot 2.0.19 on Ubuntu 12.04 using an NFS share, also a linux box. Now we want to migrate the storage to a FreeBSD server and later on the mailservers them self. In the firsts test all looks fine, but we do see some errors some times. Error: nfs_flush_chown_uid: chown(/var/mail/virtual/domain.com/user/Maildir) failed: Invalid argument This does not happen all the time but sometimes it shows up. I can read all the mail using an mailclient and the uid shows the user vmail:vmail. Is this cosmetic or is there something wrong? Thanks for your time Regards johan

1 0

Sieve with LDA
by Doug Hardie 18 Dec '17

18 Dec '17

I found an email that sieve stored in Deleted Messages incorrectly. The log messages show sieve doing that, but don't give me any indication of which sieve rule caused the problem. I went through it manually, but didn't see anything that matched. I seem to recall that there was a way to use sieve-test to show the rules and how they were applied, but I can't seem to get it to do that now. -- Doug

3 4

ot: 2.2 ghettoforge install systemctl Q
by voytek＠sbt.net.au 16 Dec '17

16 Dec '17

I've installed new Centos 7 with Dovecot 2.2 from ghettoforge and, used /etc/dovecot from current Centos 6 Dovecot 2.1 I can start/stop Dovecot with dovecot / doveadm stop BUT when I tried 'systemctl' I get # systemctl status dovecot ● dovecot.service - Dovecot IMAP/POP3 email server Loaded: loaded (/usr/lib/systemd/system/dovecot.service; disabled; vendor preset: disabled) Active: inactive (dead) Docs: man:dovecot(1) http://wiki2.dovecot.org/ how do I fix this, or, do I need to fix it ? or maybe I need to pursue this on ghettoforge list

3 3

2.1 to 2.2 server migration Qs: sanity check, config ?
by voytek＠sbt.net.au 16 Dec '17

16 Dec '17

I have an old Centos 6 running dovecot 2.1.17 with Postfix 2.1x, mysql virtual domains, in the process of setting a new Centos 7 to migrate, copied /etc/dovecot, made some minor edits to get rid of errors, added Letsencrypt in place of self certified certs, it seems to work, using mail client I can log on StartSSL/110/143, TLS/995/993 with no visible errors when login on is there any other sanity checks I should do ? before I start putting users on it ? attaching dovecot.conf at the end, appreciate any suggestion or correction I see a lot of these warning, are they benign? #grep Warning /var/log/dovecot.log | wc 74 1102 6900 # wc /var/log/dovecot.log 174 2299 19716 /var/log/dovecot.log Dec 16 00:57:12 auth: Warning: auth client 0 disconnected with 1 pending requests: Connection reset by peer Dec 16 00:57:52 auth: Warning: auth client 0 disconnected with 1 pending requests: EOF Dec 16 00:57:59 auth: Warning: auth client 0 disconnected with 1 pending requests: Connection reset by peer ( as I've re used an old host name, I can see some users already trying to connect, they must've never removed this server name when it was shut down, perhaps they're generating these errors, repeatedly logging on ?) # doveadm who username # proto (pids) (ips) five(a)aaa.com.au 1 imap (9047) (35.196.255.170) seven(a)aaa.com.au 1 imap (9056) (104.196.21.108) eight(a)aaa.com.au 1 imap (9062) (35.196.255.170) five(a)aa.com.au 2 imap (9240 9044) (203.194.43.48 35.196.255.170) six(a)aa.com.au 2 imap (9248 9063) (203.194.43.48 35.185.44.87) postbox(a)aa.com.au 1 imap (9057) (104.196.178.232) eight(a)aa.com.au 2 imap (9244 9050) (203.194.43.48 35.196.255.170) seven(a)aa.com.au 2 imap (9055 9242) (104.196.21.108 203.194.43.48) six(a)aaa.com.au 1 imap (9054) (35.185.44.87) doveconf -n -c /etc/dovecot/test/dovecot.conf > /etc/dovecot/test/dovecot.conf.new # cat dovecot.conf.new # 2.2.33.2 (d6601f4ec): /etc/dovecot/test/dovecot.conf # Pigeonhole version 0.4.21 (92477967) # OS: Linux 3.10.0-693.11.1.el7.x86_64 x86_64 CentOS Linux release 7.4.1708 (Core) auth_master_user_separator = * auth_mechanisms = PLAIN LOGIN dict { acl = mysql:/etc/dovecot/dovecot-share-folder.conf quotadict = mysql:/etc/dovecot/dovecot-used-quota.conf } first_valid_uid = 2000 last_valid_uid = 2000 listen = * log_path = /var/log/dovecot.log mail_gid = 2000 mail_location = maildir:/%Lh/Maildir/:INDEX=/%Lh/Maildir/ mail_plugins = quota mail_uid = 2000 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 = yes location = prefix = separator = / type = private } namespace { list = children location = maildir:/%%Lh/Maildir/:INDEX=/%%Lh/Maildir/Shared/%%u prefix = Shared/%%u/ separator = / subscriptions = yes type = shared } passdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } passdb { args = /etc/dovecot/dovecot-master-users-password driver = passwd-file master = yes } plugin { acl = vfile acl_shared_dict = proxy::acl auth_socket_path = /var/run/dovecot/auth-master autocreate = INBOX autocreate2 = Sent autocreate3 = Trash autocreate4 = Drafts autocreate5 = Junk autosubscribe = INBOX autosubscribe2 = Sent autosubscribe3 = Trash autosubscribe4 = Drafts autosubscribe5 = Junk quota = dict:user::proxy::quotadict quota_rule = *:storage=1G quota_warning = storage=85%% quota-warning 85 %u quota_warning2 = storage=90%% quota-warning 90 %u quota_warning3 = storage=95%% quota-warning 95 %u sieve = /%Lh/sieve/dovecot.sieve sieve_dir = /%Lh/sieve sieve_global_dir = /var/vmail/sieve sieve_global_path = /var/vmail/sieve/dovecot.sieve } protocols = pop3 imap sieve service auth { unix_listener /var/spool/postfix/dovecot-auth { group = postfix mode = 0666 user = postfix } unix_listener auth-master { group = vmail mode = 0666 user = vmail } unix_listener auth-userdb { group = vmail mode = 0660 user = vmail } } service dict { unix_listener dict { group = vmail mode = 0660 user = vmail } } service imap-login { process_limit = 500 service_count = 1 } service pop3-login { service_count = 1 } service quota-warning { executable = script /usr/local/bin/dovecot-quota-warning.sh unix_listener quota-warning { group = vmail mode = 0660 user = vmail } } ssl = required ssl_cert = </etc/letsencrypt/..fullchain.pem ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } protocol lda { auth_socket_path = /var/run/dovecot/auth-master lda_mailbox_autocreate = yes log_path = /var/log/sieve.log mail_plugins = quota sieve autocreate postmaster_address = root } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep mail_max_userip_connections = 60 mail_plugins = quota imap_quota } protocol pop3 { mail_plugins = quota pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv } #

2 3

Dovecot path separator clarification
by Davide Marchi 15 Dec '17

15 Dec '17

Hi Friends, On Debian Jessie and Dovecot 1:2.2.x using the default separator "/" (simply leave commented 10-mail.conf -> "#separator =") I've create for a vuser (from client) a subfolder Scuola/prova on server side, Dovecot create: ../Maildir/.Scuola.prova Here my question: why not ../Maildir/Scuola/prova ? Where I'm wrong? Many thanks! Davide

2 1

Re: sieve filter move wrong email to Junk folder
by Richard 15 Dec '17

15 Dec '17

> Date: Thursday, December 14, 2017 09:47:44 -0800 > From: Gao <gao(a)pztop.com> > > I use a sieve filter to move spam email to user's Junk folder: ># cat spam_to_junk.sieve > require "fileinto"; > if exists "X-Spam-Status" { > if header :contains "X-Spam-Status" "YES" { > fileinto "Junk"; > stop; > } else { > } > } > if header :contains "subject" ["SPAM?"] { > fileinto "Junk"; > stop; > } > > Most time this filter works fine but occasionally it move non-spam > in to Junk folder. Here is an example, this email is from dovecot > mailling list and it end up in my Junk folder. Mailllog and header > here. Would someone help me to figure out what went wrong here? > > Thanks. > > Gao > > X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 Because of the way you are bounding it, I suspect that the "YES" in BAYES_00, at the end of that line, is triggering the mis-filing. Why not make: contains "X-Spam-Status" "YES" a single string: contains "X-Spam-Status: YES" that would be more precise and avoid this issue.

5 7

Re: Recommended tool for migrating IMAP servers
by Davide Marchi 15 Dec '17

15 Dec '17

Sami Ketola wrote:> We run all our migrations using Dovecot internal dsync. Usually using imapc connector to connect to legacy > platform. > > Wqmi Many thanks Wqmi! Well, I've read the dsync documentation, but this warning has me a little worried: "Make sure destination is exactly as source, deleting/reverting any changes in destination if necessary" So I followed the Imapsync way, and all works fine. I seem to have understood thatImapsync works as a traditional client,for this reason also much easier to use and with less mistakes risk. And anyway a software done very well ;-) x9p wrote:> I do not believe imapsync has license issues. Its written in perl and its > hosted on github. You can pay for support if you want. and disable > stats > uploaded to their servers, via command line. Well, clear, many thanks x9p! Many thanks to all! Davide -- cosmogoniA cosmogoniA<https://www.cosmogonia.org/> n o p r o v a r e n o f a r e o n o n f a r e n o n c e p r o v a r e

2 2

Re: Mail-crypt plugin clarification
by Joseph Tam 15 Dec '17

15 Dec '17

Aki Tuomi writes: > Dovecot does support making it difficult to prevent access to the stored > mail. Those who have had problems understanding the documentation might find this unintended double-negative ironically funny. > You can, with suitable workflows, ensure that the user's emails are not > readable by anyone but the user. Of course the only way to be fully > sure is to use end-to-end encryption, ... "Ensure" (or OP: "impossible") are very high standards of privacy. If the OP really means it, then since a third party has control over the (virtual or real) hardware, the server should never have access to private keys or decrypted data. (We're in agreement I think.) If the OP lowers their standards to "inconvenient" to gain access, then the plugin is enough. It will keep the honest admin honest. > ... like PGP or S/MIME, but this does go a long way to prevent admin access > to user's email. Don't ignore metadata; who/when/where (and headers?) could reveal much information. Joseph Tam <jtam.home(a)gmail.com>

2 1