similar to: v2.2.20 release candidate released

On 05 Dec 2015, at 11:32, Gerhard Wiesinger <lists at wiesinger.com> wrote: > > Is it possible to configure the secure session caching mechanism? > e.g. like in nginx: https://bjornjohansen.no/optimizing-https-nginx I remember hearing about various security vulnerabilities in that earlier.. I guess they're fixed now then, unless people find more ways to exploit it. Anyway

http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz.sig This could be (one of) the last v2.2.x release. We're starting v2.3 development soon. + Added mailbox { autoexpunge=<time> } setting. See http://wiki2.dovecot.org/MailboxSettings for details. + ssl_options: Added support for no_ticket + imap/pop3/managesieve-login:

http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz.sig This could be (one of) the last v2.2.x release. We're starting v2.3 development soon. + Added mailbox { autoexpunge=<time> } setting. See http://wiki2.dovecot.org/MailboxSettings for details. + ssl_options: Added support for no_ticket + imap/pop3/managesieve-login:

> On 03 Dec 2015, at 16:09, Thomas Leuxner <tlx at leuxner.net> wrote: > > * Timo Sirainen <tss at iki.fi> 2015.12.03 14:51: > >> + Added mailbox { autoexpunge=<time> } setting. See >> http://wiki2.dovecot.org/MailboxSettings for details. > > namespace inbox { > mailbox Trash { > autoexpunge = 5 days > special_use = \Trash >

On Tuesday 08 of December 2015, Gerhard Wiesinger wrote: > On 07.12.2015 20:13, Timo Sirainen wrote: > > http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz > > http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz.sig > > > > This could be (one of) the last v2.2.x release. We're starting v2.3 > > development soon. > > Great! > > What's on

On 03.12.2015 14:51, Timo Sirainen wrote: > http://dovecot.org/releases/2.2/rc/dovecot-2.2.20.rc1.tar.gz > http://dovecot.org/releases/2.2/rc/dovecot-2.2.20.rc1.tar.gz.sig > > v2.2.20 probably will be released tomorrow or maybe during weekend. > > + ssl_options: Added support for no_ticket > Hello TImo, great to see that inseucre session tickets (violating PFS) can be

* Timo Sirainen <tss at iki.fi> 2015.12.03 14:51: > + Added mailbox { autoexpunge=<time> } setting. See > http://wiki2.dovecot.org/MailboxSettings for details. namespace inbox { mailbox Trash { autoexpunge = 5 days special_use = \Trash } } I'm using autoexpunge on the Trash mailbox. Looking at the wiki text I'm unclear on how to limit it to a specific

I'm trying to understand autoexpunge, but the documentation is just not clear. Hopefully, someone can clear up a few questions. http://wiki.dovecot.org/MailboxSettings says the following: autoexpunge=<time>: (v2.2.20+) Automatically at user deinitialization expunge all mails in this mailbox whose saved-timestamp is older than <time> (e.g. autoexpunge=30d). This removes the

We're using dovecot on a help desk ticketing system. The system doesn't perform any cleanup of IMAP mailboxes so we have a regular cronjob doing this: /usr/bin/doveadm flags add -A '\Deleted' SEEN SENTBEFORE 12w && /usr/bin/doveadm expunge -A DELETED MAILBOX '*' Recently, doveadm has been reporting this: doveadm(nobody): Error: User initialization failed:

On 03/12/2015 13:51, Timo Sirainen wrote: > http://dovecot.org/releases/2.2/rc/dovecot-2.2.20.rc1.tar.gz I see a clash with the pigeonhole 0.4.9 preventing compilation of pigeonhole. "sieve-settings.c", line 14: identifier redeclared: t_str_trim current : static function(pointer to const char) returning pointer to const char previous: function(pointer to const char, pointer to

http://dovecot.org/releases/2.2/dovecot-2.2.21.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.21.tar.gz.sig Due to a bit bad doveadm bugs in v2.2.20 here's a fixed v2.2.21. Also from this release forward we're finally using git with branches to make new releases. So new releases will have a bit more time to stabilize in the branch before they're being released (while still

http://dovecot.org/releases/2.2/dovecot-2.2.21.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.21.tar.gz.sig Due to a bit bad doveadm bugs in v2.2.20 here's a fixed v2.2.21. Also from this release forward we're finally using git with branches to make new releases. So new releases will have a bit more time to stabilize in the branch before they're being released (while still

Hello, I saw that OpenSSH release 6.7 removed all CBC ciphers by default. Is CBC therefore considered as broken and unsecure (in general or SSH implementation)? I also read a lot of references (see below) but still not clear to me what's the actual "security status" of CBC and why it has been removed in general. http://www.openssh.com/txt/release-6.7 sshd(8): The default set

On 15.06.2015 21:31, Christian Weisgerber wrote: > On 2015-06-15, Gerhard Wiesinger <lists at wiesinger.com> wrote: > >> I saw that OpenSSH release 6.7 removed all CBC ciphers by default. Is >> CBC therefore considered as broken and unsecure (in general or SSH >> implementation)? > CBC modes in SSH use the last encrypted block of the previous packet > as the IV

Hello! Noone has running a sendmail/Mailscanner/procmail/mbox environment? Ciao, Gerhard ---------- Forwarded message ---------- Date: Mon, 24 Apr 2006 20:27:56 +0200 (CEST) From: Gerhard Wiesinger <lists at wiesinger.com> To: dovecot at dovecot.org Subject: [Dovecot] Dovecot LDA with sendmail/Mailscanner Hello! I'm running dovecot in a sendmail/Mailscanner/procmail/mbox

Hello! I'm running squirrelmail 1.4.8 (I know this is not the latest version) and know I'm having troubles with: 1.) Folder list view 2.) Save to sent or Drafts folder. Configuration worked well. I think it has to do with the upgrade from dovecot 1.0 to 1.1 and the LIST command. Thunderbird/alpine work well. Commands from rawlog are: A002 LIST "" "~/Mail/Drafts"

http://dovecot.org/releases/dovecot-1.0.rc25.tar.gz http://dovecot.org/releases/dovecot-1.0.rc25.tar.gz.sig Instead of having "Should v1.0 be released already" discussion, how about having "What's still missing from wiki.dovecot.org and how could it be improved" discussion? And what should the wiki exported to doc/ directory in the tarball look like? * If time moves

http://dovecot.org/releases/dovecot-1.0.rc25.tar.gz http://dovecot.org/releases/dovecot-1.0.rc25.tar.gz.sig Instead of having "Should v1.0 be released already" discussion, how about having "What's still missing from wiki.dovecot.org and how could it be improved" discussion? And what should the wiki exported to doc/ directory in the tarball look like? * If time moves

Hello! Currently I'm trying to integrate dovecot's deliver program into procmail. So basically I'd write a patch for procmail to deliver not directly into the mbox file but delivering with the dovecot deliver program. Do you think this is a good concept? For testing I use the commands discussed below. Currently I'm having a problem that deliver doesn't recognize the

http://dovecot.org/releases/2.1/dovecot-2.1.5.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.5.tar.gz.sig A few announcements first: I'm now going to start being more strict about not answering Dovecot questions sent to me privately (especially support requests, but also bug reports, feature requests, etc). Often those questions could be answered by other people in the mailing list as