- dovecot - dovecot.org

Crash: setannotation Trash "/vendor/cmu/cyrus-imapd/expire" ("value.shared" NIL)
by Heiko Schlittermann 27 Apr '16

27 Apr '16

Hi, Using 2.2.9 (ubuntu 14.04 LTS) and sending the following command, the server crashes when I try to delete an annotation: … login … C: 2 setannotation Trash "/vendor/cmu/cyrus-imapd/expire" ("value.shared" NIL) Apr 27 09:29:16 backend1 dovecot: imap-login: Login: user=<heiko>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=6651, secured Apr 27 09:29:16 backend1 dovecot: imap(heiko): Fatal: master: service(imap): child 6651 killed with signal 11 (core dumped) Sending a real value it works: … login … C: 2 setannotation Trash "/vendor/cmu/cyrus-imapd/expire" ("value.shared" "27") S: 2 OK Completed. Is this a known bug that is fixed in later releases? Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de ---------------------------- internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} - gnupg encrypted messages are welcome --------------- key ID: F69376CE - ! key id 7CBF764A and 972EAC9F are revoked since 2015-01 ------------ -

3 6

apt pinning specific dovecot version
by Regan Jelčić 27 Apr '16

27 Apr '16

I currently have the dovecot-core package from wheezy-backports pinned on one of my servers to version '2.2.9', which has been working great. I now want to upgrade that to the newest version under wheezy-backports which is: dovecot-core (1:2.2.13-11~bpo70+1) but I can't figure out how to get do it. I've tried a few different formats of the name but apt-get update then apt-get dost-upgrade doesn't pick up the new version - it ignores it when trying to do an update. This is what I've got in my apt preferences and pin files... /etc/apt/preferences Explanation: Stop ALL wheezy-backports updating system. Package: * Pin: release a=wheezy-backports,n=wheezy-backports Pin-Priority: 100 /etc/apt/preferences.d/dovecot.pref Explanation: Promote wheezy-backports version of Dovecot only Package: dovecot-core /2\.2\.9/ Pin: release a=wheezy-backports Pin-Priority: 500 Can anyone advise how I get it to pull the newer version?? Thanks,

3 2

Re: dovecot Digest, Vol 156, Issue 44
by Ron Cleven 27 Apr '16

27 Apr '16

> On 26 Apr 2016, at 21:52, Hauke Fath<hf(a)spg.tu-darmstadt.de> wrote: >> > >> >On Tue, 26 Apr 2016 18:20:00 +0300, Timo Sirainen wrote: >>> >>This should be a good release.:) >> > >> >Would this release address the "reappearing emails" issue that 2.2.23 >> >introduced? > I guess you're talking about replication. I'm not aware of any specific change in v2.2.23 that could have even potentially caused it. I also don't know how I could reproduce it. Can you use git bisect to find out the specific change that broke it? > > The only thing I remember even remotely related to this ishttps://github.com/dovecot/core/commit/950a6e61d6c2dac961ce031bdd8b2895bc… but that was supposed to only fix things and I can't think of how it might break things. > > One possibility is that nothing broke this in v2.2.23. I've heard about the same issue for a long time. Maybe you just suddenly started having this problem now and it would have happened even with the old Dovecot version. I was (perhaps one of) the people who reported "reappearing emails" with 2.2.10 in the context of Maildir with replication under CentOS 7. I had spent a great deal of time making it reproducible, difficult because there was a timing element. In that context, 2.2.23 absolutely fixed the problem which was absolutely related to a timing issue with replication. If I remember right, this person was reporting a similar-sounding problem, but it did not involve replication and was not under CentOS 7. Creating a script that reproduces the problem is an important first step. Good luck.

1 0

Released Pigeonhole v0.4.14 for Dovecot v2.2.24.
by Stephan Bosch 27 Apr '16

27 Apr '16

Hello Dovecot users, The most important feature that this new release adds is the IMAPSIEVE capability, which allows executing Sieve scripts at IMAP events. It also adds the ability to obtain trace logs from Sieve execution at actual delivery (or from IMAP), rather than only using the sieve-test command line tool. This release also fixes a bug in the Sieve extprograms plugin that has been bothering a few people for a while now. Changelog v0.4.14: * The address test now allows specifying the X-Original-To header. + Implemented the Sieve imapsieve extension and its IMAP counterpart (RFC 6785) as a set of plugins. This allows running Sieve scripts at IMAP activity, rather than at delivery. There are also facilities for the familiar sieve_before/sieve_after administrator scripts. A user script is defined for a mailbox using an IMAP METADATA entry, whereas administrator scripts are configured using mailbox matching rules defined in the plugin settings. + Adjusted the Sieve ihave extension to allow capability tests to be performed at runtime. This way, scripts can be written that work both at delivery and from IMAP. + Implemented support for runtime trace debugging. This means that detailed information about which commands, actions and tests are performed is written to a file. That file is created in the configured directory, but only if that directory exists. This way, a particular user can be easily singled out for debugging. This works much like the Dovecot rawlog facility. The trace output is identical to what is produced using sieve-test with its "-t" command line option. + Added a "sieve_user_email" setting that configures the user's primary email address. This is mainly useful to have a user email address available in IMAP, where envelope data is unavailable. + Implemented the dovecot-specific "vnd.dovecot.report" extension. This allows sending report messages in the Message Abuse Reporting Format (RFC 5965). - extprograms plugin: Fixed epoll() panic caused by closing the output FD before the output stream. - Made sure that the local part of a mail address is encoded properly using quoted string syntax when it is not a dot-atom. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.14.ta… http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.14.ta… 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

