postfixadmin-tracker Mailing List for PostfixAdmin (Page 26)
Brought to you by:
christian_boltz,
gingerdog
Menu
▾
▴
postfixadmin-tracker — Postfix Admin tracker notification - READ ONLY!
You can subscribe to this list here.
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(5) |
Oct
(67) |
Nov
(83) |
Dec
(47) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2008 |
Jan
(57) |
Feb
(15) |
Mar
(21) |
Apr
(38) |
May
(27) |
Jun
(38) |
Jul
(35) |
Aug
(50) |
Sep
(8) |
Oct
(9) |
Nov
(59) |
Dec
(59) |
| 2009 |
Jan
(27) |
Feb
(42) |
Mar
(63) |
Apr
(46) |
May
(26) |
Jun
(25) |
Jul
(40) |
Aug
(19) |
Sep
(17) |
Oct
(35) |
Nov
(26) |
Dec
(21) |
| 2010 |
Jan
(11) |
Feb
(19) |
Mar
(40) |
Apr
(25) |
May
(23) |
Jun
(17) |
Jul
(10) |
Aug
(18) |
Sep
(21) |
Oct
(12) |
Nov
(10) |
Dec
(22) |
| 2011 |
Jan
(30) |
Feb
(23) |
Mar
(23) |
Apr
(38) |
May
(32) |
Jun
(19) |
Jul
(20) |
Aug
(36) |
Sep
(11) |
Oct
(28) |
Nov
(4) |
Dec
(4) |
| 2012 |
Jan
(6) |
Feb
(3) |
Mar
(16) |
Apr
(28) |
May
(29) |
Jun
(10) |
Jul
(2) |
Aug
(3) |
Sep
|
Oct
(13) |
Nov
(1) |
Dec
(1) |
| 2013 |
Jan
(11) |
Feb
(7) |
Mar
(29) |
Apr
(2) |
May
(3) |
Jun
(15) |
Jul
(8) |
Aug
(5) |
Sep
(5) |
Oct
(4) |
Nov
(27) |
Dec
(81) |
| 2014 |
Jan
(12) |
Feb
(13) |
Mar
(5) |
Apr
|
May
(41) |
Jun
(16) |
Jul
(7) |
Aug
(10) |
Sep
(24) |
Oct
(50) |
Nov
|
Dec
(2) |
| 2015 |
Jan
(5) |
Feb
(2) |
Mar
(7) |
Apr
(20) |
May
(1) |
Jun
(3) |
Jul
(12) |
Aug
(1) |
Sep
(17) |
Oct
(5) |
Nov
(20) |
Dec
(10) |
| 2016 |
Jan
(10) |
Feb
(11) |
Mar
(22) |
Apr
(30) |
May
(33) |
Jun
(3) |
Jul
|
Aug
(12) |
Sep
(20) |
Oct
(11) |
Nov
(15) |
Dec
(8) |
| 2017 |
Jan
(1) |
Feb
(11) |
Mar
(10) |
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(1) |
Nov
|
Dec
(3) |
| 2018 |
Jan
(2) |
Feb
|
Mar
(1) |
Apr
|
May
(4) |
Jun
(2) |
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: SourceForge.net <no...@so...> - 2010-03-09 17:56:02
|
Bugs item #2965196, was opened at 2010-03-07 23:52 Message generated for change (Settings changed) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2965196&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Core Group: SVN (please specify revision!) >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Colin Viebrock (cviebrock) Assigned to: Nobody/Anonymous (nobody) Summary: Superusers can't edit aliases (SVN 2.4) Initial Comment: A typo in the Smarty template, I think. This fixes it: a# svn diff templates/list-virtual_alias.tpl Index: templates/list-virtual_alias.tpl =================================================================== --- templates/list-virtual_alias.tpl (revision 806) +++ templates/list-virtual_alias.tpl (working copy) @@ -20,7 +20,7 @@ <td>{$item.goto|replace:",":"<br/>"}</td> {/if} <td>{$item.modified}</td> - {if $authentication_has_role.global_admin===true} + {if $authentication_has_role.global_admin==true} {assign var="address" value=$item.address|escape:"url"} <td><a href="edit-active.php?alias={$item.address|escape:"url"}&domain={$fDomain|escape:"url"}&return={$file|escape:"url"}?domain={$fDomain|escape:"url"}&limit={$current_limit|escape:"url"}">{if $item.active==1}{$PALANG.YES}{else}{$PALANG.NO}{/if}</a></td> <td><a href="edit-alias.php?address={$item.address|escape:"url"}&domain={$fDomain|escape:"url"}">{$PALANG.edit}</a></td> ---------------------------------------------------------------------- >Comment By: Christian Boltz (christian_boltz) Date: 2010-03-09 18:56 Message: fixed by Sebastian2009 in SVN r807 BTW: Sebastian, you should now have permissions to close tracker items yourself ;-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2965196&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2010-03-08 18:05:07
|
Feature Requests item #2965578, was opened at 2010-03-08 19:05 Message generated for change (Tracker Item Submitted) made by You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=2965578&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Core Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Valkum () Assigned to: Nobody/Anonymous (nobody) Summary: Support pipe througput by adding user defined transport Initial Comment: By adding user defined transport anyone can add postfix' pipe by simply add scriptname in master.cnf. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=2965578&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2010-03-07 22:52:47
|
Bugs item #2965196, was opened at 2010-03-07 17:52 Message generated for change (Tracker Item Submitted) made by cviebrock You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2965196&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Core Group: SVN (please specify revision!) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Colin Viebrock (cviebrock) Assigned to: Nobody/Anonymous (nobody) Summary: Superusers can't edit aliases (SVN 2.4) Initial Comment: A typo in the Smarty template, I think. This fixes it: a# svn diff templates/list-virtual_alias.tpl Index: templates/list-virtual_alias.tpl =================================================================== --- templates/list-virtual_alias.tpl (revision 806) +++ templates/list-virtual_alias.tpl (working copy) @@ -20,7 +20,7 @@ <td>{$item.goto|replace:",":"<br/>"}</td> {/if} <td>{$item.modified}</td> - {if $authentication_has_role.global_admin===true} + {if $authentication_has_role.global_admin==true} {assign var="address" value=$item.address|escape:"url"} <td><a href="edit-active.php?alias={$item.address|escape:"url"}&domain={$fDomain|escape:"url"}&return={$file|escape:"url"}?domain={$fDomain|escape:"url"}&limit={$current_limit|escape:"url"}">{if $item.active==1}{$PALANG.YES}{else}{$PALANG.NO}{/if}</a></td> <td><a href="edit-alias.php?address={$item.address|escape:"url"}&domain={$fDomain|escape:"url"}">{$PALANG.edit}</a></td> ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2965196&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2010-03-02 22:06:15
|
Bugs item #2958684, was opened at 2010-02-25 23:49 Message generated for change (Comment added) made by tabmowtez You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2958684&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 1 Private: No Submitted By: Christian Boltz (christian_boltz) Assigned to: Nobody/Anonymous (nobody) Summary: $CONF['admin_email'] ignored in most cases Initial Comment: [13:42] <mrfrenzy> in the configfile it says // This will be used to send emails from to create mailboxes. [13:42] <mrfrenzy> $CONF['admin_email'] [13:42] <mrfrenzy> however, when I create mailboxes the welcome mail is sent with my username as sender [13:44] <cboltz> indeed. a quick grep shows that it is only used by broadcast-message.php [13:44] <cboltz> the question is which behaviour is better [13:44] <cboltz> a) always use the admin_email sender [13:44] <cboltz> b) drop admin_email and use the admin username [13:44] <cboltz> what would you prefer? ;-) [13:45] <mrfrenzy> it really isn't that important, aslong as the instructions in the config filer are correct [13:46] <mrfrenzy> however. I do think there might be reasons you don't want to tell the users what username your adminuser has [13:46] <cboltz> good argument ;-) [13:47] <cboltz> I'll paste the above lines in the bugtracker... [13:47] <mrfrenzy> I really love this irc based bugtracker submission engine :P ---------------------------------------------------------------------- Comment By: Tabmow (tabmowtez) Date: 2010-03-03 09:06 Message: Well, it is a solution. I guess it depends on what sort of hosting situation we are trying to cater for. If people use postfixadmin to setup client domains, then it is feasible that people that create mailboxes in domain b don't want the welcome message to come from ad...@do.... One way is to have an extra field in the domain table called admin_email possibly? Obviously the $fFrom in create-mailbox.php would change but I see this as a full solution to cater for everyone. If that field is blank then it can resort back to $CONF['admin_email']. Alternatively you can make it a required field moving forward? Thoughts? ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2010-03-03 02:09 Message: Idea: $CONF['admin_email'] = '' -> use the mail address of the logged in admin $CONF['admin_email'] = "fo...@ex..." -> always use fo...@ex... What do you think about this solution? ---------------------------------------------------------------------- Comment By: Tabmow (tabmowtez) Date: 2010-03-02 15:52 Message: Quick change in create-mailbox.php should fix this. --- create-mailbox.php 2009-04-07 05:54:11.000000000 +1000 +++ /usr/local/www/postfixadmin/create-mailbox.php 2010-03-02 15:48:26.000000000 +1100 @@ -230,7 +230,7 @@ if ($fMail == "on") { $fTo = $fUsername; - $fFrom = $SESSID_USERNAME; + $fFrom = $CONF['admin_email']; $fHeaders = "To: " . $fTo . "\n"; $fHeaders .= "From: " . $fFrom . "\n"; Might be possible to add another config option and being able to define an address as well? Possible a per domain address? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2958684&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2010-03-02 15:18:47
|
Bugs item #2958698, was opened at 2010-02-25 14:29 Message generated for change (Comment added) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2958698&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Core Group: v 2.3 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Pierre Fagrell (mrfrenzy) Assigned to: Nobody/Anonymous (nobody) Summary: Generated passwords are all lowercase and ignore passlength Initial Comment: Autogenerated passwords are all lowercase and 8 characters long regardless of $CONF['min_password_length']. Attached patch creates a password equal in lenght to min_password_length, using numbers, upper and lowercase letters. ---------------------------------------------------------------------- >Comment By: Christian Boltz (christian_boltz) Date: 2010-03-02 16:18 Message: Thanks for the patch. Unfortunately I get an error message when applying it: patch: **** unexpected end of file in patch at line 49 Can you please re-attach it in unified format (diff -u)? BTW: I'd prefer to make the parameter of generate_password optional instead of changing each file that calls it, but that are details ;-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2958698&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2010-03-02 15:09:01
|
Bugs item #2958684, was opened at 2010-02-25 13:49 Message generated for change (Comment added) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2958684&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 1 Private: No Submitted By: Christian Boltz (christian_boltz) Assigned to: Nobody/Anonymous (nobody) Summary: $CONF['admin_email'] ignored in most cases Initial Comment: [13:42] <mrfrenzy> in the configfile it says // This will be used to send emails from to create mailboxes. [13:42] <mrfrenzy> $CONF['admin_email'] [13:42] <mrfrenzy> however, when I create mailboxes the welcome mail is sent with my username as sender [13:44] <cboltz> indeed. a quick grep shows that it is only used by broadcast-message.php [13:44] <cboltz> the question is which behaviour is better [13:44] <cboltz> a) always use the admin_email sender [13:44] <cboltz> b) drop admin_email and use the admin username [13:44] <cboltz> what would you prefer? ;-) [13:45] <mrfrenzy> it really isn't that important, aslong as the instructions in the config filer are correct [13:46] <mrfrenzy> however. I do think there might be reasons you don't want to tell the users what username your adminuser has [13:46] <cboltz> good argument ;-) [13:47] <cboltz> I'll paste the above lines in the bugtracker... [13:47] <mrfrenzy> I really love this irc based bugtracker submission engine :P ---------------------------------------------------------------------- >Comment By: Christian Boltz (christian_boltz) Date: 2010-03-02 16:09 Message: Idea: $CONF['admin_email'] = '' -> use the mail address of the logged in admin $CONF['admin_email'] = "fo...@ex..." -> always use fo...@ex... What do you think about this solution? ---------------------------------------------------------------------- Comment By: Tabmow (tabmowtez) Date: 2010-03-02 05:52 Message: Quick change in create-mailbox.php should fix this. --- create-mailbox.php 2009-04-07 05:54:11.000000000 +1000 +++ /usr/local/www/postfixadmin/create-mailbox.php 2010-03-02 15:48:26.000000000 +1100 @@ -230,7 +230,7 @@ if ($fMail == "on") { $fTo = $fUsername; - $fFrom = $SESSID_USERNAME; + $fFrom = $CONF['admin_email']; $fHeaders = "To: " . $fTo . "\n"; $fHeaders .= "From: " . $fFrom . "\n"; Might be possible to add another config option and being able to define an address as well? Possible a per domain address? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2958684&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2010-03-02 04:52:36
|
Bugs item #2958684, was opened at 2010-02-25 23:49 Message generated for change (Comment added) made by tabmowtez You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2958684&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 1 Private: No Submitted By: Christian Boltz (christian_boltz) Assigned to: Nobody/Anonymous (nobody) Summary: $CONF['admin_email'] ignored in most cases Initial Comment: [13:42] <mrfrenzy> in the configfile it says // This will be used to send emails from to create mailboxes. [13:42] <mrfrenzy> $CONF['admin_email'] [13:42] <mrfrenzy> however, when I create mailboxes the welcome mail is sent with my username as sender [13:44] <cboltz> indeed. a quick grep shows that it is only used by broadcast-message.php [13:44] <cboltz> the question is which behaviour is better [13:44] <cboltz> a) always use the admin_email sender [13:44] <cboltz> b) drop admin_email and use the admin username [13:44] <cboltz> what would you prefer? ;-) [13:45] <mrfrenzy> it really isn't that important, aslong as the instructions in the config filer are correct [13:46] <mrfrenzy> however. I do think there might be reasons you don't want to tell the users what username your adminuser has [13:46] <cboltz> good argument ;-) [13:47] <cboltz> I'll paste the above lines in the bugtracker... [13:47] <mrfrenzy> I really love this irc based bugtracker submission engine :P ---------------------------------------------------------------------- Comment By: Tabmow (tabmowtez) Date: 2010-03-02 15:52 Message: Quick change in create-mailbox.php should fix this. --- create-mailbox.php 2009-04-07 05:54:11.000000000 +1000 +++ /usr/local/www/postfixadmin/create-mailbox.php 2010-03-02 15:48:26.000000000 +1100 @@ -230,7 +230,7 @@ if ($fMail == "on") { $fTo = $fUsername; - $fFrom = $SESSID_USERNAME; + $fFrom = $CONF['admin_email']; $fHeaders = "To: " . $fTo . "\n"; $fHeaders .= "From: " . $fFrom . "\n"; Might be possible to add another config option and being able to define an address as well? Possible a per domain address? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2958684&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2010-02-25 13:33:18
|
Bugs item #2958698, was opened at 2010-02-25 14:29 Message generated for change (Settings changed) made by mrfrenzy You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2958698&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Core >Group: v 2.3 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Pierre Fagrell (mrfrenzy) Assigned to: Nobody/Anonymous (nobody) Summary: Generated passwords are all lowercase and ignore passlength Initial Comment: Autogenerated passwords are all lowercase and 8 characters long regardless of $CONF['min_password_length']. Attached patch creates a password equal in lenght to min_password_length, using numbers, upper and lowercase letters. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2958698&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2010-02-25 13:32:28
|
Bugs item #2958684, was opened at 2010-02-25 13:49 Message generated for change (Tracker Item Submitted) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2958684&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 1 Private: No Submitted By: Christian Boltz (christian_boltz) Assigned to: Nobody/Anonymous (nobody) Summary: $CONF['admin_email'] ignored in most cases Initial Comment: [13:42] <mrfrenzy> in the configfile it says // This will be used to send emails from to create mailboxes. [13:42] <mrfrenzy> $CONF['admin_email'] [13:42] <mrfrenzy> however, when I create mailboxes the welcome mail is sent with my username as sender [13:44] <cboltz> indeed. a quick grep shows that it is only used by broadcast-message.php [13:44] <cboltz> the question is which behaviour is better [13:44] <cboltz> a) always use the admin_email sender [13:44] <cboltz> b) drop admin_email and use the admin username [13:44] <cboltz> what would you prefer? ;-) [13:45] <mrfrenzy> it really isn't that important, aslong as the instructions in the config filer are correct [13:46] <mrfrenzy> however. I do think there might be reasons you don't want to tell the users what username your adminuser has [13:46] <cboltz> good argument ;-) [13:47] <cboltz> I'll paste the above lines in the bugtracker... [13:47] <mrfrenzy> I really love this irc based bugtracker submission engine :P ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2958684&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2010-02-25 13:29:56
|
Bugs item #2958698, was opened at 2010-02-25 14:29 Message generated for change (Tracker Item Submitted) made by mrfrenzy You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2958698&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Core Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Pierre Fagrell (mrfrenzy) Assigned to: Nobody/Anonymous (nobody) Summary: Generated passwords are all lowercase and ignore passlength Initial Comment: Autogenerated passwords are all lowercase and 8 characters long regardless of $CONF['min_password_length']. Attached patch creates a password equal in lenght to min_password_length, using numbers, upper and lowercase letters. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2958698&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2010-02-22 21:42:25
|
Bugs item #2956766, was opened at 2010-02-22 22:42 Message generated for change (Tracker Item Submitted) made by fenio You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2956766&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: v 2.3 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Bartosz Feński (fenio) Assigned to: Nobody/Anonymous (nobody) Summary: wrong dependencies in deb package Initial Comment: Currently postfixadmin depends on: apache2 | lighttpd It should depend on httpd meta package. There's no need to use apache nor lighttpd. All you need is WWW server and php5. I use it with nginx for example. Please add httpd dependency so it would be apache2 | lighttpd | httpd regards fEnIo ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2956766&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2010-02-21 16:06:13
|
Bugs item #2951471, was opened at 2010-02-14 05:54 Message generated for change (Comment added) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2951471&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Database Group: v 2.3 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Uwe Walter (uwalter) Assigned to: Nobody/Anonymous (nobody) Summary: Table prefix issue fixed Initial Comment: Found that the table_by_key() function on the second call only returns the table_prefix. Patch attached ---------------------------------------------------------------------- >Comment By: Christian Boltz (christian_boltz) Date: 2010-02-21 17:06 Message: Well, I'm not that strict on paperworks ;-) You found an interesting[tm] bug, but I'll use a different fix. The problem is IMHO not that table_by_key is called twice for a table (I would hopefully notice that because I use a table_prefix in my test environment since some time). I don't like the "called twice" check because it might cause funny problems - think of a prefix "mail", which will also match the "mailbox" table and leave it without prefix. The real bug (in trunk) is: table_by_key returned only the $CONF[database_prefix] if a table was unknown in $CONF[database_tables] and $CONF[database_prefix] was not empty. -> fixed in SVN r804 (for trunk) 2.3 has a slightly different bug - it does not prepend the database_prefix if a table is not listed in database_tables. I'll probably not fix this in the 2.3 branch - even if it gives wrong results, it is consistent. Fixing it would break compatibility ;-) Another thing you mention in your patch's README: > Consider a real DAU noob, thinking he was just a bit smarter than all the other > ones, setting a table_prefix containing cryptic special chars. Under MySQL > this is not a problem, because you can simply `back tick`, respectively > name-quote them, but not so under PostgreSQL. Here I would consider a plpgsql > function, building the table name. My favorite quote on this is: Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. Basically your comment is correct - but with a crazy prefix, setup.php will fail already and the admin will hopefully choose another one that is more sane. Yes, we could add a function to handle such crazy prefixes or table names, but - it adds lots of complexity with no real value for 99.9% of the users - it will never catch _all_ special chars, so it can't be called a real fix (which is the main reason why I'm against it) The only thing I would accept is checking table names and the prefix against a character whitelist (maybe [a-zA-Z0-9_-] - which other chars should be allowed?) and die() if anything else is included. > Greetings from Mainz! Greetings from Insheim (near Landau) :-) ---------------------------------------------------------------------- Comment By: Uwe Walter (uwalter) Date: 2010-02-14 06:12 Message: I'm so sorry, just saw that here's a patch section also. Would you please be so kind and move this ticket there. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2951471&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2010-02-21 14:53:22
|
Bugs item #2911106, was opened at 2009-12-09 01:57 Message generated for change (Comment added) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2911106&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface (example) Group: None >Status: Closed >Resolution: Out of Date Priority: 5 Private: No Submitted By: Phillip Smith (fukawi-2) Assigned to: Nobody/Anonymous (nobody) Summary: [patch] fetchmail.php domain list for superadmins broken Initial Comment: In fetchmail.php, the dropdown to select the account to deliver mail to doesn't work correctly for superadmins. Fixed and patch attached. ---------------------------------------------------------------------- >Comment By: Christian Boltz (christian_boltz) Date: 2010-02-21 15:53 Message: Philipp wrote in bug 2911107 that he uses 2.2.1.1 (my question here should have been about postfix_admin_ obviously...) Therefore I'm closing this bug as fixed - please reopen if you still see this problem with postfixadmin 2.3. ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2010-02-14 01:04 Message: Which version of postfix do you use? If I get it right, this should already be fixed in the 2.3 release. See also https://sourceforge.net/tracker/index.php?func=detail&aid=2147740&group_id=191583&atid=937964 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2911106&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2010-02-21 14:49:52
|
Bugs item #2911107, was opened at 2009-12-09 01:59 Message generated for change (Comment added) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2911107&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Out of Date Priority: 5 Private: No Submitted By: Phillip Smith (fukawi-2) Assigned to: Nobody/Anonymous (nobody) Summary: [patch] fetchmail.pl invalid SQL syntax for PostgreSQL Initial Comment: The SQL syntax used in fetchmail.pl is invalid for PostgreSQL databases. Fixed and patch attached. Patch also passes explicit fetchmailrc filename to fetchmail to ensure it finds the correct file. ---------------------------------------------------------------------- >Comment By: Christian Boltz (christian_boltz) Date: 2010-02-21 15:49 Message: Yes, you should really update ;-) I'm closing this bug for now - please reopen if you still see this problem in 2.3. ---------------------------------------------------------------------- Comment By: Phillip Smith (fukawi-2) Date: 2010-02-14 06:28 Message: I'm not sure why I have 2.2.1.1.... I thought it was the latest, but I only installed late last year :-/ I guess I can upgrade and you can ignore me :) ---------------------------------------------------------------------- Comment By: Phillip Smith (fukawi-2) Date: 2010-02-14 06:27 Message: Postfix Admin 2.2.1.1 ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2010-02-14 01:11 Message: Same question here - which version of postfixadmin are you using? This issue should also be fixed in the 2.3 release, see https://sourceforge.net/tracker/?func=detail&atid=937966&aid=2747526&group_id=191583 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2911107&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2010-02-18 12:29:43
|
Feature Requests item #1839070, was opened at 2007-11-27 00:52 Message generated for change (Comment added) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=1839070&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Core Group: SVN (please specify revision!) >Status: Closed >Resolution: Fixed Priority: 3 Private: No Submitted By: Christian Boltz (christian_boltz) Assigned to: Nobody/Anonymous (nobody) Summary: wrap templates into functions Initial Comment: Template files should be renamed to *.php to avoid that they are downloadable from any postfixadmin installation. Initially suggested by Jan Örnstedt (ornstedt) in http://sourceforge.net/tracker/index.php?func=detail&aid=1838327&group_id=191583&atid=937964 Note: When we do this, we also have to add a check for a constant (not: variable) and exit if it is not set. Something like "define postfixadmin=1" in common.php. Reason: Otherwise attackers could execute the templates and maybe do unexpected things with them. Note 2: Ideally, all template code should be wrapped into functions. This allows better control of global variable usage. ---------------------------------------------------------------------- >Comment By: Christian Boltz (christian_boltz) Date: 2010-02-18 13:29 Message: The remaining part (wrap templates into functions for better control on global variables) was solved by switching to smarty templates in the meantime. Therefore I consider this request as implemented. ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2007-12-02 20:23 Message: Logged In: YES user_id=593261 Originator: YES GingerDog renamed the template files in the meanwhile. A security check against direct access to the templates is needed, because with *.php template files an attacker is able to find out the path of your postfixadmin installation ("Undefined variable: PALANG in /path/to/postfixadmin/templates/users_vacation.php on line 25") which makes things worse than before :-( I just prepended all template files with (as one line) <?php if( !defined('POSTFIXADMIN') ) die( "This file cannot be used standalone." ); ?> and added define('POSTFIXADMIN', 1); to common.php. Commited to SVN r256 Advantage over checking $_SERVER or another variable: Constants can't be injected via register_globals. The remaining part in this feature request is "wrap all templates into functions" - updating the summary... ---------------------------------------------------------------------- Comment By: Jan Örnstedt (ornstedt) Date: 2007-11-27 14:32 Message: Logged In: YES user_id=498787 Originator: NO Borrowed from another project... /** * security check to prevent hackers from directly accessing this file */ if (strstr($_SERVER["SCRIPT_NAME"],"sendmail.php")) { print "Why do you want to do that?"; exit; } And a .htaccess file order allow,deny deny from all Cheers Jan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=1839070&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2010-02-18 12:18:18
|
Feature Requests item #2903088, was opened at 2009-11-24 13:49 Message generated for change (Comment added) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=2903088&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface Improvements (example) Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: J.Kruis (jan-kruis) Assigned to: Nobody/Anonymous (nobody) Summary: css file depending on language Initial Comment: Is it possible to select a different css file depending on the language a user or admin selects during login? I think that this is improving the interface because the amount of caracters depend on the language, for instance in my language dutch many of the tabpositions are to small so that words are spread over two lines in stead of one line in the englisch language. It would be nice to have the oppurtunity to change a css file depending on the choice of language. ---------------------------------------------------------------------- >Comment By: Christian Boltz (christian_boltz) Date: 2010-02-18 13:18 Message: Thinking about it, there are two options: a) $CONF['theme_css'] = css/@LANG@.css b) a class in the body tag, like <body class="lang-en"> - could then be used as ".lang-en table {...}" in the CSS file IMHO b) would be the better way because most styles are shared between all languages, but I'm open for feedback. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=2903088&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2010-02-18 12:11:42
|
Feature Requests item #2954151, was opened at 2010-02-18 13:11 Message generated for change (Tracker Item Submitted) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=2954151&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface Improvements (example) Group: SVN (please specify revision!) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Christian Boltz (christian_boltz) Assigned to: Nobody/Anonymous (nobody) Summary: config option: always_send_welcome_mail Initial Comment: mrfrenzy asked on IRC to have a $CONF option to hide the "send welcome mail" checkbox and _always_ send the welcome mail. Background/Reason: sometimes his users/admins disable the checkbox, and afterwards complain that courier denies the login to the mailbox until they received a mail. For the records: a workaround is to edit the template and replace the checkbox with a <hidden> form field. Not too nice, but works. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=2954151&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2010-02-14 05:28:51
|
Bugs item #2911107, was opened at 2009-12-09 11:59 Message generated for change (Comment added) made by fukawi-2 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2911107&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Phillip Smith (fukawi-2) Assigned to: Nobody/Anonymous (nobody) Summary: [patch] fetchmail.pl invalid SQL syntax for PostgreSQL Initial Comment: The SQL syntax used in fetchmail.pl is invalid for PostgreSQL databases. Fixed and patch attached. Patch also passes explicit fetchmailrc filename to fetchmail to ensure it finds the correct file. ---------------------------------------------------------------------- >Comment By: Phillip Smith (fukawi-2) Date: 2010-02-14 16:28 Message: I'm not sure why I have 2.2.1.1.... I thought it was the latest, but I only installed late last year :-/ I guess I can upgrade and you can ignore me :) ---------------------------------------------------------------------- Comment By: Phillip Smith (fukawi-2) Date: 2010-02-14 16:27 Message: Postfix Admin 2.2.1.1 ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2010-02-14 11:11 Message: Same question here - which version of postfixadmin are you using? This issue should also be fixed in the 2.3 release, see https://sourceforge.net/tracker/?func=detail&atid=937966&aid=2747526&group_id=191583 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2911107&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2010-02-14 05:27:35
|
Bugs item #2911107, was opened at 2009-12-09 11:59 Message generated for change (Comment added) made by fukawi-2 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2911107&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Open Resolution: None Priority: 5 Private: No Submitted By: Phillip Smith (fukawi-2) Assigned to: Nobody/Anonymous (nobody) Summary: [patch] fetchmail.pl invalid SQL syntax for PostgreSQL Initial Comment: The SQL syntax used in fetchmail.pl is invalid for PostgreSQL databases. Fixed and patch attached. Patch also passes explicit fetchmailrc filename to fetchmail to ensure it finds the correct file. ---------------------------------------------------------------------- >Comment By: Phillip Smith (fukawi-2) Date: 2010-02-14 16:27 Message: Postfix Admin 2.2.1.1 ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2010-02-14 11:11 Message: Same question here - which version of postfixadmin are you using? This issue should also be fixed in the 2.3 release, see https://sourceforge.net/tracker/?func=detail&atid=937966&aid=2747526&group_id=191583 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2911107&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2010-02-14 05:12:36
|
Bugs item #2951471, was opened at 2010-02-14 05:54 Message generated for change (Comment added) made by uwalter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2951471&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Database Group: v 2.3 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Uwe Walter (uwalter) Assigned to: Nobody/Anonymous (nobody) Summary: Table prefix issue fixed Initial Comment: Found that the table_by_key() function on the second call only returns the table_prefix. Patch attached ---------------------------------------------------------------------- >Comment By: Uwe Walter (uwalter) Date: 2010-02-14 06:12 Message: I'm so sorry, just saw that here's a patch section also. Would you please be so kind and move this ticket there. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2951471&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2010-02-14 04:54:53
|
Bugs item #2951471, was opened at 2010-02-14 05:54 Message generated for change (Tracker Item Submitted) made by uwalter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2951471&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Database Group: v 2.3 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Uwe Walter (uwalter) Assigned to: Nobody/Anonymous (nobody) Summary: Table prefix issue fixed Initial Comment: Found that the table_by_key() function on the second call only returns the table_prefix. Patch attached ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2951471&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2010-02-14 00:27:15
|
Bugs item #2909334, was opened at 2009-12-05 17:06 Message generated for change (Comment added) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2909334&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface (example) Group: v 2.3 Status: Open Resolution: None Priority: 5 Private: No Submitted By: ololo (fly-away) Assigned to: Nobody/Anonymous (nobody) Summary: seems to be alias_control in postfixadmin 2.3 broken Initial Comment: postfixadmin 2.3, php-5.3.1, mysql 5.0.77 Now I set all 3 params to YES: $CONF['alias_control'] = 'YES'; $CONF['alias_control_admin'] = 'YES'; $CONF['special_alias_control'] = 'YES'; and still cant see forward in 'Virtual list' BTW, I can see it in search output. ---------------------------------------------------------------------- >Comment By: Christian Boltz (christian_boltz) Date: 2010-02-14 01:27 Message: I assume you are talking about the aliases of mailboxes. This is fixed in trunk (r751 and r787) and will be backported to the 2.3 branch (which will be released as 2.3.1). The mailbox list will have an additional column with the alias target. I'll keep this bug open until I merged the change into the 2.3 branch. Search output is another story - historically search is handled by a seperate script (search.php), but it will be merged into list-virtual.php. The code for this is mostly in place since r751. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2909334&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2010-02-14 00:11:21
|
Bugs item #2911107, was opened at 2009-12-09 01:59 Message generated for change (Comment added) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2911107&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Pending Resolution: None Priority: 5 Private: No Submitted By: Phillip Smith (fukawi-2) Assigned to: Nobody/Anonymous (nobody) Summary: [patch] fetchmail.pl invalid SQL syntax for PostgreSQL Initial Comment: The SQL syntax used in fetchmail.pl is invalid for PostgreSQL databases. Fixed and patch attached. Patch also passes explicit fetchmailrc filename to fetchmail to ensure it finds the correct file. ---------------------------------------------------------------------- >Comment By: Christian Boltz (christian_boltz) Date: 2010-02-14 01:11 Message: Same question here - which version of postfixadmin are you using? This issue should also be fixed in the 2.3 release, see https://sourceforge.net/tracker/?func=detail&atid=937966&aid=2747526&group_id=191583 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2911107&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2010-02-14 00:04:46
|
Bugs item #2911106, was opened at 2009-12-09 01:57 Message generated for change (Comment added) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2911106&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface (example) Group: None >Status: Pending Resolution: None Priority: 5 Private: No Submitted By: Phillip Smith (fukawi-2) Assigned to: Nobody/Anonymous (nobody) Summary: [patch] fetchmail.php domain list for superadmins broken Initial Comment: In fetchmail.php, the dropdown to select the account to deliver mail to doesn't work correctly for superadmins. Fixed and patch attached. ---------------------------------------------------------------------- >Comment By: Christian Boltz (christian_boltz) Date: 2010-02-14 01:04 Message: Which version of postfix do you use? If I get it right, this should already be fixed in the 2.3 release. See also https://sourceforge.net/tracker/index.php?func=detail&aid=2147740&group_id=191583&atid=937964 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2911106&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2010-02-12 00:27:30
|
Feature Requests item #2950139, was opened at 2010-02-12 01:27 Message generated for change (Tracker Item Submitted) made by toomuchcookies You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=2950139&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface Improvements (example) Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: toomuchcookies (toomuchcookies) Assigned to: Nobody/Anonymous (nobody) Summary: subfolder delivery option Initial Comment: Postfix's 'virtual' delivery process is able to deliver emails to a subfolder of a maildir, if one instructs it to do that. For that purpose 'maildir' has to look like '/var/vmail/domain/user/.subfolder/'. This is usefull for extension based email sorting obviously (letting a mailing list send you emails at user-subfolder@domain). BUT virtual doesn't look for a .forward-... file (which the other delivery process 'local' does). Instead postfix searches for the full email address (avec extension) and in the case it doesn't find it looks for the email address without the extension. So writing a simple line into the mailbox-table that contains the email address user-subfolder@domain and the maildir /domain/user/.subfolder/ would actually do the job. I think it would be nice to have a feature implemented that enables users (or at least admins) to add extension based subfolder-delivery to their mail delivery. While we're at it, we could have a general domain-based option that would enable postfix to autocreate subfolders in maildirs. A simple column 'autofolder' could be parsed in the postfix query to determine, if extension-based automatic subfolders would be generated (i admit, this could be a security issue). Here is a postfix query, that i'm using to get the job done at the moment (having added the 'autofolder' manually). First it tries to find the exact email address with the extension. When it doesn't find it, it looks at 'autofolder'. If 'autofolder' is <>'1' then it will not instruct postfix to autodeliver to a subfolder, but rather returns the standard folder for this mailbox (sans extension). If 'autofolder' is '1', then the query would build a folderstructure with the extension(s) as subfolder(s). Hope you like! SELECT COALESCE ( (SELECT maildir from mailbox where username='%s' and active=1), (SELECT IF ( (SELECT count(*) from domain where domain = SUBSTRING_INDEX( '%s', '@',-1) and active=1 and autofolder=1)>0, NULL, (SELECT maildir FROM mailbox WHERE username= CONCAT( SUBSTRING_INDEX( SUBSTRING_INDEX( '%s', '@', 1), '+',1), '@', SUBSTRING_INDEX( '%s', '@',-1)) AND active=1) )), (SELECT CONCAT( (SELECT maildir FROM mailbox WHERE username= CONCAT( SUBSTRING_INDEX( SUBSTRING_INDEX( '%s', '@', 1), '+',1), '@', SUBSTRING_INDEX( '%s', '@',-1)) AND active=1), (SELECT CONCAT( '.', REPLACE(SUBSTRING('%s',LOCATE('+','%s')+1,(SELECT '%s' REGEXP '\\+') * LOCATE('@','%s')-LOCATE('+','%s')-1),'+','/.'), '/') ) )) ) as maildir ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=2950139&group_id=191583 |
700 messages has been excluded from this view by a project administrator.
