From noreply at sourceforge.net Mon Mar 1 10:17:36 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 1 10:17:41 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 (Comment added) 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: Open 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 Tue Mar 2 11:40:25 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 2 11:40:30 2004 Subject: [ mailman-Bugs-908414 ] www.list.org/faq.html "personalization" entry Message-ID: Bugs item #908414, was opened at 2004-03-02 11: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=908414&group_id=103 Category: documentation Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nathan Stratton Treadway (nathanst) Assigned to: Nobody/Anonymous (nobody) Summary: www.list.org/faq.html "personalization" entry Initial Comment: The FAQ located at http://www.list.org/faq.html has a section on "Can I put the user's address in the footer that Mailman adds" (currently question #4) says that various "VERP" variables need to be set in the mm_cfg.py file to turn on that site's lists' "personalization" option. But, of course, these control the VERP settings, not "personalization" itself (and, in particular, setting those variables will not actually turn the "personalize" option on that site's lists' configuration screens, as described in the paragraph immedately below those lines). I believe this section should instead give this (single) assigment line: OWNERS_CAN_ENABLE_PERSONALIZATION = 1 Thanks. Nathan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=908414&group_id=103 From noreply at sourceforge.net Tue Mar 2 20:40:28 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 2 20:40:33 2004 Subject: [ mailman-Bugs-908709 ] add-dup-header traceback Message-ID: Bugs item #908709, was opened at 2004-03-02 22: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=908709&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Juan M. Cataldo S. (jcataldo) Assigned to: Nobody/Anonymous (nobody) Summary: add-dup-header traceback Initial Comment: I think I've found a bug in Mailman from Fedora Core 1 (all errata applied). Every time someone sends a message to a list and includes in the To: or Cc: header the address of a member, a traceback like the following appears in logs/error and the message is shunted: ---------------------------------- Traceback (most recent call last): File "/var/mailman/bin/qrunner", line 270, in ? main() File "/var/mailman/bin/qrunner", line 230, in main qrunner.run() File "/var/mailman/Mailman/Queue/Runner.py", line 65, in run filecnt = self._oneloop() File "/var/mailman/Mailman/Queue/Runner.py", line 93, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File "/var/mailman/Mailman/Queue/Switchboard.py", line 156, in dequeue data = self._ext_read(dbfile) File "/var/mailman/Mailman/Queue/Switchboard.py", line 334, in _ext_read execfile(filename, dict) File "/var/mailman/qfiles/out/1078272688.60232+88a4bf4cb1ad84bb7e897338fb28343d98042476.db", line 5 add-dup-header = {'lgarcia@inf.utfsm.cl': 1, 'jcataldo@inf.utfsm.cl': 1} SyntaxError: can't assign to operator ---------------------------------- For this example, I created a list whose members are my girlfriend and me, and then I sent a message with us in the Cc: I've studied the 107827...42476.db file, and the value "add-dup-header" seems to be wrong (I don't know anything about the Mailman internals, so please don't flame me). If I change it to "add_dup_header" and run bin/unshunt, the message is processed without errors. I don't know if this breaks something, but as a workaround I've edited Mailman/Handlers/AvoidDuplicates.py and Mailman/Handlers/SMTPDirect.py to replace "add-dup-header" for "add_dup_header" and the problem stopped happening. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=908709&group_id=103 From noreply at sourceforge.net Tue Mar 2 22:03:23 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 2 22:03:26 2004 Subject: [ mailman-Bugs-908747 ] MAILMAN_URL documentation in Defaults.py Message-ID: Bugs item #908747, was opened at 2004-03-02 22:03 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=908747&group_id=103 Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Nathan Stratton Treadway (nathanst) Assigned to: Nobody/Anonymous (nobody) Summary: MAILMAN_URL documentation in Defaults.py Initial Comment: I see that the Mailman footer logos have not been HTML links to the "home" web sites since revision 2.5 of the htmlformat.py file -- but, for whatever reason, the footer does still have links to those sites when the Image Logos are tuned off. As far as I can tell, the only time the MAILMAN_URL setting is ever used is in this page footing -- and then it's used only when logos are disabled. It seems like the explaination of MAILMAN_URL in Defaults.py should be updated to mention this fact (assuming it's true). Or, htmlformat.py could be edited so that the text-only footer doesn't have links, either, and MAILMAN_URL could then be eliminated from Defaults.py completely. (The variables PYTHON_URL and GNU_URL could be eliminated from htmlformat.py, too.) (I bring this up because I saw the MAILMAN_URL mentioned in Defaults.py as I was setting up my site, and then wondered what I had done wrong/misconfigured when the Mailman icon did not take me to the Mailman web site as I expected....) Thanks. Nathan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=908747&group_id=103 From noreply at sourceforge.net Wed Mar 3 00:29:55 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Mar 3 02:15:38 2004 Subject: [ mailman-Bugs-908819 ] content filter logging Message-ID: Bugs item #908819, was opened at 2004-03-03 00:29 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=908819&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Nathan Stratton Treadway (nathanst) Assigned to: Nobody/Anonymous (nobody) Summary: content filter logging Initial Comment: When the SpamAssassin plugin causes a message to be discarded, it puts two lines in the vette log file, one to say why the message is discarded, and the other giving the message id: Mar 02 22:43:20 2004 (23164) sqr-users post from kcsdrrnbbh@qwxx.com discarded: SpamAssassin score was 16.7 (discard threshold is 10) Mar 02 22:43:20 2004 (23164) Message discarded, msgid: But when the Content Filter is set to "discard" and a message is discarded, only the second of these log entries is generated. Looking back through the vette log, it's not immediately obvious why that particular message was discarded. On the other hand, when the filter is set to "reject", the user is given an explaination of the rejection (e.g. "The message's content type was not explicitly allowed"). Could this explaination message be sent to the vette log when the message is getting discarded? Thanks. Nathan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=908819&group_id=103 From noreply at sourceforge.net Wed Mar 3 00:46:45 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Mar 3 04:53:44 2004 Subject: [ mailman-Bugs-908825 ] content filtering: replacing deleted parts with a warning Message-ID: Bugs item #908825, was opened at 2004-03-03 00: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=908825&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Nathan Stratton Treadway (nathanst) Assigned to: Nobody/Anonymous (nobody) Summary: content filtering: replacing deleted parts with a warning Initial Comment: The Mailman content filter currently strips out forbidden mime-parts from a multi-part message without any trace and with no warning. It would be nice to have a configuration option that tells the filter to replace any deleted part with a text/plain part which says something like "The message part originally found here had a forbitten MIME type xxxx/xxxx, and has been deleted." (That way, when users try to send attachments they'll at least know why the attachment isn't there any more.) Thanks. Nathan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=908825&group_id=103 From noreply at sourceforge.net Wed Mar 3 21:04:11 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Mar 3 21:04:15 2004 Subject: [ mailman-Bugs-909490 ] spams get shunted in CommandRunner Message-ID: Bugs item #909490, was opened at 2004-03-04 02:04 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=909490&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: spams get shunted in CommandRunner Initial Comment: If a spam which is directed to -request address has non-ascii subject, it is shunted by UnicodeError and the shunt directory will become full of such spams. I attach a patch to solve this by simply ignore this error. Here is the symptom in logs/error Mar 04 02:42:42 2004 (49945) Uncaught runner exception: ASCII decoding error: ordinal not in range(128) Mar 04 02:42:42 2004 (49945) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 113, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 163, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 223, in _dispose res = Results(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 77, in __init__ subj = make_header(decode_header(subj)).__unicode__() File "/usr/local/mailman/pythonlib/email/Header.py", line 144, in make_header h.append(s, charset) File "/usr/local/mailman/pythonlib/email/Header.py", line 272, in append ustr = unicode(s, incodec, errors) UnicodeError: ASCII decoding error: ordinal not in range(128) Mar 04 02:42:42 2004 (49945) SHUNTING: 1078335762.1569669+8f2d3dab0e864eb48672a4 eb8d4d0cae8f56c595 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=909490&group_id=103 From noreply at sourceforge.net Wed Mar 3 21:32:58 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Mar 3 21:33:19 2004 Subject: [ mailman-Patches-873035 ] subject handling in -request mail Message-ID: Patches item #873035, was opened at 2004-01-08 12:32 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=873035&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None >Priority: 7 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: subject handling in -request mail Initial Comment: Since spammers get one of our '-request' mail command address as target, we frequently get following error log and many such messages shunted. Jan 08 10:17:02 2004 (11705) Uncaught runner exception: ASCII decoding error: ordinal not in range(128) Jan 08 10:17:02 2004 (11705) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 110, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 160, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 223, in _dispose res = Results(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 77, in __init__ subj = make_header(decode_header(subj)).__unicode__() File "/usr/local/mailman/pythonlib/email/Header.py", line 144, in make_header h.append(s, charset) File "/usr/local/mailman/pythonlib/email/Header.py", line 272, in append ustr = unicode(s, incodec, errors) UnicodeError: ASCII decoding error: ordinal not in range(128) Jan 08 10:17:02 2004 (11705) SHUNTING: 1073506489.162806+2102abfa360c02ffb7bebbce12c1b9f09d8139f9 Apparently, following patch to Queue/CommandRunner.py may solve this problem. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-03-04 02:32 Message: Logged In: YES user_id=67709 Ok, I double-posted this item. So, raise the priority. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=873035&group_id=103 From noreply at sourceforge.net Wed Mar 3 21:34:37 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Mar 3 21:34:45 2004 Subject: [ mailman-Bugs-909490 ] spams get shunted in CommandRunner Message-ID: Bugs item #909490, was opened at 2004-03-04 02:04 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=909490&group_id=103 Category: mail delivery Group: 2.1 (stable) >Status: Closed Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: spams get shunted in CommandRunner Initial Comment: If a spam which is directed to -request address has non-ascii subject, it is shunted by UnicodeError and the shunt directory will become full of such spams. I attach a patch to solve this by simply ignore this error. Here is the symptom in logs/error Mar 04 02:42:42 2004 (49945) Uncaught runner exception: ASCII decoding error: ordinal not in range(128) Mar 04 02:42:42 2004 (49945) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 113, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 163, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 223, in _dispose res = Results(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 77, in __init__ subj = make_header(decode_header(subj)).__unicode__() File "/usr/local/mailman/pythonlib/email/Header.py", line 144, in make_header h.append(s, charset) File "/usr/local/mailman/pythonlib/email/Header.py", line 272, in append ustr = unicode(s, incodec, errors) UnicodeError: ASCII decoding error: ordinal not in range(128) Mar 04 02:42:42 2004 (49945) SHUNTING: 1078335762.1569669+8f2d3dab0e864eb48672a4 eb8d4d0cae8f56c595 ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-03-04 02:34 Message: Logged In: YES user_id=67709 Closing because of double post. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=909490&group_id=103 From noreply at sourceforge.net Thu Mar 4 00:40:45 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 4 09:23:09 2004 Subject: [ mailman-Bugs-909548 ] VERP_CONFIRMATIONS only applies to "invites" Message-ID: Bugs item #909548, was opened at 2004-03-04 00: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=909548&group_id=103 Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Nathan Stratton Treadway (nathanst) Assigned to: Nobody/Anonymous (nobody) Summary: VERP_CONFIRMATIONS only applies to "invites" Initial Comment: It appears that VERP_CONFIRMATIONS=1 in the mm_cfg.py file only turns on VERP-style messages for confirmations sent as a result of an "Invitation" on the "Mass Subscription" administration page -- not those send when the user subscribes or unsubscribes him/herself from the web page or via e-mail. I don't know if there is a reason this was only implemented for Invitations, but if the other VERP-style confirmations aren't soon going to be added, I would recommend adding an explanation of the situation to the relevent section of Defaults.py. (e.g. "Currently, VERP confirmations are only implemented for Invitations sent by the list administrator from the Mass Subscription administrative page; other confirmation messages will still be sent using default (i.e. less friendly) Subject line." ) Nathan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=909548&group_id=103 From noreply at sourceforge.net Sun Mar 7 18:19:06 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Mar 7 18:19:09 2004 Subject: [ mailman-Bugs-911648 ] AttributeError: 'module' object has no attribute 'UserDesc' Message-ID: Bugs item #911648, was opened at 2004-03-08 00:19 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=911648&group_id=103 Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: cYbErDaRk (cyberdark) Assigned to: Nobody/Anonymous (nobody) Summary: AttributeError: 'module' object has no attribute 'UserDesc' Initial Comment: When adding members via InviteNewMember, and he/she receives the emails asking for confirmation, this is the message shown when clicking: Bug in Mailman version 2.1.3 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/cpanel/3rdparty/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/cpanel/3rdparty/mailman/Mailman/Cgi/conf irm.py", line 98, in main content = Pending.confirm(cookie,expunge=0) File "/usr/local/cpanel/3rdparty/mailman/Mailman/Pending. py", line 125, in confirm db = _load() File "/usr/local/cpanel/3rdparty/mailman/Mailman/Pending. py", line 177, in _load return cPickle.load(fp) AttributeError: 'module' object has no attribute 'UserDesc' ------------------------------------------------------ -------------------------- Python information: Variable Value sys.version 2.2.2 (#1, Feb 24 2003, 19:13:11) [GCC 3.2.2 20030222 (Red Hat Linux 3.2.2-4)] sys.executable /usr/bin/python2 sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 ------------------------------------------------------ -------------------------- Environment variables: Variable Value HTTP_COOKIE cyberdark.net- publicidad_cyberdark.net+admin=28020000006935414b40 73280000003036383862303235613332633465656639303 3663931313636373239303764653936643035366334; SERVER_SOFTWARE Apache PYTHONPATH /usr/local/cpanel/3rdparty/mailman SCRIPT_FILENAME /usr/local/cpanel/3rdparty/mailman/c gi-bin/confirm SERVER_ADMIN webmaster@cyberdark.net SCRIPT_NAME /mailman/confirm REQUEST_METHOD GET HTTP_HOST cyberdark.net PATH_INFO /cyberdark.net- publicidad_cyberdark.net/9e9879dd657f06ad0871de5631 6c40405d054fcf SERVER_PROTOCOL HTTP/1.1 QUERY_STRING REQUEST_URI /mailman/confirm/cyberdark.net- publicidad_cyberdark.net/9e9879dd657f06ad0871de5631 6c40405d054fcf HTTP_ACCEPT image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/msword, application/vnd.ms- powerpoint, application/vnd.ms-excel, application/x- shockwave-flash, */* HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) SERVER_NAME www.cyberdark.net REMOTE_ADDR -- HTTP_CLIENT_IP -- REMOTE_PORT 58674 HTTP_ACCEPT_LANGUAGE es,eu;q=0.5 HTTP_VIA HTTP/1.1 proxy[AC1E0E47] (Traffic- Server/5.5.1-59096 [uScM]) PATH_TRANSLATED /home/cdkadmin/public_html/cyberd ark.net- publicidad_cyberdark.net/9e9879dd657f06ad0871de5631 6c40405d054fcf SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 HTTP_X_FORWARDED_FOR -- HTTP_ACCEPT_ENCODING gzip, deflate SERVER_ADDR -- DOCUMENT_ROOT /home/cdkadmin/public_html ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=911648&group_id=103 From noreply at sourceforge.net Mon Mar 8 21:57:58 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 8 21:58:03 2004 Subject: [ mailman-Patches-912448 ] Config setting to force relative URLs Message-ID: Patches item #912448, was opened at 2004-03-09 02: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=912448&group_id=103 Category: None Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Steve Kostecke (kostecke) Assigned to: Nobody/Anonymous (nobody) Summary: Config setting to force relative URLs Initial Comment: Mailman 2.1.1 uses absolute URLs for all references to mailing lists. This behavior may be useful when one Mailman installation runs lists on multiple virtual hosts. However, this behavior reduces the flexibility of Mailman by making it impossible to use Mailman in configurations where you need to be able to use different hostnames to refer to the same lists (e.g. where HTTP and HTTPS use different virtual hosts). This patch modifies the ScriptURL function in ./Mailman/Utils.py to allow relative URLs to be forced by setting a mm_cfg configuration variable: RELATIVE_URLS. This patch also modifies Defaults.py to provide the default value for RELATIVE_URLS. 
--- Utils.py.orig       Tue Mar  9 02:45:20 2004
+++ Utils.py    Tue Mar  9 02:10:51 2004
@@ -238,7 +238,7 @@
         fullpath = os.environ.get('SCRIPT_NAME', '') +                     os.environ.get('PATH_INFO', '')
     baseurl = urlparse.urlparse(web_page_url)[2]
