- dovecot - dovecot.org

Re: v2.2.33 released
by Aki Tuomi 13 Oct '17

13 Oct '17

try with 2.2.33.1 ---Aki TuomiDovecot oy -------- Original message --------From: Odhiambo Washington <odhiambo(a)gmail.com> Date: 13/10/2017 10:42 (GMT+02:00) To: Dovecot Mailing List <dovecot(a)dovecot.org> Cc: dovecot-news(a)dovecot.org Subject: Re: v2.2.33 released On 10 October 2017 at 18:28, Timo Sirainen <tss(a)iki.fi> wrote: > https://dovecot.org/releases/2.2/dovecot-2.2.33.tar.gz > https://dovecot.org/releases/2.2/dovecot-2.2.33.tar.gz.sig > > We're getting close to the last v2.2.x releases. Hopefully we'll have the > first v2.3 beta releases out soon. > Something is wrong with 2.2.33, but I haven't found time to catch it. I have been running 2.2.32 without issues. I use dovecot-lda with Exim. The moment I installed 2.2.33, it was all failures - mail somehow gets delivered, but a failure too is generated. I have backed off from 2.2.33 for now. Maybe I will find time to debug later. Maybe someone already found a way around, but I missed the post? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft."

2 3

v2.2.33 released
by Timo Sirainen 13 Oct '17

13 Oct '17

https://dovecot.org/releases/2.2/dovecot-2.2.33.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.33.tar.gz.sig We're getting close to the last v2.2.x releases. Hopefully we'll have the first v2.3 beta releases out soon. * doveadm director commands wait for the changes to be visible in the whole ring before they return. This is especially useful in testing. * Environments listed in import_environment setting are now set or preserved when executing standalone commands (e.g. doveadm) + doveadm proxy: Support proxying logs. Previously the logs were visible only in the backend's logs. + Added %{if}, see https://wiki2.dovecot.org/Variables#Conditionals + Added a new notify_status plugin, which can be used to update dict with current status of a mailbox when it changes. See https://wiki2.dovecot.org/Plugins/NotifyStatus + Mailbox list index can be disabled for a namespace by appending ":LISTINDEX=" to location setting. + dsync/imapc: Added dsync_hashed_headers setting to specify which headers are used to match emails. + pop3-migration: Add pop3_migration_ignore_extra_uidls=yes to ignore mails that are visible in POP3 but not IMAP. This could happen if new mails were delivered during the migration run. + pop3-migration: Further improvements to help with Zimbra + pop3-migration: Cache POP3 UIDLs in imapc's dovecot.index.cache if indexes are enabled. These are used to optimize incremental syncs. + cassandra, dict-sql: Use prepared statements if protocol version>3. + auth: Added %{ldap_dn} variable for passdb/userdb ldap - acl: The "create" (k) permission in global acl-file was sometimes ignored, allowing users to create mailboxes when they shouldn't have. - sdbox: Mails were always opened when expunging, unless mail_attachment_fs was explicitly set to empty. - lmtp/doveadm proxy: hostip passdb field was ignored, which caused unnecessary DNS lookups if host field wasn't an IP - lmtp proxy: Fix crash when receiving unexpected reply in RCPT TO - quota_clone: Update also when quota is unlimited (broken in v2.2.31) - mbox, zlib: Fix assert-crash when accessing compressed mbox - doveadm director kick -f parameter didn't work - doveadm director flush <host> resulted flushing all hosts, if <host> wasn't an IP address. - director: Various fixes to handling backend/director changes at abnormal times, especially while ring was unsynced. These could have resulted in crashes, non-optimal behavior or ignoring some of the changes. - director: Use less CPU in imap-login processes when moving/kicking many users. - lmtp: Session IDs were duplicated/confusing with multiple RCPT TOs when lmtp_rcpt_check_quota=yes - doveadm sync -1 fails when local mailboxes exist that do not exist remotely. This commonly happened when lazy_expunge mailbox was autocreated when incremental sync expunged mails. - pop3: rawlog_dir setting didn't work

2 1

Released Pigeonhole v0.4.21 for Dovecot v2.2.33.1.
by Stephan Bosch 13 Oct '17

13 Oct '17

