postfixadmin-tracker Mailing List for PostfixAdmin (Page 45)
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...> - 2008-11-12 14:03:20
|
Bugs item #2221002, was opened at 2008-11-04 13:49 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2221002&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: Fixed Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: VARCHAR alias,goto Initial Comment: It is possible to increase varchar in table alias, field goto ? Thanks, a lot of our customers need more than 255 for alias e-mail. Bye ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-11-12 14:03 Message: Thanks for this fix :) ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2008-11-06 22:10 Message: Good catch - the goto field should never have changed to varchar :-( Fixed in SVN r473. ---------------------------------------------------------------------- Comment By: GingerDog (gingerdog) Date: 2008-11-06 08:47 Message: Hi, Ideally it would remain a varchar field, and the table would be re-organised to have a proper relational model - i.e. address -> alias, goto; alias, goto etc Instead of being separated by commas. Anyway, interestingly enough, my local postfix database has alias.goto as a text field; and it is initially created as this in the upgrade.php file. However, having said this, the last update Christian made sets it to be a varchar(255). Have we gotten out of sync somewhere? ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-11-04 13:51 Message: Sorry, we forgot something, maybe it is possible to change this field in text format ? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2221002&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-11-12 09:17:32
|
Bugs item #2265333, was opened at 2008-11-11 23:09 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2265333&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: 8 Private: No Submitted By: Christian Boltz (christian_boltz) Assigned to: Nobody/Anonymous (nobody) Summary: "ssl" is a reserved word in mysql - breaks fetchmail Initial Comment: (SVN r476) The "ssl" field in the fetchmail table causes an "invalid query" error message in MySQL because "ssl" is a reserved word. Options: a) quote the field name b) rename the field a) would be the better solution, but needs to be tested against PgSQL. @GingerDog: Does the following query (with field names in backtick quotes) work in PgSQL? SELECT `id`,`mailbox`,`src_server`,`src_auth`, `src_user`,`src_password`,`src_folder`,`poll_time`, `fetchall`,`keep`,`protocol`,`ssl`,`extra_options`, `mda`,`date`,`returned_text` FROM fetchmail order by id desc This bug affects everything around fetchmail. If we go for a), we need to change - the queries in fetchmail.php - maybe fetchmail.pl - some db_* functions in functions.php ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-11-12 09:17 Message: FWIW, my preference would be to rename the field, as it's bound to cause problems later on if it needs quoting all the time. e.g. s/ssl/use_ssl/ ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-11-12 09:16 Message: I don't think PostgreSQL likes back ticks (I certainly don't anyway). I believe you "escape" key words using double quotes - like "ssl". ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2265333&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-11-12 09:16:45
|
Bugs item #2265333, was opened at 2008-11-11 23:09 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2265333&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: 8 Private: No Submitted By: Christian Boltz (christian_boltz) Assigned to: Nobody/Anonymous (nobody) Summary: "ssl" is a reserved word in mysql - breaks fetchmail Initial Comment: (SVN r476) The "ssl" field in the fetchmail table causes an "invalid query" error message in MySQL because "ssl" is a reserved word. Options: a) quote the field name b) rename the field a) would be the better solution, but needs to be tested against PgSQL. @GingerDog: Does the following query (with field names in backtick quotes) work in PgSQL? SELECT `id`,`mailbox`,`src_server`,`src_auth`, `src_user`,`src_password`,`src_folder`,`poll_time`, `fetchall`,`keep`,`protocol`,`ssl`,`extra_options`, `mda`,`date`,`returned_text` FROM fetchmail order by id desc This bug affects everything around fetchmail. If we go for a), we need to change - the queries in fetchmail.php - maybe fetchmail.pl - some db_* functions in functions.php ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-11-12 09:16 Message: I don't think PostgreSQL likes back ticks (I certainly don't anyway). I believe you "escape" key words using double quotes - like "ssl". ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2265333&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-11-11 23:09:28
|
Bugs item #2265333, was opened at 2008-11-12 00:09 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2265333&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: 8 Private: No Submitted By: Christian Boltz (christian_boltz) Assigned to: Nobody/Anonymous (nobody) Summary: "ssl" is a reserved word in mysql - breaks fetchmail Initial Comment: (SVN r476) The "ssl" field in the fetchmail table causes an "invalid query" error message in MySQL because "ssl" is a reserved word. Options: a) quote the field name b) rename the field a) would be the better solution, but needs to be tested against PgSQL. @GingerDog: Does the following query (with field names in backtick quotes) work in PgSQL? SELECT `id`,`mailbox`,`src_server`,`src_auth`, `src_user`,`src_password`,`src_folder`,`poll_time`, `fetchall`,`keep`,`protocol`,`ssl`,`extra_options`, `mda`,`date`,`returned_text` FROM fetchmail order by id desc This bug affects everything around fetchmail. If we go for a), we need to change - the queries in fetchmail.php - maybe fetchmail.pl - some db_* functions in functions.php ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2265333&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-11-11 22:02:06
|
Bugs item #2025263, was opened at 2008-07-23 03:18 Message generated for change (Comment added) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2025263&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: Vacation Group: v 2.2 >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: vacation_notification is never updated Initial Comment: According to the table relations, a "on delete cascade" from vacation to vacation_notification should remove all records in vacation_notification of people who have received an away message once the vacation message is disabled. Since in v2.2, the actual message entry in vacation is never really deleted but rather set to active=0, the "delete on cascade" is never triggered, and the notification records stay in the table. This means that once vacation is enabled (e.g. Christmas), disabled (January), and re-enabled (Easter), no new vacation messages get sent during Easter to people who received one already for Christmas. Can this be fixed with another trigger? Thanks, ach...@qu... ---------------------------------------------------------------------- >Comment By: Christian Boltz (christian_boltz) Date: 2008-11-11 23:02 Message: finally marking as fixed ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-08-07 00:03 Message: Logged In: NO This has been solved in <http://sourceforge.net/forum/forum.php?thread_id=2129163&forum_id=676076> and the patch was submitted to SVN r432. update edit-vacation.php from: // retain vacation message if possible - i.e disable vacation away-ness. $result = db_query ("UPDATE $table_vacation SET active = $db_false WHERE email='$fUsername'"); $result = db_query ("SELECT * FROM $table_alias WHERE address='$fUsername'"); to: // retain vacation message if possible - i.e disable vacation away-ness. $result = db_query ("UPDATE $table_vacation SET active = $db_false WHERE email='$fUsername'"); $result = db_query("DELETE FROM $table_vacation_notification WHERE on_vacation='$fUsername'"); $result = db_query ("SELECT * FROM $table_alias WHERE address='$fUsername'"); ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2025263&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-11-06 23:08:04
|
Bugs item #2221002, was opened at 2008-11-04 14:49 Message generated for change (Settings changed) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2221002&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: Fixed Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: VARCHAR alias,goto Initial Comment: It is possible to increase varchar in table alias, field goto ? Thanks, a lot of our customers need more than 255 for alias e-mail. Bye ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2008-11-06 23:10 Message: Good catch - the goto field should never have changed to varchar :-( Fixed in SVN r473. ---------------------------------------------------------------------- Comment By: GingerDog (gingerdog) Date: 2008-11-06 09:47 Message: Hi, Ideally it would remain a varchar field, and the table would be re-organised to have a proper relational model - i.e. address -> alias, goto; alias, goto etc Instead of being separated by commas. Anyway, interestingly enough, my local postfix database has alias.goto as a text field; and it is initially created as this in the upgrade.php file. However, having said this, the last update Christian made sets it to be a varchar(255). Have we gotten out of sync somewhere? ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-11-04 14:51 Message: Sorry, we forgot something, maybe it is possible to change this field in text format ? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2221002&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-11-06 22:10:27
|
Bugs item #2221002, was opened at 2008-11-04 14: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=2221002&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: Fixed Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: VARCHAR alias,goto Initial Comment: It is possible to increase varchar in table alias, field goto ? Thanks, a lot of our customers need more than 255 for alias e-mail. Bye ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2008-11-06 23:10 Message: Good catch - the goto field should never have changed to varchar :-( Fixed in SVN r473. ---------------------------------------------------------------------- Comment By: GingerDog (gingerdog) Date: 2008-11-06 09:47 Message: Hi, Ideally it would remain a varchar field, and the table would be re-organised to have a proper relational model - i.e. address -> alias, goto; alias, goto etc Instead of being separated by commas. Anyway, interestingly enough, my local postfix database has alias.goto as a text field; and it is initially created as this in the upgrade.php file. However, having said this, the last update Christian made sets it to be a varchar(255). Have we gotten out of sync somewhere? ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-11-04 14:51 Message: Sorry, we forgot something, maybe it is possible to change this field in text format ? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2221002&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-11-06 22:09:30
|
Bugs item #2221002, was opened at 2008-11-04 14:49 Message generated for change (Settings changed) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2221002&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: Fixed Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: VARCHAR alias,goto Initial Comment: It is possible to increase varchar in table alias, field goto ? Thanks, a lot of our customers need more than 255 for alias e-mail. Bye ---------------------------------------------------------------------- Comment By: GingerDog (gingerdog) Date: 2008-11-06 09:47 Message: Hi, Ideally it would remain a varchar field, and the table would be re-organised to have a proper relational model - i.e. address -> alias, goto; alias, goto etc Instead of being separated by commas. Anyway, interestingly enough, my local postfix database has alias.goto as a text field; and it is initially created as this in the upgrade.php file. However, having said this, the last update Christian made sets it to be a varchar(255). Have we gotten out of sync somewhere? ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-11-04 14:51 Message: Sorry, we forgot something, maybe it is possible to change this field in text format ? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2221002&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-11-06 08:49:28
|
Bugs item #2209340, was opened at 2008-10-30 09:01 Message generated for change (Comment added) made by gingerdog You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2209340&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.2 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: "invalid parameter" when deleting an alias Initial Comment: on the Admin interface, when I try to delete an alias, I've got the message "invalid parameter". ---------------------------------------------------------------------- >Comment By: GingerDog (gingerdog) Date: 2008-11-06 08:49 Message: works for me; what version of postfixadmin are you using? ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-10-30 09:08 Message: By the way, my email for responses : b.l...@is... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2209340&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-11-06 08:47:38
|
Bugs item #2221002, was opened at 2008-11-04 13:49 Message generated for change (Comment added) made by gingerdog You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2221002&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: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: VARCHAR alias,goto Initial Comment: It is possible to increase varchar in table alias, field goto ? Thanks, a lot of our customers need more than 255 for alias e-mail. Bye ---------------------------------------------------------------------- >Comment By: GingerDog (gingerdog) Date: 2008-11-06 08:47 Message: Hi, Ideally it would remain a varchar field, and the table would be re-organised to have a proper relational model - i.e. address -> alias, goto; alias, goto etc Instead of being separated by commas. Anyway, interestingly enough, my local postfix database has alias.goto as a text field; and it is initially created as this in the upgrade.php file. However, having said this, the last update Christian made sets it to be a varchar(255). Have we gotten out of sync somewhere? ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-11-04 13:51 Message: Sorry, we forgot something, maybe it is possible to change this field in text format ? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2221002&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-11-04 13:51:55
|
Bugs item #2221002, was opened at 2008-11-04 13:49 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2221002&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: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: VARCHAR alias,goto Initial Comment: It is possible to increase varchar in table alias, field goto ? Thanks, a lot of our customers need more than 255 for alias e-mail. Bye ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-11-04 13:51 Message: Sorry, we forgot something, maybe it is possible to change this field in text format ? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2221002&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-11-04 13:49:23
|
Bugs item #2221002, was opened at 2008-11-04 13:49 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2221002&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: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: VARCHAR alias,goto Initial Comment: It is possible to increase varchar in table alias, field goto ? Thanks, a lot of our customers need more than 255 for alias e-mail. Bye ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2221002&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-11-03 08:40:19
|
Feature Requests item #2214522, was opened at 2008-11-01 19:34 Message generated for change (Comment added) made by gingerdog You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=2214522&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: Christian Boltz (christian_boltz) Assigned to: Nobody/Anonymous (nobody) Summary: configuration in /etc/mail/postfixadmin for all scripts Initial Comment: Having to edit a script just to change a path or the database login details isn't the best solution. Instead, all scripts should have a configfile in /etc/mail/postfixadmin/ All scripts should still contain useful default values which are used if the config file doesn't exist. This affects: - vacation.pl (done) - postfixadmin-domain-postdeletion.sh, postfixadmin-mailbox-postcreation.sh, postfixadmin-mailbox-postdeletion.sh (basedir, trashbase, PATH) - fetchmail.pl I'm thinking about config.local.php as an exception - if we move it to /etc, the webserver needs read permissions there - which I'd like to avoid. (And it's not unusual for web apps to have a configfile in the same directory as all PHP files.) ---------------------------------------------------------------------- >Comment By: GingerDog (gingerdog) Date: 2008-11-03 08:40 Message: I'm fairly sure Debian has a /etc/squirrelmail (for example) that contains the actual .php script. They then have a symlink in e.g /usr/share/squirrelmail/ pointing to the file in /etc/ To me, this is the best option, as people tend to backup /etc with e.g. tar -zcf etc.tar.gz /etc and assume they've caught all config files. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=2214522&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-11-01 20:19:15
|
Feature Requests item #1951926, was opened at 2008-04-25 23:38 Message generated for change (Comment added) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=1951926&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: show_custom_colors - several enhancements Initial Comment: (SVN r343) (Combined to a single item because it affects one code section. Can be splitted as needed later.) While upgrading a production server to the latest SVN version (aka 2.2rc5), I found some things that show_custom_colors could do better: (1) $CONF['show_undeliverable'] shows a) aliases with non-existing local target b) aliases pointing to an external address which may cause some confusion. This should be splitted to $CONF['show_undeliverable'] for a) $CONF['show_external_alias'] for b) (We could also change "possible undeliverable" to "undeliverable".) (2) $CONF['vacation_domain'] should be in $CONF['show_undeliverable_exceptions'] by default (3) $CONF['show_status_key']='YES' shows all possible markers. I'd like to have the option to only show the _used_ markers to avoid displaying too many items (4) $CONF['vacation_domain'] should be part of $CONF['show_custom_domains']. It would be even better if it had an own setting (like $CONF['show_vacation_status']) which would allow a better description text than "delivery to autoreply.domain" (5) It should be possible to specify custom legend texts per domain in $CONF['show_custom_domains']. This could cover the special vacation marker I described above, as well as other cases. The custom legend texts should support two methods: a) static text, could also come from lang/* $text = "foobar"; b) array with translations, with fallback to "default" $text = array( 'default' => 'english text', 'de' => 'german text'); (6) $CONF['show_custom_count'] can be dropped - just use count($CONF['show_custom_domains']) instead. (7) A marker for mailboxes with non-default alias would also be helpful. ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2008-11-01 21:19 Message: (6) is done in SVN r471 ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2008-04-26 01:39 Message: Logged In: YES user_id=593261 Originator: YES (8) Postfix supports a recipient_delimiter (usually "+") which allows to specify some type of parameter to a mail adress. An example would be fo...@ex..., which delivers to the fo...@ex... mailbox. Currently a mail with fo...@ex... is tagged as undeliverable even if the fo...@ex... mailbox exists. Proposal: $CONF['recipient_delimiter'] = "+"; (or "" to disable) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=1951926&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-11-01 19:34:16
|
Feature Requests item #2214522, was opened at 2008-11-01 20:34 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=2214522&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: Christian Boltz (christian_boltz) Assigned to: Nobody/Anonymous (nobody) Summary: configuration in /etc/mail/postfixadmin for all scripts Initial Comment: Having to edit a script just to change a path or the database login details isn't the best solution. Instead, all scripts should have a configfile in /etc/mail/postfixadmin/ All scripts should still contain useful default values which are used if the config file doesn't exist. This affects: - vacation.pl (done) - postfixadmin-domain-postdeletion.sh, postfixadmin-mailbox-postcreation.sh, postfixadmin-mailbox-postdeletion.sh (basedir, trashbase, PATH) - fetchmail.pl I'm thinking about config.local.php as an exception - if we move it to /etc, the webserver needs read permissions there - which I'd like to avoid. (And it's not unusual for web apps to have a configfile in the same directory as all PHP files.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=2214522&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-10-31 10:29:17
|
Bugs item #1990191, was opened at 2008-06-10 23:12 Message generated for change (Settings changed) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1990191&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.2 >Status: Closed >Resolution: Fixed Priority: 8 Private: No Submitted By: Jon Kristian Nilsen (jonkristian) Assigned to: Nobody/Anonymous (nobody) Summary: Illegal mix of collations Initial Comment: DEBUG INFORMATION: Invalid query: Illegal mix of collations (latin1_general_ci,IMPLICIT) and (latin1_swedish_ci,IMPLICIT) for operation '=' In virtual-list.php , it's a bug in upgrade.php see attached patch. ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2008-10-31 11:28 Message: Finally found some time to fix this (sorry for the long delay!). All VARCHAR and TEXT fields now have the same charset and collation. Fixed in SVN r469 Run setup.php if you need to fix your database. ---------------------------------------------------------------------- Comment By: Harry Morgan (harrymorgan) Date: 2008-08-06 21:30 Message: Logged In: YES user_id=2171233 Originator: NO Invalid query: Illegal mix of collations (cp1251_general_ci,IMPLICIT) and (latin1_swedish_ci,IMPLICIT) for operation '=' ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-08-06 21:26 Message: Logged In: NO virtual-list.php DEBUG INFORMATION: Invalid query: Illegal mix of collations (cp1251_general_ci,IMPLICIT) and (latin1_swedish_ci,IMPLICIT) for operation '=' Please check the documentation and website for more information. ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2008-06-15 18:18 Message: Logged In: YES user_id=593261 Originator: NO I checked the 2.1 release again and found out that there was no collation specified in the MySQL dump. This means that the collation 2.1 users have in their database depends on the local MySQL settings. >From the postfixadmin point of view, we can just call it "random"... I'll add a fix to upgrade.php in the next days. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-06-11 09:06 Message: Logged In: NO Why is latin1_swedish_ci used instead of latin1_general_ci anyway? ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2008-06-11 01:52 Message: Logged In: YES user_id=593261 Originator: NO It isn't that easy (because your patch would break upgrades) and changing from latin1_swedish_ci to latin1_general_ci doesn't make a real difference, so I tend to reject your patch. However, let's wait what we find out in the forum thread where this bug report came from: https://sourceforge.net/forum/forum.php?thread_id=2039397&forum_id=676076 (The question is where the latin1_general_ci field is hidden / comes from ;-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1990191&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-10-31 10:28:23
|
Bugs item #1990191, was opened at 2008-06-10 23:12 Message generated for change (Comment added) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1990191&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.2 Status: Open Resolution: None Priority: 8 Private: No Submitted By: Jon Kristian Nilsen (jonkristian) Assigned to: Nobody/Anonymous (nobody) Summary: Illegal mix of collations Initial Comment: DEBUG INFORMATION: Invalid query: Illegal mix of collations (latin1_general_ci,IMPLICIT) and (latin1_swedish_ci,IMPLICIT) for operation '=' In virtual-list.php , it's a bug in upgrade.php see attached patch. ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2008-10-31 11:28 Message: Finally found some time to fix this (sorry for the long delay!). All VARCHAR and TEXT fields now have the same charset and collation. Fixed in SVN r469 Run setup.php if you need to fix your database. ---------------------------------------------------------------------- Comment By: Harry Morgan (harrymorgan) Date: 2008-08-06 21:30 Message: Logged In: YES user_id=2171233 Originator: NO Invalid query: Illegal mix of collations (cp1251_general_ci,IMPLICIT) and (latin1_swedish_ci,IMPLICIT) for operation '=' ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-08-06 21:26 Message: Logged In: NO virtual-list.php DEBUG INFORMATION: Invalid query: Illegal mix of collations (cp1251_general_ci,IMPLICIT) and (latin1_swedish_ci,IMPLICIT) for operation '=' Please check the documentation and website for more information. ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2008-06-15 18:18 Message: Logged In: YES user_id=593261 Originator: NO I checked the 2.1 release again and found out that there was no collation specified in the MySQL dump. This means that the collation 2.1 users have in their database depends on the local MySQL settings. >From the postfixadmin point of view, we can just call it "random"... I'll add a fix to upgrade.php in the next days. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-06-11 09:06 Message: Logged In: NO Why is latin1_swedish_ci used instead of latin1_general_ci anyway? ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2008-06-11 01:52 Message: Logged In: YES user_id=593261 Originator: NO It isn't that easy (because your patch would break upgrades) and changing from latin1_swedish_ci to latin1_general_ci doesn't make a real difference, so I tend to reject your patch. However, let's wait what we find out in the forum thread where this bug report came from: https://sourceforge.net/forum/forum.php?thread_id=2039397&forum_id=676076 (The question is where the latin1_general_ci field is hidden / comes from ;-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1990191&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-10-30 09:08:25
|
Bugs item #2209340, was opened at 2008-10-30 09:01 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2209340&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.2 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: "invalid parameter" when deleting an alias Initial Comment: on the Admin interface, when I try to delete an alias, I've got the message "invalid parameter". ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-10-30 09:08 Message: By the way, my email for responses : b.l...@is... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2209340&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-10-30 09:01:14
|
Bugs item #2209340, was opened at 2008-10-30 09:01 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2209340&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.2 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: "invalid parameter" when deleting an alias Initial Comment: on the Admin interface, when I try to delete an alias, I've got the message "invalid parameter". ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2209340&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-10-23 22:27:40
|
Feature Requests item #2190501, was opened at 2008-10-24 00:27 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=2190501&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: SVN (please specify revision!) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Christian Boltz (christian_boltz) Assigned to: Nobody/Anonymous (nobody) Summary: Superadmin should not be able to delete or disable himself Initial Comment: A superadmin should not be able to shoot himself in the foot^W^W^W^W^Wdelete or disable himself (in the list/edit admin section) because this will lock him out of postfixadmin. This can be done by a) not showing the delete link for the currently logged in superadmin b) like a, but at server side before deleting the admin c) while editing an admin, unchecking the superadmin checkbox should be impossible for the currently logged in superadmin d) c) should also be checked server-side ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=2190501&group_id=191583 |
|
From: Web U. <ww...@us...> - 2008-10-07 02:20:53
|
Bugs item #1908702, was opened at 2008-03-06 11:44 Message generated for change (Comment added) made by sf-robot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1908702&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: Closed Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: problem with login.php Initial Comment: User cannot log into system if 'session_regenerate_id();' exists in login.php, after comment this like everything works ok. ---------------------------------------------------------------------- >Comment By: SourceForge Robot (sf-robot) Date: 2008-10-07 02:20 Message: This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2008-09-22 22:46 Message: You are the only one who reported this error, and I also can't reproduce it myself. Please provide more details. Most important: what error message do you see? Which version of postfixadmin do you use? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1908702&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-10-05 12:44:27
|
Bugs item #2147740, was opened at 2008-10-05 12:43 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2147740&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.2 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Holger Ackermann (hoacker) Assigned to: Nobody/Anonymous (nobody) Summary: Superadmin can't create new "fetch email" Initial Comment: Postfixadmin 2.2.1.1 Super admin can only create "fetch email" for himself and not for other mailboxes. Reason: In sql table "domain_admins" the domain "ALL" ist the only domain listed for the super admin. Function "list_domains_for_admins()" in functions.inc.php returns "ALL" for super admins. The sql query in "fetchmail.php" then expands to "SELECT username FROM mailbox WHERE domain in ('ALL')". This query returns no result as there is no domain "ALL". ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2147740&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-10-03 08:31:10
|
Bugs item #2143861, was opened at 2008-10-03 08:06 Message generated for change (Comment added) made by gingerdog You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2143861&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: SVN (please specify revision!) >Status: Closed >Resolution: Accepted Priority: 5 Private: No Submitted By: Fabio Bonelli (fabiobon) Assigned to: Nobody/Anonymous (nobody) Summary: Always use $CONF['transport_default'] as transport Initial Comment: If $CONF['transport'] is 'NO', postfixadmin will always insert 'virtual' as transport into the domain table, even if we set $CONF['transport_default'] to something different. Patch attached. ---------------------------------------------------------------------- >Comment By: GingerDog (gingerdog) Date: 2008-10-03 08:31 Message: Hi, see changeset 463; thank you! (Patch merged etc) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2143861&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-10-03 08:06:50
|
Bugs item #2143861, was opened at 2008-10-03 10:06 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2143861&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: SVN (please specify revision!) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Fabio Bonelli (fabiobon) Assigned to: Nobody/Anonymous (nobody) Summary: Always use $CONF['transport_default'] as transport Initial Comment: If $CONF['transport'] is 'NO', postfixadmin will always insert 'virtual' as transport into the domain table, even if we set $CONF['transport_default'] to something different. Patch attached. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2143861&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-09-22 22:49:27
|
Bugs item #2021578, was opened at 2008-07-18 18:00 Message generated for change (Comment added) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2021578&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: None >Status: Closed Resolution: Duplicate Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: latin1_swedish_ci used only in swedish Initial Comment: upgrade.php brokes database when collation is not swedish. ---------------------------------------------------------------------- >Comment By: Christian Boltz (christian_boltz) Date: 2008-09-23 00:49 Message: This is a duplicate of https://sourceforge.net/tracker/index.php?func=detail&aid=1990191&group_id=191583&atid=937964 (The link given by gingerdog was refering to this tracker item.) ---------------------------------------------------------------------- Comment By: GingerDog (gingerdog) Date: 2008-07-19 00:06 Message: Logged In: YES user_id=1761957 Originator: NO I'm fairly sure this is fixed in the branches/postfixadmin-2.2.1, which probably needs beta releasing/packaging. ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2008-07-18 23:04 Message: Logged In: YES user_id=593261 Originator: NO Known bug, see https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2021578&group_id=191583 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2021578&group_id=191583 |
700 messages has been excluded from this view by a project administrator.
