qmailadmin-devel

[qmailadmin-devel] Should --enable-modify-quota be on by default?

[Tom C. <to...@to...>]

I just got an email from someone who didn't know about the modify-quota 
feature.

I'm wondering if we should turn it on by default.  I would think that 
 >50% of users would make use of it, but more importantly, if you don't 
know it's available, you might not go looking for it.  If the modify 
quota feature shows up unexpectedly, and you don't want it, you'll 
definitely look at the configure options on how to remove it.

I'm also thinking about rewriting the configure help to show the y/n 
options like this:

   --disable-ezmlm-mysql     Disable MySQL options for mailing lists.
   --enable-no-cache         Prohibit caching via http headers.
   --disable-ipauth          Disable IP address checks (NAT/proxy 
systems may not use the same IP for the whole session).
   --disable-user-index      Don't display user index on show users page.
   --disable-modify-quota    Allow domain admin (postmaster) to modify 
user quotas.
   --enable-domain-autofill  Autofill the domain on login page based on 
the URL hostname.

By just listing the option to alter default behavior, I think we make 
the options clearer.  The old formats will still work, but I think that 
it's easier to understand --disable-modify-quota than 
--enable-modify-quota=n.

I'm even tempted to change the options where you specify something to 
use "with" and "without", and list the default in square brackets 
(saving space used by "default is" on every line):

   --with-qmaildir={dir}        Directory where qmail is installed 
[/var/qmail].
   --with-maxusersperpage=15    Number of users to display at a time 
[15].
   --with-maxaliasesperpage=25  Number of aliases to display at a time 
[25].

My understanding of the configure script is that the following are 
equivalent:

--with-feature
--enable-feature
--with-feature=y
--enable-feature=y

and:

--disable-feature
--without-feature
--enable-feature=n
--with-feature=n

I think we should use the one that makes the most sense (and is easiest 
to read) in ./configure --help.

Thoughts?

--
Tom Collins
to...@to...
http://sniffter.com/ - info on the Sniffter hand-held Network Tester

RE: [qmailadmin-devel] Should --enable-modify-quota be on by default?

[Benjamin T. <in...@so...>]

> --with-feature
> --enable-feature
> --with-feature=y
> --enable-feature=y
>
> and:
>
> --disable-feature
> --without-feature
> --enable-feature=n
> --with-feature=n
>
> I think we should use the one that makes the most sense (and is easiest
> to read) in ./configure --help.
>
> Thoughts?
>
Personally, I'm a fan of using enable/disable w/o the =y/n ending for switch
flags.  For those flags with multiple values to be defined, then the --with
flags can be handy, such as when specifying a path or option X of N, etc.

In terms of what's enabled/disabled by default, it would probably be
worthwhile to list out where things currently are set and then evaluate
based on consensus which ones make more sense as enabled, and which ones
make more sense as disabled.  For instance, in addition to the quota
support, if the help files were packaged with qmailadmin (will they be
ever?), then it might make sense to enable them by default, etc.

RE: [qmailadmin-devel] Should --enable-modify-quota be on by default?

[Benjamin T. <in...@so...>]

btw, side-note on the --enable-modify-quota capability...even though my
default in vpopmail is 15MB, qmailadmin defaults to setting it at
NOQUOTA....this should not be the case, but should in fact be consistent
with vpopmail...

> -----Original Message-----
> From: qma...@li...
> [mailto:qma...@li...]On Behalf Of Tom
> Collins
> Sent: Tuesday, August 12, 2003 11:38 AM
> To: qma...@li...
> Subject: [qmailadmin-devel] Should --enable-modify-quota be on by
> default?
>
>
> I just got an email from someone who didn't know about the modify-quota
> feature.
>
> I'm wondering if we should turn it on by default.  I would think that
>  >50% of users would make use of it, but more importantly, if you don't
> know it's available, you might not go looking for it.  If the modify
> quota feature shows up unexpectedly, and you don't want it, you'll
> definitely look at the configure options on how to remove it.
>
> I'm also thinking about rewriting the configure help to show the y/n
> options like this:
>
>    --disable-ezmlm-mysql     Disable MySQL options for mailing lists.
>    --enable-no-cache         Prohibit caching via http headers.
>    --disable-ipauth          Disable IP address checks (NAT/proxy
> systems may not use the same IP for the whole session).
>    --disable-user-index      Don't display user index on show users page.
>    --disable-modify-quota    Allow domain admin (postmaster) to modify
> user quotas.
>    --enable-domain-autofill  Autofill the domain on login page based on
> the URL hostname.
>
> By just listing the option to alter default behavior, I think we make
> the options clearer.  The old formats will still work, but I think that
> it's easier to understand --disable-modify-quota than
> --enable-modify-quota=n.
>
> I'm even tempted to change the options where you specify something to
> use "with" and "without", and list the default in square brackets
> (saving space used by "default is" on every line):
>
>    --with-qmaildir={dir}        Directory where qmail is installed
> [/var/qmail].
>    --with-maxusersperpage=15    Number of users to display at a time
> [15].
>    --with-maxaliasesperpage=25  Number of aliases to display at a time
> [25].
>
> My understanding of the configure script is that the following are
> equivalent:
>
> --with-feature
> --enable-feature
> --with-feature=y
> --enable-feature=y
>
> and:
>
> --disable-feature
> --without-feature
> --enable-feature=n
> --with-feature=n
>
> I think we should use the one that makes the most sense (and is easiest
> to read) in ./configure --help.
>
> Thoughts?
>
> --
> Tom Collins
> to...@to...
> http://sniffter.com/ - info on the Sniffter hand-held Network Tester
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072
303_01/01
_______________________________________________
qmailadmin-devel mailing list
qma...@li...
https://lists.sourceforge.net/lists/listinfo/qmailadmin-devel

Re: [qmailadmin-devel] Should --enable-modify-quota be on by default?

[Tom C. <to...@to...>]

On Tuesday, August 12, 2003, at 02:19  PM, Benjamin Tomhave wrote:
> btw, side-note on the --enable-modify-quota capability...even though my
> default in vpopmail is 15MB, qmailadmin defaults to setting it at
> NOQUOTA....this should not be the case, but should in fact be 
> consistent
> with vpopmail...

You're right.  The code that is used for adding a new user should 
insert the default quota in the add user template.  It looks like the 
code that sets the quota on a new user should be reviewed as well.

--
Tom Collins
to...@to...
http://sniffter.com/ - info on the Sniffter hand-held Network Tester