Hello Dovecot users, Here's the definitive 0.4.21 release. There were no changes since the release candidate. Changelog v0.4.21: * redirect action: Always set the X-Sieve-Redirected-From header to sieve_user_email if configured. Before, it would use the envelope recipient instead if available, which makes no sense if the primary e-mail address is available. + vacation extension: Allow ignoring the envelope sender while composing the "To:" header for the reply. Normally, the "To:" header is composed from the address found in the "Sender", "Resent-From" or "From" headers that is equal to the envelope sender. If none is then found, the bare envelope sender is used. This change adds a new setting "sieve_vacation_to_header_ignore_envelope". With this setting enabled, the "To:" header is always composed from those headers in the source message. The new setting thus allows ignoring the envelope, which is useful e.g. when SRS is used. + vacation extension: Compose the "To:" header from the full sender address found in the first "Sender:", "From:" or "Resent-From:" header. Before, it would create a "To:" header without a phrase part. The new behavior is nicer, since the reply will be addressed to the sender by name if possible. - LDA Sieve plugin: Fixed sequential execution of LDAP-based scripts. A missing LDAP-based script could cause the script sequence to exit earlier. - sieve-filter: Removed the (now) duplicate utf8 to mutf7 mailbox name conversion. This caused problems with mailbox names containing UTF-8 characters. The Dovecot API was changed years ago, but apparently sieve-filter was never updated. The release is available as follows: https://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.21.t… https://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.21.t… Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

Solr 7
by Ricardo Branco 12 Oct '17

12 Oct '17

Before I go down the route of upgrading our main Solr instance from 6 to 7, just checking if anyone is using Solr 7 with Dovecot.

4 4

Re: Mail Alias Stores in mySQL Not working - SOLVED
by jason hirsh 12 Oct '17

12 Oct '17

"You have the alias abuse(a)kasdivi.com <mailto:abuse@kasdivi.com> for the address admin(a)theoceanwindow.com <mailto:admin@theoceanwindow.com> in your db and all mail to these aliases should go the the admin@ mailbox. Address mapping should be done in postfix so that the recipient address that gets used on the lmtp connection to dovecot is admin(a)theoceanwindow.com <mailto:admin@theoceanwindow.com> You probably disabled address mapping in postfix. -- Christian Kivalo” You nailed that .. I had completely forgotten about that.. I am changing a system from hash to SQL I actually feel kind of stupid I knew Postfix was supposed to do the acceptance.. and it should have been common sense that it need to rewrite.. The logs kept reminding me I had the following line in master,cf -o receive_override_options=no_address_mappings,no_header_body_checks,no_unknown_recipient_checks changed to -o receive_override_options=no_header_body_checks,no_unknown_recipient_checks and system works great.. Thanls!!

1 0

Re: Mail Alias Stores in mySQL Not working
by jason hirsh 12 Oct '17

12 Oct '17

"So abuse(a)kasdivi.com <mailto:abuse@kasdivi.com> is an alias, not a user.? You can't login with an alias because your user_query is looking at the`mailbox` table. Have your tried logging in as: admin(a)theoceanwindow.com <mailto:admin@theoceanwindow.com> OR you could put an entry forabuse(a)kasdivi.com <mailto:forabuse@kasdivi.com> in your `mailbox` table. Bill” Bill Excuse me I must have some where mi-stated myself. Yes abuse(a)variousdoamns.com is an alias going back to my admin account The issue was iin my master.cf where I had at some time disabled remapping Fixed that and all is good Thanks for your time and effort.. You helped tremendously and actually had me discover some other issues Jason

1 0

Re: Mail Alias Stores in mySQL Not working
by jason hirsh 12 Oct '17

12 Oct '17

3 2

Re: Mail Alias Stores in mySQL Not working
by jason hirsh 12 Oct '17

12 Oct '17

