<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 03/03/11 01:57, Jeroen van Meeuwen (Kolab Systems) wrote:
<blockquote cite="mid:201103021457.21590.vanmeeuwen@kolabsys.com"
type="cite">
<meta name="qrichtext" content="1">
<style type="text/css">
p, li { white-space: pre-wrap; }
</style>
<p style="margin: 0px; text-indent: 0px;">Hi there,</p>
<p style="margin: 0px; text-indent: 0px;">I would like us to take
under consideration, changing the default value for the
following configuration values for Cyrus IMAP 2.5;</p>
<p style="margin: 0px; text-indent: 0px;">The purpose is to
improve how Cyrus IMAP works out-of-the-box, and provide
defaults that are more likely to not require change.</p>
</blockquote>
<br>
I have no comment on specific options, but I agree reviewing
defaults from time to time is a good idea.<br>
<br>
I would however, suggest that the sysadmin's upgrade experience is
improved by using a technique borrowed from Linux NFS. There the
default value of one of the export options changed. For several
releases, if the default in the code was actually used (i.e. no
value was specified by the sysadmin in the config), the following
message was emitted:<br>
<br>
<blockquote type="cite">exportfs: /etc/exports [1]: No 'sync' or
'async' option specified for export "132.183.220.0/24:/apps".<br>
Assuming default behaviour ('sync').<br>
NOTE: this default has changed from previous versions</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Greg.</pre>
</body>
</html>