http://dovecot.org/releases/1.1/dovecot-1.1.7.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.7.tar.gz.sig I should have released this earlier since v1.1.6 had that annoying startup problem, but surprisingly few people complained about it so I kind of forgot about it then. BTW. v1.2 progresses nicely. Now that shared mailboxes are finally fully supported, there aren't any widely used IMAP features missing from Dovecot. v1.2.beta1 shouldn't be in too distant future anymore. * IMAP QUOTA extension now returns "MESSAGE" quota, not "MESSAGES". This makes Dovecot now RFC 2087 compliant. Hopefully this change doesn't break anyone's Dovecot-specific quota checking code.. + Added !include and !include_try directives to config file reader. Note that !include doesn't currently work with deliver. The main point here is that ssl_key_password can be placed to a different file with !include_try that deliver can just ignore. + More error/debug message logging improvements. - v1.1.6 gave "userdb didn't return a home directory" error at startup - Some config file parsers (deliver, passwd-file, acl, trash) ignored the file's last line if it didn't end with LF. - fts: SEARCH SUBJECT didn't search messages that weren't already in fts index. - fts-solr: Don't assert-crash if we couldn't connect to Solr. - IMAP: Mailbox deletion gave an error, but still worked, if mails' control directory wasn't the same as index directory. - Several fixes to rarely used mailbox list layout configurations. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://dovecot.org/pipermail/dovecot-news/attachments/20081124/6fab9102/attachment.bin
On Nov 23, 2008, at 5:28 PM, Timo Sirainen wrote:> BTW. v1.2 progresses nicely. Now that shared mailboxes are finally > fully > supported, there aren't any widely used IMAP features missing from > Dovecot. v1.2.beta1 shouldn't be in too distant future anymore.That is great news. Do you anticipate many config file changes (or other upgrade-related stuff) in the 1.2 release for current 1.1.x users? -Dave -- Dave McGuire Port Charlotte, FL
Timo Sirainen a ?crit :> BTW. v1.2 progresses nicely. Now that shared mailboxes are finally fully > supported, there aren't any widely used IMAP features missing from > Dovecot. v1.2.beta1 shouldn't be in too distant future anymore.Great, I'm quite interested in shared mailboxes!> * IMAP QUOTA extension now returns "MESSAGE" quota, not "MESSAGES". > This makes Dovecot now RFC 2087 compliant. Hopefully this change > doesn't break anyone's Dovecot-specific quota checking code..Good, does that mean the issue I've had with GETQUOTAROOT not long ago is fixed, too? Laurent -- / Leader de Projet & Communaut? | I'm working, but not speaking for \ G11N http://fr.opensolaris.org | Bull Services http://www.bull.com / FOSUG http://guses.org |
Does the managesieve patch for 1.1.6 works with it or do we need to wait for a new release? Timo Sirainen wrote:> http://dovecot.org/releases/1.1/dovecot-1.1.7.tar.gz > http://dovecot.org/releases/1.1/dovecot-1.1.7.tar.gz.sig > > I should have released this earlier since v1.1.6 had that annoying > startup problem, but surprisingly few people complained about it so I > kind of forgot about it then. > > BTW. v1.2 progresses nicely. Now that shared mailboxes are finally fully > supported, there aren't any widely used IMAP features missing from > Dovecot. v1.2.beta1 shouldn't be in too distant future anymore. > > * IMAP QUOTA extension now returns "MESSAGE" quota, not "MESSAGES". > This makes Dovecot now RFC 2087 compliant. Hopefully this change > doesn't break anyone's Dovecot-specific quota checking code.. > > + Added !include and !include_try directives to config file reader. > Note that !include doesn't currently work with deliver. The main > point here is that ssl_key_password can be placed to a different > file with !include_try that deliver can just ignore. > + More error/debug message logging improvements. > - v1.1.6 gave "userdb didn't return a home directory" error at startup > - Some config file parsers (deliver, passwd-file, acl, trash) ignored > the file's last line if it didn't end with LF. > - fts: SEARCH SUBJECT didn't search messages that weren't already > in fts index. > - fts-solr: Don't assert-crash if we couldn't connect to Solr. > - IMAP: Mailbox deletion gave an error, but still worked, if mails' > control directory wasn't the same as index directory. > - Several fixes to rarely used mailbox list layout configurations. > >-- Ala'a A. Ibrahim http://www.shoohalayam.com
Timo Sirainen wrote:> http://dovecot.org/releases/1.1/dovecot-1.1.7.tar.gz > http://dovecot.org/releases/1.1/dovecot-1.1.7.tar.gz.sig >Apparently people are very eager to try v1.1.7 and although the ManageSieve patch could still apply and compile correctly, I have refreshed it for the new release to avoid confusion: http://www.rename-it.nl/dovecot/1.1/dovecot-1.1.7-managesieve-0.10.4.diff.gz http://www.rename-it.nl/dovecot/1.1/dovecot-1.1.7-managesieve-0.10.4.diff.gz.sig New releases of Sieve and ManageSieve for v1.2.alpa4 will follow later today. Regards, Stephan
On Nov 24, 2008, at 4:15 AM, Stephan Bosch wrote:>> http://dovecot.org/releases/1.1/dovecot-1.1.7.tar.gz >> http://dovecot.org/releases/1.1/dovecot-1.1.7.tar.gz.sig > Apparently people are very eager to try v1.1.7 and although the > ManageSieve patch could still apply and compile correctly, I have > refreshed it for the new release to avoid confusion: > > http://www.rename-it.nl/dovecot/1.1/dovecot-1.1.7- > managesieve-0.10.4.diff.gz > http://www.rename-it.nl/dovecot/1.1/dovecot-1.1.7- > managesieve-0.10.4.diff.gz.sig > > New releases of Sieve and ManageSieve for v1.2.alpa4 will follow > later today.Are there plans to integrate this functionality directly into Dovecot in the future? -Dave -- Dave McGuire Port Charlotte, FL
On Monday, November 24 at 12:28 AM, quoth Timo Sirainen:>http://dovecot.org/releases/1.1/dovecot-1.1.7.tar.gz >http://dovecot.org/releases/1.1/dovecot-1.1.7.tar.gz.sigHooray! Unfortunately, I ran into a problem. In my config, I have enabled only two authentication mechanisms: plain and login. I've confirmed this by checking the output of `dovecot -a`. And these mechanisms work just fine... but if my IMAP client attempts to use CRAM-MD5, dovecot goes bonkers and then abruptly disconnects: > a0000 AUTHENTICATE DIGEST-MD5 < a0000 NO Unsupported authentication mechanism. > a0001 AUTHENTICATE CRAM-MD5 < a0001 NO Unsupported authentication mechanism. < a0001 NO Unsupported authentication mechanism. < a0001 NO Unsupported authentication mechanism. < a0001 NO Unsupported authentication mechanism. < a0001 NO Unsupported authentication mechanism. < a0001 NO Unsupported authentication mechanism. < a0001 NO Unsupported authentication mechanism. < a0001 NO Unsupported authentication mechanism. < a0001 NO Unsupported authentication mechanism. < a0001 NO Unsupported authentication mechanism. < a0001 NO Unsupported authentication mechanism. < a0001 NO Unsupported authentication mechanism. < a0001 NO Unsupported authentication mechanism. < a0001 NO Unsupported authentication mechanism. < a0001 NO Unsupported authentication mechanism. < a0001 NO Unsupported authentication mechanism. < a0001 NO Unsupported authentication mechanism. < a0001 NO Unsupported authentication mechanism. < a0001 NO Unsupported authentication mechanism. < a0001 NO Unsupported authentication mechanism. < a0001 NO Unsupported authentication mechanism. < a0001 NO Unsupported authentication mechanism. < a0001 NO Unsupported authentication mechanism. < a0001 NO Unsupported authentication mechanism. < a0001 NO Unsupported authentication mechanism. < a0001 NO Unsupported authentication mechanism. < a0001 NO Unsupported authentication mechanism. < a0001 NO Unsupported authentication mechanism. < a0001 NO Unsupported authentication mechanism. < a0001 NO Unsupported authentication mechanism. < a0001 NO Unsupported authentication mechanism. < a0001 NO Unsupported authentication mechanism. < a0001 NO Unsupported authentication mechanism. < a0001 NO Unsupported authentication mechanism. < a0001 NO Unsupported authentication mechanism. < a0001 NO Unsupported authentication mechanism. closed What's up with that? ~Kyle -- And I have other sheep, that are not of this fold. -- John 10:16 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 204 bytes Desc: not available URL: <http://dovecot.org/pipermail/dovecot/attachments/20081124/aca09bab/attachment-0002.bin>