-    if not absolute and fullpath.endswith(baseurl):
+    if mm_cfg.RELATIVE_URLS or not absolute and
fullpath.endswith(baseurl):
         # Use relative addressing
         fullpath = fullpath[len(baseurl):]
         i = fullpath.find('?')

--- Defaults.py.orig    Tue Mar  9 02:44:44 2004
+++ Defaults.py Tue Mar  9 02:15:13 2004
@@ -782,6 +782,9 @@
 # list's config variable default_member_moderation.
 DEFAULT_NEW_MEMBER_OPTIONS = 256
 
+# Set this to 1 to enable relative URLs.
+RELATIVE_URLS = 0

 #####
 # List defaults.  NOTE: Changing these values does NOT
change the
---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=912448&group_id=103 From noreply at sourceforge.net Tue Mar 9 16:09:29 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 9 16:09:34 2004 Subject: [ mailman-Feature Requests-913035 ] Headertrimmer builtin to Mailman Message-ID: Feature Requests item #913035, was opened at 2004-03-09 22:09 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=913035&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: David B (duelago) Assigned to: Nobody/Anonymous (nobody) Summary: Headertrimmer builtin to Mailman Initial Comment: A script to filter mail and manipulate arbitrary unstructured mailheaders. Get rid of multiple subjectmutations (like these: "Re:?RE:?[mylist]?SV:?Aw:?Re:[mylist]?Re:[mylist]") in to a nice header. Look at this version in perl http://x42.com/software/mail/ Fully honours RFC2047 for unstructured headers and is therefore perfect for 8-bit-charset-people in the old, eastern and other non- english part of the world. Re-encodes headers to ensure that they follow RFC2047 as a lot of clients break the standard which is the cause of MIME-headermutations. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=913035&group_id=103 From noreply at sourceforge.net Wed Mar 10 00:38:29 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Mar 10 00:38:35 2004 Subject: [ mailman-Patches-912448 ] Config setting to force relative URLs Message-ID: Patches item #912448, was opened at 2004-03-08 18:57 Message generated for change (Comment added) made by multitalents You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=912448&group_id=103 Category: None Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Steve Kostecke (kostecke) Assigned to: Nobody/Anonymous (nobody) Summary: Config setting to force relative URLs Initial Comment: Mailman 2.1.1 uses absolute URLs for all references to mailing lists. This behavior may be useful when one Mailman installation runs lists on multiple virtual hosts. However, this behavior reduces the flexibility of Mailman by making it impossible to use Mailman in configurations where you need to be able to use different hostnames to refer to the same lists (e.g. where HTTP and HTTPS use different virtual hosts). This patch modifies the ScriptURL function in ./Mailman/Utils.py to allow relative URLs to be forced by setting a mm_cfg configuration variable: RELATIVE_URLS. This patch also modifies Defaults.py to provide the default value for RELATIVE_URLS. 
--- Utils.py.orig       Tue Mar  9 02:45:20 2004
+++ Utils.py    Tue Mar  9 02:10:51 2004
@@ -238,7 +238,7 @@
         fullpath = os.environ.get('SCRIPT_NAME', '') +                     os.environ.get('PATH_INFO', '')
     baseurl = urlparse.urlparse(web_page_url)[2]
-    if not absolute and fullpath.endswith(baseurl):
+    if mm_cfg.RELATIVE_URLS or not absolute and
fullpath.endswith(baseurl):
         # Use relative addressing
         fullpath = fullpath[len(baseurl):]
         i = fullpath.find('?')

--- Defaults.py.orig    Tue Mar  9 02:44:44 2004
+++ Defaults.py Tue Mar  9 02:15:13 2004
@@ -782,6 +782,9 @@
 # list's config variable default_member_moderation.
 DEFAULT_NEW_MEMBER_OPTIONS = 256
 
+# Set this to 1 to enable relative URLs.
+RELATIVE_URLS = 0

 #####
 # List defaults.  NOTE: Changing these values does NOT
