postfixadmin-tracker Mailing List for PostfixAdmin (Page 34)
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...> - 2009-06-29 07:59:16
|
Bugs item #2796067, was opened at 2009-05-24 12:51 Message generated for change (Settings changed) made by gingerdog You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2796067&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: None >Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Christian Boltz (christian_boltz) Assigned to: Nobody/Anonymous (nobody) Summary: Vacation (nearly) always uses /tmp/vacation.log as logfile Initial Comment: vacation.pl uses /tmp/vacation.log if the given $logfile does not yet exist. The problem: There's a check if ( ! -w $logfile ) { $logfile = "/tmp/vacation.log"; } The -w check will return false if $logfile does not exist. This means that nearly all installations will log to /tmp/vacation.log - at least I doubt that many people create $logfile manually. The correct solution would be - check if $logfile exists - if yes, check if it is writeable (aka current code) - if no, check if the _directory_ of $logfile is writeable, and create the logfile If everything fails, write "can't open logfile $logfile" to syslog. The automatic fallback to /tmp/vacation.log also introduces the risk of symlink attacks, therefore I'd prefer if this fallback was completely removed. (Thanks to my AppArmor log for pointing out this bug ;-) ---------------------------------------------------------------------- Comment By: GingerDog (gingerdog) Date: 2009-06-29 07:59 Message: fixed in revision 677 ---------------------------------------------------------------------- Comment By: GingerDog (gingerdog) Date: 2009-06-29 07:59 Message: Thanks for the bug report; we believe this has been fixed in subversion. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2796067&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-06-29 07:59:07
|
Bugs item #2796067, was opened at 2009-05-24 12:51 Message generated for change (Comment added) made by gingerdog You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2796067&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: None Status: Open >Resolution: Fixed Priority: 5 Private: No Submitted By: Christian Boltz (christian_boltz) Assigned to: Nobody/Anonymous (nobody) Summary: Vacation (nearly) always uses /tmp/vacation.log as logfile Initial Comment: vacation.pl uses /tmp/vacation.log if the given $logfile does not yet exist. The problem: There's a check if ( ! -w $logfile ) { $logfile = "/tmp/vacation.log"; } The -w check will return false if $logfile does not exist. This means that nearly all installations will log to /tmp/vacation.log - at least I doubt that many people create $logfile manually. The correct solution would be - check if $logfile exists - if yes, check if it is writeable (aka current code) - if no, check if the _directory_ of $logfile is writeable, and create the logfile If everything fails, write "can't open logfile $logfile" to syslog. The automatic fallback to /tmp/vacation.log also introduces the risk of symlink attacks, therefore I'd prefer if this fallback was completely removed. (Thanks to my AppArmor log for pointing out this bug ;-) ---------------------------------------------------------------------- >Comment By: GingerDog (gingerdog) Date: 2009-06-29 07:59 Message: fixed in revision 677 ---------------------------------------------------------------------- Comment By: GingerDog (gingerdog) Date: 2009-06-29 07:59 Message: Thanks for the bug report; we believe this has been fixed in subversion. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2796067&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-06-28 21:16:00
|
Bugs item #2809905, was opened at 2009-06-21 17:23 Message generated for change (Comment added) made by normes You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2809905&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: Filipe Fagundes (piovisqui) Assigned to: Nobody/Anonymous (nobody) Summary: .deb package resquest the removal of mysql server Initial Comment: I have download the postfixadmin_2.3_RC5_all.deb on Ubuntu 9.04. When I asked the install the package requires the REMOVAL of mysql server 5.1 and mysql client 5.1 and the installation of mysql client 5.0. It does not ask the install of mysql server 5.0. I downloaded RC4 and it installed successful. ---------------------------------------------------------------------- Comment By: Norman Messtorff (normes) Date: 2009-06-28 23:15 Message: I'll check this behaviour in a fresh Ubuntu 9.04 environment the next days. We could have this issue in Ubuntu and possible Debian too, but i can't see the problem at first view. ---------------------------------------------------------------------- Comment By: GingerDog (gingerdog) Date: 2009-06-22 12:11 Message: the dependency on wwwconfig-common is now not an issue; the debian control file doesn't specify any version requirements for mysql/postgresql, so i'm not sure why you'd get these problem(s). ---------------------------------------------------------------------- Comment By: Bjorn (bjornnilsen) Date: 2009-06-22 02:14 Message: The dependancies on this latest deb are very restrictive and have caused issues for me as well. The new wwwconfig-common dependency means that this deb is no longer supported with Ubuntu 8.04. $ sudo dpkg -i postfixadmin_2.3rc5_all.deb Selecting previously deselected package postfixadmin. (Reading database ... 25961 files and directories currently installed.) Unpacking postfixadmin (from postfixadmin_2.3rc5_all.deb) ... dpkg: dependency problems prevent configuration of postfixadmin: postfixadmin depends on wwwconfig-common (>= 0.2.0); however: Version of wwwconfig-common on system is 0.0.48. dpkg: error processing postfixadmin (--install): dependency problems - leaving unconfigured Errors were encountered while processing: postfixadmin ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2809905&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-06-27 12:49:22
|
Feature Requests item #2813224, was opened at 2009-06-27 08:49 Message generated for change (Tracker Item Submitted) made by libertytrek You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=2813224&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: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Charles (libertytrek) Assigned to: Nobody/Anonymous (nobody) Summary: End user customization of header strings Initial Comment: Hi all, I've been meaning to post this FR for a while... How hard would it be to provide the ability to configure the header strings that the vacation.pl script uses to determine when NOT to send a vacation auto-response? For example, in ASSP (also a perl script), in the GUI interface, it has options that have a textbox that can take either a reference to a file - ie, file:filename, where each line in the file would be a different string, or just a comma separated list of strings... (see attached for an example of how this looks in the ASSP GUI) This way, non-programmers like myself would have the ability to adjust these values, and add to (or subtract from) them, without having to resort to trying to edit the actual vacation.pl script. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=2813224&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-06-27 12:41:14
|
Feature Requests item #2813178, was opened at 2009-06-27 05:46 Message generated for change (Comment added) made by libertytrek You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=2813178&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: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Stevan Bajic (sbajic) Assigned to: Nobody/Anonymous (nobody) Summary: More flexible vacation module regarding mailsever definition Initial Comment: The currently used Mail::sendmail module is very limited regarding the configuration of SMTP server data. You can't define: - SMTP port - SMTP username - SMTP password - SMTP authentication I am using Postfix as my MTA and using virtual vacation is a no-go for me since I do sender mismatch checking and with the currently used Mail::sendmail in virtual vacation I can use virtual vacation on my setup. I would like to replace the Mail::sendmail module with Mail::Sender which is offering much more flexibility then Mail::sendmail. Should I send a patch to virtual vacation v4 using Mail::Sender for sending mails? Is the above mentioned functionality useful for other people? How high are the chances to get such a patch merged into Postfix.Admin? ---------------------------------------------------------------------- Comment By: Charles (libertytrek) Date: 2009-06-27 08:41 Message: Can't you just override the sender_mismatch restriction for the vacation service? Or maybe you can't do that with pipes? Anyway, this sounds good... thanks for the contrib, Steve! ---------------------------------------------------------------------- Comment By: GingerDog (gingerdog) Date: 2009-06-27 07:31 Message: Cool. Thanks for the quick reply. I'm no perl pro, so I'm sure much could be improved. I hadn't heard of mail::sender before either. Keep the patches coming, will try and read/merge this evening ---------------------------------------------------------------------- Comment By: Stevan Bajic (sbajic) Date: 2009-06-27 07:04 Message: Hallo David Here a very quick shot of a patch. From my viewpoint many things could be made better. The whole enconding part could be made less depended on external modules since Mail::Sender has them built in. I will anyway post the patch but work later on it to make it more flexible. Kind Regards from Switzerland Steve ---------------------------------------------------------------------- Comment By: GingerDog (gingerdog) Date: 2009-06-27 06:51 Message: Hi, yes I'm more than happy to see a patch, and would almost certainly merge it thanks David ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=2813178&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-06-27 11:31:20
|
Feature Requests item #2813178, was opened at 2009-06-27 09:46 Message generated for change (Comment added) made by gingerdog You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=2813178&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: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Stevan Bajic (sbajic) Assigned to: Nobody/Anonymous (nobody) Summary: More flexible vacation module regarding mailsever definition Initial Comment: The currently used Mail::sendmail module is very limited regarding the configuration of SMTP server data. You can't define: - SMTP port - SMTP username - SMTP password - SMTP authentication I am using Postfix as my MTA and using virtual vacation is a no-go for me since I do sender mismatch checking and with the currently used Mail::sendmail in virtual vacation I can use virtual vacation on my setup. I would like to replace the Mail::sendmail module with Mail::Sender which is offering much more flexibility then Mail::sendmail. Should I send a patch to virtual vacation v4 using Mail::Sender for sending mails? Is the above mentioned functionality useful for other people? How high are the chances to get such a patch merged into Postfix.Admin? ---------------------------------------------------------------------- >Comment By: GingerDog (gingerdog) Date: 2009-06-27 11:31 Message: Cool. Thanks for the quick reply. I'm no perl pro, so I'm sure much could be improved. I hadn't heard of mail::sender before either. Keep the patches coming, will try and read/merge this evening ---------------------------------------------------------------------- Comment By: Stevan Bajic (sbajic) Date: 2009-06-27 11:04 Message: Hallo David Here a very quick shot of a patch. From my viewpoint many things could be made better. The whole enconding part could be made less depended on external modules since Mail::Sender has them built in. I will anyway post the patch but work later on it to make it more flexible. Kind Regards from Switzerland Steve ---------------------------------------------------------------------- Comment By: GingerDog (gingerdog) Date: 2009-06-27 10:51 Message: Hi, yes I'm more than happy to see a patch, and would almost certainly merge it thanks David ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=2813178&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-06-27 11:04:36
|
Feature Requests item #2813178, was opened at 2009-06-27 11:46 Message generated for change (Comment added) made by sbajic You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=2813178&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: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Stevan Bajic (sbajic) Assigned to: Nobody/Anonymous (nobody) Summary: More flexible vacation module regarding mailsever definition Initial Comment: The currently used Mail::sendmail module is very limited regarding the configuration of SMTP server data. You can't define: - SMTP port - SMTP username - SMTP password - SMTP authentication I am using Postfix as my MTA and using virtual vacation is a no-go for me since I do sender mismatch checking and with the currently used Mail::sendmail in virtual vacation I can use virtual vacation on my setup. I would like to replace the Mail::sendmail module with Mail::Sender which is offering much more flexibility then Mail::sendmail. Should I send a patch to virtual vacation v4 using Mail::Sender for sending mails? Is the above mentioned functionality useful for other people? How high are the chances to get such a patch merged into Postfix.Admin? ---------------------------------------------------------------------- >Comment By: Stevan Bajic (sbajic) Date: 2009-06-27 13:04 Message: Hallo David Here a very quick shot of a patch. From my viewpoint many things could be made better. The whole enconding part could be made less depended on external modules since Mail::Sender has them built in. I will anyway post the patch but work later on it to make it more flexible. Kind Regards from Switzerland Steve ---------------------------------------------------------------------- Comment By: GingerDog (gingerdog) Date: 2009-06-27 12:51 Message: Hi, yes I'm more than happy to see a patch, and would almost certainly merge it thanks David ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=2813178&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-06-27 10:51:44
|
Feature Requests item #2813178, was opened at 2009-06-27 09:46 Message generated for change (Comment added) made by gingerdog You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=2813178&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: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Stevan Bajic (sbajic) Assigned to: Nobody/Anonymous (nobody) Summary: More flexible vacation module regarding mailsever definition Initial Comment: The currently used Mail::sendmail module is very limited regarding the configuration of SMTP server data. You can't define: - SMTP port - SMTP username - SMTP password - SMTP authentication I am using Postfix as my MTA and using virtual vacation is a no-go for me since I do sender mismatch checking and with the currently used Mail::sendmail in virtual vacation I can use virtual vacation on my setup. I would like to replace the Mail::sendmail module with Mail::Sender which is offering much more flexibility then Mail::sendmail. Should I send a patch to virtual vacation v4 using Mail::Sender for sending mails? Is the above mentioned functionality useful for other people? How high are the chances to get such a patch merged into Postfix.Admin? ---------------------------------------------------------------------- >Comment By: GingerDog (gingerdog) Date: 2009-06-27 10:51 Message: Hi, yes I'm more than happy to see a patch, and would almost certainly merge it thanks David ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=2813178&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-06-27 09:46:11
|
Feature Requests item #2813178, was opened at 2009-06-27 11:46 Message generated for change (Tracker Item Submitted) made by sbajic You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=2813178&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: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Stevan Bajic (sbajic) Assigned to: Nobody/Anonymous (nobody) Summary: More flexible vacation module regarding mailsever definition Initial Comment: The currently used Mail::sendmail module is very limited regarding the configuration of SMTP server data. You can't define: - SMTP port - SMTP username - SMTP password - SMTP authentication I am using Postfix as my MTA and using virtual vacation is a no-go for me since I do sender mismatch checking and with the currently used Mail::sendmail in virtual vacation I can use virtual vacation on my setup. I would like to replace the Mail::sendmail module with Mail::Sender which is offering much more flexibility then Mail::sendmail. Should I send a patch to virtual vacation v4 using Mail::Sender for sending mails? Is the above mentioned functionality useful for other people? How high are the chances to get such a patch merged into Postfix.Admin? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=2813178&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-06-22 10:11:01
|
Bugs item #2809905, was opened at 2009-06-21 15:23 Message generated for change (Comment added) made by gingerdog You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2809905&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: Filipe Fagundes (piovisqui) Assigned to: Nobody/Anonymous (nobody) Summary: .deb package resquest the removal of mysql server Initial Comment: I have download the postfixadmin_2.3_RC5_all.deb on Ubuntu 9.04. When I asked the install the package requires the REMOVAL of mysql server 5.1 and mysql client 5.1 and the installation of mysql client 5.0. It does not ask the install of mysql server 5.0. I downloaded RC4 and it installed successful. ---------------------------------------------------------------------- >Comment By: GingerDog (gingerdog) Date: 2009-06-22 10:11 Message: the dependency on wwwconfig-common is now not an issue; the debian control file doesn't specify any version requirements for mysql/postgresql, so i'm not sure why you'd get these problem(s). ---------------------------------------------------------------------- Comment By: Bjorn (bjornnilsen) Date: 2009-06-22 00:14 Message: The dependancies on this latest deb are very restrictive and have caused issues for me as well. The new wwwconfig-common dependency means that this deb is no longer supported with Ubuntu 8.04. $ sudo dpkg -i postfixadmin_2.3rc5_all.deb Selecting previously deselected package postfixadmin. (Reading database ... 25961 files and directories currently installed.) Unpacking postfixadmin (from postfixadmin_2.3rc5_all.deb) ... dpkg: dependency problems prevent configuration of postfixadmin: postfixadmin depends on wwwconfig-common (>= 0.2.0); however: Version of wwwconfig-common on system is 0.0.48. dpkg: error processing postfixadmin (--install): dependency problems - leaving unconfigured Errors were encountered while processing: postfixadmin ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2809905&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-06-22 00:14:40
|
Bugs item #2809905, was opened at 2009-06-22 03:23 Message generated for change (Comment added) made by bjornnilsen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2809905&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: Filipe Fagundes (piovisqui) Assigned to: Nobody/Anonymous (nobody) Summary: .deb package resquest the removal of mysql server Initial Comment: I have download the postfixadmin_2.3_RC5_all.deb on Ubuntu 9.04. When I asked the install the package requires the REMOVAL of mysql server 5.1 and mysql client 5.1 and the installation of mysql client 5.0. It does not ask the install of mysql server 5.0. I downloaded RC4 and it installed successful. ---------------------------------------------------------------------- Comment By: Bjorn (bjornnilsen) Date: 2009-06-22 12:14 Message: The dependancies on this latest deb are very restrictive and have caused issues for me as well. The new wwwconfig-common dependency means that this deb is no longer supported with Ubuntu 8.04. $ sudo dpkg -i postfixadmin_2.3rc5_all.deb Selecting previously deselected package postfixadmin. (Reading database ... 25961 files and directories currently installed.) Unpacking postfixadmin (from postfixadmin_2.3rc5_all.deb) ... dpkg: dependency problems prevent configuration of postfixadmin: postfixadmin depends on wwwconfig-common (>= 0.2.0); however: Version of wwwconfig-common on system is 0.0.48. dpkg: error processing postfixadmin (--install): dependency problems - leaving unconfigured Errors were encountered while processing: postfixadmin ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2809905&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-06-21 15:23:24
|
Bugs item #2809905, was opened at 2009-06-21 12:23 Message generated for change (Tracker Item Submitted) made by piovisqui You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2809905&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: Filipe Fagundes (piovisqui) Assigned to: Nobody/Anonymous (nobody) Summary: .deb package resquest the removal of mysql server Initial Comment: I have download the postfixadmin_2.3_RC5_all.deb on Ubuntu 9.04. When I asked the install the package requires the REMOVAL of mysql server 5.1 and mysql client 5.1 and the installation of mysql client 5.0. It does not ask the install of mysql server 5.0. I downloaded RC4 and it installed successful. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2809905&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-06-10 16:12:01
|
Bugs item #2803871, was opened at 2009-06-10 02:13 Message generated for change (Comment added) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2803871&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: Closed Resolution: Works For Me Priority: 5 Private: No Submitted By: Stevan Bajic (sbajic) Assigned to: Nobody/Anonymous (nobody) Summary: emailcheck_resolve_domain=YES prevents domain to domain forw Initial Comment: If emailcheck_resolve_domain is set to YES then you can't add a domain to domain forward (aka: @firstdomain.tld -> @seconddomain.tld). Function check_email should check if one is entering a wildchar or not. Or at least create-alias.php should not call check_email if the from address is *@firstdomain.tld and the to address is *@seconddomain.tld ---------------------------------------------------------------------- >Comment By: Christian Boltz (christian_boltz) Date: 2009-06-10 18:12 Message: Just to be sure the domain is resolvable in your nameserver: Does it work in 2.2 if you use al...@ot... as target address? ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2009-06-10 18:10 Message: Looks like the code wants you to use alias domains ;-) They even have the advantage of not breaking recipient validation which avoids bounces if the address is invalid on the target domain. That said: I just tested this with the latest version (SVN r663, which is 2.3 rc5 + some minor fixes which are not related to this bug) and can create the *@ alias with *@otherdomain.tld as target. (Yes, my installation checks the mail addresses.) Please upgrade to postfixadmin 2.3 - it comes with lots of bugfixes (obviously including one for this bug) and also includes several new features. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2803871&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-06-10 16:10:22
|
Bugs item #2803871, was opened at 2009-06-10 02:13 Message generated for change (Settings changed) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2803871&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: Closed Resolution: Works For Me Priority: 5 Private: No Submitted By: Stevan Bajic (sbajic) Assigned to: Nobody/Anonymous (nobody) Summary: emailcheck_resolve_domain=YES prevents domain to domain forw Initial Comment: If emailcheck_resolve_domain is set to YES then you can't add a domain to domain forward (aka: @firstdomain.tld -> @seconddomain.tld). Function check_email should check if one is entering a wildchar or not. Or at least create-alias.php should not call check_email if the from address is *@firstdomain.tld and the to address is *@seconddomain.tld ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2009-06-10 18:10 Message: Looks like the code wants you to use alias domains ;-) They even have the advantage of not breaking recipient validation which avoids bounces if the address is invalid on the target domain. That said: I just tested this with the latest version (SVN r663, which is 2.3 rc5 + some minor fixes which are not related to this bug) and can create the *@ alias with *@otherdomain.tld as target. (Yes, my installation checks the mail addresses.) Please upgrade to postfixadmin 2.3 - it comes with lots of bugfixes (obviously including one for this bug) and also includes several new features. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2803871&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-06-10 16:10:02
|
Bugs item #2803871, was opened at 2009-06-10 02:13 Message generated for change (Comment added) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2803871&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: Closed >Resolution: Works For Me Priority: 5 Private: No Submitted By: Stevan Bajic (sbajic) Assigned to: Nobody/Anonymous (nobody) Summary: emailcheck_resolve_domain=YES prevents domain to domain forw Initial Comment: If emailcheck_resolve_domain is set to YES then you can't add a domain to domain forward (aka: @firstdomain.tld -> @seconddomain.tld). Function check_email should check if one is entering a wildchar or not. Or at least create-alias.php should not call check_email if the from address is *@firstdomain.tld and the to address is *@seconddomain.tld ---------------------------------------------------------------------- >Comment By: Christian Boltz (christian_boltz) Date: 2009-06-10 18:10 Message: Looks like the code wants you to use alias domains ;-) They even have the advantage of not breaking recipient validation which avoids bounces if the address is invalid on the target domain. That said: I just tested this with the latest version (SVN r663, which is 2.3 rc5 + some minor fixes which are not related to this bug) and can create the *@ alias with *@otherdomain.tld as target. (Yes, my installation checks the mail addresses.) Please upgrade to postfixadmin 2.3 - it comes with lots of bugfixes (obviously including one for this bug) and also includes several new features. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2803871&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-06-10 00:13:40
|
Bugs item #2803871, was opened at 2009-06-10 02:13 Message generated for change (Tracker Item Submitted) made by sbajic You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2803871&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: Stevan Bajic (sbajic) Assigned to: Nobody/Anonymous (nobody) Summary: emailcheck_resolve_domain=YES prevents domain to domain forw Initial Comment: If emailcheck_resolve_domain is set to YES then you can't add a domain to domain forward (aka: @firstdomain.tld -> @seconddomain.tld). Function check_email should check if one is entering a wildchar or not. Or at least create-alias.php should not call check_email if the from address is *@firstdomain.tld and the to address is *@seconddomain.tld ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2803871&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-06-08 20:18:35
|
Bugs item #2795764, was opened at 2009-05-23 09:26 Message generated for change (Settings changed) made by gingerdog You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2795764&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: SVN (please specify revision!) >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Andrea Soster (soster) Assigned to: Nobody/Anonymous (nobody) Summary: index name versus table name collision on postgres Initial Comment: When upgrading to DB version 655 (from SVN 664), postfixadmin will try to create an index named "alias_domain" on the table alias, for field domain: db_query_parsed(_add_index('alias', 'domain', 'domain')); this collides with the table named "alias_domain". we could add an "index_" prefix on postgres indexes: Index: upgrade.php =================================================================== --- upgrade.php (revision 664) +++ upgrade.php (working copy) @@ -229,7 +229,7 @@ if ($CONF['database_type'] == 'mysql' || $CONF['database_type'] == 'mysqli' ) { return "ALTER TABLE $table ADD INDEX `$indexname` ( `$fieldlist` )"; } elseif($CONF['database_type'] == 'pgsql') { - $pgindexname = $table . "_" . $indexname; + $pgindexname = "index_" . $table . "_" . $indexname; return "CREATE INDEX $pgindexname ON $table($fieldlist);"; # Index names are unique with a DB for PostgreSQL } else { echo "Sorry, unsupported database type " . $conf['database_type']; ---------------------------------------------------------------------- Comment By: GingerDog (gingerdog) Date: 2009-06-08 20:16 Message: hi; thanks for the bug report;i believe this is fixedin svn - i hadn't seen this bug report, and instead appended _idx on the object name. ---------------------------------------------------------------------- Comment By: GingerDog (gingerdog) Date: 2009-06-08 20:16 Message: Thanks for the bug report; we believe this has been fixed in subversion. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2795764&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-06-08 20:16:19
|
Bugs item #2795764, was opened at 2009-05-23 09:26 Message generated for change (Comment added) made by gingerdog You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2795764&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: SVN (please specify revision!) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Andrea Soster (soster) Assigned to: Nobody/Anonymous (nobody) Summary: index name versus table name collision on postgres Initial Comment: When upgrading to DB version 655 (from SVN 664), postfixadmin will try to create an index named "alias_domain" on the table alias, for field domain: db_query_parsed(_add_index('alias', 'domain', 'domain')); this collides with the table named "alias_domain". we could add an "index_" prefix on postgres indexes: Index: upgrade.php =================================================================== --- upgrade.php (revision 664) +++ upgrade.php (working copy) @@ -229,7 +229,7 @@ if ($CONF['database_type'] == 'mysql' || $CONF['database_type'] == 'mysqli' ) { return "ALTER TABLE $table ADD INDEX `$indexname` ( `$fieldlist` )"; } elseif($CONF['database_type'] == 'pgsql') { - $pgindexname = $table . "_" . $indexname; + $pgindexname = "index_" . $table . "_" . $indexname; return "CREATE INDEX $pgindexname ON $table($fieldlist);"; # Index names are unique with a DB for PostgreSQL } else { echo "Sorry, unsupported database type " . $conf['database_type']; ---------------------------------------------------------------------- >Comment By: GingerDog (gingerdog) Date: 2009-06-08 20:16 Message: hi; thanks for the bug report;i believe this is fixedin svn - i hadn't seen this bug report, and instead appended _idx on the object name. ---------------------------------------------------------------------- Comment By: GingerDog (gingerdog) Date: 2009-06-08 20:16 Message: Thanks for the bug report; we believe this has been fixed in subversion. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2795764&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-06-01 13:44:38
|
Bugs item #2799465, was opened at 2009-06-01 13:20 Message generated for change (Comment added) made by gingerdog You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2799465&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: list-domains does not list backupmx domains for domain admin Initial Comment: list_domains_for_admin() excludes domains with backupmx = true or active = false. This means that these domains are not listed in list-domains.php if a) a domain admin is logged in b) a superadmin calls it from the admin list as list-domain.php?username=XY I'm not sure what the reason for this behaviour is, but at least it worried me. Comments welcome - should we display backupmx and inactive domains when listing domains for domain admins? ---------------------------------------------------------------------- >Comment By: GingerDog (gingerdog) Date: 2009-06-01 13:44 Message: assuming the domain admin has permission for them, it would make sense (to me) for them to be able to see them. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2799465&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-06-01 13:20:13
|
Bugs item #2799465, was opened at 2009-06-01 15:20 Message generated for change (Tracker Item Submitted) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2799465&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: list-domains does not list backupmx domains for domain admin Initial Comment: list_domains_for_admin() excludes domains with backupmx = true or active = false. This means that these domains are not listed in list-domains.php if a) a domain admin is logged in b) a superadmin calls it from the admin list as list-domain.php?username=XY I'm not sure what the reason for this behaviour is, but at least it worried me. Comments welcome - should we display backupmx and inactive domains when listing domains for domain admins? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2799465&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-05-28 16:35:30
|
Feature Requests item #2686461, was opened at 2009-03-13 21:49 Message generated for change (Comment added) made by lexxai You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=2686461&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: GingerDog (gingerdog) Assigned to: Nobody/Anonymous (nobody) Summary: Custom Fields support for mailbox table Initial Comment: See https://sourceforge.net/forum/message.php?msg_id=6779222 In brief: Add support for a number of fields to the mailbox table which will allow sysadmins to customise postfixadmin to their needs - e.g. to enable webmail or remote pop3/imap access access on a per user basis etc etc. ---------------------------------------------------------------------- Comment By: Oleksiy (lexxai) Date: 2009-05-28 19:35 Message: I use custom fileld before upgrdage... ------------------------------------------------- 'ext' - Enable/disable external access by local/external IP, thanks new version of POSTFIX that now will send IP to DOVECOT auth. dovecot-sql.conf password_query = SELECT username as user, password, IF ext,NULL,'172.16.1.0/24,10.0.0.0/8,127.0.0.0/8') AS allow_nets FROM mailbox WHERE username = '%u' AND active="1" ------------------------------------------------- 'expire' - date of end time for temporary email accounts. by crone will change 'active' state. #!/bin/sh export HOME=/root echo "UPDATE mailbox SET active=0,modified=now() WHERE active=1 AND expire > 'now()';" | /usr/local/bin/mysql --defaults-file=~/.my.cnf mailusers ------------------------------------------------- 'glob-maillist' - 0/1 - enable users recieve mail for one global email "so...@my..." mysql-virtual_globalmaillist_alias_maps.cf query = SELECT username FROM mailbox WHERE '%s'='someone\@mydomain.com' AND domain='mydomain.com' AND active='1' AND ` glob-maillist`='1' main.cf virtual_alias_maps = mysql:$pfbase/sql/mysql-virtual_alias_maps.cf,mysql:$pfbase/sql/mysql-virtual_globalmaillist_alias_maps.cf For this case need custom field type too (bolean, data or numbering), depend of it web form (add/edit user) will changed. ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2009-04-25 00:20 Message: @rlaban: Your usecase is probably already covered - see $CONF['transport'] and $CONF['transport_options'] in config.inc.php. (Nevertheless I agree that custom fields should be available.) ---------------------------------------------------------------------- Comment By: Ruben Laban (rlaban) Date: 2009-04-24 11:14 Message: In addition to custom fields for mailboxes, I'd like to see custom fields for domains as well. Example use case: Store the backend server in a field which can be used by the frontend servers to use as a transport. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=2686461&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-05-28 02:27:54
|
Bugs item #2797690, was opened at 2009-05-28 14:27 Message generated for change (Tracker Item Submitted) made by bjornnilsen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2797690&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Core Group: v 2.3 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Bjorn (bjornnilsen) Assigned to: Nobody/Anonymous (nobody) Summary: When domain is deleted any domain aliases are not removed Initial Comment: When domain is deleted any related domain aliases are not removed. This occurs for both the domain and the aliased domain. I am not sure if this causes any real world problems but it certainly is not tidy :) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2797690&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-05-25 07:35:29
|
Patches item #2795780, was opened at 2009-05-23 12:12 Message generated for change (Comment added) made by soster You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937966&aid=2795780&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Core Group: SVN (please specify revision!) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Andrea Soster (soster) Assigned to: Nobody/Anonymous (nobody) Summary: Add support for "cascading" domain aliases Initial Comment: This patch add support for aliases of domains which are an alias for another domain, if configured the common scenario is: domainA -> domainB -> domainC Applies to SVN 664 ---------------------------------------------------------------------- >Comment By: Andrea Soster (soster) Date: 2009-05-25 09:35 Message: My production postfix (2.1) is running postfixadmin2.1 DB with a custom gui, now I'm trying to switch to current postfixadmin...I still haven't teste my patches in production, but on my currente postfix I have the following aliases: @a -> @b @b -> @c and it's working as expected, so there shouldn't be any troubles. I hope to move the new server to production this week, I'll let you know thanks ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2009-05-24 20:42 Message: Andrea, does this change need any changes in the postfix configuration files? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937966&aid=2795780&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-05-24 18:42:45
|
Patches item #2795780, was opened at 2009-05-23 12:12 Message generated for change (Comment added) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937966&aid=2795780&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Core Group: SVN (please specify revision!) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Andrea Soster (soster) Assigned to: Nobody/Anonymous (nobody) Summary: Add support for "cascading" domain aliases Initial Comment: This patch add support for aliases of domains which are an alias for another domain, if configured the common scenario is: domainA -> domainB -> domainC Applies to SVN 664 ---------------------------------------------------------------------- >Comment By: Christian Boltz (christian_boltz) Date: 2009-05-24 20:42 Message: Andrea, does this change need any changes in the postfix configuration files? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937966&aid=2795780&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2009-05-24 12:51:30
|
Bugs item #2796067, was opened at 2009-05-24 14:51 Message generated for change (Tracker Item Submitted) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2796067&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: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Christian Boltz (christian_boltz) Assigned to: Nobody/Anonymous (nobody) Summary: Vacation (nearly) always uses /tmp/vacation.log as logfile Initial Comment: vacation.pl uses /tmp/vacation.log if the given $logfile does not yet exist. The problem: There's a check if ( ! -w $logfile ) { $logfile = "/tmp/vacation.log"; } The -w check will return false if $logfile does not exist. This means that nearly all installations will log to /tmp/vacation.log - at least I doubt that many people create $logfile manually. The correct solution would be - check if $logfile exists - if yes, check if it is writeable (aka current code) - if no, check if the _directory_ of $logfile is writeable, and create the logfile If everything fails, write "can't open logfile $logfile" to syslog. The automatic fallback to /tmp/vacation.log also introduces the risk of symlink attacks, therefore I'd prefer if this fallback was completely removed. (Thanks to my AppArmor log for pointing out this bug ;-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=2796067&group_id=191583 |
700 messages has been excluded from this view by a project administrator.
