Thread: [Postfixadmin-devel] Changing some defaults in trunk/3.0?
Brought to you by:
christian_boltz,
gingerdog
Menu
▾
▴
postfixadmin-devel
|
From: Christian B. <pos...@cb...> - 2012-04-13 00:04:51
|
Hello,
3.0 will be a major release, which means I won't be too strict about
keeping the default config 100% backwards compatible (= unchanged).
We probably have some config options with defaults that are there for
historic reasons, but are not the best idea nowadays.
Are you aware of any setting in config.inc.php that is
- outdated (as in "everybody has to change this nowadays") or
- "not a good idea"[tm] or
- could have better default values
?
If yes, please speak up now and tell me
- which $CONF option?
- why would you change its default value?
- and to which value? (you can obviously ignore this part for YES/NO
options ;-)
Let me start with some things I noticed while scrolling over
config.inc.php:
$CONF['database_type'] = 'mysqli'; # current value: "mysql"
should be changed to "mysqli". The reason is simple - I don't expect we
have too many users using MySQL < 4.1 nowadays ;-) so using the (newer)
mysqli interface by default would make sense.
$CONF['dovecotpw'] = "/usr/sbin/doveadm pw";
# current value: "/usr/sbin/dovecotpw";
reason: dovecot 2.x comes with doveadm instead of dovecotpw
$CONF['domain_path'] = 'YES'; # was NO
$CONF['domain_in_mailbox'] = 'NO'; # was YES
in other words: domain/username/ instead of username@domain/
reason: maybe personal taste ;-)
$CONF['quota'] = 'YES'; # was NO
reason: I'm using quota everywhere - even if I make the mailbox *very*
big, just to avoid that a forgotten mailbox can fill up the harddisk.
$CONF['vacation'] = 'YES'; # was NO
why should we hide this feature? ;-)
$CONF['alias_control'] = 'YES'; # was NO
$CONF['alias_control_admin'] = 'YES'; # was NO
I stopped counting how often users asked to implement this feature ;-)
so we should enable it by default
$CONF['backup'] = 'NO'; # was YES
The backup module is basically unmaintained...
$CONF['show_status']='YES'; # was NO
Why should we hide such a nice feature?
Note that some of the related options would also need better defaults,
but let's first discuss if enabling show_status by default makes sense.
$CONF['new_quota_table'] = 'YES'; # was NO
new quota table format in dovecot 2.x
Needless to say that this *must* be documented in a very visible way to
avoid "surprising" users on upgrades ;-)
Regards,
Christian Boltz
--
>> Does this suggest to remove this feature completely?
> If you want a browser that doesn't malfunction and crash, yes.
Better: the whole networking code should be removed, so we wont get
any cookies over the network [>> Markus Fischer, > Boris Zbarsky
and Zs. G. in https://bugzilla.mozilla.org/show_bug.cgi?id=430006]
|
|
From: Robert S. <ro...@sc...> - 2012-04-13 06:25:48
|
Am 13.04.2012 02:04, schrieb Christian Boltz: > Hello, > > 3.0 will be a major release, which means I won't be too strict about > keeping the default config 100% backwards compatible (= unchanged). > We probably have some config options with defaults that are there for > historic reasons, but are not the best idea nowadays. > > Are you aware of any setting in config.inc.php that is > - outdated (as in "everybody has to change this nowadays") or > - "not a good idea"[tm] or > - could have better default values > ? > > If yes, please speak up now and tell me > - which $CONF option? > - why would you change its default value? > - and to which value? (you can obviously ignore this part for YES/NO > options ;-) > > > Let me start with some things I noticed while scrolling over > config.inc.php: > > $CONF['database_type'] = 'mysqli'; # current value: "mysql" > should be changed to "mysqli". The reason is simple - I don't expect we > have too many users using MySQL < 4.1 nowadays ;-) so using the (newer) > mysqli interface by default would make sense. ACK > > $CONF['dovecotpw'] = "/usr/sbin/doveadm pw"; > # current value: "/usr/sbin/dovecotpw"; > reason: dovecot 2.x comes with doveadm instead of dovecotpw ACK > > $CONF['domain_path'] = 'YES'; # was NO > $CONF['domain_in_mailbox'] = 'NO'; # was YES > in other words: domain/username/ instead of username@domain/ > reason: maybe personal taste ;-) there might not be a default for all people satisfy reading doku stays mandatory > > $CONF['quota'] = 'YES'; # was NO > reason: I'm using quota everywhere - even if I make the mailbox *very* > big, just to avoid that a forgotten mailbox can fill up the harddisk. NOTACK, using quota isnt so wide spreaded as you think, so stay simple default might be better choice > > $CONF['vacation'] = 'YES'; # was NO > why should we hide this feature? ;-) NOTACK, vacation is done via sieve ? > > $CONF['alias_control'] = 'YES'; # was NO > $CONF['alias_control_admin'] = 'YES'; # was NO > I stopped counting how often users asked to implement this feature ;-) > so we should enable it by default OK > > $CONF['backup'] = 'NO'; # was YES > The backup module is basically unmaintained... then it should stay NO > > $CONF['show_status']='YES'; # was NO > Why should we hide such a nice feature? > Note that some of the related options would also need better defaults, > but let's first discuss if enabling show_status by default makes sense. just forgot what show status means *g > > $CONF['new_quota_table'] = 'YES'; # was NO > new quota table format in dovecot 2.x > ACK but depend on quota enable defaults > > Needless to say that this *must* be documented in a very visible way to > avoid "surprising" users on upgrades ;-) > > > Regards, > > Christian Boltz just my thoughts , as you asked, anyway thx for coding ! is there a changelog preview by new feature sets ? -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria |
|
From: Luigi R. <li...@lu...> - 2012-04-13 14:04:30
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Christian Boltz said the following on 13/04/12 02:04:
> $CONF['database_type'] = 'mysqli'; # current value: "mysql" should be
> changed to "mysqli".
+1
> $CONF['domain_path'] = 'YES'; # was NO $CONF['domain_in_mailbox'] = 'NO'; #
> was YES in other words: domain/username/ instead of username@domain/
+1
> $CONF['quota'] = 'YES'; # was NO
I don't use quota. Personal taste and no need to use it.
> $CONF['vacation'] = 'YES'; # was NO why should we hide this feature? ;-)
I use YES; problem is that you have to do some "external work" beside enabling
it. Consider this if you want to make it default.
> $CONF['alias_control'] = 'YES'; # was NO $CONF['alias_control_admin'] =
> 'YES'; # was NO I stopped counting how often users asked to implement this
> feature ;-)
+1 expecially for the reason you gave ;)
> $CONF['backup'] = 'NO'; # was YES
+1
> $CONF['show_status']='YES'; # was NO Why should we hide such a nice
> feature?
+1
> $CONF['new_quota_table'] = 'YES'; # was NO new quota table format in
> dovecot 2.x
See my comment about quota above.
Ciao,
luigi
- --
/
+--[Luigi Rosa]--
\
Experts warn that the Internet is running out of bandw
--fark.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk+ILqAACgkQ3kWu7Tfl6ZTv8wCfQAthwpUWXZW2YiisLGYG+VE/
4u8AoKEWqfG0D/woPKp8Y4W6B1cmUykJ
=u0CT
-----END PGP SIGNATURE-----
|
|
From: Johan H. <Jo...@do...> - 2012-04-13 15:43:13
|
Christian Boltz said the following on 13/04/12 02:04: > $CONF['database_type'] = 'mysqli'; # current value: "mysql" should be > changed to "mysqli". +1 for me also > $CONF['domain_path'] = 'YES'; # was NO $CONF['domain_in_mailbox'] = > 'NO'; # was YES in other words: domain/username/ instead of > username@domain/ +1 for me also > $CONF['quota'] = 'YES'; # was NO I Use quota, but it is up to the end user if he uses it, so i say leave it to NO. > $CONF['vacation'] = 'YES'; # was NO why should we hide this feature? > ;-) I use Sieve, but just like quota leave it to the end user. It is better to Enable things than disable. > $CONF['alias_control'] = 'YES'; # was NO $CONF['alias_control_admin'] > = 'YES'; # was NO I stopped counting how often users asked to > implement this feature ;-) +1 for me also > $CONF['backup'] = 'NO'; # was YES +1, like the quota and so on. If you use it enable it. > $CONF['show_status']='YES'; # was NO Why should we hide such a nice > feature? +1 it is nice, but i could not care less if it was not enabled by default. > $CONF['new_quota_table'] = 'YES'; # was NO new quota table format in > dovecot 2.x Dovecot 1 is not really supported any more. So if this could be merged into one quota setting that would be better. Gr Johan Hendriks |
|
From: David G. <da...@co...> - 2012-04-13 14:44:00
|
> $CONF['database_type'] = 'mysqli'; # current value: "mysql"
> should be changed to "mysqli". The reason is simple - I don't expect we
> have too many users using MySQL < 4.1 nowadays ;-) so using the (newer)
> mysqli interface by default would make sense.
>
Just silently default to mysqli perhaps - i.e. if someone chooses 'mysql' they're actually using 'mysqli' ?
We could wrap this in a if(function_exists('mysqli_connect')) or something - just incase it's possible to have a php5-mysql installed without a php5-mysqli package?
So really the user is choosing whether to use MySQL or other.database - not between two flavours of MySQL.
> $CONF['domain_path'] = 'YES'; # was NO
> $CONF['domain_in_mailbox'] = 'NO'; # was YES
> in other words: domain/username/ instead of username@domain/
> reason: maybe personal taste ;-)
>
Yes.
> $CONF['quota'] = 'YES'; # was NO
> reason: I'm using quota everywhere - even if I make the mailbox *very*
> big, just to avoid that a forgotten mailbox can fill up the hard disk.
I'd always change this back to 'No'. But that's just me.
> $CONF['vacation'] = 'YES'; # was NO
> why should we hide this feature? ;-)
>
I think we should look at using sieve.
>
> $CONF['backup'] = 'NO'; # was YES
> The backup module is basically unmaintained…
>
+1 - doesn't work for PostgreSQL anyway.
> $CONF['show_status']='YES'; # was NO
What's this do? Just show whether the database thinks a mailbox/alias is in use? If so, yes.
David.
|
|
From: Christian B. <pos...@cb...> - 2012-04-13 23:44:44
|
Hello,
thanks for all the feedback!
I'll take this mail as base for my reply because you were the first to
respond ;-) and commented on all options. My response is summarized for
all mails on this topic.
The summarized votes do _not_ include my personal vote.
BTW: Did I really catch every $CONF option that might need a better
default value? ;-)
Am Freitag, 13. April 2012 schrieb Robert Schetterer:
> Am 13.04.2012 02:04, schrieb Christian Boltz:
> > $CONF['database_type'] = 'mysqli'; # current value: "mysql"
> >
> > should be changed to "mysqli". The reason is simple - I don't expect
> > we have too many users using MySQL < 4.1 nowadays ;-) so using the
> > (newer) mysqli interface by default would make sense.
>
> ACK
That makes a total of +4, which means I'll change this.
>From David's mail:
| Just silently default to mysqli perhaps - i.e. if someone chooses
| 'mysql' they're actually using 'mysqli' ?
I don't really like this idea - maybe there's someone who intentionally
uses the "old" mysql functions for whatever reasons.
Besides that, mysqli doesn't bring noticeable advantages for
postfixadmin besides the "it's newer" argument because we don't use the
additional features it provides.
We should set mysqli as default, but if someone really want to use the
old mysql functions, then I won't stop him ;-)
| We could wrap this in a if(function_exists('mysqli_connect')) or
| something - just incase it's possible to have a php5-mysql installed
| without a php5-mysqli package?
openSUSE 12.1 ships mysqli in the php5-mysql package, but older releases
(please don't ask for a version number) had separate php5-mysql and
php5-mysqli packages IIRC. So it's probably possible to have php5-mysql
without php5-mysqli.
BTW: we already have function_exists() checks in db_connect().
> > $CONF['dovecotpw'] = "/usr/sbin/doveadm pw";
> > # current value: "/usr/sbin/dovecotpw";
> >
> > reason: dovecot 2.x comes with doveadm instead of dovecotpw
>
> ACK
That's +1 (and 3 neutral / no comment), so I'll change it to doveadm pw
(with a comment about dovecotpw for dovecot 1.x)
> > $CONF['domain_path'] = 'YES'; # was NO
> > $CONF['domain_in_mailbox'] = 'NO'; # was YES
> >
> > in other words: domain/username/ instead of username@domain/
> > reason: maybe personal taste ;-)
>
> there might not be a default for all people satisfy
> reading doku stays mandatory
Indeed. Nevertheless we have a total +3 so I'll change it as proposed.
> > $CONF['quota'] = 'YES'; # was NO
> >
> > reason: I'm using quota everywhere - even if I make the mailbox
> > *very* big, just to avoid that a forgotten mailbox can fill up the
> > harddisk.
> NOTACK, using quota isnt so wide spreaded as you think, so stay simple
> default might be better choice
I'm quite surprised by the -4 result ;-) and will of course respect it.
> > $CONF['vacation'] = 'YES'; # was NO
> >
> > why should we hide this feature? ;-)
>
> NOTACK,
That sums up to -1, one neutral and one "we should use sieve", so it
will stay NO.
> vacation is done via sieve ?
No, it's done by the vacation.pl script we ship with postfixadmin.
There's a feature request to use sieve, but nobody implemented it yet.
> > $CONF['alias_control'] = 'YES'; # was NO
> > $CONF['alias_control_admin'] = 'YES'; # was NO
> >
> > I stopped counting how often users asked to implement this feature
> > ;-) so we should enable it by default
>
> OK
Total: +3
> > $CONF['backup'] = 'NO'; # was YES
> >
> > The backup module is basically unmaintained...
>
> then it should stay NO
It is currently YES ;-) which makes a total of +4 for NO.
> > $CONF['show_status']='YES'; # was NO
> >
> > Why should we hide such a nice feature?
> > Note that some of the related options would also need better
> > defaults, but let's first discuss if enabling show_status by
> > default makes sense.
> just forgot what show status means *g
This got +2 and 2 questionmarks ;-)
It displays color markers for several things based on the alias target.
I'll paste from config.inc.php because the explanation there is better
than anything I could write to sum it up ;-)
(Proposals for better default values are welcome ;-)
//set to YES to enable this feature
$CONF['show_status']='NO';
//display a guide to what these colors mean
$CONF['show_status_key']='NO';
// 'show_status_text' will be displayed with the background colors
// associated with each status, you can customize it here
$CONF['show_status_text']=' ';
// show_undeliverable is useful if most accounts are delivered to this
// postfix system. If many aliases and mailboxes are forwarded
// elsewhere, you will probably want to disable this.
$CONF['show_undeliverable']='NO';
$CONF['show_undeliverable_color']='tomato';
// mails to these domains will never be flagged as undeliverable
$CONF['show_undeliverable_exceptions']=array("unixmail.domain.ext","exchangeserver.domain.ext","gmail.com");
$CONF['show_popimap']='NO';
$CONF['show_popimap_color']='darkgrey';
// you can assign special colors to some domains. To do this,
// - add the domain to show_custom_domains
// - add the corresponding color to show_custom_colors
$CONF['show_custom_domains']=array("subdomain.domain.ext","domain2.ext");
$CONF['show_custom_colors']=array("lightgreen","lightblue");
// If you use a recipient_delimiter in your postfix config, you can also
// honor it when aliases are checked.
// Example: $CONF['recipient_delimiter'] = "+";
// Set to "" to disable this check.
$CONF['recipient_delimiter'] = "";
I'd propose the following changes:
$CONF['show_status']='YES'; # was NO
$CONF['show_status_key']='YES'; # was NO
$CONF['show_undeliverable']='YES'; # was NO
$CONF['show_undeliverable_exceptions']=array("unixmail.domain.ext","exchangeserver.domain.ext");
# removed "gmail.com"
$CONF['show_popimap']='YES'; # was NO
> > $CONF['new_quota_table'] = 'YES'; # was NO
> >
> > new quota table format in dovecot 2.x
>
> ACK but depend on quota enable defaults
That makes +2, which also makes it compatible with the changed
$CONF['dovecotpw'] ;-)
If quota support is disabled, it will be ignored regardless of its
value.
>From Johan's mail:
| Dovecot 1 is not really supported any more.
| So if this could be merged into one quota setting that would be
| better.
That would mean dropping support for Dovecot 1.x style quota tables,
which is completely different from changing a default value. I will not
do this as long as it doesn't cause noticeable maintenance work (at the
moment it "just works", so there's no reason to drop it).
> is there a changelog preview by new feature sets ?
CHANGELOG.TXT in svn trunk already lists some changes (until 2011-08),
and the second half is
svn log -r 1166:1367
The "svn log" part might sound funny, but it somehow scares me because
I'll have to read and summarize it. Paperwork... (if someone volunteers
to do it, I'll be more than happy ;-)
Regards,
Christian Boltz
--
Wenn du willst kannst du das so machen, du kannst dir dann aber auch
genausogut mit ner Hilti ein schickes Schaedel-Piercing machen... Das
tut uebrigens auch nur ganz kurz weh... [David Haller in suse-linux]
|
|
From: Sonam P. <s_p...@ru...> - 2012-06-13 13:56:45
Attachments:
postfixadmin-III-review.rar
|
Dear All, Sorry for my late response on the bulk email as I was out of station for nearly a month. Please find attached copies of files for uploading bulk email Id for III review. I would appreciate your comments, suggestions and recommendations to improve my work. Thank you Sonam Penjor |
|
From: Sonam P. <s_p...@ru...> - 2012-06-21 04:06:31
Attachments:
postfixadmin-III-review.zip
|
Dear All, Please find attached copies of files for uploading bulk email Id for III review. I would appreciate your comments, suggestions and recommendations to improve my work. Thank you Sonam Penjor |
|
From: Johnny S. <jo...@so...> - 2012-06-14 21:57:47
Attachments:
signature.asc
|
On Wednesday 13 June 2012 15:33, Sonam Penjor wrote: > postfixadmin-III-review.rar RAR format? Are you serious? If you are using a compression format, use a Free format that everyone can use. RAR is proprietary, and some Linux users, such as myselv, cannot open rar files, so we don't even try. Besides, rar-files are often a sign of virus or trojan horce attack attempts. Many will drop or delete your mail without reading it whenever they encounter rar attachments. -- Johnny A. Solbu web site, http://www.solbu.net PGP key ID: 0xFA687324 ******************************** Kom Arbeidslyst og treng deg på, her skal du motstand finne. |
|
From: Sonam P. <s_p...@ru...> - 2012-06-15 03:02:43
|
// the following javascript codes were from // http://rainbow.arch.scriptmania.com/scripts/preload_wait.html function informProgress( ) { print "<script type='text/javascript' language='javascript'> function processWaitPage() { if (document.getElementById){ document.getElementById('processPage').style.visibility='hidden'; }else{ if (document.layers){ document.prepage.visibility = 'hidden'; } } } </script> <div onload= 'processWaitPage()' id='processPage' style='position:absolute; font-family:arial; font-size:16; left:0px; top:0px; background-color:white; layer-background-color:white; height:100%; width:100%;'> <center><B>Processing.... Please wait!</center> </div>"; } |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X