help with sieve
by dovecot＠paulkoppen.com 27 Apr '16

27 Apr '16

Dear Dovecot / Pigeonhole community, I have a very specific issue, but trying to solve this for a full day, I am now getting so bold from pulling my hairs out, I thought it was time I asked for help. I hope this is a good place for that. At my hosting provider, who have been extremely helpful by the way but are not specifically skilled in Sieve, I have a catch-all address set up: *(a)domain.org (where * is literal), with a sieve script to control how messages are forwarded. Currently my rules are of the form: if address :localpart :is ["To","Cc","Bcc"] ["name1", "name2", ...] { ... } This works most of the time, but sometimes the messages are not directly addressed to me and so they slip through the filters. I figured that using envelope would solve this, so I require envelope and then do: if envelope :localpart :is "To" ["name1", "name2", ...] { ... } But this fails. After endlessly trying different combinations I figured out that the reason for failure is that the envelope believes the "To" is actually "*(a)domain.org", so it is never going to match any of the names. However, the following test succeeds: if header :contains "Envelope-To" "name1@" { ... } From this I deduce that a previous script has already done the conversion from name1 to *, and at the point where my sieve script is run the envelope picks up the *(a)domain.org address, leaving the Envelope-To header for what it is. But I am new to this. Is that likely to be the case? Is it a common sieve set-up? And most importantly, is there a better way around the issue than testing header :contains? With kind regards, Paul

2 1

v2.2.24 released
by Timo Sirainen 26 Apr '16

26 Apr '16

http://dovecot.org/releases/2.2/dovecot-2.2.24.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.24.tar.gz.sig This should be a good release. :) * doveconf now warns if it sees a global setting being changed when the same setting was already set inside some filters. (A common mistake has been adding more plugins to a global mail_plugins setting after it was already set inside protocol { .. }, which caused the global setting to be ignored for that protocol.) * LMTP proxy: Increased default timeout 30s -> 125s. This makes it less likely to reach the timeout and cause duplicate deliveries. * LMTP and indexer now append ":suffix" to session IDs to make it unique for the specific user's delivery. (Fixes duplicate session ID warnings in stats process.) + Added dict-ldap for performing read-only LDAP dict lookups. + lazy-expunge: All mails can be saved to a single specified mailbox. + mailbox { autoexpunge } supports now wildcards in mailbox names. + doveadm HTTP API: Added support for proxy commands + imapc: Reconnect when getting disconnected in non-selected state. + imapc: Added imapc_features=modseq to access MODSEQs/HIGHESTMODSEQ. This is especially useful for incremental dsync. + doveadm auth/user: Auth lookup performs debug logging if -o auth_debug=yes is given to doveadm. + Added passdb/userdb { auth_verbose=yes|no } setting. + Cassandra: Added user, password, num_threads, connect_timeout and request_timeout settings. + doveadm user -e <value>: Print <value> with %variables expanded. - Huge header lines could have caused Dovecot to use too much memory (depending on config and used IMAP commands). (Typically this would result in only the single user's process dying with out of memory due to reaching service { vsz_limit } - not a global DoS). - dsync: Detect and handle invalid/stale -s state string better. - dsync: Fixed crash caused by specific mailbox renames - auth: Auth cache is now disabled passwd-file. It was unnecessary and it broke %variables in extra fields. - fts-tika: Don't crash if it returns 500 error - dict-redis: Fixed timeout handling - SEARCH INTHREAD was crashing - stats: Only a single fifo_listeners was supported, making it impossible to use both auth_stats=yes and mail stats plugin. - SSL errors were logged in separate "Stacked error" log lines instead of as part of the disconnection reason. - MIME body parser didn't handle properly when a child MIME part's --boundary had the same prefix as the parent.

2 2

Subject: Re: v2.2.24 released
by Joseph Tam 26 Apr '16

26 Apr '16

Timo Sirainen wrote: > - auth: Auth cache is now disabled passwd-file. It was unnecessary and > it broke %variables in extra fields. So settings like auth_cache_size = 65536 auth_cache_ttl = 86400 auth_cache_negative_ttl = 600 are ignored/useless, and passwd-file auth lookups always results in file read operation? Joseph Tam <jtam.home(a)gmail.com>

2 2

Solr with shared mailboxes
by Ricardo Branco 26 Apr '16

26 Apr '16

We have multiple logins assigned to single mailboxes, so we can give one login to different devices. Does this cause a problem with mailbox guids in solr or is the ID stored within the indexes and not related to username.

2 3

doveadm search when using solr problems
by Ricardo Branco 26 Apr '16

26 Apr '16

Is there a way when using doveadm to search a users mailbox to disable using solr plugin (without changing config file). We have found that solr does not work well with certain search types and reverting to non solr searching works much better.

2 3

Possible to use Doveadm for a time range deletion
by Kenneth Ulrich 26 Apr '16

26 Apr '16

Hello All, I was wondering if it s possible to remove emails between a time range. For example, End Users have emails dating back to Aug 2000. He would like all emails deleted between the time stamp of 07/2014 to 07/2015 yet keep any emails outside of this area. I've ran into some similar examples, but nothing definite.

2 1