"In an earlier post you said your user_query was: user_query = SELECT CONCAT('/var/vmail/mail/', maildir) AS home, 5000 AS uid, 5000 AS gid, CONCAT('*:bytes=', quota) AS quota_rule FROM mailbox WHERE username = '%u' AND active=?1' Last post you said: mail is stored at /var/mail/vhosts and: mail_location = maildir:/var/mail/vhosts/%d/%n These don't agree with your user_query.” Probably my mis-statement "Run a MySQL query: SELECT `username`, `domain`, `maildir` FROM `mailbox` LIMIT 5; Let's see the value of maildir” mysql> SELECT `username`, `domain`, `maildir` FROM `mailbox` LIMIT 5; +--------------------------+--------------------+---------------------------+ | username | domain | maildir | +--------------------------+--------------------+---------------------------+ | jason(a)theoceanwindow.com | theoceanwindow.com | theoceanwindow.com/jason/ | | admin(a)gcsbonaire.com | gcsbonaire.com | gcsbonaire.com/admin/ | | admin(a)theoceanwindow.com | theoceanwindow.com | theoceanwindow.com/admin/ | | test(a)theoceanwindow.com | theoceanwindow.com | theoceanwindow.com/test/ | | lin(a)grapestreet.com | grapestreet.com | grapestreet.com/lin/ | +--------------------------+--------------------+---------------------------+ 5 rows in set (0.00 sec) "Also, lets see the output of: ls -l /var/mail/vhosts/*” drwxrwxr-x 4 1003 vmail 512 Jun 25 2016 camantonewfashion.com drwxrwxr-x 4 1003 vmail 512 Sep 6 2016 filmusfamily.com drwxrwxr-x 8 1003 vmail 512 Oct 8 13:44 gcs-bonaire.com drwxrwxr-x 4 1003 vmail 512 Oct 5 07:40 gcsbonaire.com drwxrwxr-x 3 1003 vmail 512 Jun 25 2016 grapestreet.com drwxrwxr-x 5 1003 vmail 512 Jun 25 2016 grapestreetgen.com drwxrwxr-x 5 1003 vmail 512 Jun 25 2016 grapestreetvoice.com drwxrwxr-x 11 1003 vmail 512 Oct 11 13:37 kasdivi.com drwx------ 3 1003 vmail 512 Oct 11 13:25 test.com drwxrwxr-x 7 1003 vmail 512 Oct 11 13:42 theoceanwindow.com It seems that the correct information is stored in the correct place but i get dovecot: auth-worker(21961): sql(abuse(a)kasdivi.com): unknown user Its seems like there is a simple config thing I am not getting right Jason

2 1

v2.2.33.1 released
by Timo Sirainen 12 Oct '17

12 Oct '17

https://dovecot.org/releases/2.2/dovecot-2.2.33.1.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.33.1.tar.gz.sig Oops, one a bit too bad bug was left in the release, so fixing it here. - dovecot-lda was logging to stderr instead of to the log file.

2 1

Connection closed reason
by Miloslav Hůla 12 Oct '17

12 Oct '17

Hi, we have one user using the old Alpine client with IMAP. Time to time (3 times per day or 3 times per week) he get error: "MAIL FOLDER INBOX CLOSED DUE TO ACCESS ERROR" and he complains, that inbox stops to refresh with new emails. I don't know Alpine but I can imagine, that Alpine creates TCP connection to IMAPS and uses IDLE. I read wiki page about Timeouts [1] and it seems OK. Alpine is connected 5 or more hours without interrupt. But I found 'Connection closed' at approximate times of user reports in mail.log. Am'I undestand it correctly, that 'Connection closed' is some kind of incorrect connection end? I can find 'Logged out' messages which seems to me as correct ones. I can imagine that such situations may happend for moving clients, such a smartphone with losing signal. But mentioned user is on local network connected by cable. I'm interested, what exactly 'Connection closed' in mail log means. We have following lines in log: dovecot: imap(username): Connection closed in=63 out=288442 dovecot: imap(username): Connection closed (IDLE running for 0.001 + waiting input for 0.001 secs, 2 B in + 10+0 B out, state=wait-input) in=9668 out=17375 imap(username): Connection closed: read(size=3751) failed: Connection reset by peer in=4441 out=51431 dovecot: imap(username): Connection closed (UID fetch running for 0.008 + waiting input for 0.001 secs, 0.001 in locks, 101 B in + 202+202 B out, state=wait-input) in=3330 out=436043 Could it be problem in our network or Dovecot configuration issue? Can I somehow debug all connections for single client? Thank you, Milo [1] https://wiki.dovecot.org/Timeouts

2 2