From noreply at sourceforge.net Thu Jun 3 08:46:33 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jun 3 08:46:36 2004 Subject: [ mailman-Bugs-965706 ] Mailman and windows-1256 headers Message-ID: Bugs item #965706, was opened at 2004-06-03 14:46 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=965706&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: gb (guybrand) Assigned to: Nobody/Anonymous (nobody) Summary: Mailman and windows-1256 headers Initial Comment: Hello, We have a very reproductible problem with mailman on our Debian mail server. Whenever a user sends a message to a list which encodes at least one header using windows-1256 charset, the message gets shunt by mailman. Here are a few examples: # strings /usr/local/mailman/qfiles/shunt/* | grep windows Accueil =?windows-1252?Q?Lyc=E9ens_mercredi_17_mars_14h3?= Annonce =?windows-1252?Q?Conf=E9rence_E=2E_CADOT_-_6_M?= (these are subjects) ToUC=?windows-1252?Q?Facult=E9_de_chimie?= (this is a destination) Configuration is Mailman version: 2.1.4, Debian 3.0 and Python 2.1.3. Any fix or suggestion? Regards, gb ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=965706&group_id=103 From noreply at sourceforge.net Thu Jun 3 18:06:38 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jun 3 18:06:43 2004 Subject: [ mailman-Feature Requests-966157 ] login page should have username/password Message-ID: Feature Requests item #966157, was opened at 2004-06-04 00:06 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=966157&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jack Jansen (jackjansen) Assigned to: Nobody/Anonymous (nobody) Summary: login page should have username/password Initial Comment: The login page for mailman administration should have username/ password in stead of just password. The main reason for me asking this is that it will allow Safari (and probably other browsers as well) to remember all the passwords to all the mailman lists I manage. In addition, if the username was actually used (from the previous paragraph you'll understand I'm happy enough if it is ignored:-) you could have per-admin passwords. And that would of course open the door for keeping logs of which admin did what, which'll lead to finding scapegoats when things go wrong, etc etc etc. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=966157&group_id=103 From noreply at sourceforge.net Sat Jun 5 23:40:18 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Jun 5 23:40:23 2004 Subject: [ mailman-Bugs-967410 ] incorrect attachment URL in virtual host environment Message-ID: Bugs item #967410, was opened at 2004-06-06 12:40 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=967410&group_id=103 Category: Pipermail Group: None Status: Open Resolution: None Priority: 5 Submitted By: John Belmonte (jbelmonte) Assigned to: Nobody/Anonymous (nobody) Summary: incorrect attachment URL in virtual host environment Initial Comment: This bug still exists in 2.1.5: http://mail.python.org/pipermail/mailman-users/2003-April/028187.html ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=967410&group_id=103 From noreply at sourceforge.net Sun Jun 6 00:24:35 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jun 6 00:24:57 2004 Subject: [ mailman-Bugs-967410 ] incorrect attachment URL in virtual host environment Message-ID: Bugs item #967410, was opened at 2004-06-06 03:40 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=967410&group_id=103 Category: Pipermail Group: None Status: Open Resolution: None Priority: 5 Submitted By: John Belmonte (jbelmonte) Assigned to: Nobody/Anonymous (nobody) Summary: incorrect attachment URL in virtual host environment Initial Comment: This bug still exists in 2.1.5: http://mail.python.org/pipermail/mailman-users/2003-April/028187.html ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-06-06 04:24 Message: Logged In: YES user_id=67709 Try if this patch works for you. You must also re-generate archive from the mbox file to correct older archive and you may have to invoke fix_url.py. http://sourceforge.net/tracker/?func=detail&aid=789015&group_id=103&atid=300103 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=967410&group_id=103 From noreply at sourceforge.net Sun Jun 6 01:28:28 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jun 6 01:28:32 2004 Subject: [ mailman-Bugs-967454 ] Cannot sub address using dotted quad Message-ID: Bugs item #967454, was opened at 2004-06-06 00:28 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=967454&group_id=103 Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: measl (measl) Assigned to: Nobody/Anonymous (nobody) Summary: Cannot sub address using dotted quad Initial Comment: There is no way to subscribe someone at a dotted quad IP address. The argument of userx@[1.2.3.4] is rejected as an "illegal" address (although this is in fact the RFC correct way to do it). Interestingly, I can use userx@1.2.3.4 (note lack of brackets) successfully, but since this is technically not RFC compliant, many MTAs will refuse to accept it (e.g., postfix, and probably others). For example: 220 mx1.mfn.org ESMTP Postfix ehlo mfn.org 250-mx1.mfn.org 250-PIPELINING 250-SIZE 10240000 250-VRFY 250-ETRN 250 8BITMIME mail from: userx@mfn.org 250 Ok rcpt to: antisocial@192.168.155.108 501 Bad address syntax rcpt to: antisocial@[192.168.155.108] 250 Ok quit 221 Bye ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=967454&group_id=103 From noreply at sourceforge.net Mon Jun 7 12:51:34 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jun 7 12:51:38 2004 Subject: [ mailman-Bugs-968295 ] Invitation response bad interaction with autoreply Message-ID: Bugs item #968295, was opened at 2004-06-07 12:51 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=968295&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Paul Aitkenhead (unionchurch) Assigned to: Nobody/Anonymous (nobody) Summary: Invitation response bad interaction with autoreply Initial Comment: If the admin has set an autoreply message for the -request mailbox, the autoreply will be sent to a new subscriber that is replying to an invitation to join. This is undesirable because the autoreply feature is typically used to formulate a message like "If you intended to send a new posting, you sent it to the wrong address". ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=968295&group_id=103 From noreply at sourceforge.net Mon Jun 7 15:23:26 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jun 7 15:23:35 2004 Subject: [ mailman-Patches-931515 ] Provides more documentation for mass subscribing to the list Message-ID: Patches item #931515, was opened at 2004-04-08 01:15 Message generated for change (Comment added) made by progressd You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=931515&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Darrell Duane (progressd) Assigned to: Nobody/Anonymous (nobody) Summary: Provides more documentation for mass subscribing to the list Initial Comment: I've added documentation so that administrators who are mass subscribing members know the proper formats for associating names with e-mail addresses. ---------------------------------------------------------------------- >Comment By: Darrell Duane (progressd) Date: 2004-06-07 15:23 Message: Logged In: YES user_id=563493 I've added documentation so that administrators who are mass subscribing members know the proper formats for associating names with e-mail addresses. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=931515&group_id=103 From noreply at sourceforge.net Tue Jun 8 03:13:56 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jun 8 03:13:58 2004 Subject: [ mailman-Bugs-968680 ] PDF file for list members won't print Message-ID: Bugs item #968680, was opened at 2004-06-08 09:13 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=968680&group_id=103 Category: documentation Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ulrich Windl (windl) Assigned to: Nobody/Anonymous (nobody) Summary: PDF file for list members won't print Initial Comment: The file at http://mailman.sourceforge.net/mailman-member.pdf won't print with Adobe Acrobat 5: At page 3 it gets some error, saying the file can't be printed. My version has been created at 2003-10-07 18:17:00 with pdfTeX-0.14h. The file displays correctly on the screen however. If possible, provide a corrected PDF file, please ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=968680&group_id=103 From noreply at sourceforge.net Tue Jun 8 03:29:52 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Jun 8 03:29:55 2004 Subject: [ mailman-Bugs-968680 ] PDF file for list members won't print Message-ID: Bugs item #968680, was opened at 2004-06-08 09:13 Message generated for change (Comment added) made by windl You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=968680&group_id=103 Category: documentation Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ulrich Windl (windl) Assigned to: Nobody/Anonymous (nobody) Summary: PDF file for list members won't print Initial Comment: The file at http://mailman.sourceforge.net/mailman-member.pdf won't print with Adobe Acrobat 5: At page 3 it gets some error, saying the file can't be printed. My version has been created at 2003-10-07 18:17:00 with pdfTeX-0.14h. The file displays correctly on the screen however. If possible, provide a corrected PDF file, please ---------------------------------------------------------------------- >Comment By: Ulrich Windl (windl) Date: 2004-06-08 09:29 Message: Logged In: YES user_id=181779 After doing a "pdf2ps" and a "ps2pdf" (using Ghostscript 7), the file looked a lot uglier, but it could be printed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=968680&group_id=103 From noreply at sourceforge.net Wed Jun 9 09:54:28 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jun 9 09:54:33 2004 Subject: [ mailman-Bugs-969613 ] double-quotes incorrectly converted to HTML in header values Message-ID: Bugs item #969613, was opened at 2004-06-09 15:54 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=969613&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ulrich Windl (windl) Assigned to: Nobody/Anonymous (nobody) Summary: double-quotes incorrectly converted to HTML in header values Initial Comment: (I'll use a double exclamation mark (!!) instead of a double-quote here, because it seems the double-quotes are converted to """ here by mistake) If I enter a short description like the following line for a mailing list: List about !!something interesting!! mailman-2.1.4 cunnecessarily converts the double quotes (!!) to " in EMail header values. Example: List-Id: !!List about "something interesting" !! I think that the quoting in font of an EMail address enclosed by anglr brackets (<...>) is not necessary, and using HTML is wron and not portable. I might work with some broken clients however. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=969613&group_id=103 From noreply at sourceforge.net Wed Jun 9 15:39:32 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jun 9 15:39:36 2004 Subject: [ mailman-Bugs-864700 ] Extra period in attachment name problem Message-ID: Bugs item #864700, was opened at 2003-12-22 14:33 Message generated for change (Settings changed) made by kwgagel You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=864700&group_id=103 Category: None Group: 2.1 (stable) >Status: Deleted Resolution: None Priority: 5 Submitted By: Kevin W. Gagel (kwgagel) Assigned to: Nobody/Anonymous (nobody) Summary: Extra period in attachment name problem Initial Comment: Having more than one period "." in the name of an attachment causes mailman to disregard portions of the file name, including the extention of the file. For example a file named: PRESIDENT'S NEWSLETTER NO. 2 - 2003-2004 ACADEMIC December.pdf Results in a file attachment of: PRESIDENT'S_NEWSLETTER_NO._2_-_2003- 2004_ACADEMIC (the above is wraped by the textbox input). Sending the same file attachment directly to a user does not cause this problem. Sending it through mailman does result in the change to the file name and extenton. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-12-24 21:02 Message: Logged In: YES user_id=12800 Please upload a message which exibits this behavior. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=864700&group_id=103 From noreply at sourceforge.net Thu Jun 10 02:42:31 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jun 10 02:42:37 2004 Subject: [ mailman-Bugs-948064 ] email address will slashes Message-ID: Bugs item #948064, was opened at 2004-05-04 12:39 Message generated for change (Comment added) made by litrium You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=948064&group_id=103 Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Michael (ciberous) Assigned to: Nobody/Anonymous (nobody) Summary: email address will slashes Initial Comment: The mailing list login/(un)subscribe form does not accept email addresses with slashes in the name. In particular, the user has a LotusNotes email address which contains slashes. For example, an email address such as foo_bar/myschool/mydoe@notes.k12.hi.us will not be accepted by the form. It responds that the email address is illegal. ---------------------------------------------------------------------- Comment By: Vince Hoang (litrium) Date: 2004-06-09 20:42 Message: Logged In: YES user_id=635707 This patch for 2.1.4 removes / as a bad character to enable Lotus Notes compatibility. # diff -u Utils.py.old Utils.py --- Utils.py.old Wed Jun 9 20:37:06 2004 +++ Utils.py Wed Jun 9 20:36:58 2004 @@ -198,7 +198,7 @@ # TBD: what other characters should be disallowed? -_badchars = re.compile(r'[][()<>|;^,/\200-\377]') +_badchars = re.compile(r'[][()<>|;^,\200-\377]') def ValidateEmail(s): """Verify that the an email address isn't grossly evil.""" ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2004-05-12 08:10 Message: Logged In: NO I can confirm this bug on Mailman 2.1.4. Addresses with slashes are rejected as hostile although they conform to rfc822. Such addresses are also used on some systems to deliver mail to subfolders, e.g.: user+folder/subfolder@domain ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=948064&group_id=103 From noreply at sourceforge.net Thu Jun 10 09:57:33 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jun 10 10:31:17 2004 Subject: [ mailman-Patches-970383 ] moderator -1 admin requests pending Message-ID: Patches item #970383, was opened at 2004-06-10 22:57 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=970383&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Jim Tittsler (jtittsler) Assigned to: Nobody/Anonymous (nobody) Summary: moderator -1 admin requests pending Initial Comment: ListAdmin.NumRequestsPending() presumes that the request database always has at least one entry... a dummy "request" containing the version number of the request database. bin/newlist does not create a request database for each list, so the moderator gets a daily mail saying there are -1 requests pending. I propose that when __opendb() fails because the file didn't exist, the version number be added to the __db dict. Two additional points: - perhaps __open_db should ALWAYS add the version to the db, in case a request.pck somehow was created without a version key (especially since the version isn't currently checked) - the closedb setting of the version could *probably* be safely removed ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=970383&group_id=103 From noreply at sourceforge.net Thu Jun 10 15:00:07 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jun 10 15:00:10 2004 Subject: [ mailman-Bugs-970631 ] Invitation response bad interaction with autoreply Message-ID: Bugs item #970631, was opened at 2004-06-10 15:00 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=970631&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Paul Aitkenhead (unionchurch) Assigned to: Nobody/Anonymous (nobody) Summary: Invitation response bad interaction with autoreply Initial Comment: If the admin has set an autoreply message for the -request mailbox, the autoreply will be sent to a new subscriber that is replying to an invitation to join. This is undesirable because the autoreply feature is typically used to formulate a message like "If you intended to send a new posting, you sent it to the wrong address". ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=970631&group_id=103 From noreply at sourceforge.net Thu Jun 10 15:05:44 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jun 10 15:05:49 2004 Subject: [ mailman-Bugs-970631 ] Invitation response bad interaction with autoreply Message-ID: Bugs item #970631, was opened at 2004-06-10 15:00 Message generated for change (Settings changed) made by unionchurch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=970631&group_id=103 Category: None Group: None >Status: Deleted Resolution: None Priority: 5 Submitted By: Paul Aitkenhead (unionchurch) Assigned to: Nobody/Anonymous (nobody) Summary: Invitation response bad interaction with autoreply Initial Comment: If the admin has set an autoreply message for the -request mailbox, the autoreply will be sent to a new subscriber that is replying to an invitation to join. This is undesirable because the autoreply feature is typically used to formulate a message like "If you intended to send a new posting, you sent it to the wrong address". ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=970631&group_id=103 From noreply at sourceforge.net Thu Jun 10 15:09:33 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jun 10 15:09:38 2004 Subject: [ mailman-Bugs-896524 ] Explicit (non-80) port sometimes missing from URL Message-ID: Bugs item #896524, was opened at 2004-02-13 09:39 Message generated for change (Settings changed) made by unionchurch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=896524&group_id=103 Category: Web/CGI Group: 2.1 (stable) >Status: Deleted Resolution: None Priority: 5 Submitted By: Paul Aitkenhead (unionchurch) Assigned to: Nobody/Anonymous (nobody) Summary: Explicit (non-80) port sometimes missing from URL Initial Comment: I run my Mailman admin web site on a non-standard port which I stated back at build time using the configure tool. It works correctly but there is at least one link from which the port number is missing from the URL. It is the link for which the hyertext says "Overview of all myserver.mydomain.com lists". ---------------------------------------------------------------------- Comment By: Paul Aitkenhead (unionchurch) Date: 2004-03-01 10:17 Message: Logged In: YES user_id=974801 OK, I have learned more about this. The behavior comes about when generating the "Overvew" link as I mentioned when I first logged the bug report. The hypertest link is made by calling Mailman/Utils/ScriptURL(), which calls Mailman/Utils.py/get_domain(), which looks for an OS environment variable SERVER_PORT. The routine is probably relying on Apache to set SERVER_PORT as an enviornment variable in the cgi-bin execution process and it s not happening. Wouldn't it be better to just rely on DEFAULT_URL_HOST in Defaults.py ? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=896524&group_id=103 From noreply at sourceforge.net Fri Jun 11 00:40:48 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jun 11 00:40:52 2004 Subject: [ mailman-Patches-970873 ] typo in english template user options page Message-ID: Patches item #970873, was opened at 2004-06-11 13:40 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=970873&group_id=103 Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Jim Tittsler (jtittsler) Assigned to: Nobody/Anonymous (nobody) Summary: typo in english template user options page Initial Comment: says to delivery such non-matching messages to you. should be says to deliver such non-matching messages to you. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=970873&group_id=103 From noreply at sourceforge.net Fri Jun 11 18:02:47 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jun 11 18:02:54 2004 Subject: [ mailman-Bugs-896524 ] Explicit (non-80) port sometimes missing from URL Message-ID: Bugs item #896524, was opened at 2004-02-13 14:39 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=896524&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Deleted Resolution: None Priority: 5 Submitted By: Paul Aitkenhead (unionchurch) Assigned to: Nobody/Anonymous (nobody) Summary: Explicit (non-80) port sometimes missing from URL Initial Comment: I run my Mailman admin web site on a non-standard port which I stated back at build time using the configure tool. It works correctly but there is at least one link from which the port number is missing from the URL. It is the link for which the hyertext says "Overview of all myserver.mydomain.com lists". ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2004-06-11 22:02 Message: Logged In: YES user_id=75166 Per the CGI 1.1 spec (see http://hoohoo.ncsa.uiuc.edu/cgi/env.html), a Mailman CGI script is entitled to expect the SERVER_PORT environment variable to be set by the server before the script is run. ---------------------------------------------------------------------- Comment By: Paul Aitkenhead (unionchurch) Date: 2004-03-01 15:17 Message: Logged In: YES user_id=974801 OK, I have learned more about this. The behavior comes about when generating the "Overvew" link as I mentioned when I first logged the bug report. The hypertest link is made by calling Mailman/Utils/ScriptURL(), which calls Mailman/Utils.py/get_domain(), which looks for an OS environment variable SERVER_PORT. The routine is probably relying on Apache to set SERVER_PORT as an enviornment variable in the cgi-bin execution process and it s not happening. Wouldn't it be better to just rely on DEFAULT_URL_HOST in Defaults.py ? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=896524&group_id=103 From noreply at sourceforge.net Fri Jun 11 21:28:34 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jun 11 21:28:40 2004 Subject: [ mailman-Bugs-961587 ] Incorrect -1 or 1 messages in moderator queue Message-ID: Bugs item #961587, was opened at 2004-05-27 23:12 Message generated for change (Comment added) made by jtittsler You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=961587&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Matt Domsch (mdomsch) Assigned to: Nobody/Anonymous (nobody) Summary: Incorrect -1 or 1 messages in moderator queue Initial Comment: Mailman 2.1.5, upgraded from 2.1.4. Two different lists exhibit similar behaviour. One list gets admin notices daily that there are -1 messages in the moderator queue, when there are none displayed. A second list gets admin notices daily that there are 1 messages in the moderator queue, when there are none displayed. For this list, I have rmlist'd it and re-created it, to no avail. Please advise. ---------------------------------------------------------------------- Comment By: Jim Tittsler (jtittsler) Date: 2004-06-12 10:28 Message: Logged In: YES user_id=1488 One way to fix the "-1 messages" in the moderator queue is patch 970383. (The even easier solution is to create an empty requests.pck file for the list... either by having it process any administrative request, or copying an empty one from another list.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=961587&group_id=103 From noreply at sourceforge.net Sat Jun 12 23:36:32 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Jun 12 23:36:35 2004 Subject: [ mailman-Bugs-971957 ] Uncaught runner exception Message-ID: Bugs item #971957, was opened at 2004-06-13 03:36 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=971957&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: John Distler (jd_waverly) Assigned to: Nobody/Anonymous (nobody) Summary: Uncaught runner exception Initial Comment: In 2.1.5 Apparently some email message characters can crash the Runner.py. I have inserted $mailman in place of my mailman path in the message below from $mailman/logs/error Jun 12 01:25:48 2004 (16604) Uncaught runner exception: ASCII decoding error: ordinal not in range (128) Jun 12 01:25:48 2004 (16604) Traceback (most recent call last): File "$mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File $mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "$mailman/Mailman/Queue/CommandRunner.py", line 223, in _dispose res = Results(mlist, msg, msgdata) File "$mailman/Mailman/Queue/CommandRunner.py", line 77, in __init__ subj = make_header(decode_header (subj)).__unicode__() File "$mailman/pythonlib/email/Header.py", line 144, in make_header h.append(s, charset) File "$mailman/pythonlib/email/Header.py", line 272, in append ustr = unicode(s, incodec, errors) UnicodeError: ASCII decoding error: ordinal not in range (128) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=971957&group_id=103 From noreply at sourceforge.net Mon Jun 14 10:02:41 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jun 14 10:02:44 2004 Subject: [ mailman-Bugs-972562 ] No leading dash on email addresses accepted Message-ID: Bugs item #972562, was opened at 2004-06-14 09:02 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=972562&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: markcov (markcov) Assigned to: Nobody/Anonymous (nobody) Summary: No leading dash on email addresses accepted Initial Comment: mailman's web interface rejects emails that start with a dash. I.E. -username@domain.tld Running 2.1.1 on RH9 error message: Error subscribing: -test@domain.tld -- Hostile address (illegal characters) According to RFC2822 this should be a valid email address. (If I read it correctly) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=972562&group_id=103 From noreply at sourceforge.net Mon Jun 14 11:35:00 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jun 14 11:35:11 2004 Subject: [ mailman-Bugs-972607 ] 2.1.5 member moderation action Message-ID: Bugs item #972607, was opened at 2004-06-14 11:35 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=972607&group_id=103 Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Linda Betts (llbetts) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1.5 member moderation action Initial Comment: Via the mm_cfg.py file you can set Default_member_moderation_action to: 0=open 1=hold 2=reject 3=discard Via the web admin interface you can set this same option to 0=hold 1=reject 2=discard The web interface needs updated to include the 0=open option and to keep it consistant with the text file settings. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=972607&group_id=103 From noreply at sourceforge.net Mon Jun 14 11:57:41 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jun 14 11:58:01 2004 Subject: [ mailman-Bugs-972607 ] 2.1.5 member moderation action Message-ID: Bugs item #972607, was opened at 2004-06-14 11:35 Message generated for change (Comment added) made by llbetts You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=972607&group_id=103 Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Linda Betts (llbetts) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1.5 member moderation action Initial Comment: Via the mm_cfg.py file you can set Default_member_moderation_action to: 0=open 1=hold 2=reject 3=discard Via the web admin interface you can set this same option to 0=hold 1=reject 2=discard The web interface needs updated to include the 0=open option and to keep it consistant with the text file settings. ---------------------------------------------------------------------- >Comment By: Linda Betts (llbetts) Date: 2004-06-14 11:57 Message: Logged In: YES user_id=1063268 would suggest a change to the distribution Mailman/Gui/Privacy.py file to change line ( _('Hold'), _('Reject'), _('Discard')), 0, to (_('Open), _('Hold'), _('Reject'), _('Discard')), 0, So that the Open member_moderation_action option is available via the web interface. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=972607&group_id=103 From noreply at sourceforge.net Mon Jun 14 12:05:25 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jun 14 12:05:36 2004 Subject: [ mailman-Bugs-972607 ] 2.1.5 member moderation action Message-ID: Bugs item #972607, was opened at 2004-06-14 11:35 Message generated for change (Comment added) made by llbetts You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=972607&group_id=103 Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Linda Betts (llbetts) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1.5 member moderation action Initial Comment: Via the mm_cfg.py file you can set Default_member_moderation_action to: 0=open 1=hold 2=reject 3=discard Via the web admin interface you can set this same option to 0=hold 1=reject 2=discard The web interface needs updated to include the 0=open option and to keep it consistant with the text file settings. ---------------------------------------------------------------------- >Comment By: Linda Betts (llbetts) Date: 2004-06-14 12:05 Message: Logged In: YES user_id=1063268 actually I meant: (_('Open'), _('Hold'), _('Reject'), _('Discard')), 0, as the change to line(properly closed single quotes). ---------------------------------------------------------------------- Comment By: Linda Betts (llbetts) Date: 2004-06-14 11:57 Message: Logged In: YES user_id=1063268 would suggest a change to the distribution Mailman/Gui/Privacy.py file to change line ( _('Hold'), _('Reject'), _('Discard')), 0, to (_('Open), _('Hold'), _('Reject'), _('Discard')), 0, So that the Open member_moderation_action option is available via the web interface. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=972607&group_id=103 From noreply at sourceforge.net Mon Jun 14 12:35:40 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jun 14 12:35:45 2004 Subject: [ mailman-Bugs-961587 ] Incorrect -1 or 1 messages in moderator queue Message-ID: Bugs item #961587, was opened at 2004-05-27 09:12 Message generated for change (Comment added) made by mdomsch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=961587&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Matt Domsch (mdomsch) Assigned to: Nobody/Anonymous (nobody) Summary: Incorrect -1 or 1 messages in moderator queue Initial Comment: Mailman 2.1.5, upgraded from 2.1.4. Two different lists exhibit similar behaviour. One list gets admin notices daily that there are -1 messages in the moderator queue, when there are none displayed. A second list gets admin notices daily that there are 1 messages in the moderator queue, when there are none displayed. For this list, I have rmlist'd it and re-created it, to no avail. Please advise. ---------------------------------------------------------------------- >Comment By: Matt Domsch (mdomsch) Date: 2004-06-14 11:35 Message: Logged In: YES user_id=27266 The patch below solves the -1 messages problem, thanks. The 1 messages problem was operator error; I moved the service from one system to another, but didn't stop the crontabs on the first system, and it hadn't gotten its moderator queues cleared, so it kept sending mail. ---------------------------------------------------------------------- Comment By: Jim Tittsler (jtittsler) Date: 2004-06-11 20:28 Message: Logged In: YES user_id=1488 One way to fix the "-1 messages" in the moderator queue is patch 970383. (The even easier solution is to create an empty requests.pck file for the list... either by having it process any administrative request, or copying an empty one from another list.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=961587&group_id=103 From noreply at sourceforge.net Mon Jun 14 12:39:15 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jun 14 12:39:24 2004 Subject: [ mailman-Bugs-961587 ] Incorrect -1 messages in moderator queue Message-ID: Bugs item #961587, was opened at 2004-05-27 09:12 Message generated for change (Settings changed) made by mdomsch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=961587&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Matt Domsch (mdomsch) Assigned to: Nobody/Anonymous (nobody) >Summary: Incorrect -1 messages in moderator queue Initial Comment: Mailman 2.1.5, upgraded from 2.1.4. Two different lists exhibit similar behaviour. One list gets admin notices daily that there are -1 messages in the moderator queue, when there are none displayed. A second list gets admin notices daily that there are 1 messages in the moderator queue, when there are none displayed. For this list, I have rmlist'd it and re-created it, to no avail. Please advise. ---------------------------------------------------------------------- Comment By: Matt Domsch (mdomsch) Date: 2004-06-14 11:35 Message: Logged In: YES user_id=27266 The patch below solves the -1 messages problem, thanks. The 1 messages problem was operator error; I moved the service from one system to another, but didn't stop the crontabs on the first system, and it hadn't gotten its moderator queues cleared, so it kept sending mail. ---------------------------------------------------------------------- Comment By: Jim Tittsler (jtittsler) Date: 2004-06-11 20:28 Message: Logged In: YES user_id=1488 One way to fix the "-1 messages" in the moderator queue is patch 970383. (The even easier solution is to create an empty requests.pck file for the list... either by having it process any administrative request, or copying an empty one from another list.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=961587&group_id=103 From noreply at sourceforge.net Wed Jun 16 17:55:14 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jun 17 08:58:43 2004 Subject: [ mailman-Bugs-974290 ] unknown encoding crashes qrunner Message-ID: Bugs item #974290, was opened at 2004-06-16 17:55 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=974290&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Nathan Coraor (ncoraor) Assigned to: Nobody/Anonymous (nobody) Summary: unknown encoding crashes qrunner Initial Comment: Certain messages encoded with gb2312 are causing qrunner to crash. This is version 2.1.5. Here's the traceback: Jun 16 12:17:47 2004 (16350) Uncaught runner exception: unknown encoding: gb2312 Jun 16 12:17:48 2004 (16350) Traceback (most recent call last): File "/export/local/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/export/local/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/export/local/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/export/local/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/export/local/mailman/Mailman/Handlers/CookHeaders.py", line 74, in process prefix_subject(mlist, msg, msgdata) File "/export/local/mailman/Mailman/Handlers/CookHeaders.py", line 262, in prefix_subject h.append(s, c) File "/export/local/mailman/pythonlib/email/Header.py", line 285, in append s = s.encode(outcodec, errors) LookupError: unknown encoding: gb2312 Jun 16 12:17:48 2004 (16350) SHUNTING: 1087397495.8902061+fc54fd2fa39a5ae96ee648333b6f1adf782a385 7 Here are the message headers: From: =?GB2312?B?uePW3cfsyPA=?= Content-Type: text/plain;charset="GB2312" Content-Transfer-Encoding: 8bit ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=974290&group_id=103 From noreply at sourceforge.net Thu Jun 17 10:16:57 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jun 17 10:17:03 2004 Subject: [ mailman-Bugs-974759 ] HTML email and attachment archiving inconsistencies Message-ID: Bugs item #974759, was opened at 2004-06-17 14:16 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=974759&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Nick Bower (nickbower) Assigned to: Nobody/Anonymous (nobody) Summary: HTML email and attachment archiving inconsistencies Initial Comment: With archiving set to on and content filtering off (default options everywhere), I've encountered inconsistencies with the mail archiving and multipart attachments. If I send a HTML email, the arhived message correctly shows the text/plain porition with a link to the HTML version. However if I send a HTML email with an image attachment, the archived message shows nothing except for the link to the image. The original message (in either plain text or HTML) is lost. I would have expected the same plain text view with now 2 links to both the HTML part and image attachment. I've tested this with Outlook and Evolution. Note that if I send 1 or more images attached to a plain text message, everything works as expected. Thanks, Nick ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=974759&group_id=103 From noreply at sourceforge.net Wed Jun 16 16:43:03 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jun 17 12:49:49 2004 Subject: [ mailman-Patches-778929 ] templates/cs/listinfo.html: Small grammar fix Message-ID: Patches item #778929, was opened at 2003-07-28 15:44 Message generated for change (Comment added) made by danohnesorg You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=778929&group_id=103 Category: internationalization Group: None Status: Open Resolution: None Priority: 5 Submitted By: Rudolf Cejka (cejkar) Assigned to: Nobody/Anonymous (nobody) Summary: templates/cs/listinfo.html: Small grammar fix Initial Comment: Changed prohl?dnou to prohl?dnout. ---------------------------------------------------------------------- Comment By: Dan Ohnesorg (danohnesorg) Date: 2004-06-16 22:43 Message: Logged In: YES user_id=28644 Fixed ---------------------------------------------------------------------- Comment By: Martin Mokrejs (mmokrejs) Date: 2004-04-20 02:02 Message: Logged In: YES user_id=696559 This should be committed without any hesitation (it is actually a typo fix). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=778929&group_id=103 From noreply at sourceforge.net Fri Jun 18 02:20:30 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Jun 20 23:54:53 2004 Subject: [ mailman-Bugs-975145 ] Description of -owner field is wrong Message-ID: Bugs item #975145, was opened at 2004-06-18 08:20 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=975145&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Heiko (hgerstung) Assigned to: Nobody/Anonymous (nobody) Summary: Description of -owner field is wrong Initial Comment: In the web interface, list administration section "General options" there is a field called "umbrella_member_suffix", which is "-owner" by default. In the detailed help for this field it reads: When "umbrella_list" is set to indicate that this list has other mailing lists as members, then administrative notices like confirmations and password reminders need to not be sent to the member list addresses, but rather to the owner of those member lists. In that case, the value of this setting is appended to the member's account name for such notices. `-owner' is the typical choice. This setting has no effect when "umbrella_list" is "No". The last sentence indicates that this field is not used anywhere when the field umbrella_list is set to No. This is wrong, because the owner address is used in automatic replies sent to non-subscripted users trying to send a mail to the list, which is automatically rejected. So, I see two possibilities: Change the description of the field, saying that this suffix also is used for building the list owner address (e.g. list "xxx" means a xxx-owner@domain mail address) or (my favourite way) introduce a new field for setting up a list owner address AND be able to edit this "your message has been rejected" mail message (e.g. using a template for this), because even when I edit the LC_MESSAGES file, I have no chance to edit the english texts without diving into the sources, which makes upgrades a crap. Great software, keep on! Kind regards, Heiko ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=975145&group_id=103 From noreply at sourceforge.net Sat Jun 19 03:07:09 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jun 21 00:23:51 2004 Subject: [ mailman-Bugs-975768 ] senddigests doesn't handle consecutive unparseable messages Message-ID: Bugs item #975768, was opened at 2004-06-19 09:07 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=975768&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Andreas Voegele (voegelas) Assigned to: Nobody/Anonymous (nobody) Summary: senddigests doesn't handle consecutive unparseable messages Initial Comment: The following code fragment in send_i18n_digests in Mailman/ Handlers/ToDigest.py doesn't take into account that there could be several consecutive messages that are unparseable: msg = mbox.next() while msg is not None: if msg == '': # It was an unparseable message msg = mbox.next() [...] # Get the next message in the digest mailbox msg = mbox.next() I'm not that familiar with Python but I think that the following code should fix the problem: while 1: msg = mbox.next() if msg is None: break if msg == '': # It was an unparseable message continue [...] ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=975768&group_id=103 From noreply at sourceforge.net Thu Jun 24 03:21:54 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jun 24 03:22:03 2004 Subject: [ mailman-Bugs-975145 ] Description of -owner field is wrong Message-ID: Bugs item #975145, was opened at 2004-06-18 06:20 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=975145&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Heiko (hgerstung) Assigned to: Nobody/Anonymous (nobody) Summary: Description of -owner field is wrong Initial Comment: In the web interface, list administration section "General options" there is a field called "umbrella_member_suffix", which is "-owner" by default. In the detailed help for this field it reads: When "umbrella_list" is set to indicate that this list has other mailing lists as members, then administrative notices like confirmations and password reminders need to not be sent to the member list addresses, but rather to the owner of those member lists. In that case, the value of this setting is appended to the member's account name for such notices. `-owner' is the typical choice. This setting has no effect when "umbrella_list" is "No". The last sentence indicates that this field is not used anywhere when the field umbrella_list is set to No. This is wrong, because the owner address is used in automatic replies sent to non-subscripted users trying to send a mail to the list, which is automatically rejected. So, I see two possibilities: Change the description of the field, saying that this suffix also is used for building the list owner address (e.g. list "xxx" means a xxx-owner@domain mail address) or (my favourite way) introduce a new field for setting up a list owner address AND be able to edit this "your message has been rejected" mail message (e.g. using a template for this), because even when I edit the LC_MESSAGES file, I have no chance to edit the english texts without diving into the sources, which makes upgrades a crap. Great software, keep on! Kind regards, Heiko ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2004-06-24 07:21 Message: Logged In: YES user_id=75166 You observation is incorrect because the description is about the use of the field NOT the alias and it is NOT said that the alias specified is used for no other purpose. The -owner alias is defined on all lists and has other uses. The use of the -owner alias for other purposes is not directly related to its use as a target for certain types of message when the list is marked as being an umbrella list. If you do not want the -owner alias used this way when the list is an umbrella list you can define an alternative alias, -stuff for example, setting the field on the GUI accordingly. You can then specify what the incoming MTA is to do with messages addressed to the -stuff alias in whatever way you want (> /dev/null for instance) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=975145&group_id=103 From noreply at sourceforge.net Thu Jun 24 03:49:46 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Jun 24 03:49:52 2004 Subject: [ mailman-Bugs-975145 ] Description of -owner field is wrong Message-ID: Bugs item #975145, was opened at 2004-06-18 08:20 Message generated for change (Comment added) made by hgerstung You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=975145&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Heiko (hgerstung) Assigned to: Nobody/Anonymous (nobody) Summary: Description of -owner field is wrong Initial Comment: In the web interface, list administration section "General options" there is a field called "umbrella_member_suffix", which is "-owner" by default. In the detailed help for this field it reads: When "umbrella_list" is set to indicate that this list has other mailing lists as members, then administrative notices like confirmations and password reminders need to not be sent to the member list addresses, but rather to the owner of those member lists. In that case, the value of this setting is appended to the member's account name for such notices. `-owner' is the typical choice. This setting has no effect when "umbrella_list" is "No". The last sentence indicates that this field is not used anywhere when the field umbrella_list is set to No. This is wrong, because the owner address is used in automatic replies sent to non-subscripted users trying to send a mail to the list, which is automatically rejected. So, I see two possibilities: Change the description of the field, saying that this suffix also is used for building the list owner address (e.g. list "xxx" means a xxx-owner@domain mail address) or (my favourite way) introduce a new field for setting up a list owner address AND be able to edit this "your message has been rejected" mail message (e.g. using a template for this), because even when I edit the LC_MESSAGES file, I have no chance to edit the english texts without diving into the sources, which makes upgrades a crap. Great software, keep on! Kind regards, Heiko ---------------------------------------------------------------------- >Comment By: Heiko (hgerstung) Date: 2004-06-24 09:49 Message: Logged In: YES user_id=1009520 Sorry, but I did not get it. Is there any other field which is used to setup the list-owner address used in several messages or procedures? The field "owner" is used to setup "The list administrator email addresses." , so please let me suggest to use this field (e.g. the first entry) instead of the "list-owner" address which - this is unusual for mailman - seems to be hardcoded in sourcecode and can not be altered. This looks like a special requirement for me, but I do not want to have an alias "-owner" for every list I run, a single mail address used to let the list members know where they can get further help would be sufficient for me. So, please consider this as a humble request for feature: Do not use a hardcoded "-owner"-alias for creating reject messages or other types of error/notification messages, use the first "owner" address entry OR Create and use a template for those messages, which could easily be customized by everyone - even for the english language texts (which is not possible for the LC_MESSAGES, at the moment) Thank you very much for taking the time to answer me, kind regards, Heiko ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2004-06-24 09:21 Message: Logged In: YES user_id=75166 You observation is incorrect because the description is about the use of the field NOT the alias and it is NOT said that the alias specified is used for no other purpose. The -owner alias is defined on all lists and has other uses. The use of the -owner alias for other purposes is not directly related to its use as a target for certain types of message when the list is marked as being an umbrella list. If you do not want the -owner alias used this way when the list is an umbrella list you can define an alternative alias, -stuff for example, setting the field on the GUI accordingly. You can then specify what the incoming MTA is to do with messages addressed to the -stuff alias in whatever way you want (> /dev/null for instance) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=975145&group_id=103 From noreply at sourceforge.net Fri Jun 25 06:05:23 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Jun 25 06:05:29 2004 Subject: [ mailman-Bugs-979631 ] Better aliases generation for Postfix (webmin) Message-ID: Bugs item #979631, was opened at 2004-06-25 12:05 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=979631&group_id=103 Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Christophe Chisogne (wombachi) Assigned to: Nobody/Anonymous (nobody) Summary: Better aliases generation for Postfix (webmin) Initial Comment: The data/aliases file generated by MTA/Postfix.py can be slightly improved, notably when using webmin (little patch below). I didnt check if alias generation with other MTAs have the same problem. Postfix.py generates lines like # STANZA START: # CREATED: (...) # STANZA END: Problem is the "# CREATED:" line. To disable a mail alias, some admin simply put a '# ' in front of that alias. So that line could be interpreted as a user 'CREATED' that has been disabled. And webmin (v1.150, last one) just do that in the postfix module, displaying wrong infos for postfix aliases. That webmin module use a regex to check these 'disabled' aliases with this Perl code (sorry, not Python:) if (/^(#*)\s*([^:$ \t]+)\s*:\s*(.*)$/) The '# STANZA' lines dont match, so it's ok. But the '# CREATED:' line do match, causing wrong results in webmin. A simple solution is to replace the 'CREATED:' word with two word, by example 'ALIASES CREATED:' MTA/Postfix.py line 108 (mailman-2.1.5) print >> fp, '# CREATED:', time.ctime(time.time()) proposed change print >> fp, '# ALIASES CREATED:', time.ctime(time.time()) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=979631&group_id=103 From noreply at sourceforge.net Mon Jun 28 07:32:46 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jun 28 07:32:50 2004 Subject: [ mailman-Bugs-981188 ] Cannot cancel subscription on confirmation page Message-ID: Bugs item #981188, was opened at 2004-06-28 13:32 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=981188&group_id=103 Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: mranner (mranner) Assigned to: Nobody/Anonymous (nobody) Summary: Cannot cancel subscription on confirmation page Initial Comment: Bug in Mailman version 2.1.5 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/confirm.py", line 114, in main subscription_cancel(mlist, doc, cookie) File "/usr/local/mailman/Mailman/Cgi/confirm.py", line 312, in subscription_cancel userdesc = mlist.pend_confirm(cookie)[1] File "/usr/local/mailman/Mailman/Pending.py", line 141, in pend_confirm assert self.Locked() AssertionError Python information: Variable Value sys.version 2.3.3 (#1, Jan 10 2004, 17:19:45) [GCC 2.95.4 20020320 [FreeBSD]] sys.executable /usr/local/bin/python sys.prefix /usr/local sys.exec_prefix /usr/local sys.path /usr/local sys.platform freebsd4 Environment variables: Variable Value HTTP_REFERER https://secure.inforum.at/mailman/confirm/vinegar-newsletter/c082c7391977d2edb7c174f3ac3318964119fc24 SERVER_SOFTWARE Apache/1.3.31 (Unix) mod_gzip/1.3.26.1a DAV/1.0.3 FrontPage/5.0.2.2623 mod_ssl/2.8.18 OpenSSL/0.9.7c PHP/4.3.5 SCRIPT_NAME /mailman/confirm SERVER_SIGNATURE Apache/1.3.31 Server at secure.inforum.at Port 443 REQUEST_METHOD POST PATH_INFO /vinegar-newsletter SERVER_PROTOCOL HTTP/1.1 QUERY_STRING CONTENT_LENGTH 121 HTTP_ACCEPT_CHARSET iso-8859-15, utf-8;q=0.5, *;q=0.5 HTTP_USER_AGENT Mozilla/5.0 (compatible; Konqueror/3.2; FreeBSD; X11; i386) (KHTML, like Gecko) HTTP_CONNECTION Keep-Alive SERVER_NAME secure.inforum.at REMOTE_ADDR 213.229.17.146 PATH_TRANSLATED /www/virtual/secure.inforum.at/data/vinegar-newsletter SERVER_PORT 443 SERVER_ADDR 195.58.178.86 DOCUMENT_ROOT /www/virtual/secure.inforum.at/data HTTP_PRAGMA no-cache PYTHONPATH /usr/local/mailman SCRIPT_FILENAME /usr/local/mailman/cgi-bin/confirm SERVER_ADMIN webmaster@inforum.at HTTP_HOST secure.inforum.at HTTPS on HTTP_CACHE_CONTROL no-cache REQUEST_URI /mailman/confirm/vinegar-newsletter HTTP_ACCEPT text/html, image/jpeg, image/png, text/*, image/*, */* GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 49579 HTTP_ACCEPT_LANGUAGE de, en CONTENT_TYPE application/x-www-form-urlencoded HTTP_ACCEPT_ENCODING x-gzip, x-deflate, gzip, deflate UNIQUE_ID QOAAWMM6slYAAD56QB4 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=981188&group_id=103 From noreply at sourceforge.net Mon Jun 28 07:34:14 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Jun 28 07:34:19 2004 Subject: [ mailman-Bugs-981188 ] Cannot cancel subscription on confirmation page Message-ID: Bugs item #981188, was opened at 2004-06-28 13:32 Message generated for change (Comment added) made by mranner You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=981188&group_id=103 Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: mranner (mranner) Assigned to: Nobody/Anonymous (nobody) Summary: Cannot cancel subscription on confirmation page Initial Comment: Bug in Mailman version 2.1.5 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/confirm.py", line 114, in main subscription_cancel(mlist, doc, cookie) File "/usr/local/mailman/Mailman/Cgi/confirm.py", line 312, in subscription_cancel userdesc = mlist.pend_confirm(cookie)[1] File "/usr/local/mailman/Mailman/Pending.py", line 141, in pend_confirm assert self.Locked() AssertionError Python information: Variable Value sys.version 2.3.3 (#1, Jan 10 2004, 17:19:45) [GCC 2.95.4 20020320 [FreeBSD]] sys.executable /usr/local/bin/python sys.prefix /usr/local sys.exec_prefix /usr/local sys.path /usr/local sys.platform freebsd4 Environment variables: Variable Value HTTP_REFERER https://secure.inforum.at/mailman/confirm/vinegar-newsletter/c082c7391977d2edb7c174f3ac3318964119fc24 SERVER_SOFTWARE Apache/1.3.31 (Unix) mod_gzip/1.3.26.1a DAV/1.0.3 FrontPage/5.0.2.2623 mod_ssl/2.8.18 OpenSSL/0.9.7c PHP/4.3.5 SCRIPT_NAME /mailman/confirm SERVER_SIGNATURE Apache/1.3.31 Server at secure.inforum.at Port 443 REQUEST_METHOD POST PATH_INFO /vinegar-newsletter SERVER_PROTOCOL HTTP/1.1 QUERY_STRING CONTENT_LENGTH 121 HTTP_ACCEPT_CHARSET iso-8859-15, utf-8;q=0.5, *;q=0.5 HTTP_USER_AGENT Mozilla/5.0 (compatible; Konqueror/3.2; FreeBSD; X11; i386) (KHTML, like Gecko) HTTP_CONNECTION Keep-Alive SERVER_NAME secure.inforum.at REMOTE_ADDR 213.229.17.146 PATH_TRANSLATED /www/virtual/secure.inforum.at/data/vinegar-newsletter SERVER_PORT 443 SERVER_ADDR 195.58.178.86 DOCUMENT_ROOT /www/virtual/secure.inforum.at/data HTTP_PRAGMA no-cache PYTHONPATH /usr/local/mailman SCRIPT_FILENAME /usr/local/mailman/cgi-bin/confirm SERVER_ADMIN webmaster@inforum.at HTTP_HOST secure.inforum.at HTTPS on HTTP_CACHE_CONTROL no-cache REQUEST_URI /mailman/confirm/vinegar-newsletter HTTP_ACCEPT text/html, image/jpeg, image/png, text/*, image/*, */* GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 49579 HTTP_ACCEPT_LANGUAGE de, en CONTENT_TYPE application/x-www-form-urlencoded HTTP_ACCEPT_ENCODING x-gzip, x-deflate, gzip, deflate UNIQUE_ID QOAAWMM6slYAAD56QB4 ---------------------------------------------------------------------- >Comment By: mranner (mranner) Date: 2004-06-28 13:34 Message: Logged In: YES user_id=1072505 cannot cancel "pending" subscribtion on confirmation page ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=981188&group_id=103 From noreply at sourceforge.net Wed Jun 30 06:18:10 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jun 30 06:18:14 2004 Subject: [ mailman-Patches-982644 ] command line util for setting member options Message-ID: Patches item #982644, was opened at 2004-06-30 10:18 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=982644&group_id=103 Category: command line scripts Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: fvm (mfvmheise) Assigned to: Nobody/Anonymous (nobody) Summary: command line util for setting member options Initial Comment: I missed a command line tool for setting user options, so I modified remove_members to fit my needs. The tool won't check whether a list is digestable or not, if it is not and you set digest to 1, the script will fail with an uncaught exception. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=982644&group_id=103 From noreply at sourceforge.net Wed Jun 30 16:40:14 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Jun 30 16:40:22 2004 Subject: [ mailman-Feature Requests-983002 ] Add names to roster Message-ID: Feature Requests item #983002, was opened at 2004-06-30 16:40 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=983002&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jason Diceman (jasondiceman) Assigned to: Nobody/Anonymous (nobody) Summary: Add names to roster Initial Comment: On /mailman/roster/listname it would be great to see names beside email email. Also, unless the user is logged in as admin, each subscriber should not link to their admin page. Thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=983002&group_id=103