postfixadmin-tracker Mailing List for PostfixAdmin (Page 53)
Brought to you by:
christian_boltz,
gingerdog
Menu
▾
▴
postfixadmin-tracker — Postfix Admin tracker notification - READ ONLY!
You can subscribe to this list here.
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(5) |
Oct
(67) |
Nov
(83) |
Dec
(47) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2008 |
Jan
(57) |
Feb
(15) |
Mar
(21) |
Apr
(38) |
May
(27) |
Jun
(38) |
Jul
(35) |
Aug
(50) |
Sep
(8) |
Oct
(9) |
Nov
(59) |
Dec
(59) |
| 2009 |
Jan
(27) |
Feb
(42) |
Mar
(63) |
Apr
(46) |
May
(26) |
Jun
(25) |
Jul
(40) |
Aug
(19) |
Sep
(17) |
Oct
(35) |
Nov
(26) |
Dec
(21) |
| 2010 |
Jan
(11) |
Feb
(19) |
Mar
(40) |
Apr
(25) |
May
(23) |
Jun
(17) |
Jul
(10) |
Aug
(18) |
Sep
(21) |
Oct
(12) |
Nov
(10) |
Dec
(22) |
| 2011 |
Jan
(30) |
Feb
(23) |
Mar
(23) |
Apr
(38) |
May
(32) |
Jun
(19) |
Jul
(20) |
Aug
(36) |
Sep
(11) |
Oct
(28) |
Nov
(4) |
Dec
(4) |
| 2012 |
Jan
(6) |
Feb
(3) |
Mar
(16) |
Apr
(28) |
May
(29) |
Jun
(10) |
Jul
(2) |
Aug
(3) |
Sep
|
Oct
(13) |
Nov
(1) |
Dec
(1) |
| 2013 |
Jan
(11) |
Feb
(7) |
Mar
(29) |
Apr
(2) |
May
(3) |
Jun
(15) |
Jul
(8) |
Aug
(5) |
Sep
(5) |
Oct
(4) |
Nov
(27) |
Dec
(81) |
| 2014 |
Jan
(12) |
Feb
(13) |
Mar
(5) |
Apr
|
May
(41) |
Jun
(16) |
Jul
(7) |
Aug
(10) |
Sep
(24) |
Oct
(50) |
Nov
|
Dec
(2) |
| 2015 |
Jan
(5) |
Feb
(2) |
Mar
(7) |
Apr
(20) |
May
(1) |
Jun
(3) |
Jul
(12) |
Aug
(1) |
Sep
(17) |
Oct
(5) |
Nov
(20) |
Dec
(10) |
| 2016 |
Jan
(10) |
Feb
(11) |
Mar
(22) |
Apr
(30) |
May
(33) |
Jun
(3) |
Jul
|
Aug
(12) |
Sep
(20) |
Oct
(11) |
Nov
(15) |
Dec
(8) |
| 2017 |
Jan
(1) |
Feb
(11) |
Mar
(10) |
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(1) |
Nov
|
Dec
(3) |
| 2018 |
Jan
(2) |
Feb
|
Mar
(1) |
Apr
|
May
(4) |
Jun
(2) |
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: SourceForge.net <no...@so...> - 2008-04-15 06:59:03
|
Bugs item #1942748, was opened at 2008-04-15 08:59 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1942748&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: SVN (please specify revision!) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Dennis Lichtenthäler (episodeiv) Assigned to: Nobody/Anonymous (nobody) Summary: One admin, multiple domains not possible Initial Comment: Even in recent SVN versions (tested r331) it's not possible to give one admin (not super-admin) access to more than one domain. The 'admin' and 'domain_admins' tables are indexed by the 'username' column. Accordingly, two rows with the same username are impossible and trying to create them results in: Invalid query: Duplicate entry 'admin_address@domain' for key 1 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1942748&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-04-11 22:59:13
|
Bugs item #1938119, was opened at 2008-04-08 22:41 Message generated for change (Comment added) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1938119&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: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Database rights in DATABASE-MYSQL.txt Initial Comment: Hello I'm testing the rc3 release of PostfixAdmin. I'm not sure, but I think there is an error in the database rights. The user postfix and postfixadmin have the same rights on the database, but I think, postfix needs only select rights, because this user is normally only used to get information from the database. The user postfixadmin is used to managed the database, therefore it needs the update, delete and insert rights. Am I wrong? Best regards M. Kreis ---------------------------------------------------------------------- >Comment By: Christian Boltz (christian_boltz) Date: 2008-04-12 00:59 Message: Logged In: YES user_id=593261 Originator: NO You are right - postfix doesn't need write access to the database. There is now (SVN r329) a DOCUMENTS/SECURITY.TXT which describes the needed permissions for the database users. (BTW: DATABASE_*.TXT no longer exist, database creation is now done using setup.php / upgrade.php.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1938119&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-04-10 11:05:15
|
Feature Requests item #1939286, was opened at 2008-04-10 14:05 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=1939286&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: 9evill (simpsas) Assigned to: Nobody/Anonymous (nobody) Summary: Check box to insert into alias then creating new mailbox. Initial Comment: Hi when creating new mailbox it would be nice to have a checkbox to select in witch alises to insert new email. For now you have to create new email, and then manualy go to all needed aliases and insert that email. Then i say aliases i mean groups like of...@do...d eve...@do... etc... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=1939286&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-04-10 10:37:27
|
Bugs item #1936331, was opened at 2008-04-06 23:42 Message generated for change (Comment added) made by gingerdog You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1936331&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: 8 Private: No Submitted By: Christian Boltz (christian_boltz) Assigned to: Nobody/Anonymous (nobody) Summary: setup.php should check if database is up to date Initial Comment: (SVN r320) setup.php should check if the database is up to date by reading the version from the config table. (Errors should be ignored because this table might not exist yet.) It should also check if the admin table exists (pgsql table creation isn't included in upgrade.php yet - should be changed...) and if it contains at least one superadmin. If the database is not up to date (or the config table is missing at all), - display a link to upgrade.php - hide the "create superadmin" box Unfortunately another release blocker IMHO :-( but at least not too difficult to implement. ---------------------------------------------------------------------- >Comment By: GingerDog (gingerdog) Date: 2008-04-10 10:37 Message: Logged In: YES user_id=1761957 Originator: NO fixed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1936331&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-04-09 17:20:56
|
Bugs item #1938812, was opened at 2008-04-09 10:21 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1938812&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: SVN (please specify revision!) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: CSS font size choice squashes text Initial Comment: https://postfixadmin.svn.sourceforge.net/svnroot/postfixadmin/trunk/css/default.css body { background: #ffffff; color: #000000; font-family: BitStream Vera Sans, Verdana, Arial, Helvetica, sans-serif; font-size: 11px; font-weight: normal; } The choice of 11 point BitStream Vera Sans causes some display errors for Mac users that can be seen on http://postfixadmin.sourceforge.net/ in the text "However, it may contain bugs." toward the bottom of the page. The 11pt font causes text overlapping when rendered bold (either <b> or <strong>) or italic, so that the "it may contain bugs" text is itself squashed like a bug ;) At least, that's the rendering I get from the chosen fonts for Firefox on Mac OS X. Setting the font size to 10 or 12 resolves the issue for me. So this is probably as much a bug in the font "BitStream Vera Sans" on Mac OS X, since if I put arial, verdana or helvetica ahead I get fine rendering at 11pt. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1938812&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-04-08 20:41:10
|
Bugs item #1938119, was opened at 2008-04-08 13:41 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1938119&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: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Database rights in DATABASE-MYSQL.txt Initial Comment: Hello I'm testing the rc3 release of PostfixAdmin. I'm not sure, but I think there is an error in the database rights. The user postfix and postfixadmin have the same rights on the database, but I think, postfix needs only select rights, because this user is normally only used to get information from the database. The user postfixadmin is used to managed the database, therefore it needs the update, delete and insert rights. Am I wrong? Best regards M. Kreis ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1938119&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-04-06 23:41:59
|
Bugs item #1936331, was opened at 2008-04-07 01:42 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1936331&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: 8 Private: No Submitted By: Christian Boltz (christian_boltz) Assigned to: Nobody/Anonymous (nobody) Summary: setup.php should check if database is up to date Initial Comment: (SVN r320) setup.php should check if the database is up to date by reading the version from the config table. (Errors should be ignored because this table might not exist yet.) It should also check if the admin table exists (pgsql table creation isn't included in upgrade.php yet - should be changed...) and if it contains at least one superadmin. If the database is not up to date (or the config table is missing at all), - display a link to upgrade.php - hide the "create superadmin" box Unfortunately another release blocker IMHO :-( but at least not too difficult to implement. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1936331&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-04-06 23:31:42
|
Bugs item #1875897, was opened at 2008-01-20 19:57 Message generated for change (Comment added) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1875897&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: SVN (please specify revision!) Status: Open Resolution: None Priority: 8 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: "invalid query" in upgrade.php (caused by foreign keys?) Initial Comment: SVN version 2008-01-19T16:48:15.336774Z 297 in file backup.php - $result = db_query ("SHOW CREATE TABLE ".table_by_pos($i)); + $result = db_query ("SHOW CREATE TABLE $tables[$i]"); - $result = db_query ("SELECT * FROM ".table_by_pos($i)); + $result = db_query ("SELECT * FROM $tables[$i]"); - $tables = array('admin','alias','config','domain','domain_admins','log','mailbox','vacation','vacation_notification'); + $tables = array('admin','alias','domain','domain_admins','log','mailbox','vacation','vacation_notification'); ---------------------------------------------------------------------- >Comment By: Christian Boltz (christian_boltz) Date: 2008-04-07 01:31 Message: Logged In: YES user_id=593261 Originator: NO This should be fixed in the latest SVN version (r319). Can you please test it by running upgrade.php? Note: I can't guarantee a clean update. If something goes wrong (you'll see an "Invalid query" message in this case), please drop the table vacation_notification (it contains a list of mail adresses who have received vacation notifications already, so the worst thing that might happen is that some of them receive another one when sending the next mail). ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2008-03-05 01:24 Message: Logged In: YES user_id=593261 Originator: NO The comment from "nobody" on 2008-01-21 17:21 shows two problems: 1) the "invalid query" shown by upgrade.php I'll have to check this, probably it is caused by the foreign keys, which make altering tables an interesting challenge ;-) 2) creation of vacation_notification fails This part looks like a duplicate of http://sourceforge.net/tracker/index.php?func=detail&aid=1828857&group_id=191583&atid=937964 ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-01-21 17:21 Message: Logged In: NO sorry, I run upgrade.php and problem was solved. But when I run the upgrade.php, I saw this problem: ALTER TABLE `vacation` CHANGE `email` `email` VARCHAR( 255 ) /*!40100 CHARACTER SET latin1 COLLATE latin1_swedish_ci */ NOT NULL DEBUG INFORMATION: Invalid query: Error on rename of './postfix/#sql-33c0_2b1' to './postfix/vacation' (errno: 150) if I remove table vacation and vacation_notificaion and then I create it using CREATE TABLE `vacation` ( `email` varchar(255) /*!40100 CHARACTER SET latin1 COLLATE latin1_swedish_ci */ NOT NULL default '', `subject` varchar(255) /*!40100 CHARACTER SET latin1 COLLATE latin1_swedish_ci */ NOT NULL default '', `body` text NOT NULL, `cache` text NOT NULL, `domain` varchar(255) /*!40100 CHARACTER SET latin1 COLLATE latin1_swedish_ci */ NOT NULL default '', `created` datetime NOT NULL default '0000-00-00 00:00:00', `active` tinyint(4) NOT NULL default '1', PRIMARY KEY (`email`), KEY `email` (`email`) ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COMMENT='Postfix Admin - Virtual Vacation'; everything is done, but I can`t create table vacation_notification using CREATE TABLE vacation_notification ( on_vacation varchar(255) NOT NULL, notified varchar(255) NOT NULL, notified_at timestamp NOT NULL default now(), CONSTRAINT vacation_notification_pkey PRIMARY KEY(on_vacation, notified), FOREIGN KEY (on_vacation) REFERENCES vacation(email) ON DELETE CASCADE ) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_general_ci TYPE=InnoDB COMMENT='Postfix Admin - Virtual Vacation Notifications'; I obtain error that table /postfix/vacation_notification.frm can`t be created errono=150 ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2008-01-20 21:37 Message: Logged In: YES user_id=593261 Originator: NO Hmm, I can't see what fails here - I just tested and the backup seems to work. Can you please add some details? What is the problem you want to solve? BTW: Your $tables does not include the "config" table. If you have updated from an earlier version of postfixadmin, please run upgrade.php to create it (and to update your other tables also). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1875897&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-04-06 23:30:58
|
Bugs item #1828870, was opened at 2007-11-09 11:16 Message generated for change (Comment added) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1828870&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: 9 Private: No Submitted By: frn (frn123) Assigned to: Nobody/Anonymous (nobody) Summary: cannot view a domain page Initial Comment: using and url like http://foo/pa/list-virtual.php?domain=foo.com i get a following error: -- DEBUG INFORMATION: Invalid query: Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,IMPLICIT) for operation '=' Please check the documentation and website for more information. Postfix Admin Knowledge Base -- Using svn revision 204, debian sarge, mysql4-1.11a from sarge backports. mysql driver. Lookind at the DATABASE_MYSQL.TXT i notice that some of the tables are InnoDB and some MyISAM. MyISAM tables use latin_1 encodoing, InnoDB use utf8. I think all the tables should be innodb/utf8. ---------------------------------------------------------------------- >Comment By: Christian Boltz (christian_boltz) Date: 2008-04-07 01:31 Message: Logged In: YES user_id=593261 Originator: NO This should be fixed in the latest SVN version (r319). Can you please test it by running upgrade.php? Note: I can't guarantee a clean update. If something goes wrong (you'll see an "Invalid query" message in this case), please drop the table vacation_notification (it contains a list of mail adresses who have received vacation notifications already, so the worst thing that might happen is that some of them receive another one when sending the next mail). ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2007-11-17 23:27 Message: Logged In: YES user_id=593261 Originator: NO Using utf8 everywhere is a bad idea - it wastes some space (a char needs 3 bytes in utf8) and, biger problem, causes problems with the key length in vacation_notification (see bug 1828857). I'll change fields for email addresses to latin1 - mail adresses can't contain utf8 anyway. OTOH, the description fields should really be utf8 because people can enter anything they want there. ---------------------------------------------------------------------- Comment By: frn (frn123) Date: 2007-11-09 11:23 Message: Logged In: YES user_id=1933384 Originator: YES changing all the tables to type innodb made the bug go away with no apparent ill effects (yet?) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1828870&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-04-06 23:30:34
|
Bugs item #1828857, was opened at 2007-11-09 11:00 Message generated for change (Comment added) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1828857&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: 9 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: mysql create database broken Initial Comment: >mysql -u root -p < DATABASE_MYSQL.TXT Enter password: ERROR 1071 (42000) at line 144: Specified key was too long; max key length is 1024 bytes Using svn revision 204, debian sarge, mysql4-1.11a from sarge backports changing the DATABASE_MYSQL.txt file to: -- CREATE TABLE vacation_notification ( on_vacation varchar(170) NOT NULL, notified varchar(170) NOT NULL, -- fixed the problem for me tho. Dunno if it is a mysql bug or not. ---------------------------------------------------------------------- >Comment By: Christian Boltz (christian_boltz) Date: 2008-04-07 01:30 Message: Logged In: YES user_id=593261 Originator: NO This should be fixed in the latest SVN version (r319). Can you please test it by running upgrade.php? Note: I can't guarantee a clean update. If something goes wrong (you'll see an "Invalid query" message in this case), please drop the table vacation_notification (it contains a list of mail adresses who have received vacation notifications already, so the worst thing that might happen is that some of them receive another one when sending the next mail). ---------------------------------------------------------------------- Comment By: Georgi Naplatanov (goshoo) Date: 2008-01-03 16:04 Message: Logged In: YES user_id=181398 Originator: NO > problem will then be that we loose utf8 encoded email handle, is this > problem olso with postgresql and unicode ? Not really, it's a mysql bug - see http://bugs.mysql.com/bug.php?id=4541 UTF-8 has a variable lenght ( between 1 and 3 bytes per character), mysql allocates maximum space. ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2007-11-18 20:19 Message: Logged In: YES user_id=593261 Originator: NO unicode domains are always "punicode"-encoded, for example "blöd.de" is encoded as "xn--bld-tna.de". Does anyone see non-ASCII characters? ;-) See https://sourceforge.net/forum/message.php?msg_id=4572821 for more details. ---------------------------------------------------------------------- Comment By: amsys (amsys) Date: 2007-11-18 15:13 Message: Logged In: YES user_id=1299438 Originator: NO I have already tried to solve this, but the problem is someone want's to make unicode domains in future, adresses as standart (probably someone very crazy, like bunch of managers) a) make collation latin1 general b) store used emails as hash in vacation table (shortens key) I've placed this long time ago, but it's probably outdated now?: http://sourceforge.net/tracker/index.php?func=detail&aid=1801073&group_id=191583&atid=937966 ---------------------------------------------------------------------- Comment By: Benny Pedersen (xpunkt) Date: 2007-11-18 02:49 Message: Logged In: YES user_id=774995 Originator: NO and the vacation.pl is utf8 so we have to find a better way ---------------------------------------------------------------------- Comment By: Benny Pedersen (xpunkt) Date: 2007-11-18 02:44 Message: Logged In: YES user_id=774995 Originator: NO problem will then be that we loose utf8 encoded email handle, is this problem olso with postgresql and unicode ? i prefer unicode over latin-1 ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2007-11-17 22:29 Message: Logged In: YES user_id=593261 Originator: NO Looks like an utf8 problem... The key uses two varchar(255) field, which means the key is 2 * 255 chars long. And utf8 means 3 bytes per char, which results in 1530 bytes. Since these fields only contain mail addresses, I'll change them to latin1 encoding. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1828857&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-04-05 18:13:32
|
Patches item #1901104, was opened at 2008-02-24 17:42 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937966&aid=1901104&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: Guido Boehm (lenix) Assigned to: Nobody/Anonymous (nobody) Summary: domain aliases without bounces/backscatter Initial Comment: see http://sourceforge.net/forum/message.php?msg_id=4678100 for full problem description. in short: the current mechanism to do domain-aliasing (joh...@al... goes to joh...@re..., fo...@al... goes to fo...@re..., ...) is to insert a record into the alias-table, like address:@alias.com goto:@real.com. unless @real.com has catchall configured (address:@real.com, goto:us...@re...) this solution will generate bounce-mails. postfix will accept all mail for @alias.com, and only afterwards notice that there's no such user @real.com. this "backscatter"-problem makes you unpopular among other postmasters, so you would better try to avoid bouncing many messages. unfortunately, the only way to handle such situations in postfix without producing backscatter involves creating another table and modifying some main.cf configuration. this patch adds an alias_domain table to the setup, includes documentation for postfix-configuration and adds proper listing and forms for handling those alias-domains. it can peacefully co-exists with the "old" way to do domain-aliasing, that means that @alias.com -> @real.com in 'alias'-table will keep working, but it'll still have the same problems described above. since there are new forms/errors/... there are a lot of new strings to translate, i'll provide a german translation myself the next days. Do these new items have to be added to DOCUMENTS/LANGUAGE.txt? regarding PgSQL, i tried to support it everywhere i added new queries, but since i have no postgres-installation at hand i didn't test the relevant parts. it would be nice if somebody could provide some feedback/fixups on this topic. have fun, guido 'lenix' boehm ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-04-05 11:13 Message: Logged In: NO Hi Lenix, hope you got some sleep! Thanks for answering my questions. It's a great patch (useful, AND well written) so many thanks for sharing it with us. I hope the postfixadmin team get chance to add it to upstream as it addresses a real problem with the existing system - nobody wants a backscattering mail server! Best Chris ---------------------------------------------------------------------- Comment By: Guido Boehm (lenix) Date: 2008-04-04 17:26 Message: Logged In: YES user_id=142401 Originator: YES Hello Chris, thanks for testing :-) It does mean exactly what you described, although it works for (regular) aliases configured for foo.com, too. So if you happen to have a "fhk...@fo..." alias defined in your example (2), an email to "fhk...@ba..." would be accepted and delivered to whatever turns to be the target (goto/..) of "fhk...@fo...". Next to this you could configure additional addresses which exist only for "bar.com", but would be rejected for "foo.com". Let me know if there's anything left unclear to you, it is currently 2:20am over here, so i might sound a bit confusing again.. ---------------------------------------------------------------------- Comment By: Chris Nolan (chris_nolan) Date: 2008-04-04 14:57 Message: Logged In: YES user_id=2054925 Originator: NO Hmmmm, this looks useful although I'm *slightly* confused about it... Does this patch in effect mean that 1) if I have user1, user2 and user3 set up as mailboxes on foo.com then I alias bar.com to foo.com that postfix will now automatically accept all mail for us...@ba... us...@ba... and us...@ba... and they will be delivered to us...@fo... us...@fo... and us...@fo... respectively? 2) that any mail to an unknown user "fhk...@ba..." that is not set up as a mailbox on foo.com will be rejected with a 550 response? Anyway, the patch applies very nicely against revision 316 too (there is a 2 line difference somewhere, but it applies fine). You need to add a line to templates/menu.php at line 26 for the new feature to be available from the admin menu: $submenu_domain .= _menulink("create-alias-domain.php", $PALANG['pMenu_create_alias_domain']); Hope you can answer my two questions! ---------------------------------------------------------------------- Comment By: Guido Boehm (lenix) Date: 2008-02-24 17:44 Message: Logged In: YES user_id=142401 Originator: YES oh, and patch is diff -pruN against svn 299 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937966&aid=1901104&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-04-05 00:26:30
|
Patches item #1901104, was opened at 2008-02-25 02:42 Message generated for change (Comment added) made by lenix You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937966&aid=1901104&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: Guido Boehm (lenix) Assigned to: Nobody/Anonymous (nobody) Summary: domain aliases without bounces/backscatter Initial Comment: see http://sourceforge.net/forum/message.php?msg_id=4678100 for full problem description. in short: the current mechanism to do domain-aliasing (joh...@al... goes to joh...@re..., fo...@al... goes to fo...@re..., ...) is to insert a record into the alias-table, like address:@alias.com goto:@real.com. unless @real.com has catchall configured (address:@real.com, goto:us...@re...) this solution will generate bounce-mails. postfix will accept all mail for @alias.com, and only afterwards notice that there's no such user @real.com. this "backscatter"-problem makes you unpopular among other postmasters, so you would better try to avoid bouncing many messages. unfortunately, the only way to handle such situations in postfix without producing backscatter involves creating another table and modifying some main.cf configuration. this patch adds an alias_domain table to the setup, includes documentation for postfix-configuration and adds proper listing and forms for handling those alias-domains. it can peacefully co-exists with the "old" way to do domain-aliasing, that means that @alias.com -> @real.com in 'alias'-table will keep working, but it'll still have the same problems described above. since there are new forms/errors/... there are a lot of new strings to translate, i'll provide a german translation myself the next days. Do these new items have to be added to DOCUMENTS/LANGUAGE.txt? regarding PgSQL, i tried to support it everywhere i added new queries, but since i have no postgres-installation at hand i didn't test the relevant parts. it would be nice if somebody could provide some feedback/fixups on this topic. have fun, guido 'lenix' boehm ---------------------------------------------------------------------- >Comment By: Guido Boehm (lenix) Date: 2008-04-05 02:26 Message: Logged In: YES user_id=142401 Originator: YES Hello Chris, thanks for testing :-) It does mean exactly what you described, although it works for (regular) aliases configured for foo.com, too. So if you happen to have a "fhk...@fo..." alias defined in your example (2), an email to "fhk...@ba..." would be accepted and delivered to whatever turns to be the target (goto/..) of "fhk...@fo...". Next to this you could configure additional addresses which exist only for "bar.com", but would be rejected for "foo.com". Let me know if there's anything left unclear to you, it is currently 2:20am over here, so i might sound a bit confusing again.. ---------------------------------------------------------------------- Comment By: Chris Nolan (chris_nolan) Date: 2008-04-04 23:57 Message: Logged In: YES user_id=2054925 Originator: NO Hmmmm, this looks useful although I'm *slightly* confused about it... Does this patch in effect mean that 1) if I have user1, user2 and user3 set up as mailboxes on foo.com then I alias bar.com to foo.com that postfix will now automatically accept all mail for us...@ba... us...@ba... and us...@ba... and they will be delivered to us...@fo... us...@fo... and us...@fo... respectively? 2) that any mail to an unknown user "fhk...@ba..." that is not set up as a mailbox on foo.com will be rejected with a 550 response? Anyway, the patch applies very nicely against revision 316 too (there is a 2 line difference somewhere, but it applies fine). You need to add a line to templates/menu.php at line 26 for the new feature to be available from the admin menu: $submenu_domain .= _menulink("create-alias-domain.php", $PALANG['pMenu_create_alias_domain']); Hope you can answer my two questions! ---------------------------------------------------------------------- Comment By: Guido Boehm (lenix) Date: 2008-02-25 02:44 Message: Logged In: YES user_id=142401 Originator: YES oh, and patch is diff -pruN against svn 299 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937966&aid=1901104&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-04-04 22:24:52
|
Patches item #1711767, was opened at 2007-05-03 10:45 Message generated for change (Comment added) made by chris_nolan You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937966&aid=1711767&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: Cyril Jaquier (lostcontrol) Assigned to: Nobody/Anonymous (nobody) Summary: Allow SMTP option Initial Comment: Hi, I don't want to allow all my virtual users to send e-mails using my mail server. I have added a "smtp" field to the DB schema (in "mailbox" table). I have quickly patched postfixadmin last evening to allow me setting this flag. This is more a feature request than a correct implementation. Sorry :/ TODO: - Add this flag to user creation too - Translations - An enum type with a combo box could be better (sender only, recipient only, both) - Is "mailbox" the correct table to handle this? Thank you ---------------------------------------------------------------------- Comment By: Chris Nolan (chris_nolan) Date: 2008-04-04 23:24 Message: Logged In: YES user_id=2054925 Originator: NO Interesting... can you post the changes you made to /etc/postfix/main.cf to make this work? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937966&aid=1711767&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-04-04 21:57:52
|
Patches item #1901104, was opened at 2008-02-25 01:42 Message generated for change (Comment added) made by chris_nolan You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937966&aid=1901104&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: Guido Boehm (lenix) Assigned to: Nobody/Anonymous (nobody) Summary: domain aliases without bounces/backscatter Initial Comment: see http://sourceforge.net/forum/message.php?msg_id=4678100 for full problem description. in short: the current mechanism to do domain-aliasing (joh...@al... goes to joh...@re..., fo...@al... goes to fo...@re..., ...) is to insert a record into the alias-table, like address:@alias.com goto:@real.com. unless @real.com has catchall configured (address:@real.com, goto:us...@re...) this solution will generate bounce-mails. postfix will accept all mail for @alias.com, and only afterwards notice that there's no such user @real.com. this "backscatter"-problem makes you unpopular among other postmasters, so you would better try to avoid bouncing many messages. unfortunately, the only way to handle such situations in postfix without producing backscatter involves creating another table and modifying some main.cf configuration. this patch adds an alias_domain table to the setup, includes documentation for postfix-configuration and adds proper listing and forms for handling those alias-domains. it can peacefully co-exists with the "old" way to do domain-aliasing, that means that @alias.com -> @real.com in 'alias'-table will keep working, but it'll still have the same problems described above. since there are new forms/errors/... there are a lot of new strings to translate, i'll provide a german translation myself the next days. Do these new items have to be added to DOCUMENTS/LANGUAGE.txt? regarding PgSQL, i tried to support it everywhere i added new queries, but since i have no postgres-installation at hand i didn't test the relevant parts. it would be nice if somebody could provide some feedback/fixups on this topic. have fun, guido 'lenix' boehm ---------------------------------------------------------------------- Comment By: Chris Nolan (chris_nolan) Date: 2008-04-04 22:57 Message: Logged In: YES user_id=2054925 Originator: NO Hmmmm, this looks useful although I'm *slightly* confused about it... Does this patch in effect mean that 1) if I have user1, user2 and user3 set up as mailboxes on foo.com then I alias bar.com to foo.com that postfix will now automatically accept all mail for us...@ba... us...@ba... and us...@ba... and they will be delivered to us...@fo... us...@fo... and us...@fo... respectively? 2) that any mail to an unknown user "fhk...@ba..." that is not set up as a mailbox on foo.com will be rejected with a 550 response? Anyway, the patch applies very nicely against revision 316 too (there is a 2 line difference somewhere, but it applies fine). You need to add a line to templates/menu.php at line 26 for the new feature to be available from the admin menu: $submenu_domain .= _menulink("create-alias-domain.php", $PALANG['pMenu_create_alias_domain']); Hope you can answer my two questions! ---------------------------------------------------------------------- Comment By: Guido Boehm (lenix) Date: 2008-02-25 01:44 Message: Logged In: YES user_id=142401 Originator: YES oh, and patch is diff -pruN against svn 299 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937966&aid=1901104&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-04-03 22:24:01
|
Bugs item #1908127, was opened at 2008-03-05 17:30 Message generated for change (Settings changed) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1908127&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface (example) Group: v 2.1 >Status: Closed Resolution: Out of Date Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: unable to add multiple recipients to an alias Initial Comment: When attempting to add multiple recipients to an alias, the addresses are listed as invalid. I think this is due to adding the \r\n to the text upon submit. I'll work on fixing it in the next couple days and submit a patch if I can. ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2008-04-04 00:09 Message: Logged In: YES user_id=593261 Originator: NO Yes, your patch looks correct - and the SVN version already has the same ;-) I recommend to use the latest SVN revision - it has much more bugs fixed and is currently at 2.2RC state, so it should be nearly production ready (minus the known blocker bugs, but these will not hit you if you have already created the database). ---------------------------------------------------------------------- Comment By: Samuel Abreu de Paula (cartz) Date: 2008-04-03 20:21 Message: Logged In: YES user_id=817632 Originator: NO > If you have a specific reason to stick with 2.1, please tell me. Maybe you > have just found a bug or problem nobody reported yet... I've suffer from the same problem lately, and the reason i stick on 2.1 is (From http://postfixadmin.sourceforge.net/): "Download - Stable release The latest stable release is 2.1.0. You can download it here" I came here to submit this bug, but found this report and im just commenting here. My patch for this is: --- edit-alias.php.bkp 2008-04-03 15:14:29.000000000 -0300 +++ edit-alias.php 2008-04-03 15:21:15.000000000 -0300 @@ -76,11 +76,11 @@ $tMessage = $PALANG['pEdit_alias_goto_text_error1']; } - $goto = preg_replace ('/\\\r\\\n/', ',', $fGoto); - $goto = preg_replace ('/\r\n/', ',', $fGoto); - $goto = preg_replace ('/[\s]+/i', '', $goto); - $goto = preg_replace ('/\,*$/', '', $goto); - $array = preg_split ('/,/', $goto); + $goto = preg_replace ('/\\\r\\\n/', ',', $fGoto); + $goto = preg_replace ('/\r\n/', ',', $goto); + $goto = preg_replace ('/[\s]+/i', '', $goto); + $goto = preg_replace ('/,*$|^,*/', '', $goto); + $goto = preg_replace ('/,,*/', ',', $goto); for ($i = 0; $i < sizeof ($array); $i++) { if (in_array ("$array[$i]", $CONF['default_aliases'])) continue; ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2008-03-06 01:00 Message: Logged In: YES user_id=593261 Originator: NO > Forgot to mention that this has been fixed in the SVN version (2.2). Why don't you update to 2.2 then? It has lots of bugs fixed (see svn log), and backporting all those fixes to 2.1 will basically result in the 2.2 release. OK, you will miss some new features, but still. The current version also includes upgrade.php which does the necessary database changes for existing 2.1 installations. Don't get me wrong - I really like contributions. But I don't see a point in providing patches against 2.1. IMHO, it is nearly impossible to maintain 2.1 because lots of code duplication (yes, I did the cleanup and merge, so I really know what I'm talking about) and, additionally, lack of time. If you want to spend your time on postfixadmin, please work on the current version. I'm quite sure it has some bugs left - fixing those has a greater value :-) If you have a specific reason to stick with 2.1, please tell me. Maybe you have just found a bug or problem nobody reported yet... BTW: Please login to sourceforge before posting. This makes things easier (for example, you will get a mail when a tracker item you opened is updated) and also gives you some kudos for the time you invested ;-) ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-03-05 17:31 Message: Logged In: NO Forgot to mention that this has been fixed in the SVN version (2.2). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1908127&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-04-03 22:21:05
|
Bugs item #1927707, was opened at 2008-03-28 04:50 Message generated for change (Comment added) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1927707&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: Master Merlin Kull Kirkpatrick (thefathermind) Assigned to: Nobody/Anonymous (nobody) Summary: tFmail error on line 35 in fetchmail.php Initial Comment: I was getting an error of this nature. I am using a slightly older version of PHP and I suppose in newer versions it does not complain about variables that have not been defined yet. So I simply put an @ sign in front of the variable and this resolves the problem totally. Perhaps that should be implimented into the original source. Old Line... if (sizeof ($tFmail) > 0){ new Line... if (sizeof (@$tFmail) > 0){ ---------------------------------------------------------------------- >Comment By: Christian Boltz (christian_boltz) Date: 2008-04-04 00:21 Message: Logged In: YES user_id=593261 Originator: NO Usage of @ only supresses the error message, but not the problem (which might even become security relevant if register_globals is still on). I fixed the root of the problem instead - $tFmail was not initialized if the database doesn't contain any fetchmail entry. Fixed in SVN r316. BTW: The notice on undefined variables is also available in newer PHP versions (error_reporting = E_ALL). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1927707&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-04-03 22:09:46
|
Bugs item #1908127, was opened at 2008-03-05 17:30 Message generated for change (Comment added) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1908127&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface (example) Group: v 2.1 Status: Open Resolution: Out of Date Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: unable to add multiple recipients to an alias Initial Comment: When attempting to add multiple recipients to an alias, the addresses are listed as invalid. I think this is due to adding the \r\n to the text upon submit. I'll work on fixing it in the next couple days and submit a patch if I can. ---------------------------------------------------------------------- >Comment By: Christian Boltz (christian_boltz) Date: 2008-04-04 00:09 Message: Logged In: YES user_id=593261 Originator: NO Yes, your patch looks correct - and the SVN version already has the same ;-) I recommend to use the latest SVN revision - it has much more bugs fixed and is currently at 2.2RC state, so it should be nearly production ready (minus the known blocker bugs, but these will not hit you if you have already created the database). ---------------------------------------------------------------------- Comment By: Samuel Abreu de Paula (cartz) Date: 2008-04-03 20:21 Message: Logged In: YES user_id=817632 Originator: NO > If you have a specific reason to stick with 2.1, please tell me. Maybe you > have just found a bug or problem nobody reported yet... I've suffer from the same problem lately, and the reason i stick on 2.1 is (From http://postfixadmin.sourceforge.net/): "Download - Stable release The latest stable release is 2.1.0. You can download it here" I came here to submit this bug, but found this report and im just commenting here. My patch for this is: --- edit-alias.php.bkp 2008-04-03 15:14:29.000000000 -0300 +++ edit-alias.php 2008-04-03 15:21:15.000000000 -0300 @@ -76,11 +76,11 @@ $tMessage = $PALANG['pEdit_alias_goto_text_error1']; } - $goto = preg_replace ('/\\\r\\\n/', ',', $fGoto); - $goto = preg_replace ('/\r\n/', ',', $fGoto); - $goto = preg_replace ('/[\s]+/i', '', $goto); - $goto = preg_replace ('/\,*$/', '', $goto); - $array = preg_split ('/,/', $goto); + $goto = preg_replace ('/\\\r\\\n/', ',', $fGoto); + $goto = preg_replace ('/\r\n/', ',', $goto); + $goto = preg_replace ('/[\s]+/i', '', $goto); + $goto = preg_replace ('/,*$|^,*/', '', $goto); + $goto = preg_replace ('/,,*/', ',', $goto); for ($i = 0; $i < sizeof ($array); $i++) { if (in_array ("$array[$i]", $CONF['default_aliases'])) continue; ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2008-03-06 01:00 Message: Logged In: YES user_id=593261 Originator: NO > Forgot to mention that this has been fixed in the SVN version (2.2). Why don't you update to 2.2 then? It has lots of bugs fixed (see svn log), and backporting all those fixes to 2.1 will basically result in the 2.2 release. OK, you will miss some new features, but still. The current version also includes upgrade.php which does the necessary database changes for existing 2.1 installations. Don't get me wrong - I really like contributions. But I don't see a point in providing patches against 2.1. IMHO, it is nearly impossible to maintain 2.1 because lots of code duplication (yes, I did the cleanup and merge, so I really know what I'm talking about) and, additionally, lack of time. If you want to spend your time on postfixadmin, please work on the current version. I'm quite sure it has some bugs left - fixing those has a greater value :-) If you have a specific reason to stick with 2.1, please tell me. Maybe you have just found a bug or problem nobody reported yet... BTW: Please login to sourceforge before posting. This makes things easier (for example, you will get a mail when a tracker item you opened is updated) and also gives you some kudos for the time you invested ;-) ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-03-05 17:31 Message: Logged In: NO Forgot to mention that this has been fixed in the SVN version (2.2). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1908127&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-04-03 19:01:38
|
Feature Requests item #1933663, was opened at 2008-04-03 21:00 Message generated for change (Settings changed) made by nuxwin You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=1933663&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: DECLERCQ Laurent (nuxwin) Assigned to: Nobody/Anonymous (nobody) Summary: Defines delivery agent (transport) by email Initial Comment: Hi ; Actually, with PostfixAdmin ( latest svn version ) we can defines the delivery agent by domain recipient only. It's possible integrated option to defines the delivery agent by complet email recipient You can integrates this option ? Thank Sorry for my very bad english, i'm french user of PostfixAdmin. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=1933663&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-04-03 19:00:41
|
Feature Requests item #1933663, was opened at 2008-04-03 21:00 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=1933663&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: DECLERCQ Laurent (nuxwin) Assigned to: Nobody/Anonymous (nobody) Summary: Defines delivery agent (transport) by email Initial Comment: Hi ; Actually, with PostfixAdmin ( latest svn version ) we can defines the delivery agent by domain recipient only. It's possible integrated option to defines the delivery agent by complet email recipient You can integrates this option ? Thank Sorry for my very bad english, i'm french user of PostfixAdmin. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=1933663&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-04-03 18:21:19
|
Bugs item #1908127, was opened at 2008-03-05 13:30 Message generated for change (Comment added) made by cartz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1908127&group_id=191583 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface (example) Group: v 2.1 Status: Closed Resolution: Out of Date Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: unable to add multiple recipients to an alias Initial Comment: When attempting to add multiple recipients to an alias, the addresses are listed as invalid. I think this is due to adding the \r\n to the text upon submit. I'll work on fixing it in the next couple days and submit a patch if I can. ---------------------------------------------------------------------- Comment By: Samuel Abreu de Paula (cartz) Date: 2008-04-03 15:21 Message: Logged In: YES user_id=817632 Originator: NO > If you have a specific reason to stick with 2.1, please tell me. Maybe you > have just found a bug or problem nobody reported yet... I've suffer from the same problem lately, and the reason i stick on 2.1 is (From http://postfixadmin.sourceforge.net/): "Download - Stable release The latest stable release is 2.1.0. You can download it here" I came here to submit this bug, but found this report and im just commenting here. My patch for this is: --- edit-alias.php.bkp 2008-04-03 15:14:29.000000000 -0300 +++ edit-alias.php 2008-04-03 15:21:15.000000000 -0300 @@ -76,11 +76,11 @@ $tMessage = $PALANG['pEdit_alias_goto_text_error1']; } - $goto = preg_replace ('/\\\r\\\n/', ',', $fGoto); - $goto = preg_replace ('/\r\n/', ',', $fGoto); - $goto = preg_replace ('/[\s]+/i', '', $goto); - $goto = preg_replace ('/\,*$/', '', $goto); - $array = preg_split ('/,/', $goto); + $goto = preg_replace ('/\\\r\\\n/', ',', $fGoto); + $goto = preg_replace ('/\r\n/', ',', $goto); + $goto = preg_replace ('/[\s]+/i', '', $goto); + $goto = preg_replace ('/,*$|^,*/', '', $goto); + $goto = preg_replace ('/,,*/', ',', $goto); for ($i = 0; $i < sizeof ($array); $i++) { if (in_array ("$array[$i]", $CONF['default_aliases'])) continue; ---------------------------------------------------------------------- Comment By: Christian Boltz (christian_boltz) Date: 2008-03-05 21:00 Message: Logged In: YES user_id=593261 Originator: NO > Forgot to mention that this has been fixed in the SVN version (2.2). Why don't you update to 2.2 then? It has lots of bugs fixed (see svn log), and backporting all those fixes to 2.1 will basically result in the 2.2 release. OK, you will miss some new features, but still. The current version also includes upgrade.php which does the necessary database changes for existing 2.1 installations. Don't get me wrong - I really like contributions. But I don't see a point in providing patches against 2.1. IMHO, it is nearly impossible to maintain 2.1 because lots of code duplication (yes, I did the cleanup and merge, so I really know what I'm talking about) and, additionally, lack of time. If you want to spend your time on postfixadmin, please work on the current version. I'm quite sure it has some bugs left - fixing those has a greater value :-) If you have a specific reason to stick with 2.1, please tell me. Maybe you have just found a bug or problem nobody reported yet... BTW: Please login to sourceforge before posting. This makes things easier (for example, you will get a mail when a tracker item you opened is updated) and also gives you some kudos for the time you invested ;-) ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2008-03-05 13:31 Message: Logged In: NO Forgot to mention that this has been fixed in the SVN version (2.2). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1908127&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-03-28 03:50:30
|
Bugs item #1927707, was opened at 2008-03-27 20:50 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1927707&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: Master Merlin Kull Kirkpatrick (thefathermind) Assigned to: Nobody/Anonymous (nobody) Summary: tFmail error on line 35 in fetchmail.php Initial Comment: I was getting an error of this nature. I am using a slightly older version of PHP and I suppose in newer versions it does not complain about variables that have not been defined yet. So I simply put an @ sign in front of the variable and this resolves the problem totally. Perhaps that should be implimented into the original source. Old Line... if (sizeof ($tFmail) > 0){ new Line... if (sizeof (@$tFmail) > 0){ ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1927707&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-03-28 03:47:36
|
Bugs item #1927706, was opened at 2008-03-27 20:47 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1927706&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: Master Merlin Kull Kirkpatrick (thefathermind) Assigned to: Nobody/Anonymous (nobody) Summary: cannot yet handle MBCS in html_entity_decode Initial Comment: In the vacation module I got this error about 200 times.. "cannot yet handle MBCS in html_entity_decode" This is a documented bug in the 4.3 versions of PHP that they say they are not going to resolve stated here... http://bugs.php.net/bug.php?id=25670 I implemented the following work around to resolve this... in common.php I added the following 2 functions... // Returns the utf string corresponding to the unicode value (from php.net, courtesy - ro...@vo...) function code2utf($num) { if ($num < 128) return chr($num); if ($num < 2048) return chr(($num >> 6) + 192) . chr(($num & 63) + 128); if ($num < 65536) return chr(($num >> 12) + 224) . chr((($num >> 6) & 63) + 128) . chr(($num & 63) + 128); if ($num < 2097152) return chr(($num >> 18) + 240) . chr((($num >> 12) & 63) + 128) . chr((($num >> 6) & 63) + 128) . chr(($num & 63) + 128); return ''; } function html_entity_decode_fixed($str) { return preg_replace('/&#(\\d+);/e', 'code2utf($1)', utf8_encode($str)); } Then I edited edit-vacation.php and users/vacation.php and replaced all "html_entity_decode" with "html_entity_decode_fixed" ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937964&aid=1927706&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-03-22 14:39:37
|
Patches item #1923030, was opened at 2008-03-22 14:39 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937966&aid=1923030&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: Michiel van Baak (mvanbaak) Assigned to: Nobody/Anonymous (nobody) Summary: quota and scripthook for edit-mailbox.php Initial Comment: This patch is against revision 313 of trunk. The mailbox_postcreation hook does not send the quota to the script. We need this in order to run 'maildirmake -q' Also, when you alter a mailbox you need to run a script to alter the quota as well. I found no hook for it so implemented it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937966&aid=1923030&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-03-20 12:04:12
|
Patches item #1910916, was opened at 2008-03-10 10:15 Message generated for change (Settings changed) made by christian_boltz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937966&aid=1910916&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: Accepted Priority: 5 Private: No Submitted By: Johan Hendriks (sylhouette) Assigned to: Nobody/Anonymous (nobody) Summary: update to Dutch language Initial Comment: I attach a updated language file of the nl.lang file regards, Johan ---------------------------------------------------------------------- >Comment By: Christian Boltz (christian_boltz) Date: 2008-03-20 13:04 Message: Logged In: YES user_id=593261 Originator: NO Commited to SVN r313. Thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937966&aid=1910916&group_id=191583 |
|
From: SourceForge.net <no...@so...> - 2008-03-14 15:25:23
|
Feature Requests item #1914367, was opened at 2008-03-14 15:25 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=1914367&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: GingerDog (gingerdog) Assigned to: Nobody/Anonymous (nobody) Summary: Broadcast message - per domain etc Initial Comment: The broadcast message 'stuff' should also work for non-global admins, namely it should allow them to either send a message to all users in the domains they can control, or allow them to select which domains to send messages to. (i.e. perhaps the interface needs to allow users to select which domains to send the message to, with an 'ALL' option at the top? the list could then be filterable based on what sort of admin you are). See also : http://sourceforge.net/forum/forum.php?thread_id=1963431&forum_id=676076 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=937967&aid=1914367&group_id=191583 |
700 messages has been excluded from this view by a project administrator.