change the
---------------------------------------------------------------------- Comment By: Multitalents (multitalents) Date: 2004-03-09 21:38 Message: Logged In: YES user_id=994460 Your patch seems to be fine for the web interface but it breaks the URLs in e-mail notifications. Relative URLs are worthless in e-mails. Any ideas on how to fix this? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=912448&group_id=103 From noreply at sourceforge.net Wed Mar 10 05:53:07 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Mar 10 05:53:13 2004 Subject: [ mailman-Bugs-913397 ] Subscriber E-Mail-Address: GlobalChange causes removal Message-ID: Bugs item #913397, was opened at 2004-03-10 11:53 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=913397&group_id=103 Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: chris-taylor (chris-taylor) Assigned to: Nobody/Anonymous (nobody) Summary: Subscriber E-Mail-Address: GlobalChange causes removal Initial Comment: A subscriber of some mailinglists on my site tried to change his email address globally. The change for one of the lists only affected a correction of upper- and lower-case letters in the local part of the address(e.g. will.smith@... -> Will.Smith@....). After confirming the change an error occured and the subscriber was completely unsubscribed from the list. Neither the old address nor the new address were registered in the subscribers list. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=913397&group_id=103 From noreply at sourceforge.net Thu Mar 11 11:28:12 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 11 11:28:16 2004 Subject: [ mailman-Bugs-914249 ] Virus posts to moderated lists Message-ID: Bugs item #914249, was opened at 2004-03-11 10: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=914249&group_id=103 Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ted Peterson (knighted) Assigned to: Nobody/Anonymous (nobody) Summary: Virus posts to moderated lists Initial Comment: The W32.Beagle virus has been able to post multiple times to a moderated Mailman 2.1.3 mailing list, so emergency moderation of the list has been enabled. At least two other people, as reported on mailman-users, have had this trouble since last Friday, March 5th, when W32.Beagle was spreading. The virus was posting using a moderator address, so that moderator was removed. The moderator bit is and was turned on for all users, including the now *sole* moderator. I can send the mbox archive headers to anybody who is interested. Mail: ted ire.org --Ted ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=914249&group_id=103 From noreply at sourceforge.net Thu Mar 11 12:20:09 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 11 12:20:21 2004 Subject: [ mailman-Bugs-914249 ] Virus posts to moderated lists Message-ID: Bugs item #914249, was opened at 2004-03-11 10:28 Message generated for change (Comment added) made by karres You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=914249&group_id=103 Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ted Peterson (knighted) Assigned to: Nobody/Anonymous (nobody) Summary: Virus posts to moderated lists Initial Comment: The W32.Beagle virus has been able to post multiple times to a moderated Mailman 2.1.3 mailing list, so emergency moderation of the list has been enabled. At least two other people, as reported on mailman-users, have had this trouble since last Friday, March 5th, when W32.Beagle was spreading. The virus was posting using a moderator address, so that moderator was removed. The moderator bit is and was turned on for all users, including the now *sole* moderator. I can send the mbox archive headers to anybody who is interested. Mail: ted ire.org --Ted ---------------------------------------------------------------------- Comment By: dk (karres) Date: 2004-03-11 11:20 Message: Logged In: YES user_id=995621 More generally we have only moderated, read-only lists for our users. All incoming, non-member messages should be discarded. We are seeing a few virus laden messages from obvious non-members getting past the non-member filters. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=914249&group_id=103 From noreply at sourceforge.net Thu Mar 11 12:28:21 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 11 12:28:26 2004 Subject: [ mailman-Bugs-914249 ] Virus posts to moderated lists Message-ID: Bugs item #914249, was opened at 2004-03-11 10:28 Message generated for change (Comment added) made by karres You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=914249&group_id=103 Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ted Peterson (knighted) Assigned to: Nobody/Anonymous (nobody) Summary: Virus posts to moderated lists Initial Comment: The W32.Beagle virus has been able to post multiple times to a moderated Mailman 2.1.3 mailing list, so emergency moderation of the list has been enabled. At least two other people, as reported on mailman-users, have had this trouble since last Friday, March 5th, when W32.Beagle was spreading. The virus was posting using a moderator address, so that moderator was removed. The moderator bit is and was turned on for all users, including the now *sole* moderator. I can send the mbox archive headers to anybody who is interested. Mail: ted ire.org --Ted ---------------------------------------------------------------------- Comment By: dk (karres) Date: 2004-03-11 11:28 Message: Logged In: YES user_id=995621 ... sorry, hit the submit button too soon... THe nom-member messages that get past the non-member filter are being caught by the forced moderation so the messages are not getting to the list itself. It does make us nervous though. ---------------------------------------------------------------------- Comment By: dk (karres) Date: 2004-03-11 11:20 Message: Logged In: YES user_id=995621 More generally we have only moderated, read-only lists for our users. All incoming, non-member messages should be discarded. We are seeing a few virus laden messages from obvious non-members getting past the non-member filters. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=914249&group_id=103 From noreply at sourceforge.net Thu Mar 11 14:15:31 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 11 14:15:38 2004 Subject: [ mailman-Bugs-914249 ] Virus posts to moderated lists Message-ID: Bugs item #914249, was opened at 2004-03-11 11:28 Message generated for change (Comment added) made by nes49 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=914249&group_id=103 Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ted Peterson (knighted) Assigned to: Nobody/Anonymous (nobody) Summary: Virus posts to moderated lists Initial Comment: The W32.Beagle virus has been able to post multiple times to a moderated Mailman 2.1.3 mailing list, so emergency moderation of the list has been enabled. At least two other people, as reported on mailman-users, have had this trouble since last Friday, March 5th, when W32.Beagle was spreading. The virus was posting using a moderator address, so that moderator was removed. The moderator bit is and was turned on for all users, including the now *sole* moderator. I can send the mbox archive headers to anybody who is interested. Mail: ted ire.org --Ted ---------------------------------------------------------------------- Comment By: NancyS (nes49) Date: 2004-03-11 14:15 Message: Logged In: YES user_id=995718 As one of the other people reporting the problem, let me add a bit of info on our experience. Mailman 2.1.1 My hypothesis now is that one of the people who could post without moderation released the virus. [I haven't been able to get definitive confirmation of that, but coupling "we were having some trouble" with a match on the ISP domain name leads me to that guess.] I haven't been able to tie the messages to a specific address subscribed to the list, but would be glad to probe further if given some direction. We haven't seen any additional occurrences since turning on moderation for all users. Between the first and second attack, I changed the passwords for the affected lists thinking that an Approved: header might have been used, but there's no evidence that was the case. -Nancy mailman sgtst.com ---------------------------------------------------------------------- Comment By: dk (karres) Date: 2004-03-11 12:28 Message: Logged In: YES user_id=995621 ... sorry, hit the submit button too soon... THe nom-member messages that get past the non-member filter are being caught by the forced moderation so the messages are not getting to the list itself. It does make us nervous though. ---------------------------------------------------------------------- Comment By: dk (karres) Date: 2004-03-11 12:20 Message: Logged In: YES user_id=995621 More generally we have only moderated, read-only lists for our users. All incoming, non-member messages should be discarded. We are seeing a few virus laden messages from obvious non-members getting past the non-member filters. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=914249&group_id=103 From noreply at sourceforge.net Thu Mar 11 14:36:43 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 11 14:36:51 2004 Subject: [ mailman-Bugs-914249 ] Virus posts to moderated lists Message-ID: Bugs item #914249, was opened at 2004-03-11 16:28 Message generated for change (Comment added) made by cepstein You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=914249&group_id=103 Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ted Peterson (knighted) Assigned to: Nobody/Anonymous (nobody) Summary: Virus posts to moderated lists Initial Comment: The W32.Beagle virus has been able to post multiple times to a moderated Mailman 2.1.3 mailing list, so emergency moderation of the list has been enabled. At least two other people, as reported on mailman-users, have had this trouble since last Friday, March 5th, when W32.Beagle was spreading. The virus was posting using a moderator address, so that moderator was removed. The moderator bit is and was turned on for all users, including the now *sole* moderator. I can send the mbox archive headers to anybody who is interested. Mail: ted ire.org --Ted ---------------------------------------------------------------------- Comment By: Caleb Epstein (cepstein) Date: 2004-03-11 19:36 Message: Logged In: YES user_id=36183 The virus is making it through to the lists by using an "envelope-from" (I believe that is the right term) of a valid, subscribed list member, but a From: header which is some address that does not exist and is not a member of the list (usually admin@ or management@ the mailing list's domain). See for example the message at http://bklyn. org/~cae/mailman-stumper.txt This message appears first in the MTA's logs as: 2004-03-11 16:31:44 1B1T5z-0009zY-00 <= SUBSCRIBER@DOMAIN.COM H=(srr2) [192.168.100.17] P=smtp S=17730 id=pbecvykwgcgqjemyxjx@Etree.org from for Announce@etree.org where SUBSCRIBER@DOMAIN.COM is a valid list subscriber with posting privileges. ---------------------------------------------------------------------- Comment By: NancyS (nes49) Date: 2004-03-11 19:15 Message: Logged In: YES user_id=995718 As one of the other people reporting the problem, let me add a bit of info on our experience. Mailman 2.1.1 My hypothesis now is that one of the people who could post without moderation released the virus. [I haven't been able to get definitive confirmation of that, but coupling "we were having some trouble" with a match on the ISP domain name leads me to that guess.] I haven't been able to tie the messages to a specific address subscribed to the list, but would be glad to probe further if given some direction. We haven't seen any additional occurrences since turning on moderation for all users. Between the first and second attack, I changed the passwords for the affected lists thinking that an Approved: header might have been used, but there's no evidence that was the case. -Nancy mailman sgtst.com ---------------------------------------------------------------------- Comment By: dk (karres) Date: 2004-03-11 17:28 Message: Logged In: YES user_id=995621 ... sorry, hit the submit button too soon... THe nom-member messages that get past the non-member filter are being caught by the forced moderation so the messages are not getting to the list itself. It does make us nervous though. ---------------------------------------------------------------------- Comment By: dk (karres) Date: 2004-03-11 17:20 Message: Logged In: YES user_id=995621 More generally we have only moderated, read-only lists for our users. All incoming, non-member messages should be discarded. We are seeing a few virus laden messages from obvious non-members getting past the non-member filters. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=914249&group_id=103 From noreply at sourceforge.net Thu Mar 11 15:01:45 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 11 15:01:50 2004 Subject: [ mailman-Bugs-914249 ] Virus posts to moderated lists Message-ID: Bugs item #914249, was opened at 2004-03-11 11:28 Message generated for change (Comment added) made by nes49 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=914249&group_id=103 Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ted Peterson (knighted) Assigned to: Nobody/Anonymous (nobody) Summary: Virus posts to moderated lists Initial Comment: The W32.Beagle virus has been able to post multiple times to a moderated Mailman 2.1.3 mailing list, so emergency moderation of the list has been enabled. At least two other people, as reported on mailman-users, have had this trouble since last Friday, March 5th, when W32.Beagle was spreading. The virus was posting using a moderator address, so that moderator was removed. The moderator bit is and was turned on for all users, including the now *sole* moderator. I can send the mbox archive headers to anybody who is interested. Mail: ted ire.org --Ted ---------------------------------------------------------------------- Comment By: NancyS (nes49) Date: 2004-03-11 15:01 Message: Logged In: YES user_id=995718 As one of the other people reporting the problem, let me add a bit of info on our experience. Mailman 2.1.1 My hypothesis now is that one of the people who could post without moderation released the virus. [I haven't been able to get definitive confirmation of that, but coupling "we were having some trouble" with a match on the ISP domain name leads me to that guess.] I haven't been able to tie the messages to a specific address subscribed to the list, but would be glad to probe further if given some direction. We haven't seen any additional occurrences since turning on moderation for all users. Between the first and second attack, I changed the passwords for the affected lists thinking that an Approved: header might have been used, but there's no evidence that was the case. -Nancy mailman sgtst.com ---------------------------------------------------------------------- Comment By: Caleb Epstein (cepstein) Date: 2004-03-11 14:36 Message: Logged In: YES user_id=36183 The virus is making it through to the lists by using an "envelope-from" (I believe that is the right term) of a valid, subscribed list member, but a From: header which is some address that does not exist and is not a member of the list (usually admin@ or management@ the mailing list's domain). See for example the message at http://bklyn. org/~cae/mailman-stumper.txt This message appears first in the MTA's logs as: 2004-03-11 16:31:44 1B1T5z-0009zY-00 <= SUBSCRIBER@DOMAIN.COM H=(srr2) [192.168.100.17] P=smtp S=17730 id=pbecvykwgcgqjemyxjx@Etree.org from for Announce@etree.org where SUBSCRIBER@DOMAIN.COM is a valid list subscriber with posting privileges. ---------------------------------------------------------------------- Comment By: NancyS (nes49) Date: 2004-03-11 14:15 Message: Logged In: YES user_id=995718 As one of the other people reporting the problem, let me add a bit of info on our experience. Mailman 2.1.1 My hypothesis now is that one of the people who could post without moderation released the virus. [I haven't been able to get definitive confirmation of that, but coupling "we were having some trouble" with a match on the ISP domain name leads me to that guess.] I haven't been able to tie the messages to a specific address subscribed to the list, but would be glad to probe further if given some direction. We haven't seen any additional occurrences since turning on moderation for all users. Between the first and second attack, I changed the passwords for the affected lists thinking that an Approved: header might have been used, but there's no evidence that was the case. -Nancy mailman sgtst.com ---------------------------------------------------------------------- Comment By: dk (karres) Date: 2004-03-11 12:28 Message: Logged In: YES user_id=995621 ... sorry, hit the submit button too soon... THe nom-member messages that get past the non-member filter are being caught by the forced moderation so the messages are not getting to the list itself. It does make us nervous though. ---------------------------------------------------------------------- Comment By: dk (karres) Date: 2004-03-11 12:20 Message: Logged In: YES user_id=995621 More generally we have only moderated, read-only lists for our users. All incoming, non-member messages should be discarded. We are seeing a few virus laden messages from obvious non-members getting past the non-member filters. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=914249&group_id=103 From noreply at sourceforge.net Thu Mar 11 19:19:51 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 11 19:19:59 2004 Subject: [ mailman-Bugs-688751 ] Scrubber/attachment bug on NetBSD Message-ID: Bugs item #688751, was opened at 2003-02-18 11:55 Message generated for change (Comment added) made by awrede You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=688751&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Eric Ding (ericding) Assigned to: Nobody/Anonymous (nobody) Summary: Scrubber/attachment bug on NetBSD Initial Comment: I'm using Mailman 2.1.1, and have encountered issues with mail delivery of messages with attachments (having to do, I think, with the recent change to use the scrubber on such messages for digests). I actually have ARCHIVE_SCRUBBER set to 0 on my system, since I use MHonArc for archiving. Still, the scrubber is called from ToDigest. As a result of this bug, ANY message with an attachment is currently getting shunted!! :( Here's an example stacktrace from the error log: Feb 18 11:20:55 2003 (7122) Uncaught runner exception: [Errno 1] Operation not permitted: '/home/mailman/archives/private/greengrass_coordinator/attachments/20030217/d2897c2f' Feb 18 11:20:55 2003 (7122) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 82, in process send_digests(mlist, mboxfp) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 123, in send_digests send_i18n_digests(mlist, mboxfp) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 295, in send_i18n_digests msg = scrubber(mlist, msg) File "/home/mailman/Mailman/Handlers/Scrubber.py", line 219, in process url = save_attachment(mlist, part, dir, filter_html=0) File "/home/mailman/Mailman/Handlers/Scrubber.py", line 341, in save_attachment makedirs(fsdir) File "/home/mailman/Mailman/Handlers/Scrubber.py", line 333, in makedirs os.path.walk(dir, twiddle, None) File "/usr/pkg/lib/python2.2/posixpath.py", line 279, in walk func(arg, top, names) File "/home/mailman/Mailman/Handlers/Scrubber.py", line 332, in twiddle os.chmod(dirname, 02775) OSError: [Errno 1] Operation not permitted: '/home/mailman/archives/private/greengrass_coordinator/attachments/20030217/d2897c2f' To work aorund this issue, I've currently commented out lines 331-333 on my system. ---------------------------------------------------------------------- Comment By: Andreas Wrede (awrede) Date: 2004-03-11 19:19 Message: Logged In: YES user_id=11718 I can confirm the original problem. Unlike dkhelmet's problem on OpenBSD with incorrect permissions, my check_perm reports No Problem. The work-around of commenting out the function twiddle() and the os.path.walk on lines 342ff works. Enviroment is NetBSD 1.6.1, with python 2.1.3 and mailman 2.1.4, both installed from NetBSD's pkgsrc system (ie. mailman gets installed with DIRSETGID) ---------------------------------------------------------------------- Comment By: Jeff Labonski (dkhelmet) Date: 2003-10-16 00:23 Message: Logged In: YES user_id=8939 I can confirm this on OpenBSD 3.3 running Mailman 2.1.3 and Postfix 2.0.16. I get the same exact error. Perhaps I should try reinstalling without following the setgid flag for BSD. Just for confirmation, after each email is sent with an attachment, check_perms reports it doesn't have 02775 permissions. After check_perms -f is run and another email sent, the same thing occurs, but for a different directory. Commenting out the offending lines seems to have fixed the problem; even the archive is correct. I'll try recompiling in a day or two after I get some sleep. ---------------------------------------------------------------------- Comment By: Eric Ding (ericding) Date: 2003-04-08 12:07 Message: Logged In: YES user_id=302756 The only problems that check_perms reveals are all the directories that do not have the setgid bit set. I installed with README.BSD in mind, assuming that the setgid bit is unnecessary. Running check_perms -f to turn on that bit has no effect on the behavior. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-07 18:37 Message: Logged In: YES user_id=12800 I need more information for this one. Do you still get the crash if you run check_perms first? I've never seen this on Linux and I don't have a NetBSD box available to see if there's some platform specific problem involved. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=688751&group_id=103 From noreply at sourceforge.net Fri Mar 12 09:46:55 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Mar 12 09:47:06 2004 Subject: [ mailman-Bugs-665732 ] List-Id should be one line Message-ID: Bugs item #665732, was opened at 2003-01-10 15:05 Message generated for change (Comment added) made by ber You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=665732&group_id=103 Category: mail delivery Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 7 Submitted By: Bernhard Reiter (ber) Assigned to: Nobody/Anonymous (nobody) >Summary: List-Id should be one line Initial Comment: If the List-Id: header gets splitted into several lines, which I could observe on lists I'm on which switched to mailman 2.1 now, it is getting harder to filter the list based on the fixed part of the list id. Filtering would need to look at more than one line. So a procmail pattern (procmail uses egrep an basically work on one line) like :0: *^List-Id:.* $ kmail-incoming would not work anymore reliably when the description of the mailinglist is getting longer. Before mailman 2.1 the above pattern was save against the changes in the description. I know that headers longer than one line are allowed, still I consider is a design bug at mailman does not necessrily need to make filtering harder at this point. ---------------------------------------------------------------------- >Comment By: Bernhard Reiter (ber) Date: 2004-03-12 15:46 Message: Logged In: YES user_id=113859 I have done more research on this bug over time. Procmail does concatenate the header lines, but it leaves the tabular character in. The version I've tried: debian package 3.22-5 So it looks more like a procmail bug to me now. I suggest to to the mailman documentation that the following procmail pattern will work with changing List-Id lines. The brackets contain a space and a tabular. :0: *^List-Id:.*[ ]$ kmail-incoming KMail also can utilise those extended header lines. Mailman 2.1.4 leaves in the long line, but has other problems violating the standards for List-Id. ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2003-08-05 19:05 Message: Logged In: YES user_id=113859 I'm attaching a patch which fixes this bug against 2.1.2. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=665732&group_id=103 From noreply at sourceforge.net Fri Mar 12 10:51:50 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Mar 12 10:51:54 2004 Subject: [ mailman-Bugs-915075 ] virtual-mailman is missing domain entry Message-ID: Bugs item #915075, was opened at 2004-03-12 16: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=915075&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Boris Folgmann (bytemaster) Assigned to: Nobody/Anonymous (nobody) Summary: virtual-mailman is missing domain entry Initial Comment: I've configured mailman-2.1.1-5 (RH9 RPM) according to README.POSTFIX. Support for a Postfix-style virtual domain in general looks like: virtual.domain anything (right-hand content does not matter) user1@virtual.domain address1 user2@virtual.domain address2, address3 ... But Mailman is not adding the domain entry at the start of the virtual-mailman file, which is required for Postfix-style virtual domains. This means that mm is configuring a sendmail-style domain. That's not what we want. I had to add the virtual.domain line by myself, because otherwise Postfix does not accept mails sent to virtual.domain. Is there already a fix? I assume that mm will always overwrite my edited virtual-mailman when a new list is added. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=915075&group_id=103 From noreply at sourceforge.net Fri Mar 12 23:27:22 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Mar 12 23:27:31 2004 Subject: [ mailman-Patches-912448 ] Config setting to force relative URLs Message-ID: Patches item #912448, was opened at 2004-03-09 02:57 Message generated for change (Comment added) made by kostecke You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=912448&group_id=103 Category: None Group: Mailman 2.1 >Status: Deleted Resolution: None Priority: 5 Submitted By: Steve Kostecke (kostecke) Assigned to: Nobody/Anonymous (nobody) Summary: Config setting to force relative URLs Initial Comment: Mailman 2.1.1 uses absolute URLs for all references to mailing lists. This behavior may be useful when one Mailman installation runs lists on multiple virtual hosts. However, this behavior reduces the flexibility of Mailman by making it impossible to use Mailman in configurations where you need to be able to use different hostnames to refer to the same lists (e.g. where HTTP and HTTPS use different virtual hosts). This patch modifies the ScriptURL function in ./Mailman/Utils.py to allow relative URLs to be forced by setting a mm_cfg configuration variable: RELATIVE_URLS. This patch also modifies Defaults.py to provide the default value for RELATIVE_URLS. 
--- Utils.py.orig       Tue Mar  9 02:45:20 2004
+++ Utils.py    Tue Mar  9 02:10:51 2004
@@ -238,7 +238,7 @@
         fullpath = os.environ.get('SCRIPT_NAME', '') +                     os.environ.get('PATH_INFO', '')
     baseurl = urlparse.urlparse(web_page_url)[2]
