[Dovecot] 1.0.beta9 released
Fixes a lot of bugs. The next release will be the first "release candidate" instead of a beta.
* PAM: Don't call pam_setcred() unless setcred=yes PAM passdb
argument was given.
* Moved around settings in dovecot-example.conf to be in more logical
groups.
+ Local delivery agent (deliver binary) works again.
+ LDAP: Added support for SASL binding. Patch by Geert Jansen
+ ssl_verify_client_cert: Check CRLs. If auth_verbose=yes, log
invalid sent certificates. If verbose_ssl=yes, log even the valid
certificates. When using the username from the certificate, use
CommonName. Based on patch by HenkJan Wolthuis
+ PAM: Set PAM_TTY which is needed by some PAM plugins
+ dovecot --exec-mail ext <binary path> can now be used to start
binaries which want dovecot.conf to be read, for example the
convert-tool.
- Expunging needed to be done twice if client used STORE +FLAGS.SILENT
command to set the \Deleted flags
- Added sql_escape_string() to lib-sql API and use it instead of
normal \-escaping.
- ACL plugin fixes
- DIGEST-MD5: Trying to use subsequent authentication crashed
dovecot-auth.
- Fetching BODY when BODYSTRUCTURE was already cached caused the
reply to be broken in some cases
- Lots of fixes for index file handling
- dbox fixes and changes
- mbox syncing broke if some extraneous/broken headers were removed
(eg. extra X-IMAPbase headers in mails)
- Running Dovecot from inetd work now properly with POP3
- Quota plugin fixes for calculating the quota correctlyQuoting Timo Sirainen tss@iki.fi:
Fixes a lot of bugs. The next release will be the first "release candidate" instead of a beta.
- PAM: Don't call pam_setcred() unless setcred=yes PAM passdb argument was given.
- Moved around settings in dovecot-example.conf to be in more logical groups.
- Local delivery agent (deliver binary) works again.
- LDAP: Added support for SASL binding. Patch by Geert Jansen
- ssl_verify_client_cert: Check CRLs. If auth_verbose=yes, log invalid sent certificates. If verbose_ssl=yes, log even the valid certificates. When using the username from the certificate, use CommonName. Based on patch by HenkJan Wolthuis
- PAM: Set PAM_TTY which is needed by some PAM plugins
- dovecot --exec-mail ext <binary path> can now be used to start binaries which want dovecot.conf to be read, for example the convert-tool.
- Expunging needed to be done twice if client used STORE +FLAGS.SILENT command to set the \Deleted flags
- Added sql_escape_string() to lib-sql API and use it instead of normal \-escaping.
- ACL plugin fixes
- DIGEST-MD5: Trying to use subsequent authentication crashed dovecot-auth.
Thank you! Rebooting the machine Dovecot runs on always caused dovecot-auth to dump core. Rather than exiting normally. This will be a welcome fix for me. :)
- Fetching BODY when BODYSTRUCTURE was already cached caused the reply to be broken in some cases
- Lots of fixes for index file handling
- dbox fixes and changes
- mbox syncing broke if some extraneous/broken headers were removed (eg. extra X-IMAPbase headers in mails)
- Running Dovecot from inetd work now properly with POP3
- Quota plugin fixes for calculating the quota correctly
--
FreeBSD 5.4-RELEASE-p12 (SMP - 900x2) Tue Mar 7 19:37:23 PST 2006 /////////////////////////////////////////////////////////////////
On 6/14/06, Timo Sirainen tss@iki.fi wrote:
Fixes a lot of bugs. The next release will be the first "release candidate" instead of a beta.
Yay! :-D
+ Local delivery agent (deliver binary) works again.
Do we still need to get it from CVS for sieve support?
- ACL plugin fixes
Curious, do we have more details of the fixes somewhere? I seem to have missed what they are, and only just subscribed to the CVS list
- Quota plugin fixes for calculating the quota correctly
Yay!
Thanks a lot Timo, I'll be getting Beta 9 this evening, and testing it hard!
Tim p.s. When we reply to emails you post to list, I assume you would prefer we didn't include you in the CC list (i.e. when we hit reply to all)?
Linux Counter user #273956
On Wed, Jun 14, 2006 at 07:34:49AM +0800, Timothy White may have written:
p.s. When we reply to emails you post to list, I assume you would prefer we didn't include you in the CC list (i.e. when we hit reply to all)?
Why would you ever use "Reply All" for a mailing list?
-- http://www.delink.net/ Your step will soil many countries.
Brian T Glenn wrote:
On Wed, Jun 14, 2006 at 07:34:49AM +0800, Timothy White may have written:
p.s. When we reply to emails you post to list, I assume you would prefer we didn't include you in the CC list (i.e. when we hit reply to all)?
Why would you ever use "Reply All" for a mailing list?
because if I just hit reply, it would only go to you and not the list? for this list it seems to remove an individuals email, but the freebsd lists it does not.
On Thu, Jun 15, 2006 at 10:14:12AM -0500, Eric may have written:
Brian T Glenn wrote:
On Wed, Jun 14, 2006 at 07:34:49AM +0800, Timothy White may have written:
p.s. When we reply to emails you post to list, I assume you would prefer we didn't include you in the CC list (i.e. when we hit reply to all)?
Why would you ever use "Reply All" for a mailing list?
because if I just hit reply, it would only go to you and not the list? for this list it seems to remove an individuals email, but the freebsd lists it does not.
I'm not going to start the holy war about Reply-To: headers in mailing lists versus a "Reply to List" feature in MUAs once again. That horse has been beaten into glue many times on other mailing lists I am on. The Mail-Followup-To header falls into this category as well.
I think it is much more important to be mindful of what you are about to do before pressing Send. Many people aren't.
Cheers,
http://www.delink.net/ So, Atal said, it would be much better to let all gods alone except in tactful prayers. -- H.P. Lovecraft, "The Dream Quest of Unknown Kadath"
Quoting Brian T Glenn:
I think it is much more important to be mindful of what you are about to do before pressing Send. Many people aren't.
I can not be mindful if the list message I'm answering to does not contain any hint what the writer of it wants. Most MUAs only have "reply" (private) and "reply all" (private and public). If somebody (like you and me) does not want private replies, there are reply-to or mail-followup-to to prevent that or at least give a good hint.
EOD from my side.
hi,
the SuSE packages for 1.0.beta9 are ready. How to use the packages is explained at [2]. If you dont want to add the source to your package manager you can grab the rpms directly from [3].
Packages are build for: SUSE_SLES-9 SuSE_Linux_9.3 SuSE_Linux_10.0 SuSE_Linux_10.1 SuSE_Linux_Factory
additionally it is build for Fedora_Core_5/i586 but i didnt have a chance to test it there yet.
hope this helps
darix[1] http://en.opensuse.org/Build_Service [2] http://en.opensuse.org/Build_Service/User [3] http://software.opensuse.org/download/server:/mail/
-- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org
On Tue, Jun 13, 2006 at 07:16:50PM +0300, Timo Sirainen wrote:
Fixes a lot of bugs. The next release will be the first "release candidate" instead of a beta.
I've updated the packages at ATrpms to dovecot 1.0beta9.
http://atrpms.net/name/dovecot/(Unfortunately RH7.3 doesn't build anymore due to sasl, so I had to remove the RH7.3 builds.)
Axel.Thimm at ATrpms.net
On Mon, Jun 19, 2006 at 05:48:25PM +0300, Timo Sirainen wrote:
On Mon, 2006-06-19 at 16:27 +0200, Axel Thimm wrote:
(Unfortunately RH7.3 doesn't build anymore due to sasl, so I had to remove the RH7.3 builds.)
What do you mean by this? I haven't intentionally broken anything.
No, the sasl implementation on RH7.3 is just ancient. It starts with
#include
I don't think there really are that many RH7.3 users that would use dovecot out there, so I don't think it's worth while reviving it.
Axel.Thimm at ATrpms.net
On Mon, 2006-06-19 at 16:59 +0200, Axel Thimm wrote:
On Mon, Jun 19, 2006 at 05:48:25PM +0300, Timo Sirainen wrote:
On Mon, 2006-06-19 at 16:27 +0200, Axel Thimm wrote:
(Unfortunately RH7.3 doesn't build anymore due to sasl, so I had to remove the RH7.3 builds.)
What do you mean by this? I haven't intentionally broken anything.
No, the sasl implementation on RH7.3 is just ancient. It starts with #include
not mapping RH7.3's cyrus-sasl 1.5.24 which uses /usr/include/sasl.h, and fixing this just opens another can of worms.
But still why is anything including sasl.h? Dovecot itself isn't doing that. Or is it LDAP or OpenSSL that does that? In those cases you could just disable those..
On Mon, Jun 19, 2006 at 06:27:53PM +0300, Timo Sirainen wrote:
On Mon, 2006-06-19 at 16:59 +0200, Axel Thimm wrote:
On Mon, Jun 19, 2006 at 05:48:25PM +0300, Timo Sirainen wrote:
On Mon, 2006-06-19 at 16:27 +0200, Axel Thimm wrote:
(Unfortunately RH7.3 doesn't build anymore due to sasl, so I had to remove the RH7.3 builds.)
What do you mean by this? I haven't intentionally broken anything.
No, the sasl implementation on RH7.3 is just ancient. It starts with #include
not mapping RH7.3's cyrus-sasl 1.5.24 which uses /usr/include/sasl.h, and fixing this just opens another can of worms. But still why is anything including sasl.h? Dovecot itself isn't doing that. Or is it LDAP or OpenSSL that does that? In those cases you could just disable those..
beta9 added:
+ LDAP: Added support for SASL binding. Patch by Geert Jansen-- Axel.Thimm at ATrpms.net
On Mon, 2006-06-19 at 17:53 +0200, Axel Thimm wrote:
But still why is anything including sasl.h? Dovecot itself isn't doing that. Or is it LDAP or OpenSSL that does that? In those cases you could just disable those..
beta9 added:
+ LDAP: Added support for SASL binding. Patch by Geert Jansen
Oh, didn't think of that. I'll make it optional.
participants (8)
-
Axel Thimm
-
Brian T Glenn
-
Chris H.
-
Eric
-
Jakob Hirsch
-
Marcus Rueckert
-
Timo Sirainen
-
Timothy White