postfixadmin-tracker Mailing List for PostfixAdmin (Page 27)
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-02-04 12:51:49
|
Bugs item #2859165, was opened at 2009-09-15 12:43 Message generated for change (Comment added) made by ksb4ever You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2859165&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: ksb (ksb4ever) Assigned to: Nobody/Anonymous (nobody) Summary: domain list incorrect SELECT Initial Comment: Hi! 2.3rc7 For me list-domain.php gives an error: DEBUG INFORMATION: Invalid query: ERROR: column "domain.uid" must appear in the GROUP BY clause or be used in an aggregate function So as I have uid and gid columns (used by dovecot) in domain and mailboxes tables (now filled with default values) error comes out. Backend - ppostgresql. # fetch domain data and number of mailboxes # (PgSQL requires the extensive GROUP BY statement, https://sourceforge.net/forum/message.php?msg_id=7386240) $query = " SELECT domain.* , COUNT( DISTINCT mailbox.username ) AS mailbox_count FROM domain LEFT JOIN mailbox ON domain.domain = mailbox.domain $where GROUP BY domain.domain, domain.description, domain.aliases, domain.mailboxes, domain.maxquota, domain.quota, domain.transport, domain.backupmx, domain.created, domain.modified, domain.active ORDER BY domain.domain "; $result = db_query($query); Good comment, yeah ;) but no so good practice to use "SELECT * " even it isn't postgresql and without GROUP BY clause. I think, best way to resove this problem would be exact select of columns! ---------------------------------------------------------------------- >Comment By: ksb (ksb4ever) Date: 2010-02-04 14:51 Message: Bug still exists in 2.3 final! Resolution is easy as 123, exact select on columns. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2859165&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2010-01-31 22:42:57
|
Patches item #2943017, was opened at 2010-01-31 03:20 Message generated for change (Comment added) made by dehalion You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937966&aid=2943017&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: Dehalion (dehalion) Assigned to: Nobody/Anonymous (nobody) Summary: Dovecot SSHA support Initial Comment: Dovecot SSHA encryption is not supported by default because dovecotpw doesn't allow to give a salt for creating a password. I found a PHP function written by chantra at http://coding.debuntu.org/php-how-calculate-ssha-value-string which verifies a given SSHA hash and a plaintext password. This function is used if the password in the database starts with {SSHA} and dovecot is used as encryption type. ---------------------------------------------------------------------- >Comment By: Dehalion (dehalion) Date: 2010-01-31 23:42 Message: I forgot: affected files: only functions.inc.php modified function pacrypt() added function ssha_verify_password() ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937966&aid=2943017&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2010-01-31 02:20:35
|
Patches item #2943017, was opened at 2010-01-31 03:20 Message generated for change (Tracker Item Submitted) made by dehalion You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937966&aid=2943017&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: Dehalion (dehalion) Assigned to: Nobody/Anonymous (nobody) Summary: Dovecot SSHA support Initial Comment: Dovecot SSHA encryption is not supported by default because dovecotpw doesn't allow to give a salt for creating a password. I found a PHP function written by chantra at http://coding.debuntu.org/php-how-calculate-ssha-value-string which verifies a given SSHA hash and a plaintext password. This function is used if the password in the database starts with {SSHA} and dovecot is used as encryption type. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937966&aid=2943017&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2010-01-14 02:02:17
|
Bugs item #2931773, was opened at 2010-01-14 01:58 Message generated for change (Tracker Item Submitted) made by You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2931773&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: W. Rossmann () Assigned to: Nobody/Anonymous (nobody) Summary: No keys in log table Initial Comment: There are no keys defined for the log table, which can make it difficult to manage the data on busier servers where it's just not possible to get even a unique composite key. Two solutions occur to me: 1. Add an autoincremented INT or BIGINT column for a unique ID on each record. 2. Incorporate microtime information into the timestamp, or a separate column The first method would be easiest, as it only requires adding a column. The second is more efficient though as the microtime could be stored in something as small as an UNSIGNED MEDIUMINT, and you never have to worry about running out of AUTOINCREMENT space. The caveat to approach #2 would be that log entries prior to the version incorporating this change would have to be discarded as updating all entries prior with new values unique enough to compute a key would be an exercise in tedium. ie. modifying log entries made in the same second to have different microtime values. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2931773&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2010-01-06 19:47:01
|
Bugs item #2927127, was opened at 2010-01-06 20:47 Message generated for change (Tracker Item Submitted) made by mize You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2927127&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: Michael Zenke (mize) Assigned to: Nobody/Anonymous (nobody) Summary: Entreis in quota-Table not deleted when Mailbox is deleted Initial Comment: If you delete a mailbox it is correctly removed from the mailbox-table. Bu in the quota and quota2 tables the entries remain which may result in incorrect quota-calculation by, in my case dovecot, if you re-add the mailbox. I attach a patch which adds the required lines to delete.php. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2927127&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2010-01-05 20:15:05
|
Patches item #2925620, was opened at 2010-01-04 14:10 Message generated for change (Comment added) made by eirmag You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937966&aid=2925620&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: Open Resolution: None Priority: 1 Private: No Submitted By: Gabriel Serme (eirmag) Assigned to: Nobody/Anonymous (nobody) Summary: password column name in configuration Initial Comment: Sometimes you may want to have multiple columns in your database to store your password, or simply have a different name than "password". The problem is that the column name is hard written in source code. This patch gives you the possibility to change the database password column name for USERS ONLY from the configuration file. Postfixadmin's column password remains "password". The new config name is : "database_password_column_name", and impacted files are config.inc.php and model/UserHandler.php Greetings for this new year, Gabriel ---------------------------------------------------------------------- Comment By: Gabriel Serme (eirmag) Date: 2010-01-05 21:15 Message: No problem, I understand your point and solutions you give are enough to motivate not applying the patch. thanks for both create-mailbox and edit-mailbox. I'll fix it on my version. ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2010-01-05 21:03 Message: Well, my solution would be to ignore the historical reasons and just use the 'password' column ;-) That said: If you are fine with having the same content in the 'password' and 'passcyrpt' column, you can add triggers in your database that update the 'passcrypt' column whenever 'password' is changed. Both MySQL and PostgreSQL support this. Or you can add a view that renames the column at access time (SELECT username, password as passcrypt, ...). BTW: Your patch is incomplete - you'll also have to modify create-mailbox.php and edit-mailbox.php that are used in admin mode... ---------------------------------------------------------------------- Comment By: Gabriel Serme (eirmag) Date: 2010-01-05 16:37 Message: Hi, when I created this patch, it was more for information than for mergin request ;) In fact, I wrote it because I was unable to change the database password column name in postfixadmin. And I made change recently to my postfix/courier configuration from passwords stored in column named "password" to column named "passcrypt". Doing this, I break compatibility with postfixadmin, and for historical reasons I want to keep my column "password". So, to make converge all my authentication in a same place, I modify postfixadmin. Also, modifying postfixadmin files directly wasn't a good optoin for me, so I added the property "database_password_column_name". If you have another solution, let me know. And thx for your reply. Gabriel ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2010-01-05 13:19 Message: Can you please describe _why_ the additional or renamed password column is useful? At the moment I don't see the advantage. OTOH your patch would make upgrades harder because database changes would be applied to the wrong column etc. I'm not totally against merging this patch, but I'd like to know your usecase and reason first. (Maybe we find another solution for your problem, which would be the better way IMHO.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937966&aid=2925620&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2010-01-05 20:03:11
|
Patches item #2925620, was opened at 2010-01-04 14:10 Message generated for change (Comment added) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937966&aid=2925620&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: Open Resolution: None >Priority: 1 Private: No Submitted By: Gabriel Serme (eirmag) Assigned to: Nobody/Anonymous (nobody) Summary: password column name in configuration Initial Comment: Sometimes you may want to have multiple columns in your database to store your password, or simply have a different name than "password". The problem is that the column name is hard written in source code. This patch gives you the possibility to change the database password column name for USERS ONLY from the configuration file. Postfixadmin's column password remains "password". The new config name is : "database_password_column_name", and impacted files are config.inc.php and model/UserHandler.php Greetings for this new year, Gabriel ---------------------------------------------------------------------- >Comment By: Christian Boltz (christian_boltz) Date: 2010-01-05 21:03 Message: Well, my solution would be to ignore the historical reasons and just use the 'password' column ;-) That said: If you are fine with having the same content in the 'password' and 'passcyrpt' column, you can add triggers in your database that update the 'passcrypt' column whenever 'password' is changed. Both MySQL and PostgreSQL support this. Or you can add a view that renames the column at access time (SELECT username, password as passcrypt, ...). BTW: Your patch is incomplete - you'll also have to modify create-mailbox.php and edit-mailbox.php that are used in admin mode... ---------------------------------------------------------------------- Comment By: Gabriel Serme (eirmag) Date: 2010-01-05 16:37 Message: Hi, when I created this patch, it was more for information than for mergin request ;) In fact, I wrote it because I was unable to change the database password column name in postfixadmin. And I made change recently to my postfix/courier configuration from passwords stored in column named "password" to column named "passcrypt". Doing this, I break compatibility with postfixadmin, and for historical reasons I want to keep my column "password". So, to make converge all my authentication in a same place, I modify postfixadmin. Also, modifying postfixadmin files directly wasn't a good optoin for me, so I added the property "database_password_column_name". If you have another solution, let me know. And thx for your reply. Gabriel ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2010-01-05 13:19 Message: Can you please describe _why_ the additional or renamed password column is useful? At the moment I don't see the advantage. OTOH your patch would make upgrades harder because database changes would be applied to the wrong column etc. I'm not totally against merging this patch, but I'd like to know your usecase and reason first. (Maybe we find another solution for your problem, which would be the better way IMHO.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937966&aid=2925620&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2010-01-05 15:37:15
|
Patches item #2925620, was opened at 2010-01-04 14:10 Message generated for change (Comment added) made by eirmag You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937966&aid=2925620&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: Open Resolution: None Priority: 5 Private: No Submitted By: Gabriel Serme (eirmag) Assigned to: Nobody/Anonymous (nobody) Summary: password column name in configuration Initial Comment: Sometimes you may want to have multiple columns in your database to store your password, or simply have a different name than "password". The problem is that the column name is hard written in source code. This patch gives you the possibility to change the database password column name for USERS ONLY from the configuration file. Postfixadmin's column password remains "password". The new config name is : "database_password_column_name", and impacted files are config.inc.php and model/UserHandler.php Greetings for this new year, Gabriel ---------------------------------------------------------------------- Comment By: Gabriel Serme (eirmag) Date: 2010-01-05 16:37 Message: Hi, when I created this patch, it was more for information than for mergin request ;) In fact, I wrote it because I was unable to change the database password column name in postfixadmin. And I made change recently to my postfix/courier configuration from passwords stored in column named "password" to column named "passcrypt". Doing this, I break compatibility with postfixadmin, and for historical reasons I want to keep my column "password". So, to make converge all my authentication in a same place, I modify postfixadmin. Also, modifying postfixadmin files directly wasn't a good optoin for me, so I added the property "database_password_column_name". If you have another solution, let me know. And thx for your reply. Gabriel ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2010-01-05 13:19 Message: Can you please describe _why_ the additional or renamed password column is useful? At the moment I don't see the advantage. OTOH your patch would make upgrades harder because database changes would be applied to the wrong column etc. I'm not totally against merging this patch, but I'd like to know your usecase and reason first. (Maybe we find another solution for your problem, which would be the better way IMHO.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937966&aid=2925620&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2010-01-05 12:19:29
|
Patches item #2925620, was opened at 2010-01-04 14:10 Message generated for change (Comment added) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937966&aid=2925620&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: Open Resolution: None Priority: 5 Private: No Submitted By: Gabriel Serme (eirmag) Assigned to: Nobody/Anonymous (nobody) Summary: password column name in configuration Initial Comment: Sometimes you may want to have multiple columns in your database to store your password, or simply have a different name than "password". The problem is that the column name is hard written in source code. This patch gives you the possibility to change the database password column name for USERS ONLY from the configuration file. Postfixadmin's column password remains "password". The new config name is : "database_password_column_name", and impacted files are config.inc.php and model/UserHandler.php Greetings for this new year, Gabriel ---------------------------------------------------------------------- >Comment By: Christian Boltz (christian_boltz) Date: 2010-01-05 13:19 Message: Can you please describe _why_ the additional or renamed password column is useful? At the moment I don't see the advantage. OTOH your patch would make upgrades harder because database changes would be applied to the wrong column etc. I'm not totally against merging this patch, but I'd like to know your usecase and reason first. (Maybe we find another solution for your problem, which would be the better way IMHO.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937966&aid=2925620&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2010-01-04 13:10:36
|
Patches item #2925620, was opened at 2010-01-04 14:10 Message generated for change (Tracker Item Submitted) made by eirmag You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937966&aid=2925620&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: Open Resolution: None Priority: 5 Private: No Submitted By: Gabriel Serme (eirmag) Assigned to: Nobody/Anonymous (nobody) Summary: password column name in configuration Initial Comment: Sometimes you may want to have multiple columns in your database to store your password, or simply have a different name than "password". The problem is that the column name is hard written in source code. This patch gives you the possibility to change the database password column name for USERS ONLY from the configuration file. Postfixadmin's column password remains "password". The new config name is : "database_password_column_name", and impacted files are config.inc.php and model/UserHandler.php Greetings for this new year, Gabriel ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937966&aid=2925620&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2010-01-02 20:34:37
|
Bugs item #2924880, was opened at 2010-01-02 14:02 Message generated for change (Settings changed) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2924880&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: https://www.google.com/accounts () Assigned to: Nobody/Anonymous (nobody) Summary: quota2 don't show current quota size Initial Comment: Hello, I using quota2 engine in postfixadmin and i muss fixed following problem with display current quota in list-virtual. The Solution is easy. Just rewrite templates/list-virtual.php on line 299 from: print divide_quota ($tMailbox[$i]['current']).'/'; to: print divide_quota ($tMailbox[$i]['bytes']).'/'; Just for information :) thankz bubulak ---------------------------------------------------------------------- >Comment By: Christian Boltz (christian_boltz) Date: 2010-01-02 21:34 Message: This is already fixed in SVN, including other bugfixes since the 2.3 release. If you want to use the fixed version, use the 2.3 branch from SVN (will be released as 2.3.1) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2924880&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2010-01-02 13:02:29
|
Bugs item #2924880, was opened at 2010-01-02 13:02 Message generated for change (Tracker Item Submitted) made by You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2924880&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: https://www.google.com/accounts () Assigned to: Nobody/Anonymous (nobody) Summary: quota2 don't show current quota size Initial Comment: Hello, I using quota2 engine in postfixadmin and i muss fixed following problem with display current quota in list-virtual. The Solution is easy. Just rewrite templates/list-virtual.php on line 299 from: print divide_quota ($tMailbox[$i]['current']).'/'; to: print divide_quota ($tMailbox[$i]['bytes']).'/'; Just for information :) thankz bubulak ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2924880&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-12-29 10:56:59
|
Bugs item #2922730, was opened at 2009-12-29 10:43 Message generated for change (Comment added) made by normes You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2922730&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: Graeme (gruthven) Assigned to: Nobody/Anonymous (nobody) Summary: dpkg complains about script - Debian lenny 5.0.3 Initial Comment: The output below says it all! Passing to package maintainer as requested. web01:/usr/src/postfixadmin# dpkg -i postfixadmin_2.3_all.deb (Reading database ... 20662 files and directories currently installed.) Preparing to replace postfixadmin 2.3 (using postfixadmin_2.3_all.deb) ... Unpacking replacement postfixadmin ... Setting up postfixadmin (2.3) ... dbconfig-common: writing config to /etc/dbconfig-common/postfixadmin.conf *** WARNING: ucf was run from a maintainer script that uses debconf, but the script did not pass --debconf-ok to ucf. The maintainer script should be fixed to not stop debconf before calling ucf, and pass it this parameter. For now, ucf will revert to using old-style, non-debconf prompting. Ugh! Please inform the package maintainer about this problem. ---------------------------------------------------------------------- Comment By: Norman Messtorff (normes) Date: 2009-12-29 11:56 Message: Thank you for reporting! Debconf is also asking the user to really overwrite /etc/postfixadmin/config.inc.php during the installation. I would be glad if somebody could help me in this topic. The debconf / ucf documentation isn't that good... Norman ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2922730&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-12-29 10:19:39
|
Bugs item #2922742, was opened at 2009-12-29 23:18 Message generated for change (Comment added) made by gruthven You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2922742&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: Deleted >Resolution: Duplicate Priority: 5 Private: No Submitted By: Graeme (gruthven) Assigned to: Nobody/Anonymous (nobody) Summary: dpkg complains about script - Debian lenny 5.0.3 Initial Comment: The output below says it all! Passing to package maintainer as requested. web01:/usr/src/postfixadmin# dpkg -i postfixadmin_2.3_all.deb (Reading database ... 20662 files and directories currently installed.) Preparing to replace postfixadmin 2.3 (using postfixadmin_2.3_all.deb) ... Unpacking replacement postfixadmin ... Setting up postfixadmin (2.3) ... dbconfig-common: writing config to /etc/dbconfig-common/postfixadmin.conf *** WARNING: ucf was run from a maintainer script that uses debconf, but the script did not pass --debconf-ok to ucf. The maintainer script should be fixed to not stop debconf before calling ucf, and pass it this parameter. For now, ucf will revert to using old-style, non-debconf prompting. Ugh! Please inform the package maintainer about this problem. ---------------------------------------------------------------------- >Comment By: Graeme (gruthven) Date: 2009-12-29 23:19 Message: Oops. Duplicate... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2922742&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-12-29 10:18:09
|
Bugs item #2922742, was opened at 2009-12-29 23:18 Message generated for change (Tracker Item Submitted) made by gruthven You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2922742&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: Graeme (gruthven) Assigned to: Nobody/Anonymous (nobody) Summary: dpkg complains about script - Debian lenny 5.0.3 Initial Comment: The output below says it all! Passing to package maintainer as requested. web01:/usr/src/postfixadmin# dpkg -i postfixadmin_2.3_all.deb (Reading database ... 20662 files and directories currently installed.) Preparing to replace postfixadmin 2.3 (using postfixadmin_2.3_all.deb) ... Unpacking replacement postfixadmin ... Setting up postfixadmin (2.3) ... dbconfig-common: writing config to /etc/dbconfig-common/postfixadmin.conf *** WARNING: ucf was run from a maintainer script that uses debconf, but the script did not pass --debconf-ok to ucf. The maintainer script should be fixed to not stop debconf before calling ucf, and pass it this parameter. For now, ucf will revert to using old-style, non-debconf prompting. Ugh! Please inform the package maintainer about this problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2922742&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-12-29 09:43:33
|
Bugs item #2922730, was opened at 2009-12-29 22:43 Message generated for change (Tracker Item Submitted) made by gruthven You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2922730&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: Graeme (gruthven) Assigned to: Nobody/Anonymous (nobody) Summary: dpkg complains about script - Debian lenny 5.0.3 Initial Comment: The output below says it all! Passing to package maintainer as requested. web01:/usr/src/postfixadmin# dpkg -i postfixadmin_2.3_all.deb (Reading database ... 20662 files and directories currently installed.) Preparing to replace postfixadmin 2.3 (using postfixadmin_2.3_all.deb) ... Unpacking replacement postfixadmin ... Setting up postfixadmin (2.3) ... dbconfig-common: writing config to /etc/dbconfig-common/postfixadmin.conf *** WARNING: ucf was run from a maintainer script that uses debconf, but the script did not pass --debconf-ok to ucf. The maintainer script should be fixed to not stop debconf before calling ucf, and pass it this parameter. For now, ucf will revert to using old-style, non-debconf prompting. Ugh! Please inform the package maintainer about this problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2922730&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-12-25 00:36:02
|
Bugs item #2918426, was opened at 2009-12-21 04:46 Message generated for change (Comment added) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2918426&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: Fixed Priority: 5 Private: No Submitted By: John Blue (john-blue) Assigned to: Nobody/Anonymous (nobody) Summary: mysql 5.0 type definition TYPE=MyISAM has been superceed Initial Comment: mysql 5.0 type definition TYPE=MyISAM has been superceed in 5.1 and higher by ENGINE=MyISAM ---------------------------------------------------------------------- >Comment By: Christian Boltz (christian_boltz) Date: 2009-12-25 01:36 Message: Unfortunately you didn't specify which version of postfixadmin you use, but it looks like you are using 2.2.1.1 or older which indeed had this bug. The latest release (postfixadmin 2.3) already uses ENGINE= everywhere AFAIK - in case we overlooked something, please reopen this bugreport. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2918426&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-12-21 03:46:05
|
Bugs item #2918426, was opened at 2009-12-20 21:46 Message generated for change (Tracker Item Submitted) made by john-blue You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2918426&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: Open Resolution: None Priority: 5 Private: No Submitted By: John Blue (john-blue) Assigned to: Nobody/Anonymous (nobody) Summary: mysql 5.0 type definition TYPE=MyISAM has been superceed Initial Comment: mysql 5.0 type definition TYPE=MyISAM has been superceed in 5.1 and higher by ENGINE=MyISAM ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2918426&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-12-16 23:13:44
|
Patches item #2915887, was opened at 2009-12-17 00:13 Message generated for change (Tracker Item Submitted) made by jan-kruis You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937966&aid=2915887&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: J.Kruis (jan-kruis) Assigned to: Nobody/Anonymous (nobody) Summary: wrong display Initial Comment: The version 2.4 dev svn #788 display in many cases the code text and not the html also it does not display the languages select menu and the domainname select menu. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937966&aid=2915887&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-12-09 01:00:24
|
Bugs item #2911106, was opened at 2009-12-09 11:57 Message generated for change (Settings changed) made by fukawi-2 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: Open 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. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2911106&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-12-09 00:59:11
|
Bugs item #2911107, was opened at 2009-12-09 11:59 Message generated for change (Tracker Item Submitted) 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. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2911107&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-12-09 00:57:21
|
Bugs item #2911106, was opened at 2009-12-09 11:57 Message generated for change (Tracker Item Submitted) made by fukawi-2 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: Database Group: None Status: Open 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. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2911106&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-12-07 00:24:57
|
Feature Requests item #2909792, was opened at 2009-12-07 01:24 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=2909792&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: drop motd.txt / motd-users.txt Initial Comment: (SVN r783) motd.txt / motd-users.txt should be dropped IMHO. The only thing I always do with them is removing all content ;-) If someone really needs to have something like the motd*.txt, he can still edit the template and insert it there. If someone really wants the motd functionality without template editing, it could be made a $CONF['motd'] setting (default: empty). Depends on the feedback I get here ;-) - please speak up if you want $CONF settings for the motd. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=2909792&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-12-06 21:00:21
|
Feature Requests item #1690316, was opened at 2007-03-28 22:18 Message generated for change (Comment added) made by roe1234 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=1690316&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: 4 Private: No Submitted By: Josh Cheney (sysandnet) Assigned to: Nobody/Anonymous (nobody) Summary: Domain administrator login - use mailbox passwords? Initial Comment: Is there any reason that the domain administrator shouldn't use the mail password associated with that account? I noticed the other day that the password for the domain admin accounts is stored seperately, but still uses an email address for the user name. I would think that it would be simpler for the users (and for the admins) to have the domain admin login use the same password as the mail account. If there is a reason that this has not been done yet, just let me know, otherwise, I can make the change and submit a patch. ---------------------------------------------------------------------- Comment By: Munroe Sollog (roe1234) Date: 2009-12-06 16:00 Message: Security is always going to be a concern. However, I think that adding a checkbox to 'use mailbox credentials' is a valid feature. This feature should probably be off by default with a nice description of the potential dangers and some attack vectors to consider, like force HTTPS, IMAPS/POPS and STARTTLS etc. An alternative would be, when a mailbox user changes his/her password to also update their admin password. This has the same security concerns as above. However, if the domain admin username and the mailbox username is already the same, it isn't a bad assumption to think the passwords are the same, and the security hole already exists. ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2008-01-13 13:58 Message: Logged In: YES user_id=593261 Originator: NO In case we bind the admin password to the mailbox password, we should add a checkbox to create-mailbox: [ ] is admin for $this_domain ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2007-12-30 17:00 Message: Logged In: YES user_id=593261 Originator: NO Good question. My personal opinion is that the passwords should stay separated. Some random thoughts: - we (developers) discussed to always encrypt admin passwords independent of $CONF['encrypt']. This would mean that admin passwords _have to_ be separate. - if admin accounts have separate passwords, they don't necessarily need to use mail addresses as account names. (I often use postmaster@<domain>, but using names like "cboltz" would fit my need better.) This would be an easy change - just remove the syntax check for admin names. Anyway - this is nothing we'll change for 2.2. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=1690316&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-12-06 01:07:45
|
Bugs item #2905599, was opened at 2009-11-29 11:39 Message generated for change (Settings changed) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2905599&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: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: https://www.google.com/accounts () Assigned to: Nobody/Anonymous (nobody) Summary: wapity found XSS in login.php Initial Comment: Penetration tests with Wapity 1.6 found a XSS vulnerability in login.php. Site is running version 2.3. on https. . dani@danici:~$ wapiti https://postfixadmin-server/pfadm Wapiti-1.1.6 (wapiti.sourceforge.net) .... Attacking urls (GET)... ----------------------- Attacking forms (POST)... ------------------------- Found XSS in https://postfixadmin-server/pfadm/users/login.php with params = lang=on&fUsername=%3Cscript%3Evar+wapiti_68747470733a2f2f6272756767652e7479646e65742e6f72672f706661646d2f75736572732f6c6f67696e2e706870_66557365726e616d65%3Dnew+Boolean%28%29%3B%3C%2Fscript%3E&fPassword=on&submit=Login coming from https://postfixadmin-server/pfadm/users/login.php ---------------------------------------------------------------------- >Comment By: Christian Boltz (christian_boltz) Date: 2009-12-06 02:07 Message: IMHO a 2.3 bugfix release (non-smarty) makes sense - there have been some bugfixes since the release. However this is just my opinion - I'll bring up the topic on the -devel mailinglist. ---------------------------------------------------------------------- Comment By: Charles (libertytrek) Date: 2009-12-02 18:26 Message: Thanks! So... will there be ongoing bugfix releases for the 2.3 non-smarty version going forward? Or is the plan for 2.3.1 to be the first smarty based release? ---------------------------------------------------------------------- Comment By: GingerDog (gingerdog) Date: 2009-12-02 14:25 Message: Ah good point Charles; sorry I should have realised that. Patch to do this : Index: login.php =================================================================== --- login.php (revision 782) +++ login.php (working copy) @@ -65,7 +65,7 @@ { $error = 1; $tMessage = '<span class="error_msg">' . $PALANG['pLogin_failed'] . '</span>'; - $tUsername = $fUsername; + $tUsername = htmlentities($fUsername, ENT_QUOTES, 'UTF-8'); } } else (See changeset 783) ---------------------------------------------------------------------- Comment By: Charles (libertytrek) Date: 2009-12-02 12:56 Message: Question... This bug was reported against 2.3 - but 2.3 is NOT a smarty version... There WILL be NON-smarty 2.3.x bugfix releases, right? ---------------------------------------------------------------------- Comment By: GingerDog (gingerdog) Date: 2009-12-02 11:33 Message: Hi, I'll agree this is a bug/security flaw. I had assumed that Smarty would have been configured to escape all output (i.e using something like htmlentities($data, ENT_QUOTES, 'uff-8'); but it hasn't been I've changed the inc.smarty.php file in revision 782 And now I get the following : orange:~ $ wapiti http://orange/david/postfixadmin/trunk Wapiti-1.1.6 (wapiti.sourceforge.net) .... Attacking urls (GET)... ----------------------- Attacking forms (POST)... ------------------------- Looking for permanent XSS ------------------------- Thanks for reporting this; and thanks for making me aware of wapiti - i hadn't come across it before :) ---------------------------------------------------------------------- Comment By: GingerDog (gingerdog) Date: 2009-12-02 11:33 Message: Thanks for the bug report; we believe this has been fixed in subversion. ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2009-11-29 22:30 Message: I just read the code and can't follow you. The only result I get is a message that my username or password is wrong (as expected), but the script tag is not included anywhere AFAIK. Can you give some details how to exploit this without using wapity? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2905599&group_id=191583 |
700 messages has been excluded from this view by a project administrator.