-    if not absolute and fullpath.endswith(baseurl):
+    if mm_cfg.RELATIVE_URLS or not absolute and
fullpath.endswith(baseurl):
         # Use relative addressing
         fullpath = fullpath[len(baseurl):]
         i = fullpath.find('?')

--- Defaults.py.orig    Tue Mar  9 02:44:44 2004
+++ Defaults.py Tue Mar  9 02:15:13 2004
@@ -782,6 +782,9 @@
 # list's config variable default_member_moderation.
 DEFAULT_NEW_MEMBER_OPTIONS = 256
 
+# Set this to 1 to enable relative URLs.
+RELATIVE_URLS = 0

 #####
 # List defaults.  NOTE: Changing these values does NOT
change the
---------------------------------------------------------------------- >Comment By: Steve Kostecke (kostecke) Date: 2004-03-13 04:27 Message: Logged In: YES user_id=926494 I'm withdrawing this patch until I can fix it. ---------------------------------------------------------------------- Comment By: Multitalents (multitalents) Date: 2004-03-10 05:38 Message: Logged In: YES user_id=994460 Your patch seems to be fine for the web interface but it breaks the URLs in e-mail notifications. Relative URLs are worthless in e-mails. Any ideas on how to fix this? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=912448&group_id=103 From noreply at sourceforge.net Sun Mar 14 00:52:07 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Mar 14 00:52:12 2004 Subject: [ mailman-Feature Requests-915891 ] Add approve, reject, discard all buttons on admin req page Message-ID: Feature Requests item #915891, was opened at 2004-03-13 21:52 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=915891&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Arthur Jones (lolo2103) Assigned to: Nobody/Anonymous (nobody) Summary: Add approve,reject,discard all buttons on admin req page Initial Comment: Great product, thanks for the efforts! I use version 2.0 of Mailman (thru Pair networks) and spend alot of time discarding pending messages thru the admin request page. It would be nice to have some javascript code on that page that would allow you to "approve all", "reject all", and "discard all" messages. I figure it may make more sense to handle this type of thing on the browser side as opposed to having the server do it. I've attached an example page (from my admin req.) where I've added a simple function called checkAll and some buttons. It basically just sets all the radio buttons on the page to either 1, 2, or 3. Sorry if you all have already addressed this in a recent version! Thanks and keep up the good work! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=915891&group_id=103 From noreply at sourceforge.net Sun Mar 14 14:10:21 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Mar 14 14:10:28 2004 Subject: [ mailman-Bugs-915075 ] virtual-mailman is missing domain entry Message-ID: Bugs item #915075, was opened at 2004-03-12 16:51 Message generated for change (Comment added) made by bytemaster You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=915075&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Boris Folgmann (bytemaster) Assigned to: Nobody/Anonymous (nobody) Summary: virtual-mailman is missing domain entry Initial Comment: I've configured mailman-2.1.1-5 (RH9 RPM) according to README.POSTFIX. Support for a Postfix-style virtual domain in general looks like: virtual.domain anything (right-hand content does not matter) user1@virtual.domain address1 user2@virtual.domain address2, address3 ... But Mailman is not adding the domain entry at the start of the virtual-mailman file, which is required for Postfix-style virtual domains. This means that mm is configuring a sendmail-style domain. That's not what we want. I had to add the virtual.domain line by myself, because otherwise Postfix does not accept mails sent to virtual.domain. Is there already a fix? I assume that mm will always overwrite my edited virtual-mailman when a new list is added. ---------------------------------------------------------------------- >Comment By: Boris Folgmann (bytemaster) Date: 2004-03-14 20:10 Message: Logged In: YES user_id=91946 Since genaliases in fact owerwrites always the entire file, Postfix-style virtual domains are really broken in mailman 2.1.1 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=915075&group_id=103 From noreply at sourceforge.net Sun Mar 14 17:55:30 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Mar 14 21:34:53 2004 Subject: [ mailman-Patches-916196 ] broken link in german online messages Message-ID: Patches item #916196, was opened at 2004-03-14 23:55 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=916196&group_id=103 Category: internationalization Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: GCS (gcsideal) Assigned to: Nobody/Anonymous (nobody) Summary: broken link in german online messages Initial Comment: Submitted by Ralf Doeblitz for the Debian package of MailMan. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=916196&group_id=103 From noreply at sourceforge.net Fri Mar 19 11:12:48 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Mar 19 12:02:56 2004 Subject: [ mailman-Bugs-914249 ] Virus posts to moderated lists Message-ID: Bugs item #914249, was opened at 2004-03-11 11:28 Message generated for change (Comment added) made by sekhar-cu You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=914249&group_id=103 Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ted Peterson (knighted) Assigned to: Nobody/Anonymous (nobody) Summary: Virus posts to moderated lists Initial Comment: The W32.Beagle virus has been able to post multiple times to a moderated Mailman 2.1.3 mailing list, so emergency moderation of the list has been enabled. At least two other people, as reported on mailman-users, have had this trouble since last Friday, March 5th, when W32.Beagle was spreading. The virus was posting using a moderator address, so that moderator was removed. The moderator bit is and was turned on for all users, including the now *sole* moderator. I can send the mbox archive headers to anybody who is interested. Mail: ted ire.org --Ted ---------------------------------------------------------------------- Comment By: Sekhar Ramakrishnan (sekhar-cu) Date: 2004-03-19 11:12 Message: Logged In: YES user_id=1001877 I don't know if this is the same bug, but a Mailman 2.1.3 members-only list that I administer had two messages that got through, one from staff@ and the other from management@. Other messages at the same time from official-sounding id's on our domain got held up as being from nonmembers. Sekhar ---------------------------------------------------------------------- Comment By: NancyS (nes49) Date: 2004-03-11 15:01 Message: Logged In: YES user_id=995718 As one of the other people reporting the problem, let me add a bit of info on our experience. Mailman 2.1.1 My hypothesis now is that one of the people who could post without moderation released the virus. [I haven't been able to get definitive confirmation of that, but coupling "we were having some trouble" with a match on the ISP domain name leads me to that guess.] I haven't been able to tie the messages to a specific address subscribed to the list, but would be glad to probe further if given some direction. We haven't seen any additional occurrences since turning on moderation for all users. Between the first and second attack, I changed the passwords for the affected lists thinking that an Approved: header might have been used, but there's no evidence that was the case. -Nancy mailman sgtst.com ---------------------------------------------------------------------- Comment By: Caleb Epstein (cepstein) Date: 2004-03-11 14:36 Message: Logged In: YES user_id=36183 The virus is making it through to the lists by using an "envelope-from" (I believe that is the right term) of a valid, subscribed list member, but a From: header which is some address that does not exist and is not a member of the list (usually admin@ or management@ the mailing list's domain). See for example the message at http://bklyn. org/~cae/mailman-stumper.txt This message appears first in the MTA's logs as: 2004-03-11 16:31:44 1B1T5z-0009zY-00 <= SUBSCRIBER@DOMAIN.COM H=(srr2) [192.168.100.17] P=smtp S=17730 id=pbecvykwgcgqjemyxjx@Etree.org from for Announce@etree.org where SUBSCRIBER@DOMAIN.COM is a valid list subscriber with posting privileges. ---------------------------------------------------------------------- Comment By: NancyS (nes49) Date: 2004-03-11 14:15 Message: Logged In: YES user_id=995718 As one of the other people reporting the problem, let me add a bit of info on our experience. Mailman 2.1.1 My hypothesis now is that one of the people who could post without moderation released the virus. [I haven't been able to get definitive confirmation of that, but coupling "we were having some trouble" with a match on the ISP domain name leads me to that guess.] I haven't been able to tie the messages to a specific address subscribed to the list, but would be glad to probe further if given some direction. We haven't seen any additional occurrences since turning on moderation for all users. Between the first and second attack, I changed the passwords for the affected lists thinking that an Approved: header might have been used, but there's no evidence that was the case. -Nancy mailman sgtst.com ---------------------------------------------------------------------- Comment By: dk (karres) Date: 2004-03-11 12:28 Message: Logged In: YES user_id=995621 ... sorry, hit the submit button too soon... THe nom-member messages that get past the non-member filter are being caught by the forced moderation so the messages are not getting to the list itself. It does make us nervous though. ---------------------------------------------------------------------- Comment By: dk (karres) Date: 2004-03-11 12:20 Message: Logged In: YES user_id=995621 More generally we have only moderated, read-only lists for our users. All incoming, non-member messages should be discarded. We are seeing a few virus laden messages from obvious non-members getting past the non-member filters. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=914249&group_id=103 From noreply at sourceforge.net Mon Mar 22 07:09:09 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 22 07:09:16 2004 Subject: [ mailman-Bugs-920947 ] Exception when trying to edit non-member preferences Message-ID: Bugs item #920947, was opened at 2004-03-22 13:09 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=920947&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Sylvain BEUCLER (beuc) Assigned to: Nobody/Anonymous (nobody) Summary: Exception when trying to edit non-member preferences Initial Comment: At Savannah, you get: "Bug in Mailman version 2.1.4 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 "/var/lib/mailman/scripts/driver", line 97, in run_main main() File "/usr/lib/mailman/Mailman/Cgi/options.py", line 226, in main password, user): File "/var/lib/mailman/Mailman/SecurityManager.py", line 220, in WebAuthenticate ok = self.CheckCookie(ac, user) File "/var/lib/mailman/Mailman/SecurityManager.py", line 300, in CheckCookie ok = self.__checkone(c, authcontext, user) File "/var/lib/mailman/Mailman/SecurityManager.py", line 310, in __checkone key, secret = self.AuthContextInfo(authcontext, user) File "/var/lib/mailman/Mailman/SecurityManager.py", line 105, in AuthContextInfo secret = self.getMemberPassword(user) File "/var/lib/mailman/Mailman/OldStyleMemberships.py", line 102, in getMemberPassword raise Errors.NotAMemberError, member NotAMemberError: GianUberto.Lauri@eng.it Python information: Variable Value sys.version 2.3.3 (#2, Mar 10 2004, 17:12:43) [GCC 2.95.4 20011002 (Debian prerelease)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2" when you enter a non-member address in the listinfo page, in the small textbox with the button "unsubscribe edit options". It should display a user friendly message, just like when you enter a malformed e-mail. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=920947&group_id=103 From noreply at sourceforge.net Wed Mar 24 15:46:07 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Mar 24 15:46:16 2004 Subject: [ mailman-Bugs-920947 ] Exception when trying to edit non-member preferences Message-ID: Bugs item #920947, was opened at 2004-03-22 13:09 Message generated for change (Comment added) made by ikarisan You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=920947&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Sylvain BEUCLER (beuc) Assigned to: Nobody/Anonymous (nobody) Summary: Exception when trying to edit non-member preferences Initial Comment: At Savannah, you get: "Bug in Mailman version 2.1.4 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 "/var/lib/mailman/scripts/driver", line 97, in run_main main() File "/usr/lib/mailman/Mailman/Cgi/options.py", line 226, in main password, user): File "/var/lib/mailman/Mailman/SecurityManager.py", line 220, in WebAuthenticate ok = self.CheckCookie(ac, user) File "/var/lib/mailman/Mailman/SecurityManager.py", line 300, in CheckCookie ok = self.__checkone(c, authcontext, user) File "/var/lib/mailman/Mailman/SecurityManager.py", line 310, in __checkone key, secret = self.AuthContextInfo(authcontext, user) File "/var/lib/mailman/Mailman/SecurityManager.py", line 105, in AuthContextInfo secret = self.getMemberPassword(user) File "/var/lib/mailman/Mailman/OldStyleMemberships.py", line 102, in getMemberPassword raise Errors.NotAMemberError, member NotAMemberError: GianUberto.Lauri@eng.it Python information: Variable Value sys.version 2.3.3 (#2, Mar 10 2004, 17:12:43) [GCC 2.95.4 20011002 (Debian prerelease)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2" when you enter a non-member address in the listinfo page, in the small textbox with the button "unsubscribe edit options". It should display a user friendly message, just like when you enter a malformed e-mail. ---------------------------------------------------------------------- Comment By: Thorsten Reichelt (ikarisan) Date: 2004-03-24 21:46 Message: Logged In: YES user_id=1005754 I have the same problem when I enter a non-member address. But it works if you enter dummyuser@domain Just enter a full stop behind "domain" and the bug page appears! (dummyuser@domain.) sys.version 2.3.3 (#2, Feb 24 2004, 09:29:20) [GCC 3.3.3 (Debian)] ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=920947&group_id=103 From noreply at sourceforge.net Thu Mar 25 05:38:31 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 25 05:38:40 2004 Subject: [ mailman-Bugs-911648 ] AttributeError: 'module' object has no attribute 'UserDesc' Message-ID: Bugs item #911648, was opened at 2004-03-07 18:19 Message generated for change (Comment added) made by cdrum You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=911648&group_id=103 Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: cYbErDaRk (cyberdark) Assigned to: Nobody/Anonymous (nobody) Summary: AttributeError: 'module' object has no attribute 'UserDesc' Initial Comment: When adding members via InviteNewMember, and he/she receives the emails asking for confirmation, this is the message shown when clicking: Bug in Mailman version 2.1.3 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/cpanel/3rdparty/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/cpanel/3rdparty/mailman/Mailman/Cgi/conf irm.py", line 98, in main content = Pending.confirm(cookie,expunge=0) File "/usr/local/cpanel/3rdparty/mailman/Mailman/Pending. py", line 125, in confirm db = _load() File "/usr/local/cpanel/3rdparty/mailman/Mailman/Pending. py", line 177, in _load return cPickle.load(fp) AttributeError: 'module' object has no attribute 'UserDesc' ------------------------------------------------------ -------------------------- Python information: Variable Value sys.version 2.2.2 (#1, Feb 24 2003, 19:13:11) [GCC 3.2.2 20030222 (Red Hat Linux 3.2.2-4)] sys.executable /usr/bin/python2 sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 ------------------------------------------------------ -------------------------- Environment variables: Variable Value HTTP_COOKIE cyberdark.net- publicidad_cyberdark.net+admin=28020000006935414b40 73280000003036383862303235613332633465656639303 3663931313636373239303764653936643035366334; SERVER_SOFTWARE Apache PYTHONPATH /usr/local/cpanel/3rdparty/mailman SCRIPT_FILENAME /usr/local/cpanel/3rdparty/mailman/c gi-bin/confirm SERVER_ADMIN webmaster@cyberdark.net SCRIPT_NAME /mailman/confirm REQUEST_METHOD GET HTTP_HOST cyberdark.net PATH_INFO /cyberdark.net- publicidad_cyberdark.net/9e9879dd657f06ad0871de5631 6c40405d054fcf SERVER_PROTOCOL HTTP/1.1 QUERY_STRING REQUEST_URI /mailman/confirm/cyberdark.net- publicidad_cyberdark.net/9e9879dd657f06ad0871de5631 6c40405d054fcf HTTP_ACCEPT image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/msword, application/vnd.ms- powerpoint, application/vnd.ms-excel, application/x- shockwave-flash, */* HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) SERVER_NAME www.cyberdark.net REMOTE_ADDR -- HTTP_CLIENT_IP -- REMOTE_PORT 58674 HTTP_ACCEPT_LANGUAGE es,eu;q=0.5 HTTP_VIA HTTP/1.1 proxy[AC1E0E47] (Traffic- Server/5.5.1-59096 [uScM]) PATH_TRANSLATED /home/cdkadmin/public_html/cyberd ark.net- publicidad_cyberdark.net/9e9879dd657f06ad0871de5631 6c40405d054fcf SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 HTTP_X_FORWARDED_FOR -- HTTP_ACCEPT_ENCODING gzip, deflate SERVER_ADDR -- DOCUMENT_ROOT /home/cdkadmin/public_html ---------------------------------------------------------------------- Comment By: Chris Drumgoole (cdrum) Date: 2004-03-25 05:38 Message: Logged In: YES user_id=429400 Me, too: Traceback: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/subscribe.py", line 96, in main process_form(mlist, doc, cgidata, language) File "/usr/local/mailman/Mailman/Cgi/subscribe.py", line 176, in process_form mlist.AddMember(userdesc, remote) File "/usr/local/mailman/Mailman/MailList.py", line 818, in AddMember cookie = Pending.new(Pending.SUBSCRIPTION, userdesc) File "/usr/local/mailman/Mailman/Pending.py", line 80, in new db = _load() File "/usr/local/mailman/Mailman/Pending.py", line 191, in _load return cPickle.load(fp) AttributeError: 'module' object has no attribute 'UserDesc' Python information: Variable Value sys.version 2.2.3 (#1, Mar 23 2004, 15:57:20) [GCC 2.96 20000731 (Red Hat Linux 7.3 2.96-110)] sys.executable /usr/local/bin/python sys.prefix /usr/local sys.exec_prefix /usr/local sys.path /usr/local sys.platform linux2 Environment variables: Variable Value PATH_INFO /scac HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,*/*;q=0.1 CONTENT_TYPE application/x-www-form-urlencoded HTTP_REFERER http://listes.ambafrance-cn.org/mailman/listinfo/scac SERVER_SOFTWARE Apache/1.3.27 (Unix) mod_ssl/2.8.14 OpenSSL/0.9.7b PHP/4.3.2 PYTHONPATH /usr/local/mailman SCRIPT_FILENAME /usr/local/mailman/cgi-bin/subscribe SERVER_ADMIN chris.drumgoole@ituc.com SCRIPT_NAME /mailman/subscribe SERVER_SIGNATURE Apache/1.3.27 Server at listes.ambafrance-cn.org Port 80 REQUEST_METHOD POST HTTP_HOST listes.ambafrance-cn.org HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.0 QUERY_STRING HTTP_CACHE_CONTROL max-age=0 REQUEST_URI /mailman/subscribe/scac CONTENT_LENGTH 92 HTTP_ACCEPT_CHARSET ISO-8859-1,utf-8;q=0.7,*;q=0.7 HTTP_USER_AGENT Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8 HTTP_CONNECTION Keep-Alive HTTP_COOKIE mailman+admin=28020000006945236140732800000062356562353762313334663132343936653666376263323438663462386432623636303661366334; scac+admin=2802000000691a666140732800000063376331326335313964613965323761366661633038643233393962396162623735323033643435; epiaf+admin=28020000006908666140732800000038656237616332616332643431663930346334383833386365653831623837353363383332376662; pekin_info+admin=280200000069ef656140732800000033383339303132636131653232393133306364323533626536313637303532366532313466346539; label_france+admin=280200000069e3646140732800000038363561636439656263666463663732396165353165346461363331353036666639353164333564; epiaf+user+cdrum--at--cdrum.com=280200000069b5646140732800000032646635333930633263353763393338623434333335663137646361646538316637643932623936; test2-mod+admin=280200000069903d6140732800000035666162663162633239643662336230636363646661393938373461623538326139633562353766; test2-mod+moderator=280200000069663d6140732800000064393932633162623539373139613634306532346530633866313863613331343264373536376562; paris_shanghai+admin=280200000069126b6240732800000061383166376637616534336230356263646437633466656530313736646665326437366636636334 SERVER_NAME listes.ambafrance-cn.org REMOTE_ADDR 203.212.4.78 REMOTE_PORT 42207 HTTP_ACCEPT_LANGUAGE en-us,en;q=0.5 HTTP_VIA 1.1 ITUCBJS04 PATH_TRANSLATED /var/www/html/scac SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 HTTP_ACCEPT_ENCODING gzip,deflate SERVER_ADDR 210.192.99.50 DOCUMENT_ROOT /var/www/html ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=911648&group_id=103 From noreply at sourceforge.net Thu Mar 25 09:01:13 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 25 12:03:36 2004 Subject: [ mailman-Feature Requests-923122 ] reply_goes_to_list allow poster+list option Message-ID: Feature Requests item #923122, was opened at 2004-03-25 14:01 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=923122&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: karl berry (kberry) Assigned to: Nobody/Anonymous (nobody) Summary: reply_goes_to_list allow poster+list option Initial Comment: Right now, the reply_goes_to_list option allows (a) poster, (b), list, and (c) explicit. How about (d) poster AND list? That is, insert/override a reply-to: header containing both the list name, and the original reply-to (if present, else From: address). For extra credit, omit the original poster if they are a list member. This would be very useful for a number of lists I maintain, where 90% of the traffic is among the list members (hence having a simple reply go to the list), yet a few messages come in from the outside world (hence including the original poster's address). I'm using mailman 2.1.4 on GNU/Linux. Thanks, karl@freefriends.org ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=923122&group_id=103 From noreply at sourceforge.net Thu Mar 25 15:16:44 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Mar 25 15:17:03 2004 Subject: [ mailman-Patches-923428 ] VERP subscription confirmations Message-ID: Patches item #923428, was opened at 2004-03-25 15:16 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=923428&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Gordon Rowell (gordonr) Assigned to: Nobody/Anonymous (nobody) Summary: VERP subscription confirmations Initial Comment: From: Gordon Rowell To: mailman-developers@python.org [...] On Thu, Feb 05, 2004 at 09:44:05PM -0500, Gordon Rowell wrote: > If I enable VERP_CONFIRMATIONS and "Invite" > someone from the admin page, I get a VERP > invite and a "nice" Subject line: > [...] > It appears that the VERP confirmations are only > partially implemented, but maybe I've missed > something. > [...] The attached patch seems to DTRT for me. Gordon ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=923428&group_id=103 From noreply at sourceforge.net Mon Mar 29 09:55:34 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 29 09:55:43 2004 Subject: [ mailman-Bugs-925337 ] quoted-printable encoding in web archive Message-ID: Bugs item #925337, was opened at 2004-03-29 16: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=925337&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Thomas Arendsen Hein (thomas_ah) Assigned to: Nobody/Anonymous (nobody) Summary: quoted-printable encoding in web archive Initial Comment: Mailman 2.1.2 received a mail with charset windows-1252 and Content-Transfer-Encoding: quoted-printable The email is attached in mbox format. In the web archive at http://intevation.de/pipermail/mapserver-de/2004-March/000176.html some characters are still in their =XY encoding. Other mails with windows-1252 or quoted-printable work fine, but I don't have another example of both in a single mail. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=925337&group_id=103 From noreply at sourceforge.net Mon Mar 29 09:15:09 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Mar 29 11:04:12 2004 Subject: [ mailman-Bugs-925319 ] SMTP error code 550 not seen as bounce Message-ID: Bugs item #925319, was opened at 2004-03-29 09:15 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=925319&group_id=103 Category: bounce detection Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Michael Cashwell (cashwell) Assigned to: Nobody/Anonymous (nobody) Summary: SMTP error code 550 not seen as bounce Initial Comment: >From the collection of uncaught bounces I'm dealing with it seems that Mailman does not treat an unknown user account as a fatal error (despite the 5xx code). This must be a bug. It's a real headache as these clearly fatal errors constitute more than 80% of the unchaught bounces I must wade through. Here are several examples (and I have many more if you need them!): From: E500_SMTP_Mail_Service@lists.sld.tld Date: March 25, 2004 11:06:51 PM EST To: Subject: Returned Mail - Error During Delivery ------ Failed Recipients ------ : Requested action not taken: mailbox unavailable. [SMTP Error Code 550] -------- Returned Mail -------- ..... From: "InterScan MSS Notification" Date: March 25, 2004 11:08:25 PM EST To: Subject: Mail could not be delivered This message was AUTO GENERATED. Please DO NOT RESPOND to this EMAIL. Sent <<< RCPT TO: Received >>> 550 5.1.1 ... user unknown Unable to deliver message to (and other recipients in the same domain). ..... From: "InterScan MSS Notification" Date: March 25, 2004 11:08:25 PM EST To: Subject: Mail could not be delivered This message was AUTO GENERATED. Please DO NOT RESPOND to this EMAIL. Sent <<< RCPT TO: Received >>> 550 5.1.1 ... user unknown Unable to deliver message to (and other recipients in the same domain). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=925319&group_id=103 From noreply at sourceforge.net Tue Mar 30 05:33:48 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 30 05:33:59 2004 Subject: [ mailman-Bugs-781977 ] Attempt to invoke directory as as script Message-ID: Bugs item #781977, was opened at 2003-08-02 14:46 Message generated for change (Comment added) made by winnegan You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=781977&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: John A. Martin (jamux) Assigned to: Nobody/Anonymous (nobody) Summary: Attempt to invoke directory as as script Initial Comment: Package: mailman Version: 2.1.2-7 Log entries like the following appear with some regularity. ,----[ Excerpt from: /var/log/apache-ssl ] [Fri Aug 1 15:54:12 2003] [error] [client 128.242.232.130] attempt to invoke directory as script: /usr/lib/cgi-bin/mailman `---- -- System Information Debian Release: 3.0 Kernel Version: Linux lists 2.4.20-bf2.4 #1 Wed Dec 25 13:17:08 UTC 2002 i686 GNU/Linux Versions of the packages mailman depends on: ii cron 3.0pl1-72 management of regular background processing ii debconf 1.0.32 Debian configuration management system ii libc6 2.3.1-17 GNU C Library: Shared libraries and Timezone ii logrotate 3.5.9-8 Log rotation utility ii pwgen 2.03-1 Automatic Password generation ii python 2.2.3-3 An interactive high-level object-oriented la ii ucf 0.18 Update Configuration File: preserves user ch exim Not installed or no info ii postfix 2.0.13-2003070 A high-performance mail transport agent ^^^ (Provides virtual package mail-transport-agent) apache Not installed or no info ii apache-ssl 1.3.27.0-2 Versatile, high-performance HTTP server with ^^^ (Provides virtual package httpd) ---------------------------------------------------------------------- Comment By: Bernd S. Brentrup (winnegan) Date: 2004-03-30 10:33 Message: Logged In: YES user_id=168018 Has this been submitted to the Debian BTS? I can't find any reference. (I'm a co-maintainer of Debian's mailman package) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=781977&group_id=103 From noreply at sourceforge.net Tue Mar 30 09:06:10 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 30 09:06:16 2004 Subject: [ mailman-Bugs-926034 ] Crashes on encoding errors Message-ID: Bugs item #926034, was opened at 2004-03-30 16:06 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=926034&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Heikki Levanto (heikkilevanto) Assigned to: Nobody/Anonymous (nobody) Summary: Crashes on encoding errors Initial Comment: I have seen crashes on some Danish-speaking lists, where users put Danish characters in the headers. It seems to depend on the encoding used. I do not have much statistical material, as I can not produce the crash myself, but have to ask some of the "troublemakers" to post a test message every time I need to see the crash. Here is a traceback: Mar 30 15:17:03 2004 (339) Uncaught runner exception: unknown encoding Mar 30 15:17:03 2004 (339) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/home/mailman/Mailman/Handlers/CookHeaders.py", line 75, in process prefix_subject(mlist, msg, msgdata) File "/home/mailman/Mailman/Handlers/CookHeaders.py", line 262, in prefix_subject h.append(s, c) File "/home/mailman/pythonlib/email/Header.py", line 285, in append s = s.encode(outcodec, errors) LookupError: unknown encoding The sad thing is that these mails just disappear, and my users wonder why they can not post to the list. Even a bounce would be to prefer, or at least something in the log that tells whom I could send apologies to... Here are the headers of one offending message, as sent directly to my mailbox: >From cfb@pikobryg.dk Tue Mar 30 15:47:23 2004 Return-path: Envelope-to: heikki@indexdata.dk Delivery-date: Tue, 30 Mar 2004 15:47:23 +0200 Received: from smtp020.tiscali.dk ([212.54.64.104]) by bagel.index with esmtp (Exim 3.35 #1 (Debian)) id 1B8JaM-0003l8-00 for ; Tue, 30 Mar 2004 15:47:22 +0200 Received: from pikobryg.dk (213.237.80.191.adsl.vbr.worldonline.dk [213.237.80.191]) by smtp020.tiscali.dk (8.12.10/8.12.10) with ESMTP id i2UDlKsm001688 for ; Tue, 30 Mar 2004 15:47:20 +0200 (MEST) Message-ID: <40697A66.5030604@pikobryg.dk> Date: Tue, 30 Mar 2004 15:47:18 +0200 From: "Christian F. Behrens" Reply-To: cfb@pikobryg.dk Organization: Pikobryg User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: da, en-us, en MIME-Version: 1.0 To: heikki@indexdata.dk Subject: Korrektion af =?windows-1252?Q?sukkerm=E6ngde_til_den_sids?= =?windows-1252?Q?te_nadver?= Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by smtp020.tiscali.dk id i2UDlKsm001688 Note that the subject line carries encoding "windows-1252", which comes from Mime-Autoconversion at tiscali.dk. The sender claims (and I believe him) that in his end the subject line looks something like this: Subjekt: Test mail encoded =?ISO-8859-1?Q?=5B=E6=F8=E5_=C6=C5=D8=5D?= I am not asking mailman to support mysterious windows code pages, but if it could handle unknown encodings better (ie without crashing) I would be much happier. I am also sending a polite letter to tiscali.dk, asking them to get their act together. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=926034&group_id=103 From noreply at sourceforge.net Tue Mar 30 09:51:22 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 30 09:51:36 2004 Subject: [ mailman-Bugs-926034 ] Crashes on encoding errors Message-ID: Bugs item #926034, was opened at 2004-03-30 16:06 Message generated for change (Comment added) made by heikkilevanto You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=926034&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Heikki Levanto (heikkilevanto) Assigned to: Nobody/Anonymous (nobody) Summary: Crashes on encoding errors Initial Comment: I have seen crashes on some Danish-speaking lists, where users put Danish characters in the headers. It seems to depend on the encoding used. I do not have much statistical material, as I can not produce the crash myself, but have to ask some of the "troublemakers" to post a test message every time I need to see the crash. Here is a traceback: Mar 30 15:17:03 2004 (339) Uncaught runner exception: unknown encoding Mar 30 15:17:03 2004 (339) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/home/mailman/Mailman/Handlers/CookHeaders.py", line 75, in process prefix_subject(mlist, msg, msgdata) File "/home/mailman/Mailman/Handlers/CookHeaders.py", line 262, in prefix_subject h.append(s, c) File "/home/mailman/pythonlib/email/Header.py", line 285, in append s = s.encode(outcodec, errors) LookupError: unknown encoding The sad thing is that these mails just disappear, and my users wonder why they can not post to the list. Even a bounce would be to prefer, or at least something in the log that tells whom I could send apologies to... Here are the headers of one offending message, as sent directly to my mailbox: >From cfb@pikobryg.dk Tue Mar 30 15:47:23 2004 Return-path: Envelope-to: heikki@indexdata.dk Delivery-date: Tue, 30 Mar 2004 15:47:23 +0200 Received: from smtp020.tiscali.dk ([212.54.64.104]) by bagel.index with esmtp (Exim 3.35 #1 (Debian)) id 1B8JaM-0003l8-00 for ; Tue, 30 Mar 2004 15:47:22 +0200 Received: from pikobryg.dk (213.237.80.191.adsl.vbr.worldonline.dk [213.237.80.191]) by smtp020.tiscali.dk (8.12.10/8.12.10) with ESMTP id i2UDlKsm001688 for ; Tue, 30 Mar 2004 15:47:20 +0200 (MEST) Message-ID: <40697A66.5030604@pikobryg.dk> Date: Tue, 30 Mar 2004 15:47:18 +0200 From: "Christian F. Behrens" Reply-To: cfb@pikobryg.dk Organization: Pikobryg User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: da, en-us, en MIME-Version: 1.0 To: heikki@indexdata.dk Subject: Korrektion af =?windows-1252?Q?sukkerm=E6ngde_til_den_sids?= =?windows-1252?Q?te_nadver?= Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by smtp020.tiscali.dk id i2UDlKsm001688 Note that the subject line carries encoding "windows-1252", which comes from Mime-Autoconversion at tiscali.dk. The sender claims (and I believe him) that in his end the subject line looks something like this: Subjekt: Test mail encoded =?ISO-8859-1?Q?=5B=E6=F8=E5_=C6=C5=D8=5D?= I am not asking mailman to support mysterious windows code pages, but if it could handle unknown encodings better (ie without crashing) I would be much happier. I am also sending a polite letter to tiscali.dk, asking them to get their act together. ---------------------------------------------------------------------- >Comment By: Heikki Levanto (heikkilevanto) Date: 2004-03-30 16:51 Message: Logged In: YES user_id=854974 Sorry, forgot to specify that I run on a Debian/Stable, with hand-installed mailman 2.1.2 from June 2003. It may also be that the original mail in my example was written in MS-Word, and pasted from there to Mozilla. Maybe that has something to do with the encoding, perhaps more than tiscali.dk's autoconversion. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=926034&group_id=103 From noreply at sourceforge.net Tue Mar 30 22:38:42 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 30 22:38:47 2004 Subject: [ mailman-Patches-871062 ] A MemberAdaptor for LDAP-based membership Message-ID: Patches item #871062, was opened at 2004-01-05 12:09 Message generated for change (Comment added) made by cdrum You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=871062&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: K. A. Krueger (fubarobfusco) Assigned to: Nobody/Anonymous (nobody) Summary: A MemberAdaptor for LDAP-based membership Initial Comment: This is a module, LDAPMemberships, which extends MemberAdaptor to support membership lists based on a search in an enterprise LDAP directory. With this module, you can make mailing lists which, rather than having a list of member addresses stored in the list, query your LDAP server for member addresses whenever necessary. For instance, if you wish to have a mailing list of all the Vice Presidents in your company, you can express this as an LDAP search: "(title=Vice President*)" and create a mailing list which performs this search and delivers mail to the resulting user accounts when a message is sent to it. This way, rather than manually adding new Vice Presidents to the mailing list, you can simply have Human Resources update the LDAP records, and the change will immediately take effect for the mailing list. Mailman lists with LDAP-based membership can still have moderators, list policies, and the other usual features of Mailman lists. There are a few missing features; notably: 1. There is no bounce processing. 2. There are no per-user preferences. 3. The Web interface still allows you to try setting user preferences, but if you do you will get a stack thrown at you. (Only the "readable" interface of MemberAdaptor is implemented.) 4. The LDAP settings of a list (e.g. LDAP server and search string) are only administrable by editing its "extend.py" file, not over the Web. 5. There is no digest mode. To use this module, you must have the "ldap" Python module installed (aka "python-ldap"). Then just put LDAPMemberships.py in the "Mailman" directory (~mailman/Mailman), create a new list, and write an "extend.py" file in the list directory like so: ##### from Mailman.LDAPMemberships import LDAPMemberships def extend(list): ldap = LDAPMemberships(list) ldap.ldapsearch = "(title=Vice President*)" # members search string ldap.ldapserver = "ldap.example.net" # your enterprise LDAP server ldap.ldapbasedn = "dc=Example dc=net" # your LDAP base DN ldap.ldapbinddn = '' # a bind DN which can read people's 'mail' field ldap.ldappasswd = '' # the password for the bind DN list._memberadaptor = ldap ##### This module has been tested at my site and is in production on a Mailman 2.1.2 installation. ---------------------------------------------------------------------- Comment By: Chris Drumgoole (cdrum) Date: 2004-03-30 22:38 Message: Logged In: YES user_id=429400 why use this when you can just use Sendmail's LDAP -> Alias functions? No need for a mailing list program like mailman.. right? ---------------------------------------------------------------------- Comment By: K. A. Krueger (fubarobfusco) Date: 2004-01-26 15:35 Message: Logged In: YES user_id=944208 Yet another new version (0.3) of LDAPMemberships.py. This one fixes some ambiguities with LDAP record handling, particularly for users with multiple "cn" values, and those who send mail as their "mailalternateaddress" field address rather than their "mail" field. If anyone is actually using this, please email me and let me know :) ---------------------------------------------------------------------- Comment By: K. A. Krueger (fubarobfusco) Date: 2004-01-20 11:53 Message: Logged In: YES user_id=944208 I've uploaded a new version (0.2) of LDAPMemberships.py. This one is some ungodly number of times faster, as it does not do redundant LDAP queries in a single load. ---------------------------------------------------------------------- Comment By: K. A. Krueger (fubarobfusco) Date: 2004-01-05 12:18 Message: Logged In: YES user_id=944208 Er. SF ate the indentation on my "extend.py" example in the patch description. All of the lines after "def extend(list):" are meant to be indented once. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=871062&group_id=103 From noreply at sourceforge.net Tue Mar 30 22:59:15 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Mar 30 22:59:19 2004 Subject: [ mailman-Patches-871062 ] A MemberAdaptor for LDAP-based membership Message-ID: Patches item #871062, was opened at 2004-01-05 12:09 Message generated for change (Comment added) made by fubarobfusco You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=871062&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: K. A. Krueger (fubarobfusco) Assigned to: Nobody/Anonymous (nobody) Summary: A MemberAdaptor for LDAP-based membership Initial Comment: This is a module, LDAPMemberships, which extends MemberAdaptor to support membership lists based on a search in an enterprise LDAP directory. With this module, you can make mailing lists which, rather than having a list of member addresses stored in the list, query your LDAP server for member addresses whenever necessary. For instance, if you wish to have a mailing list of all the Vice Presidents in your company, you can express this as an LDAP search: "(title=Vice President*)" and create a mailing list which performs this search and delivers mail to the resulting user accounts when a message is sent to it. This way, rather than manually adding new Vice Presidents to the mailing list, you can simply have Human Resources update the LDAP records, and the change will immediately take effect for the mailing list. Mailman lists with LDAP-based membership can still have moderators, list policies, and the other usual features of Mailman lists. There are a few missing features; notably: 1. There is no bounce processing. 2. There are no per-user preferences. 3. The Web interface still allows you to try setting user preferences, but if you do you will get a stack thrown at you. (Only the "readable" interface of MemberAdaptor is implemented.) 4. The LDAP settings of a list (e.g. LDAP server and search string) are only administrable by editing its "extend.py" file, not over the Web. 5. There is no digest mode. To use this module, you must have the "ldap" Python module installed (aka "python-ldap"). Then just put LDAPMemberships.py in the "Mailman" directory (~mailman/Mailman), create a new list, and write an "extend.py" file in the list directory like so: ##### from Mailman.LDAPMemberships import LDAPMemberships def extend(list): ldap = LDAPMemberships(list) ldap.ldapsearch = "(title=Vice President*)" # members search string ldap.ldapserver = "ldap.example.net" # your enterprise LDAP server ldap.ldapbasedn = "dc=Example dc=net" # your LDAP base DN ldap.ldapbinddn = '' # a bind DN which can read people's 'mail' field ldap.ldappasswd = '' # the password for the bind DN list._memberadaptor = ldap ##### This module has been tested at my site and is in production on a Mailman 2.1.2 installation. ---------------------------------------------------------------------- >Comment By: K. A. Krueger (fubarobfusco) Date: 2004-03-30 22:59 Message: Logged In: YES user_id=944208 Well, Mailman does a lot more than just keep track of who's subscribed -- for instance, restricted posters, list moderation, archiving. LDAPMemberships is not meant to be useful for Internet mailing lists with people signing up for them, but rather for institutional or enterprise lists. These have a lot of the same requirements (moderation etc.) as Internet lists, but don't need subscription/unsubscription -- since employees are usually required to be on them. My workplace is using this (well, actually a later version than the one I've uploaded here) as a replacement for an LDAP mailing-list feature in Netscape SuiteSpot now that we have migrated away from that system. We -also- use LDAP-based aliases (in Postfix, not Sendmail, actually) -- but for some things we need the moderation and other facilities that Mailman has. For instance, we have an announcements list that goes to all regular employees. A simple alias would allow anyone to send stuff to it, and certain senior scientists would love to send big PDFs to everyone. A Mailman list with LDAPMemberships can have sender restrictions so that only our IT Director and our mail systems admin can approve posts to it. Archiving is also quite useful for announcements lists. ---------------------------------------------------------------------- Comment By: Chris Drumgoole (cdrum) Date: 2004-03-30 22:38 Message: Logged In: YES user_id=429400 why use this when you can just use Sendmail's LDAP -> Alias functions? No need for a mailing list program like mailman.. right? ---------------------------------------------------------------------- Comment By: K. A. Krueger (fubarobfusco) Date: 2004-01-26 15:35 Message: Logged In: YES user_id=944208 Yet another new version (0.3) of LDAPMemberships.py. This one fixes some ambiguities with LDAP record handling, particularly for users with multiple "cn" values, and those who send mail as their "mailalternateaddress" field address rather than their "mail" field. If anyone is actually using this, please email me and let me know :) ---------------------------------------------------------------------- Comment By: K. A. Krueger (fubarobfusco) Date: 2004-01-20 11:53 Message: Logged In: YES user_id=944208 I've uploaded a new version (0.2) of LDAPMemberships.py. This one is some ungodly number of times faster, as it does not do redundant LDAP queries in a single load. ---------------------------------------------------------------------- Comment By: K. A. Krueger (fubarobfusco) Date: 2004-01-05 12:18 Message: Logged In: YES user_id=944208 Er. SF ate the indentation on my "extend.py" example in the patch description. All of the lines after "def extend(list):" are meant to be indented once. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=871062&group_id=103