From noreply at sourceforge.net Thu Apr 1 11:05:25 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Apr 1 11:05:32 2004 Subject: [ mailman-Bugs-927601 ] sending reminder mail: UnicodeError: ASCII encoding error Message-ID: Bugs item #927601, was opened at 2004-04-01 16:05 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=927601&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Derek Atkins (mit_warlord) Assigned to: Nobody/Anonymous (nobody) Summary: sending reminder mail: UnicodeError: ASCII encoding error Initial Comment: Received the following log. See attached (shunted) message. Apr 01 05:07:27 2004 (1416) Uncaught runner exception: ASCII encoding error: ord inal not in range(128) Apr 01 05:07:27 2004 (1416) Traceback (most recent call last): File "/var/mailman/Mailman/Queue/Runner.py", line 110, in _oneloop self._onefile(msg, msgdata) File "/var/mailman/Mailman/Queue/Runner.py", line 160, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/var/mailman/Mailman/Queue/OutgoingRunner.py", line 74, in _dispose self._func(mlist, msg, msgdata) File "/var/mailman/Mailman/Handlers/SMTPDirect.py", line 152, in process deliveryfunc(mlist, msg, msgdata, envsender, refused, conn) File "/var/mailman/Mailman/Handlers/SMTPDirect.py", line 351, in bulkdeliver msgtext = msg.as_string() File "/var/mailman/pythonlib/email/Message.py", line 113, in as_string g.flatten(self, unixfrom=unixfrom) File "/var/mailman/pythonlib/email/Generator.py", line 103, in flatten self._write(msg) File "/var/mailman/pythonlib/email/Generator.py", line 131, in _write self._dispatch(msg) File "/var/mailman/pythonlib/email/Generator.py", line 157, in _dispatch meth(msg) File "/var/mailman/pythonlib/email/Generator.py", line 203, in _handle_text self._fp.write(payload) UnicodeError: ASCII encoding error: ordinal not in range(128) Apr 01 05:07:27 2004 (1416) SHUNTING: 1080813617.0319071+02c673bc9cd2432c98aac5c 6fc1303c5bea02623 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=927601&group_id=103 From noreply at sourceforge.net Thu Apr 1 11:07:31 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Apr 1 11:07:38 2004 Subject: [ mailman-Bugs-927601 ] sending reminder mail: UnicodeError: ASCII encoding error Message-ID: Bugs item #927601, was opened at 2004-04-01 16:05 Message generated for change (Comment added) made by mit_warlord You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=927601&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Derek Atkins (mit_warlord) Assigned to: Nobody/Anonymous (nobody) Summary: sending reminder mail: UnicodeError: ASCII encoding error Initial Comment: Received the following log. See attached (shunted) message. Apr 01 05:07:27 2004 (1416) Uncaught runner exception: ASCII encoding error: ord inal not in range(128) Apr 01 05:07:27 2004 (1416) Traceback (most recent call last): File "/var/mailman/Mailman/Queue/Runner.py", line 110, in _oneloop self._onefile(msg, msgdata) File "/var/mailman/Mailman/Queue/Runner.py", line 160, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/var/mailman/Mailman/Queue/OutgoingRunner.py", line 74, in _dispose self._func(mlist, msg, msgdata) File "/var/mailman/Mailman/Handlers/SMTPDirect.py", line 152, in process deliveryfunc(mlist, msg, msgdata, envsender, refused, conn) File "/var/mailman/Mailman/Handlers/SMTPDirect.py", line 351, in bulkdeliver msgtext = msg.as_string() File "/var/mailman/pythonlib/email/Message.py", line 113, in as_string g.flatten(self, unixfrom=unixfrom) File "/var/mailman/pythonlib/email/Generator.py", line 103, in flatten self._write(msg) File "/var/mailman/pythonlib/email/Generator.py", line 131, in _write self._dispatch(msg) File "/var/mailman/pythonlib/email/Generator.py", line 157, in _dispatch meth(msg) File "/var/mailman/pythonlib/email/Generator.py", line 203, in _handle_text self._fp.write(payload) UnicodeError: ASCII encoding error: ordinal not in range(128) Apr 01 05:07:27 2004 (1416) SHUNTING: 1080813617.0319071+02c673bc9cd2432c98aac5c 6fc1303c5bea02623 ---------------------------------------------------------------------- >Comment By: Derek Atkins (mit_warlord) Date: 2004-04-01 16:07 Message: Logged In: YES user_id=181397 I nelgected to add that this is mailman-2.1.4-1 on Fedora Core 1. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=927601&group_id=103 From noreply at sourceforge.net Thu Apr 1 11:35:43 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Apr 1 11:35:47 2004 Subject: [ mailman-Bugs-927639 ] 2.1.4 failed to recognize a bounce Message-ID: Bugs item #927639, was opened at 2004-04-01 16:35 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=927639&group_id=103 Category: bounce detection Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Derek Atkins (mit_warlord) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1.4 failed to recognize a bounce Initial Comment: Using mailman-2.1.4-1 on Fedora Core 1, I received a few bounces (from one user) that were shunted into "qfiles/bad" with a log message of: Mar 31 01:20:19 2004 (1408) bounce message w/no discernable addresses: <1080714020-1324@myrealbox.com> Mar 31 01:20:19 2004 (1408) forwarding unrecognized, message-id: <1080714020-1324@myrealbox.com> See the attached "bad" message. I was certainly able to discern from this message that the bouncing user is "fancylad@myrealbox.com". ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=927639&group_id=103 From noreply at sourceforge.net Thu Apr 1 14:36:51 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Apr 1 14:37:00 2004 Subject: [ mailman-Patches-927761 ] Courier MTA list submission handler Message-ID: Patches item #927761, was opened at 2004-04-01 13:36 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=927761&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Lindsay Haisley (fmouse) Assigned to: Nobody/Anonymous (nobody) Summary: Courier MTA list submission handler Initial Comment: This script is meant to be called from /alias/.courier-default. It catches all mail to any address at a Courier virtual domain not otherwise handled by an explicit account or a .courier file. It looks at the recepient for each mail message not otherwise handled and decides if the mail is addressed to a valid list or not, and bounces the message with a helpful suggestion if it's not addressed to a list. This script is based on Bruce Perens' qmail-to-mailman.py script, and is specifically designed for use with Courier. You may wish to put this into the contrib section of the distributed mailman source. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=927761&group_id=103 From noreply at sourceforge.net Fri Apr 2 18:26:48 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Apr 2 18:26:54 2004 Subject: [ mailman-Bugs-928624 ] bin/arch break on one possibly broken message Message-ID: Bugs item #928624, was opened at 2004-04-03 01:26 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=928624&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Martin Mokrejs (mmokrejs) Assigned to: Nobody/Anonymous (nobody) Summary: bin/arch break on one possibly broken message Initial Comment: I have 2.1.4 version with soem sSF patches isntalled. However, this bug has been occuring even with plain mailman-2.1.4 (linux). $ /usr/bin/python /usr/local/mailman/bin/arch --wipe montana montana.200101 Ukl?d?m stav archivu do/usr/local/mailman/archives/private/montana/pipermail.pck Traceback (most recent call last): File "/usr/local/mailman/bin/arch", line 189, in ? main() File "/usr/local/mailman/bin/arch", line 177, in main archiver.processUnixMailbox(fp, start, end) File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 592, in processUnixMailbox m = mbox.next() File "/usr/lib/python2.3/mailbox.py", line 35, in next return self.factory(_Subfile(self.fp, start, stop)) File "/usr/local/mailman/Mailman/Mailbox.py", line 89, in scrubber return mailbox.scrub(msg) File "/usr/local/mailman/Mailman/Mailbox.py", line 109, in scrub return self._scrubber(self._mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 278, in process submsg = part.get_payload(0) File "/usr/local/mailman/pythonlib/email/Message.py", line 189, in get_payload raise TypeError, 'Expected list, got %s' % type(self._payload) TypeError: Expected list, got $ ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=928624&group_id=103 From noreply at sourceforge.net Fri Apr 2 22:58:46 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Apr 2 22:58:49 2004 Subject: [ mailman-Feature Requests-928714 ] "sender" variable substitutions in header/footer Message-ID: Feature Requests item #928714, was opened at 2004-04-02 19:58 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=928714&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jason (jnewborn) Assigned to: Nobody/Anonymous (nobody) Summary: "sender" variable substitutions in header/footer Initial Comment: I want two new "sender" variable substitutions in for the header/footer. One should be the Sender's name and the other should be the sender's email address. For example: %(sender_name)s %(sender_email)s Adding this functonality will allow the headers/footers to contain links that point to the sender's information, bio, or public key (based on their name/email address). This is different than personalization because the sender's address is the same for all emails. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=928714&group_id=103 From noreply at sourceforge.net Sat Apr 3 09:03:52 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Apr 3 09:03:57 2004 Subject: [ mailman-Bugs-782024 ] Private archives link error Message-ID: Bugs item #782024, was opened at 2003-08-02 10:24 Message generated for change (Comment added) made by halw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=782024&group_id=103 Category: Pipermail Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nicola Soranzo (soranzo) Assigned to: Nobody/Anonymous (nobody) Summary: Private archives link error Initial Comment: If I visit http://domain/mailman/private/listname/ all the links to the Thread, Subject, ... monthly archives are correct, but if the URL is http://domain/mailman/private/listname (without the trailing slash), the links are incorrect, eg.: http://domain/mailman/private/2003-July/thread.html (without the listname between private and the month). ---------------------------------------------------------------------- Comment By: Hal Wine (halw) Date: 2004-04-03 06:03 Message: Logged In: YES user_id=630568 Note: this bug is still in 2.1.4, and affects users since the URL provided by mailman in the List-Archive: email header does not contain the trailing slash. ---------------------------------------------------------------------- Comment By: Thomas Arendsen Hein (thomas_ah) Date: 2003-09-02 03:27 Message: Logged In: YES user_id=839582 A quick fix is to add a redirect in your web server. But since the List-Archive mail header points to the link without a trailing slash, this should be done in the cgi script, too. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=782024&group_id=103 From noreply at sourceforge.net Sun Apr 4 18:21:27 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Apr 4 18:21:33 2004 Subject: [ mailman-Feature Requests-928714 ] "sender" variable substitutions in header/footer Message-ID: Feature Requests item #928714, was opened at 2004-04-02 19:58 Message generated for change (Comment added) made by jnewborn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=928714&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jason (jnewborn) Assigned to: Nobody/Anonymous (nobody) Summary: "sender" variable substitutions in header/footer Initial Comment: I want two new "sender" variable substitutions in for the header/footer. One should be the Sender's name and the other should be the sender's email address. For example: %(sender_name)s %(sender_email)s Adding this functonality will allow the headers/footers to contain links that point to the sender's information, bio, or public key (based on their name/email address). This is different than personalization because the sender's address is the same for all emails. ---------------------------------------------------------------------- >Comment By: Jason (jnewborn) Date: 2004-04-04 15:21 Message: Logged In: YES user_id=1012659 After a very brief glance at the code, this may be as simple as adding to the SafeDict definition in the decorate function of Mailman/Handlers/Decorate.py, although I'm not sure if or where the variables/arrays that I want are populated. Perhaps "msg.get_sender()" would work. Just trying to give someone a head start if they decide to take this on. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=928714&group_id=103 From noreply at sourceforge.net Mon Apr 5 09:47:18 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 5 09:48:05 2004 Subject: [ mailman-Patches-871062 ] A MemberAdaptor for LDAP-based membership Message-ID: Patches item #871062, was opened at 2004-01-05 17:09 Message generated for change (Comment added) made by the_olo 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: Aleksander Adamowski (the_olo) Date: 2004-04-05 13:47 Message: Logged In: YES user_id=244001 I suggest this patch to allow senders use any source address they might have set in LDAP (the 'mail' attribute can have multiple values!) --- LDAPMemberships.py.orig 2004-04-01 12:31:54.000000000 +0200 +++ LDAPMemberships.py 2004-04-05 15:40:03.000000000 +0200 @@ -115,7 +115,9 @@ # mail is unique mail = attrs['mail'][0].strip() self.__members.append(mail) - self.__member_map[mail] = mail + # mail can have multiple values + for secondarymail in attrs['mail']: + self.__member_map[secondarymail.strip()] = mail if attrs.has_key('mailalternateaddress'): malts = attrs['mailalternateaddress'] for malt in malts: ---------------------------------------------------------------------- Comment By: K. A. Krueger (fubarobfusco) Date: 2004-03-31 03: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-31 03: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 20: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 16: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 17: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 Mon Apr 5 17:55:55 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 5 17:56:00 2004 Subject: [ mailman-Bugs-930055 ] respond_to_post_requests is not configurable but should be Message-ID: Bugs item #930055, was opened at 2004-04-05 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=100103&aid=930055&group_id=103 Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Steffen Mueller (mixonx) Assigned to: Nobody/Anonymous (nobody) Summary: respond_to_post_requests is not configurable but should be Initial Comment: One can choose to send mail to poster when their posting is held for approval. To turn this on/off, respond_to_post_requests is set or unset. According to the comments in mailman/Mailman/MailList.py, respond_to_post_requests is configurable (as list default in Defaults.py as well as in mm_cfg.py), but it isn't. <--- snip 288 # This stuff is configurable 289 self.respond_to_post_requests = 1 ---> snap See attached patches to fix this. Using Mailman version 2.1.4 from Debian Backport 2.1.4-1.backports.org.1 But this appears in the latest 2.x CVS-tree, too. Thank you for mailman development. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=930055&group_id=103 From noreply at sourceforge.net Tue Apr 6 10:17:34 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Apr 6 17:04:03 2004 Subject: [ mailman-Bugs-930469 ] Include text for held notification Message-ID: Bugs item #930469, was opened at 2004-04-06 07:17 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=930469&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Stephen Samuel (darkonc) Assigned to: Nobody/Anonymous (nobody) Summary: Include text for held notification Initial Comment: When an email is held for moderation, the message sent should include the body of themessage itself (or, at least , the first few lines_ if it is text. This is simpy to hel identify the message... If nothing tlse, the text should be displayed for the 'delete message' dialogue. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=930469&group_id=103 From noreply at sourceforge.net Tue Apr 6 08:34:36 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Apr 6 17:04:11 2004 Subject: [ mailman-Bugs-930410 ] Error when using list info page to view a non-existant user Message-ID: Bugs item #930410, was opened at 2004-04-06 12:34 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=930410&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Andrew Yager (yogel) Assigned to: Nobody/Anonymous (nobody) Summary: Error when using list info page to view a non-existant user Initial Comment: After you have been logged in as an admin, and go back to the list info page to view a user profile, and you enter a user email address that doesn't exist, the following error occurs: 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 "/home/mailmandir/mailman/scripts/driver", line 87, in run_main main() File "/home/mailmandir/mailman/Mailman/Cgi/options.py", line 226, in main password, user): File "/home/mailmandir/mailman/Mailman/SecurityManager.py", line 220, in WebAuthenticate ok = self.CheckCookie(ac, user) File "/home/mailmandir/mailman/Mailman/SecurityManager.py", line 300, in CheckCookie ok = self.__checkone(c, authcontext, user) File "/home/mailmandir/mailman/Mailman/SecurityManager.py", line 310, in __checkone key, secret = self.AuthContextInfo(authcontext, user) File "/home/mailmandir/mailman/Mailman/SecurityManager.py", line 105, in AuthContextInfo secret = self.getMemberPassword(user) File "/home/mailmandir/mailman/Mailman/ OldStyleMemberships.py", line 102, in getMemberPassword raise Errors.NotAMemberError, member NotAMemberError: user@somewhere.com Python information: Variable Value sys.version 2.3.2 (#1, Nov 7 2003, 22:27:17) [GCC 2.95.4 20020320 [FreeBSD]] sys.executable /usr/local/bin/python sys.prefix /usr/local sys.exec_prefix /usr/local sys.path /usr/local sys.platform freebsd4 Environment variables: Variable Value HTTP_COOKIE info+admin= SERVER_SOFTWARE Apache/2.0.48 (Unix) mod_ssl/2.0.48 OpenSSL/0.9.7a PHP/4.3.4 SCRIPT_NAME /mailman/options SERVER_SIGNATURE Apache/2.0.48 (Unix) mod_ssl/2.0.48 OpenSSL/0.9.7a PHP/4.3.4 Server at lists.mailmandir.org.au Port 80 REQUEST_METHOD POST PATH_INFO /info SERVER_PROTOCOL HTTP/1.1 QUERY_STRING CONTENT_LENGTH 78 HTTP_USER_AGENT Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-us) AppleWebKit/124 (KHTML, like Gecko) Safari/125.1 HTTP_CONNECTION close HTTP_REFERER http://lists.mailmandir.org.au/mailman/listinfo/info SERVER_NAME lists.mailmandir.org.au REMOTE_ADDR 211.30.19.65 PATH_TRANSLATED /home/mailmandir/mailman/www/info SERVER_PORT 80 SERVER_ADDR 192.168.2.99 DOCUMENT_ROOT /home/mailmandir/mailman/www/ PYTHONPATH /home/mailmandir/mailman SCRIPT_FILENAME /home/mailmandir/mailman/cgi-bin/options SERVER_ADMIN user@somewhere.com HTTP_HOST lists.mailmandir.org.au REQUEST_URI /mailman/options/info HTTP_ACCEPT */* GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 61245 HTTP_ACCEPT_LANGUAGE en-us, ja;q=0.33, en;q=0.67 CONTENT_TYPE application/x-www-form-urlencoded HTTP_ACCEPT_ENCODING gzip, deflate;q=1.0, identity;q=0.5, *;q=0 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=930410&group_id=103 From noreply at sourceforge.net Tue Apr 6 23:13:01 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Apr 6 23:13:06 2004 Subject: [ mailman-Bugs-930819 ] Focus form entry onload in admlogin.html Message-ID: Bugs item #930819, was opened at 2004-04-07 00:13 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=930819&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Christian Reis (kiko_async) Assigned to: Nobody/Anonymous (nobody) Summary: Focus form entry onload in admlogin.html Initial Comment: I run quite a few mailing lists, and boy is it annoying to have to click on each and every password box in the administration login page. So here's a patch that fixes the pages to use DOM-compliant javascript to focus the field (which is provably harmless in JS-deprived situations) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=930819&group_id=103 From noreply at sourceforge.net Tue Apr 6 23:14:38 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Apr 6 23:14:43 2004 Subject: [ mailman-Bugs-930819 ] Focus form entry onload in admlogin.html Message-ID: Bugs item #930819, was opened at 2004-04-07 00:13 Message generated for change (Comment added) made by kiko_async You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=930819&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Christian Reis (kiko_async) Assigned to: Nobody/Anonymous (nobody) Summary: Focus form entry onload in admlogin.html Initial Comment: I run quite a few mailing lists, and boy is it annoying to have to click on each and every password box in the administration login page. So here's a patch that fixes the pages to use DOM-compliant javascript to focus the field (which is provably harmless in JS-deprived situations) ---------------------------------------------------------------------- >Comment By: Christian Reis (kiko_async) Date: 2004-04-07 00:14 Message: Logged In: YES user_id=222305 Tested and working locally: http://www.async.com.br/mailman/admin/kiwi ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=930819&group_id=103 From noreply at sourceforge.net Wed Apr 7 02:46:32 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Apr 7 02:46:36 2004 Subject: [ mailman-Bugs-930881 ] Messages being overwritten in PiperMail Message-ID: Bugs item #930881, was opened at 2004-04-07 09: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=930881&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Alek Andreev (aandreev) Assigned to: Nobody/Anonymous (nobody) Summary: Messages being overwritten in PiperMail Initial Comment: New messages sent to the mailing list do not appear as new messages in the Pipermail archive, but instead overwrite the latest, 12th message. So now in the archives there are the first 11 messages and the latest message at number 12. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=930881&group_id=103 From noreply at sourceforge.net Wed Apr 7 06:26:39 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Apr 7 06:26:44 2004 Subject: [ mailman-Feature Requests-930969 ] Duplicated storage of attachments with MM 2.1 Message-ID: Feature Requests item #930969, was opened at 2004-04-07 10:26 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=930969&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Duplicated storage of attachments with MM 2.1 Initial Comment: In Mailman 2.1.4 the process() function in $prefix/Mailman/ Handlers/Scrubber.py is called by instances of the ArchiverMailbox class ($prefix/Mailman/Mailbox.py) and by the process() function for the ToDigest handler ($prefix/Mailman/Handlers/ToDigest.py) via the send_digests() and send_i18n_digests() functions. In former case the function may extract attachments from a message before that message is archived by pipermail. In the latter case the function may extract attachments from a message before that message is added to a text-only digest that is being prepared. If extraction is done in both situations for the same message, this appears to lead to two copies of the same attachment being stored in different files in the relevant $prefix/archives/private/ /attachments/ directory. While not suggesting this is an easy problem to fix, the increase in disc storage for busy lists whose messages carry large attachments can be a problem. Optimising so that only one copy is saved seems appropriate. Incorporating a solution to this in Mailman 3 seems like a good thing. The problem can be ameliorated by setting the 'digestable' attribute of affected lists to No. As an aside, digests for digestable lists are constructed even if no list subscriber is a digest member. Again, an optimisation to avoid this wasted processing might be appropriate for Mailman 3. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=930969&group_id=103 From noreply at sourceforge.net Thu Apr 8 01:15:19 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Apr 8 01:15:22 2004 Subject: [ mailman-Patches-931515 ] Provides more documentation for mass subscribing to the list Message-ID: Patches item #931515, was opened at 2004-04-08 01:15 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=931515&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Darrell Duane (progressd) Assigned to: Nobody/Anonymous (nobody) Summary: Provides more documentation for mass subscribing to the list Initial Comment: I've added documentation so that administrators who are mass subscribing members know the proper formats for associating names with e-mail addresses. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=931515&group_id=103 From noreply at sourceforge.net Thu Apr 8 13:19:33 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Apr 8 13:19:36 2004 Subject: [ mailman-Bugs-931861 ] MemoryError when running senddigests Message-ID: Bugs item #931861, was opened at 2004-04-08 17: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=931861&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Patrick Finnerty (finnertyp) Assigned to: Nobody/Anonymous (nobody) Summary: MemoryError when running senddigests Initial Comment: Using Mailman v2.1.4 & Python v2.3.3. OS = TRU64 5.1a Problem only occurs on one mailing list: /usr/local/bin/python -S /usr/local/mailman/cron/senddigests -l shc.nt Traceback (most recent call last): File "/usr/local/mailman/cron/senddigests", line 94, in ? main() File "/usr/local/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/usr/local/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 132, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 306, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 304, in process t = part.get_payload(decode=True) File "/usr/local/mailman/pythonlib/email/Message.py", line 197, in get_payload return Utils._qdecode(payload) File "/usr/local/lib/python2.3/quopri.py", line 161, in decodestring return a2b_qp(s, header = header) MemoryError ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=931861&group_id=103 From noreply at sourceforge.net Fri Apr 9 04:24:47 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Apr 9 04:25:00 2004 Subject: [ mailman-Bugs-932220 ] MemoryError when running senddigests Message-ID: Bugs item #932220, was opened at 2004-04-09 08:24 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=932220&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Patrick Finnerty (finnertyp) Assigned to: Nobody/Anonymous (nobody) Summary: MemoryError when running senddigests Initial Comment: Using Mailman v2.1.4 & Python v2.3.3. OS = TRU64 5.1a Problem only occurs on one mailing list: /usr/local/bin/python -S /usr/local/mailman/cron/senddigests -l shc.nt Traceback (most recent call last): File "/usr/local/mailman/cron/senddigests", line 94, in ? main() File "/usr/local/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/usr/local/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 132, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 306, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 304, in process t = part.get_payload(decode=True) File "/usr/local/mailman/pythonlib/email/Message.py", line 197, in get_payload return Utils._qdecode(payload) File "/usr/local/lib/python2.3/quopri.py", line 161, in decodestring return a2b_qp(s, header = header) MemoryError ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=932220&group_id=103 From noreply at sourceforge.net Fri Apr 9 12:39:24 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Apr 9 12:39:28 2004 Subject: [ mailman-Patches-932383 ] Include FullName in roster views Message-ID: Patches item #932383, was opened at 2004-04-09 12:39 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=932383&group_id=103 Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: M. C. B. (u4forge) Assigned to: Nobody/Anonymous (nobody) Summary: Include FullName in roster views Initial Comment: Patch HTMLFormat.py FormatUsers() to return "fullname" alongside email. This is used by the "Show Members" button on the listinfo page. Patch is for HTMLFormat.py at CVS rev 2.38 (2.1.3) and was tested with rev 2.39. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=932383&group_id=103 From noreply at sourceforge.net Mon Apr 12 13:15:08 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 12 13:15:25 2004 Subject: [ mailman-Patches-933757 ] fix for [815297] signatures break Message-ID: Patches item #933757, was opened at 2004-04-12 19:15 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=933757&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Bernhard Reiter (ber) Assigned to: Nobody/Anonymous (nobody) Summary: fix for [815297] signatures break Initial Comment: Fix attempt for [ 815297 ] Breaking signatures in message/rfc822 attachement! https://sourceforge.net/tracker/?func=detail&aid=815297&group_id=103&atid=100103 The patch introduces a new Mailman specific Generator class and only enables header folding for the top object and Mailbox.py and SMTPDirect.py. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=933757&group_id=103 From noreply at sourceforge.net Mon Apr 12 13:17:20 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 12 13:17:35 2004 Subject: [ mailman-Bugs-815297 ] Breaking signatures in message/rfc822 attachement! Message-ID: Bugs item #815297, was opened at 2003-09-30 19:42 Message generated for change (Comment added) made by ber You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=815297&group_id=103 Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 8 Submitted By: Bernhard Reiter (ber) Assigned to: Nobody/Anonymous (nobody) Summary: Breaking signatures in message/rfc822 attachement! Initial Comment: Mailman _must_ not touch MIME-parts which are nested more deeply in the mail. As tested with Mailman 2.1.2, header lines will be sometimes reformatted in message/rfc822 attachments which will break the OpenPGP signature (also conforming to the PGP/MIME standard) on that part. I'm attaching a simple email with on long header. Forward this as MIME part and sign it sending it through Mailman, the signature will be broken. This is an email security affecting bug, because if people start believing that a *BAD* signature does not mean much, because they get many broken by mailman, they will not react to a seriously manipulated email anymore! ---------------------------------------------------------------------- >Comment By: Bernhard Reiter (ber) Date: 2004-04-12 19:17 Message: Logged In: YES user_id=113859 I have created a patch to address the problem. [ 933757 ] fix for [815297] signatures break https://sourceforge.net/tracker/index.php?func=detail&aid=933757&group_id=103&atid=300103 ---------------------------------------------------------------------- Comment By: Marc Mutz (mmutz) Date: 2003-10-03 17:54 Message: Logged In: YES user_id=82377 This is not limited to message/rfc822 at all: As a specific example, create a message with an attachment and add the header Content-Disposition: attachment; filename="more-than-70-chars. txt" (all in a single line), then send it through a mailman-managed ml. Result: mailman "fixes" the message to look like Content-Disposition: attachment; \tfilename="more-than-70-chars.txt" It even does that inside a multipart/signed part, and this is where it breaks the signature verification. ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2003-09-30 19:46 Message: Logged In: YES user_id=113859 Here is the email signed by myself and broken after delivery through mailman. Check the "To:" header line. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=815297&group_id=103 From noreply at sourceforge.net Mon Apr 12 13:22:18 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 12 13:22:21 2004 Subject: [ mailman-Patches-933762 ] fix for #880073 list-id can violate RFC2919 Message-ID: Patches item #933762, was opened at 2004-04-12 19:22 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=933762&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Bernhard Reiter (ber) Assigned to: Nobody/Anonymous (nobody) Summary: fix for #880073 list-id can violate RFC2919 Initial Comment: To make sure RFC2919 is not violated. "<" and ">" will be added if no list description exists. The maxlinelen=998 is a precaution to keep the may line length of RFC2822. Fixes [ 880073 ] list-id might violate RFC2919 and RFC2822 https://sourceforge.net/tracker/index.php?func=detail&aid=880073&group_id=103&atid=100103 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=933762&group_id=103 From noreply at sourceforge.net Mon Apr 12 13:23:44 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 12 13:23:48 2004 Subject: [ mailman-Bugs-880073 ] list-id might violate RFC2919 and RFC2822 Message-ID: Bugs item #880073, was opened at 2004-01-19 21:23 Message generated for change (Comment added) made by ber You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=880073&group_id=103 Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 6 Submitted By: Bernhard Reiter (ber) Assigned to: Nobody/Anonymous (nobody) Summary: list-id might violate RFC2919 and RFC2822 Initial Comment: Code in http://cvs.sourceforge.net/viewcvs.py/mailman/mailman/Mailman/Handlers/CookHeaders.py?rev=2.33.2.5&view=markup (as shipped with mailman 2.1.4) will use formataddr for the List-Id: listid_h = formataddr((desc, listid)) This will violate the RFC2919, if not(desc), because the angle-brackets might be left out. 3. The List-Id Header Field The List-Id header MAY optionally include a description by including it as a "phrase" [DRUMS] before the angle-bracketed list identifier. The syntax of the List-Id header follows: list-id-header = "List-ID:" [phrase] "<" list-id ">" CRLF Unlike most headers in [RFC822], the List-Id header does not allow free insertion of whitespace and comments around tokens. [Go inside ~mailman/bin] python Python 2.1.3 (#1, Sep 7 2002, 15:29:56) [GCC 2.95.4 20011002 (Debian prerelease)] on linux2 Type "copyright", "credits" or "license" for more information. >>> import paths >>> from email.Utils import formataddr >>> formataddr(("A strange mailing list","strange.list.org")) 'A strange mailing list ' >>> formataddr((None,"strange.list.org")) 'strange.list.org' >>> formataddr(("","strange.list.org")) 'strange.list.org' Solution: go back to old code and check http://sourceforge.net/tracker/download.php?group_id=103&atid=100103&file_id=57904&aid=665732 to limit the line length so you don't violate RFC2822 ---------------------------------------------------------------------- >Comment By: Bernhard Reiter (ber) Date: 2004-04-12 19:23 Message: Logged In: YES user_id=113859 Added a fix for the problem: [ 933762 ] fix for #880073 list-id can violate RFC2919 https://sourceforge.net/tracker/index.php?func=detail&aid=933762&group_id=103&atid=300103 ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2004-01-19 21:25 Message: Logged In: YES user_id=113859 I'm raising the priority to 6 because many people get annoyed if the List-ID headers change. Mailman 2.1.3 did better in the RFC2919 regard, 2.1.4 breaks it in an attempt to fix other bugs. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=880073&group_id=103 From noreply at sourceforge.net Mon Apr 12 13:23:54 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 12 13:23:59 2004 Subject: [ mailman-Patches-933762 ] fix for #880073 list-id can violate RFC2919 Message-ID: Patches item #933762, was opened at 2004-04-12 19:22 Message generated for change (Settings changed) made by ber You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=933762&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None >Priority: 6 Submitted By: Bernhard Reiter (ber) Assigned to: Nobody/Anonymous (nobody) Summary: fix for #880073 list-id can violate RFC2919 Initial Comment: To make sure RFC2919 is not violated. "<" and ">" will be added if no list description exists. The maxlinelen=998 is a precaution to keep the may line length of RFC2822. Fixes [ 880073 ] list-id might violate RFC2919 and RFC2822 https://sourceforge.net/tracker/index.php?func=detail&aid=880073&group_id=103&atid=100103 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=933762&group_id=103 From noreply at sourceforge.net Mon Apr 12 13:24:58 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 12 13:25:02 2004 Subject: [ mailman-Patches-933757 ] fix for [815297] signatures break Message-ID: Patches item #933757, was opened at 2004-04-12 19:15 Message generated for change (Comment added) made by ber You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=933757&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None >Priority: 8 Submitted By: Bernhard Reiter (ber) Assigned to: Nobody/Anonymous (nobody) Summary: fix for [815297] signatures break Initial Comment: Fix attempt for [ 815297 ] Breaking signatures in message/rfc822 attachement! https://sourceforge.net/tracker/?func=detail&aid=815297&group_id=103&atid=100103 The patch introduces a new Mailman specific Generator class and only enables header folding for the top object and Mailbox.py and SMTPDirect.py. ---------------------------------------------------------------------- >Comment By: Bernhard Reiter (ber) Date: 2004-04-12 19:24 Message: Logged In: YES user_id=113859 A bug fix to a priority 8 bug... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=933757&group_id=103 From noreply at sourceforge.net Tue Apr 13 19:54:03 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Apr 13 19:54:09 2004 Subject: [ mailman-Feature Requests-934617 ] Option for enable/disable combining multipart/alternative Message-ID: Feature Requests item #934617, was opened at 2004-04-13 15:54 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=934617&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Paul Barnett (ptbarnett) Assigned to: Nobody/Anonymous (nobody) Summary: Option for enable/disable combining multipart/alternative Initial Comment: If filter_content is true, process() in MimeDel.py removes all but the first non-empty part in a multipart/alternative. All other functionality in process() can be enabled/disabled individually, but this particular sub-function cannot. A message with a text/plain and text/html alternative is usually reduced to text/plain, since that's usually the first alternative -- even if convert_html_to_plaintext is false. An option should be provided on the Content Filtering administration page to enable/disable this sub-function. This would permit the filtering of attachments, while preserving the HTML and plaintext versions of the message. Note: text/html must be added to pass_mime_types in order for the HTML part to be preserved, but I'm not advocating that change to the default content filter. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=934617&group_id=103 From noreply at sourceforge.net Wed Apr 14 12:25:54 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Apr 14 12:26:04 2004 Subject: [ mailman-Bugs-932220 ] MemoryError when running senddigests Message-ID: Bugs item #932220, was opened at 2004-04-09 08:24 Message generated for change (Comment added) made by finnertyp You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=932220&group_id=103 Category: mail delivery Group: 2.1 (stable) >Status: Deleted >Resolution: Duplicate Priority: 5 Submitted By: Patrick Finnerty (finnertyp) Assigned to: Nobody/Anonymous (nobody) Summary: MemoryError when running senddigests Initial Comment: Using Mailman v2.1.4 & Python v2.3.3. OS = TRU64 5.1a Problem only occurs on one mailing list: /usr/local/bin/python -S /usr/local/mailman/cron/senddigests -l shc.nt Traceback (most recent call last): File "/usr/local/mailman/cron/senddigests", line 94, in ? main() File "/usr/local/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/usr/local/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 132, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 306, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 304, in process t = part.get_payload(decode=True) File "/usr/local/mailman/pythonlib/email/Message.py", line 197, in get_payload return Utils._qdecode(payload) File "/usr/local/lib/python2.3/quopri.py", line 161, in decodestring return a2b_qp(s, header = header) MemoryError ---------------------------------------------------------------------- >Comment By: Patrick Finnerty (finnertyp) Date: 2004-04-14 16:25 Message: Logged In: YES user_id=594846 Duplicate ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=932220&group_id=103 From noreply at sourceforge.net Wed Apr 14 13:56:00 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Apr 14 13:56:06 2004 Subject: [ mailman-Patches-933757 ] fix for [815297] signatures break Message-ID: Patches item #933757, was opened at 2004-04-12 19:15 Message generated for change (Comment added) made by ber You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=933757&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 8 Submitted By: Bernhard Reiter (ber) Assigned to: Nobody/Anonymous (nobody) Summary: fix for [815297] signatures break Initial Comment: Fix attempt for [ 815297 ] Breaking signatures in message/rfc822 attachement! https://sourceforge.net/tracker/?func=detail&aid=815297&group_id=103&atid=100103 The patch introduces a new Mailman specific Generator class and only enables header folding for the top object and Mailbox.py and SMTPDirect.py. ---------------------------------------------------------------------- >Comment By: Bernhard Reiter (ber) Date: 2004-04-14 19:56 Message: Logged In: YES user_id=113859 My patch was tested with python 2.3.3. Thomas K?ster made a patch which also works with python 2.1.x I'll attach it. ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2004-04-12 19:24 Message: Logged In: YES user_id=113859 A bug fix to a priority 8 bug... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=933757&group_id=103 From noreply at sourceforge.net Wed Apr 14 14:00:51 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Apr 14 14:00:57 2004 Subject: [ mailman-Patches-927761 ] Courier MTA list submission handler Message-ID: Patches item #927761, was opened at 2004-04-01 13:36 Message generated for change (Comment added) made by fmouse You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=927761&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Lindsay Haisley (fmouse) Assigned to: Nobody/Anonymous (nobody) Summary: Courier MTA list submission handler Initial Comment: This script is meant to be called from /alias/.courier-default. It catches all mail to any address at a Courier virtual domain not otherwise handled by an explicit account or a .courier file. It looks at the recepient for each mail message not otherwise handled and decides if the mail is addressed to a valid list or not, and bounces the message with a helpful suggestion if it's not addressed to a list. This script is based on Bruce Perens' qmail-to-mailman.py script, and is specifically designed for use with Courier. You may wish to put this into the contrib section of the distributed mailman source. ---------------------------------------------------------------------- >Comment By: Lindsay Haisley (fmouse) Date: 2004-04-14 13:00 Message: Logged In: YES user_id=694133 The courier-to-mailman.py which I submitted contains a small error in VERP handling. Here's a re-post of it with the fix. For anyone simply wanting to patch the file I previously submitted .... --- courier-to-mailman.py~ 2004-04-14 12:54:23.000000000 -0500 +++ courier-to-mailman.py 2004-04-14 12:54:23.000000000 -0500 @@ -76,7 +76,7 @@ listname = local types = (("-admin$", "admin"), ("-bounces$", "bounces"), - ("-bounces-.*$", "bounces"), # Handles VERPs + ("-bounces\+.*$", "bounces"), # Handles VERPs ("-confirm$", "confirm"), ("-join$", "join"), ("-leave$", "leave"), ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=927761&group_id=103 From noreply at sourceforge.net Wed Apr 14 14:53:02 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Apr 14 14:53:21 2004 Subject: [ mailman-Patches-891491 ] Scrubber.py patch Message-ID: Patches item #891491, was opened at 2004-02-06 02:26 Message generated for change (Comment added) made by ber You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=891491&group_id=103 Category: Pipermail Group: Mailman 2.1 Status: Open Resolution: None Priority: 8 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: Scrubber.py patch Initial Comment: Scrubber.py has number of bugs for processing various types of attachment and languages and many have submitted patches to fix them. This patch item is opened to collect such patches for convenience. This patch corrects: - if an attached text is composed by win notepad, it has no charset specified and actual charset may be different from message/list charset. This sometimes cause error in composing digest message. - sometimes, null charset is represented by '' as well as None. - embedded rfc-2822 message is lost if you don't use msg.walk() - special problem with japanese charsets. - t (stringfied part) may be None which you can't append a '\n'. ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2004-04-14 20:53 Message: Logged In: YES user_id=113859 Thanks for working on the patch. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-02-25 11:42 Message: Logged In: YES user_id=67709 uploading revised patch. Now fixes a few more bugs which try to decode scrub plain text message and result in mojibake. Also, japanese filename tend to become so long that system limit may exceeded because of mime encoding, so add an option not to use the filename in the message but to use 'attachment' as filename. Because this patch spans two files (Defaults.py.in and Handlers/Scrubber.py) you have to cd mailman and patch -p1 < this_patch. (Well, I think it is -p1. If it didn't work, try -p0 ;-) ---------------------------------------------------------------------- Comment By: Jonathan Larmour (jifl) Date: 2004-02-22 18:25 Message: Logged In: YES user_id=817601 I strongly recommend applying this patch. I received a mail bounce on a list with an empty charset in a part (i.e. "charset=") and it caused /var/mailman/cron/senddigest and thus all digest processing to fail because of this error: Traceback (most recent call last): File "/var/mailman/cron/senddigests", line 94, in ? main() File "/var/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/var/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 123, in send_digests send_i18n_digests(mlist, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 295, in send_i18n_digests msg = scrubber(mlist, msg) File "/var/mailman/Mailman/Handlers/Scrubber.py", line 308, in process t = t.encode(charset, 'replace') File "/usr/lib/python2.2/encodings/__init__.py", line 51, in search_function mod = __import__(modname,globals(),locals(),'*') which is something this patch fixes. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=891491&group_id=103 From noreply at sourceforge.net Thu Apr 15 06:29:04 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Apr 15 06:29:09 2004 Subject: [ mailman-Bugs-931861 ] MemoryError when running senddigests Message-ID: Bugs item #931861, was opened at 2004-04-08 17:19 Message generated for change (Comment added) made by finnertyp You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=931861&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Patrick Finnerty (finnertyp) Assigned to: Nobody/Anonymous (nobody) Summary: MemoryError when running senddigests Initial Comment: Using Mailman v2.1.4 & Python v2.3.3. OS = TRU64 5.1a Problem only occurs on one mailing list: /usr/local/bin/python -S /usr/local/mailman/cron/senddigests -l shc.nt Traceback (most recent call last): File "/usr/local/mailman/cron/senddigests", line 94, in ? main() File "/usr/local/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/usr/local/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 132, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 306, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 304, in process t = part.get_payload(decode=True) File "/usr/local/mailman/pythonlib/email/Message.py", line 197, in get_payload return Utils._qdecode(payload) File "/usr/local/lib/python2.3/quopri.py", line 161, in decodestring return a2b_qp(s, header = header) MemoryError ---------------------------------------------------------------------- >Comment By: Patrick Finnerty (finnertyp) Date: 2004-04-15 10:29 Message: Logged In: YES user_id=594846 The list in question is also shunting all posts. Disabling the Digest option allowed posts to come through again and also allowed the posts in te queue to be unshunted. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=931861&group_id=103 From noreply at sourceforge.net Fri Apr 16 11:55:43 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Apr 16 11:55:48 2004 Subject: [ mailman-Bugs-936432 ] python name generators? Message-ID: Bugs item #936432, was opened at 2004-04-16 17:55 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=936432&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Martin Steldinger (tribble23) Assigned to: Nobody/Anonymous (nobody) Summary: python name generators? Initial Comment: Hejho, can anybody help please? the whole mailman does not work anymore. this is only the weboutput of it. 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 80, in run_main pkg = __import__('Mailman.Cgi', globals(), locals(), [scriptname]) File "/usr/lib/mailman/Mailman/Cgi/listinfo.py", line 26, in ? from Mailman import Utils File "/var/lib/mailman/Mailman/Utils.py", line 37, in ? import email.Header File "/usr/lib/python2.3/email/Header.py", line 11, in ? import email.base64MIME File "/usr/lib/python2.3/email/base64MIME.py", line 31, in ? from email._compat22 import _floordiv File "/usr/lib/python2.3/email/_compat22.py", line 7, in ? from __future__ import generators ImportError: cannot import name generators Python information: Variable Value sys.version 2.3.3 (#2, Jan 13 2004, 00:47:05) [GCC 3.3.3 20040110 (prerelease) (Debian)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 is it an broken python? the debian mailmanpackage maintainer sais so...? thanx, m. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=936432&group_id=103 From noreply at sourceforge.net Sun Apr 18 08:26:49 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Apr 18 08:26:57 2004 Subject: [ mailman-Bugs-707610 ] Uncaught runner exception: Empty module name Message-ID: Bugs item #707610, was opened at 2003-03-21 16:55 Message generated for change (Comment added) made by zebaoth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=707610&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jan Kellermann (werk21) Assigned to: Nobody/Anonymous (nobody) Summary: Uncaught runner exception: Empty module name Initial Comment: mailman is shunting a lot of mails with this message in error-log, my language-version is german. i work with the current cvs-version Mar 21 16:11:21 2003 (12591) Uncaught runner exception: Empty module name Mar 21 16:11:21 2003 (12591) Traceback (most recent call last): File "/usr/local/mailman- 2.1//Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman- 2.1//Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman- 2.1//Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman- 2.1//Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman- 2.1//Mailman/Handlers/ToDigest.py", line 82, in process send_digests(mlist, mboxfp) File "/usr/local/mailman- 2.1//Mailman/Handlers/ToDigest.py", line 123, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman- 2.1//Mailman/Handlers/ToDigest.py", line 295, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman- 2.1//Mailman/Handlers/Scrubber.py", line 308, in process t = t.encode(charset, 'replace') File "/usr/lib/python2.2/encodings/__init__.py", line 51, in search_function mod = __import__(modname,globals(),locals(),'*') ValueError: Empty module name Mar 21 16:11:21 2003 (12591) SHUNTING: 1048241610.7517231+289483353c3e3632ab0892d8ceb 8c936f107bc5e ---------------------------------------------------------------------- Comment By: Jochen Witte (zebaoth) Date: 2004-04-18 12:26 Message: Logged In: YES user_id=565663 See Bug 871050 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=707610&group_id=103 From noreply at sourceforge.net Mon Apr 19 19:53:00 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 19 19:53:13 2004 Subject: [ mailman-Patches-820723 ] Mailman/pipermail/MHonArc integration patch Message-ID: Patches item #820723, was opened at 2003-10-09 18:19 Message generated for change (Comment added) made by mmokrejs You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=820723&group_id=103 Category: Pipermail Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Mailman/pipermail/MHonArc integration patch Initial Comment: This patch tightly integrates the MHonArc mail-to-HTML convertor with Mailman and its internal pipermail archiving code. The purpose of the patch is to produce a fusion of (hopefully) the best features of pipermail and MHonArc for handling Mailman mailing list archives. For more detail see patch content or http://www.openinfo.co.uk/mailman/patches/mhonarc/index.html ---------------------------------------------------------------------- Comment By: Martin Mokrejs (mmokrejs) Date: 2004-04-20 01:53 Message: Logged In: YES user_id=696559 I've applied this patch(mhonarc-2.1.4-0.1.patch.gz) and it works great for me. Would someone apply to offcial cvs tree? Thanks. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2004-01-02 16:32 Message: Logged In: YES user_id=75166 mhonarc-2.1.4-0.1.patch is a MM 2.1.4 compatible version of this patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-10-22 16:32 Message: Logged In: YES user_id=75166 mhonarc-2.1.3-0.6.patch better supports the use of MHonArc -saveresources option. Also fixes minor HTML syntax error in mhonarc.mrc and author.mrc that affected generated date and author index pages. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-10-14 07:49 Message: Logged In: YES user_id=75166 With mhonarc-2.1.3-0.4.patch, the default path to MHonArc itself defined in Defaults.py is the empty string and, until this is changed, the option to select MHonArc instead of pipermail for per-list archiving is not offered on the web admin GUI. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-10-10 19:51 Message: Logged In: YES user_id=75166 Under some circumstances, when a single message is passed to MHonArc for archiving via a pipe, MHonArc may finish its processing and exit, closing its STDIN before the Mailman process that invoked it has finished output of the message to the pipe. Mistakenly, the patched pipermail code treated this as an error. mhonarc-2.1.3-0.3.patch corrects this mistake. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=820723&group_id=103 From noreply at sourceforge.net Mon Apr 19 20:00:24 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 19 20:00:30 2004 Subject: [ mailman-Patches-850805 ] Aggressive anti email address harvesting measure Message-ID: Patches item #850805, was opened at 2003-11-28 17:23 Message generated for change (Comment added) made by mmokrejs You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=850805&group_id=103 Category: Pipermail Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Aggressive anti email address harvesting measure Initial Comment: This patch is prompted by discussion on the mailman- developers list won the following subject: Re: [Mailman-Developers] bugtraq submission warning: email address harvesting exploit For those with deep concerns about email address harvesting this patch offers a more aggressive masking of email addresses in Mailman mail archive files. The patch modifes two files in the standard Mailman distribution: Mailman/Defaults.py and Mailman/Cgi/ private.py and can be applied using the following command from within the Mailman build directory: path -p1 < path-to-patch-file It would be fairly trivial to make enabling this feature per- list configurable rather than it being a site admin decision and I will enhance this patch for that purpose if people show an interest in it being done. The following notes about the patch can be found in Defaults.py. Rather idiosyncratically most of the operational elements of this patch are in that file. My reasoning behind this decision is that if people want to fool with the regexes that are at the heart of this patch they can see what will be affected by the changes more readily if the related bits are in the same place. ##### # Anti-spam email address harvesting prevention measures. # # These measures are to limit the ability of spam generators to acquire # email address from archived material in Mailman's list archives. # Implementation is via a dynamic search and replace for email # addresses, appearing in files of MIME type text/html or text/plain, as # those files are requested. The underlying archive file content as # generated by the archiving software remains unchanged. # # The implementation requires that archive files are all delivered by a # modified private.py CGI script which only requires user authentication # if the list whose archive material is being requested is set up as a private # list. In order to get public archives served by private.py a RewriteRule # like this: # # RewriteRule ^/pipermail/(.*) /mailman/private/$1 [PT] # # needs to be used in the Apache httpd.conf to transparently redirect # public arechive file requests. # # When email addresses are found, the domain part of the addressed is replaced # with a string of 'x' characters. If the local part of the address appears to # have been VERP'ed then the VERP information is similarly obscured. This is # a fairly brutal set of irreversible modifications to any email addresses in # the returned text and will break any mailto: links in the text. # # Th eamil address regex looks for either an '@' character or its HTML escaped # version '%40' as the local-part/domain separator. You should set # ARCHIVER_OBSCURES_EMAILADDRS = 0 and run bin/arch to rebuild existing archives # to prevent that feature interfering with the operation of these harvesting # prevention measures. # # If you decide to change the regexes then copy all of this stuff into # mm_cfg.py and make the changes there. # ##### ---------------------------------------------------------------------- Comment By: Martin Mokrejs (mmokrejs) Date: 2004-04-20 02:00 Message: Logged In: YES user_id=696559 What sould I do with this error caused by the patch? Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/private.py", line 165, in main sys.stdout.write(mm_cfg.deny_harvest(f.read())) AttributeError: 'module' object has no attribute 'deny_harvest' ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-11-30 08:02 Message: Logged In: YES user_id=75166 As pointed out on the mailman-developers list, potential users of this patch should be aware that the simple approach to masking email addresses used by this patch will also capture and munge any other strings in the archive data that resemble email addresses. This can include mailto URLs, other URLs and Message ids. This side-effect may make the patch unsuitable for use with your system, although you also need to consider that the patch does not irreversibly change the source pipermail archived material held on the server; the changes are only made in the copy of the archive material sent to the requesting browser by the server. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=850805&group_id=103 From noreply at sourceforge.net Mon Apr 19 20:02:02 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 19 20:02:12 2004 Subject: [ mailman-Patches-778929 ] templates/cs/listinfo.html: Small grammar fix Message-ID: Patches item #778929, was opened at 2003-07-28 15:44 Message generated for change (Comment added) made by mmokrejs You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=778929&group_id=103 Category: internationalization Group: None Status: Open Resolution: None Priority: 5 Submitted By: Rudolf Cejka (cejkar) Assigned to: Nobody/Anonymous (nobody) Summary: templates/cs/listinfo.html: Small grammar fix Initial Comment: Changed prohl?dnou to prohl?dnout. ---------------------------------------------------------------------- Comment By: Martin Mokrejs (mmokrejs) Date: 2004-04-20 02:02 Message: Logged In: YES user_id=696559 This should be committed without any hesitation (it is actually a typo fix). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=778929&group_id=103 From noreply at sourceforge.net Mon Apr 19 22:37:18 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 19 22:37:22 2004 Subject: [ mailman-Patches-938301 ] Fix for bug 740457 Message-ID: Patches item #938301, was opened at 2004-04-19 19:37 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=938301&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: David J. Mellor (djmellor) Assigned to: Nobody/Anonymous (nobody) Summary: Fix for bug 740457 Initial Comment: The code in ArchRunner that attempts to extract a date from a message's Date header invokes email.Utils.mktime_tz, which in turn invokes Python's time.mktime builtin. This builtin can throw either an OverflowError or a ValueError exception if the date cannot be converted. For example, the implementation of mktime in glibc on Linux always returns -1 for dates before the epoch, and on Linux an OverflowError exception will be generatedin this case. The code in ArchRunner was only handling ValueError exceptions, with the result that messages whose dates were invalid would be shunted on Linux instead of appearing in the archive. The fix is simply to make the code in ArchRunner handle both error conditions. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=938301&group_id=103 From noreply at sourceforge.net Tue Apr 20 05:52:26 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Apr 20 05:52:38 2004 Subject: [ mailman-Patches-850805 ] Aggressive anti email address harvesting measure Message-ID: Patches item #850805, was opened at 2003-11-28 17:23 Message generated for change (Comment added) made by mmokrejs You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=850805&group_id=103 Category: Pipermail Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Aggressive anti email address harvesting measure Initial Comment: This patch is prompted by discussion on the mailman- developers list won the following subject: Re: [Mailman-Developers] bugtraq submission warning: email address harvesting exploit For those with deep concerns about email address harvesting this patch offers a more aggressive masking of email addresses in Mailman mail archive files. The patch modifes two files in the standard Mailman distribution: Mailman/Defaults.py and Mailman/Cgi/ private.py and can be applied using the following command from within the Mailman build directory: path -p1 < path-to-patch-file It would be fairly trivial to make enabling this feature per- list configurable rather than it being a site admin decision and I will enhance this patch for that purpose if people show an interest in it being done. The following notes about the patch can be found in Defaults.py. Rather idiosyncratically most of the operational elements of this patch are in that file. My reasoning behind this decision is that if people want to fool with the regexes that are at the heart of this patch they can see what will be affected by the changes more readily if the related bits are in the same place. ##### # Anti-spam email address harvesting prevention measures. # # These measures are to limit the ability of spam generators to acquire # email address from archived material in Mailman's list archives. # Implementation is via a dynamic search and replace for email # addresses, appearing in files of MIME type text/html or text/plain, as # those files are requested. The underlying archive file content as # generated by the archiving software remains unchanged. # # The implementation requires that archive files are all delivered by a # modified private.py CGI script which only requires user authentication # if the list whose archive material is being requested is set up as a private # list. In order to get public archives served by private.py a RewriteRule # like this: # # RewriteRule ^/pipermail/(.*) /mailman/private/$1 [PT] # # needs to be used in the Apache httpd.conf to transparently redirect # public arechive file requests. # # When email addresses are found, the domain part of the addressed is replaced # with a string of 'x' characters. If the local part of the address appears to # have been VERP'ed then the VERP information is similarly obscured. This is # a fairly brutal set of irreversible modifications to any email addresses in # the returned text and will break any mailto: links in the text. # # Th eamil address regex looks for either an '@' character or its HTML escaped # version '%40' as the local-part/domain separator. You should set # ARCHIVER_OBSCURES_EMAILADDRS = 0 and run bin/arch to rebuild existing archives # to prevent that feature interfering with the operation of these harvesting # prevention measures. # # If you decide to change the regexes then copy all of this stuff into # mm_cfg.py and make the changes there. # ##### ---------------------------------------------------------------------- Comment By: Martin Mokrejs (mmokrejs) Date: 2004-04-20 11:52 Message: Logged In: YES user_id=696559 Ohh, sorry, the patch really wasn't applied. After proper installation, I can confirm it works fine. ---------------------------------------------------------------------- Comment By: Martin Mokrejs (mmokrejs) Date: 2004-04-20 02:00 Message: Logged In: YES user_id=696559 What sould I do with this error caused by the patch? Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/private.py", line 165, in main sys.stdout.write(mm_cfg.deny_harvest(f.read())) AttributeError: 'module' object has no attribute 'deny_harvest' ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-11-30 08:02 Message: Logged In: YES user_id=75166 As pointed out on the mailman-developers list, potential users of this patch should be aware that the simple approach to masking email addresses used by this patch will also capture and munge any other strings in the archive data that resemble email addresses. This can include mailto URLs, other URLs and Message ids. This side-effect may make the patch unsuitable for use with your system, although you also need to consider that the patch does not irreversibly change the source pipermail archived material held on the server; the changes are only made in the copy of the archive material sent to the requesting browser by the server. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=850805&group_id=103 From noreply at sourceforge.net Tue Apr 20 17:21:02 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Apr 20 17:21:41 2004 Subject: [ mailman-Bugs-936432 ] python name generators? Message-ID: Bugs item #936432, was opened at 2004-04-16 08:55 Message generated for change (Comment added) made by zakureth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=936432&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Martin Steldinger (tribble23) Assigned to: Nobody/Anonymous (nobody) Summary: python name generators? Initial Comment: Hejho, can anybody help please? the whole mailman does not work anymore. this is only the weboutput of it. 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 80, in run_main pkg = __import__('Mailman.Cgi', globals(), locals(), [scriptname]) File "/usr/lib/mailman/Mailman/Cgi/listinfo.py", line 26, in ? from Mailman import Utils File "/var/lib/mailman/Mailman/Utils.py", line 37, in ? import email.Header File "/usr/lib/python2.3/email/Header.py", line 11, in ? import email.base64MIME File "/usr/lib/python2.3/email/base64MIME.py", line 31, in ? from email._compat22 import _floordiv File "/usr/lib/python2.3/email/_compat22.py", line 7, in ? from __future__ import generators ImportError: cannot import name generators Python information: Variable Value sys.version 2.3.3 (#2, Jan 13 2004, 00:47:05) [GCC 3.3.3 20040110 (prerelease) (Debian)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 is it an broken python? the debian mailmanpackage maintainer sais so...? thanx, m. ---------------------------------------------------------------------- Comment By: Michael Newlyn Blake (zakureth) Date: 2004-04-20 14:21 Message: Logged In: YES user_id=111909 I to am having this problem on an up to date Suse 9.0 system with Mailman 2.1.2. Messages I'm getting in the error log are: Apr 20 14:14:51 2004 (7447) uncaught archiver exception at filepos: 0 Apr 20 14:14:51 2004 (7447) Uncaught runner exception: Empty module name Apr 20 14:14:51 2004 (7447) Traceback (most recent call last): File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/ArchRunner.py", line 73, in _dispose mlist.ArchiveMail(msg) File "/usr/lib/mailman/Mailman/Archiver/Archiver.py", line 206, in ArchiveMail h.processUnixMailbox(f) File "/usr/lib/mailman/Mailman/Archiver/pipermail.py", line 544, in processUnixMailbox m = mbox.next() File "/usr/lib/python2.3/mailbox.py", line 35, in next return self.factory(_Subfile(self.fp, start, stop)) File "/usr/lib/mailman/Mailman/Mailbox.py", line 89, in scrubber return mailbox.scrub(msg) File "/usr/lib/mailman/Mailman/Mailbox.py", line 109, in scrub return self._scrubber(self._mlist, msg) File "/usr/lib/mailman/Mailman/Handlers/Scrubber.py", line 308, in process t = t.encode(charset, 'replace') File "/usr/lib/python2.3/encodings/__init__.py", line 84, in search_function globals(), locals(), _import_tail) ValueError: Empty module name Apr 20 14:14:51 2004 (7447) SHUNTING: 1082469143.1593151+1674b479f52223bba07f4eda7f29b743c99ae34f And an occasional: Apr 20 14:07:58 2004 (3191) Uncaught runner exception: unknown encoding: big5 Apr 20 14:07:58 2004 (3191) Traceback (most recent call last): File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/CommandRunner.py", line 218, in _dispose res = Results(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/CommandRunner.py", line 75, in __init__ subj = make_header(decode_header(subj)).__unicode__() File "/usr/lib/mailman/pythonlib/email/Header.py", line 144, in make_header h.append(s, charset) File "/usr/lib/mailman/pythonlib/email/Header.py", line 272, in append ustr = unicode(s, incodec, errors) LookupError: unknown encoding: big5 Apr 20 14:07:58 2004 (3191) SHUNTING: 1080098916.48541+a5acb6484d8d579d298079c3ebc3d255953e217c Disabling digest doesn't seem to have any effect. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=936432&group_id=103 From noreply at sourceforge.net Tue Apr 20 17:30:15 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Apr 20 17:30:25 2004 Subject: [ mailman-Bugs-931861 ] MemoryError when running senddigests Message-ID: Bugs item #931861, was opened at 2004-04-08 10:19 Message generated for change (Comment added) made by zakureth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=931861&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Patrick Finnerty (finnertyp) Assigned to: Nobody/Anonymous (nobody) Summary: MemoryError when running senddigests Initial Comment: Using Mailman v2.1.4 & Python v2.3.3. OS = TRU64 5.1a Problem only occurs on one mailing list: /usr/local/bin/python -S /usr/local/mailman/cron/senddigests -l shc.nt Traceback (most recent call last): File "/usr/local/mailman/cron/senddigests", line 94, in ? main() File "/usr/local/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/usr/local/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 132, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 306, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 304, in process t = part.get_payload(decode=True) File "/usr/local/mailman/pythonlib/email/Message.py", line 197, in get_payload return Utils._qdecode(payload) File "/usr/local/lib/python2.3/quopri.py", line 161, in decodestring return a2b_qp(s, header = header) MemoryError ---------------------------------------------------------------------- Comment By: Michael Newlyn Blake (zakureth) Date: 2004-04-20 14:30 Message: Logged In: YES user_id=111909 I to am having this problem on an up to date Suse 9.0 system with Mailman 2.1.2. Messages I'm getting in the error log are: Apr 20 14:14:51 2004 (7447) uncaught archiver exception at filepos: 0 Apr 20 14:14:51 2004 (7447) Uncaught runner exception: Empty module name Apr 20 14:14:51 2004 (7447) Traceback (most recent call last): File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/ArchRunner.py", line 73, in _dispose mlist.ArchiveMail(msg) File "/usr/lib/mailman/Mailman/Archiver/Archiver.py", line 206, in ArchiveMail h.processUnixMailbox(f) File "/usr/lib/mailman/Mailman/Archiver/pipermail.py", line 544, in processUnixMailbox m = mbox.next() File "/usr/lib/python2.3/mailbox.py", line 35, in next return self.factory(_Subfile(self.fp, start, stop)) File "/usr/lib/mailman/Mailman/Mailbox.py", line 89, in scrubber return mailbox.scrub(msg) File "/usr/lib/mailman/Mailman/Mailbox.py", line 109, in scrub return self._scrubber(self._mlist, msg) File "/usr/lib/mailman/Mailman/Handlers/Scrubber.py", line 308, in process t = t.encode(charset, 'replace') File "/usr/lib/python2.3/encodings/__init__.py", line 84, in search_function globals(), locals(), _import_tail) ValueError: Empty module name Apr 20 14:14:51 2004 (7447) SHUNTING: 1082469143.1593151+1674b479f52223bba07f4eda7f29b743c99ae34f And an occasional: Apr 20 14:07:58 2004 (3191) Uncaught runner exception: unknown encoding: big5 Apr 20 14:07:58 2004 (3191) Traceback (most recent call last): File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/CommandRunner.py", line 218, in _dispose res = Results(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/CommandRunner.py", line 75, in __init__ subj = make_header(decode_header(subj)).__unicode__() File "/usr/lib/mailman/pythonlib/email/Header.py", line 144, in make_header h.append(s, charset) File "/usr/lib/mailman/pythonlib/email/Header.py", line 272, in append ustr = unicode(s, incodec, errors) LookupError: unknown encoding: big5 Apr 20 14:07:58 2004 (3191) SHUNTING: 1080098916.48541+a5acb6484d8d579d298079c3ebc3d255953e217c Disabling digest doesn't seem to have any effect. ---------------------------------------------------------------------- Comment By: Patrick Finnerty (finnertyp) Date: 2004-04-15 03:29 Message: Logged In: YES user_id=594846 The list in question is also shunting all posts. Disabling the Digest option allowed posts to come through again and also allowed the posts in te queue to be unshunted. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=931861&group_id=103 From noreply at sourceforge.net Tue Apr 20 17:30:51 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Tue Apr 20 17:30:56 2004 Subject: [ mailman-Bugs-936432 ] python name generators? Message-ID: Bugs item #936432, was opened at 2004-04-16 08:55 Message generated for change (Comment added) made by zakureth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=936432&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Martin Steldinger (tribble23) Assigned to: Nobody/Anonymous (nobody) Summary: python name generators? Initial Comment: Hejho, can anybody help please? the whole mailman does not work anymore. this is only the weboutput of it. 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 80, in run_main pkg = __import__('Mailman.Cgi', globals(), locals(), [scriptname]) File "/usr/lib/mailman/Mailman/Cgi/listinfo.py", line 26, in ? from Mailman import Utils File "/var/lib/mailman/Mailman/Utils.py", line 37, in ? import email.Header File "/usr/lib/python2.3/email/Header.py", line 11, in ? import email.base64MIME File "/usr/lib/python2.3/email/base64MIME.py", line 31, in ? from email._compat22 import _floordiv File "/usr/lib/python2.3/email/_compat22.py", line 7, in ? from __future__ import generators ImportError: cannot import name generators Python information: Variable Value sys.version 2.3.3 (#2, Jan 13 2004, 00:47:05) [GCC 3.3.3 20040110 (prerelease) (Debian)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 is it an broken python? the debian mailmanpackage maintainer sais so...? thanx, m. ---------------------------------------------------------------------- Comment By: Michael Newlyn Blake (zakureth) Date: 2004-04-20 14:30 Message: Logged In: YES user_id=111909 Sorry, I added that comment to the wrong bug. Please delete. ---------------------------------------------------------------------- Comment By: Michael Newlyn Blake (zakureth) Date: 2004-04-20 14:21 Message: Logged In: YES user_id=111909 I to am having this problem on an up to date Suse 9.0 system with Mailman 2.1.2. Messages I'm getting in the error log are: Apr 20 14:14:51 2004 (7447) uncaught archiver exception at filepos: 0 Apr 20 14:14:51 2004 (7447) Uncaught runner exception: Empty module name Apr 20 14:14:51 2004 (7447) Traceback (most recent call last): File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/ArchRunner.py", line 73, in _dispose mlist.ArchiveMail(msg) File "/usr/lib/mailman/Mailman/Archiver/Archiver.py", line 206, in ArchiveMail h.processUnixMailbox(f) File "/usr/lib/mailman/Mailman/Archiver/pipermail.py", line 544, in processUnixMailbox m = mbox.next() File "/usr/lib/python2.3/mailbox.py", line 35, in next return self.factory(_Subfile(self.fp, start, stop)) File "/usr/lib/mailman/Mailman/Mailbox.py", line 89, in scrubber return mailbox.scrub(msg) File "/usr/lib/mailman/Mailman/Mailbox.py", line 109, in scrub return self._scrubber(self._mlist, msg) File "/usr/lib/mailman/Mailman/Handlers/Scrubber.py", line 308, in process t = t.encode(charset, 'replace') File "/usr/lib/python2.3/encodings/__init__.py", line 84, in search_function globals(), locals(), _import_tail) ValueError: Empty module name Apr 20 14:14:51 2004 (7447) SHUNTING: 1082469143.1593151+1674b479f52223bba07f4eda7f29b743c99ae34f And an occasional: Apr 20 14:07:58 2004 (3191) Uncaught runner exception: unknown encoding: big5 Apr 20 14:07:58 2004 (3191) Traceback (most recent call last): File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/CommandRunner.py", line 218, in _dispose res = Results(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/CommandRunner.py", line 75, in __init__ subj = make_header(decode_header(subj)).__unicode__() File "/usr/lib/mailman/pythonlib/email/Header.py", line 144, in make_header h.append(s, charset) File "/usr/lib/mailman/pythonlib/email/Header.py", line 272, in append ustr = unicode(s, incodec, errors) LookupError: unknown encoding: big5 Apr 20 14:07:58 2004 (3191) SHUNTING: 1080098916.48541+a5acb6484d8d579d298079c3ebc3d255953e217c Disabling digest doesn't seem to have any effect. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=936432&group_id=103 From noreply at sourceforge.net Wed Apr 21 13:13:06 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Apr 21 13:13:22 2004 Subject: [ mailman-Bugs-660733 ] pipermail date handling Message-ID: Bugs item #660733, was opened at 2003-01-01 09:29 Message generated for change (Comment added) made by cem You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=660733&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 7 Submitted By: Bryan Fullerton (fehwalker) Assigned to: Nobody/Anonymous (nobody) Summary: pipermail date handling Initial Comment: I moved my first list to mailman 2.1 and tried to re-generate the pipermail archives (just, ya know, to see how it'd work :), and got the following traceback. This is a list that's been around for a long time (archives back to 1995), and the .mbox file was generated from a majordomo/hypermail archive when it was moved to mailman 2.0 a couple of years ago. Here's a ls -l of the .mbox file: -rw-rw-r-- 1 mailman mailman 17741891 Jan 1 10:36 bryans-list.mbox Here's the traceback: Updating HTML for article 467 Updating HTML for article 468 Updating HTML for article 469 Updating HTML for article 473 Updating HTML for article 472 Pickling archive state into /home/mailman-2.1/archives/private/bryans-list/pipermail.pck Traceback (most recent call last): File "bin/arch", line 187, in ? main() File "bin/arch", line 175, in main archiver.processUnixMailbox(fp, start, end) File "/home/mailman-2.1/Mailman/Archiver/pipermail.py", line 544, in processUnixMailbox m = mbox.next() File "/usr/local/lib/python2.2/mailbox.py", line 34, in next return self.factory(_Subfile(self.fp, start, stop)) File "/home/mailman-2.1/Mailman/Mailbox.py", line 79, in scrubber return mailbox.scrub(msg) File "/home/mailman-2.1/Mailman/Mailbox.py", line 99, in scrub return self._scrubber(self._mlist, msg) File "/home/mailman-2.1/Mailman/Handlers/Scrubber.py", line 132, in process dir = calculate_attachments_dir(mlist, msg, msgdata) File "/home/mailman-2.1/Mailman/Handlers/Scrubber.py", line 93, in calculate_attachments_dir datedir = safe_strftime(fmt, now) File "/home/mailman-2.1/Mailman/Handlers/Scrubber.py", line 77, in safe_strftime return time.strftime(fmt, floatsecs) TypeError: argument must be 9-item sequence, not None I'm guessing it's a header problem in one of the messages, but I'm not sure what. Thanks, Bryan ---------------------------------------------------------------------- Comment By: Christine Moore (cem) Date: 2004-04-21 10:13 Message: Logged In: YES user_id=170050 Not being a python programmer I'm not sure how difficult it would be to do this. But would it be possible to code it so that it just uses the envelope date instead or maybe if it can't get validly formatted data for the date it uses currently it would use the envelope date? The majority of the email that the archives here are having this problem with have a valid envelope date on them. ---------------------------------------------------------------------- Comment By: Zoran Dzelajlija (followme) Date: 2003-12-31 07:31 Message: Logged In: YES user_id=106281 I can confirm this with 2.1.2. Is there a simple way to make arch guess dates better? I would settle for arch using the date of the previous message, but I don't know wher to start digging in the code. ---------------------------------------------------------------------- Comment By: Bryan Fullerton (fehwalker) Date: 2003-01-01 10:45 Message: Logged In: YES user_id=660772 After some investigation, the following (admittedly invalid) date headers cause tracebacks similar to the above. After reformatting them I'm able to generate the archive. Date: 25 Aug 95 18.00 Date: Thursday, 30 October 1997 3:02pm PT Date: Mon, 29 Nov 1999 Pacific Standard Time Note that these messages *didn't* cause bin/arch|pipermail in mailman 2.0.x to fail, though it probably didn't parse them properly. Perhaps trapping the error and/or skipping these messages might be more useful? It also appears that bin/arch is throwing all messages with dates it can't figure out (after the above were removed) into the current day. An example can be seen at http://lists.samurai.com/pipermail/bryans-list/2003-January/thread.html . I'm unsure if there's any way to better handle this, but just wanted to note it - I can create a separate bug report if it's important. Thanks, Bryan ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=660733&group_id=103 From noreply at sourceforge.net Thu Apr 22 11:32:47 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Apr 22 11:32:54 2004 Subject: [ mailman-Bugs-940106 ] Characters incorrectly replaced with HTML entities Message-ID: Bugs item #940106, was opened at 2004-04-22 17:32 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=940106&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Gunnar Hjalmarsson (gunnarh) Assigned to: Nobody/Anonymous (nobody) Summary: Characters incorrectly replaced with HTML entities Initial Comment: Version: 2.1.4 When customizing the listinfo page from the "General Options Section", characters such as '<' and '>' are replaced with HTML entities. Consequently they are displayed literally instead of as HTML, while they should be treated as HTML according to the documentation. Even if you can accomplish the desired changes by customizing listinfo.html directly instead, this is reasonably a bug that should be fixed. Regards, Gunnar Hjalmarsson ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=940106&group_id=103 From noreply at sourceforge.net Thu Apr 22 18:29:04 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Apr 22 18:29:09 2004 Subject: [ mailman-Bugs-940386 ] Mail with no Subject line causes DOS Message-ID: Bugs item #940386, was opened at 2004-04-22 18: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=940386&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Kevin Myer (kevin_myer) Assigned to: Nobody/Anonymous (nobody) Summary: Mail with no Subject line causes DOS Initial Comment: One of the fixes for 2.0.14 included some patches to the way Mailman/MailCommandHandler.py handles the subject line. After applying this patch to 2.0.13, I found that if a message is sent to a list that contains no Subject: line in the header, all processing of messages stops. Once I clear out that particular message, the queue processing starts again. Note: Its not a blank Subject: line thats causing this problem - its a message without a Subject: line at all. Maybe its coincidental and not related to the patch I applied for 2.0.14 but the timing it too close to be not related somehow. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=940386&group_id=103 From noreply at sourceforge.net Fri Apr 23 00:47:51 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Apr 23 00:47:55 2004 Subject: [ mailman-Bugs-940497 ] substitute poster's address but keep name Message-ID: Bugs item #940497, was opened at 2004-04-23 04:47 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=940497&group_id=103 Category: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Pierre Abbat (phma) Assigned to: Nobody/Anonymous (nobody) Summary: substitute poster's address but keep name Initial Comment: I was on a list that uses the feature in which the poster's From: header is replaced with the list address to prevent spammers from harvesting addresses. Unfortunately, this makes it impossible, in the second pane of my mail client, to see who said what. I suggest substituting only the address, leaving the name intact. For example: From: Ellie Vator To: foo@bar.baz should become From: Ellie Vator To: foo@bar.baz and From: l.e.vator@otis.com (Ellie Vator) should become From: foo@bar.baz (Ellie Vator) . ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=940497&group_id=103 From noreply at sourceforge.net Sat Apr 24 20:19:18 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sat Apr 24 22:02:04 2004 Subject: [ mailman-Patches-810675 ] Add 'Discard all messages marked "Defer"' option t Message-ID: Patches item #810675, was opened at 2003-09-22 11:44 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=810675&group_id=103 Category: Web UI Group: Mailman 2.1 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Eddie Kohler (xexd) Assigned to: Nobody/Anonymous (nobody) >Summary: Add 'Discard all messages marked "Defer"' option t Initial Comment: Hi, This slight change to the admindb page is useful for filtering spam from a mailing list. Instead of individually clicking "Discard" on every spam message (timeconsuming), you go through the messages, mark only the Accepts and Rejects, then check the 'Discard all messages marked "Defer"' box. This speeds up my mailing list processing significantly. Eddie ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2004-04-24 20:19 Message: Logged In: YES user_id=12800 Thanks, I've added this for Mailman 2.1.5. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=810675&group_id=103 From noreply at sourceforge.net Sun Apr 25 00:13:40 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Apr 25 00:13:48 2004 Subject: [ mailman-Bugs-707610 ] Uncaught runner exception: Empty module name Message-ID: Bugs item #707610, was opened at 2003-03-21 11:55 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=707610&group_id=103 Category: None >Group: 2.1 (stable) >Status: Closed >Resolution: Duplicate Priority: 5 Submitted By: Jan Kellermann (werk21) Assigned to: Nobody/Anonymous (nobody) Summary: Uncaught runner exception: Empty module name Initial Comment: mailman is shunting a lot of mails with this message in error-log, my language-version is german. i work with the current cvs-version Mar 21 16:11:21 2003 (12591) Uncaught runner exception: Empty module name Mar 21 16:11:21 2003 (12591) Traceback (most recent call last): File "/usr/local/mailman- 2.1//Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman- 2.1//Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman- 2.1//Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman- 2.1//Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman- 2.1//Mailman/Handlers/ToDigest.py", line 82, in process send_digests(mlist, mboxfp) File "/usr/local/mailman- 2.1//Mailman/Handlers/ToDigest.py", line 123, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman- 2.1//Mailman/Handlers/ToDigest.py", line 295, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman- 2.1//Mailman/Handlers/Scrubber.py", line 308, in process t = t.encode(charset, 'replace') File "/usr/lib/python2.2/encodings/__init__.py", line 51, in search_function mod = __import__(modname,globals(),locals(),'*') ValueError: Empty module name Mar 21 16:11:21 2003 (12591) SHUNTING: 1048241610.7517231+289483353c3e3632ab0892d8ceb 8c936f107bc5e ---------------------------------------------------------------------- Comment By: Jochen Witte (zebaoth) Date: 2004-04-18 08:26 Message: Logged In: YES user_id=565663 See Bug 871050 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=707610&group_id=103 From noreply at sourceforge.net Mon Apr 26 12:53:51 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 26 12:54:18 2004 Subject: [ mailman-Bugs-803729 ] LookupError: unknown encoding: X-UNKNOWN Message-ID: Bugs item #803729, was opened at 2003-09-10 13:31 Message generated for change (Comment added) made by maiergre You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=803729&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ervin N?meth (nemethe) Assigned to: Nobody/Anonymous (nobody) Summary: LookupError: unknown encoding: X-UNKNOWN Initial Comment: Our site encounters the following problem. mailman-2.1.2 installed from OpenBSD ports. Traceback (most recent call last): File "/usr/local/mailman/cron/senddigests", line 94, in ? main() File "/usr/local/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/usr/local/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 257, in process url = save_attachment(mlist, part, dir) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 348, in save_attachment fnext = os.path.splitext(msg.get_filename(''))[1] File "/usr/local/mailman/pythonlib/email/Message.py", line 707, in get_filename return unicode(newvalue[2], newvalue[0]) LookupError: unknown encoding: X-UNKNOWN ---------------------------------------------------------------------- Comment By: Gregor Maier (maiergre) Date: 2004-04-26 16:53 Message: Logged In: YES user_id=38025 Hello, I have the same problem with mailmain-2.1.4 with python-2.3.3 under linux gentoo. Are there any clues where the problem lies or any workarounds? Disableing the digest option works but is not really a solution. Another interesting fact is, that the only some lists show this problem and that the prolbem just "occurs" and then it doesn't go away.. Here's a part of my error log: Apr 26 18:27:05 2004 (17449) Uncaught runner exception: unknown encoding: X-UNKNOWN Apr 26 18:27:05 2004 (17449) 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/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 91, in process send_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 132, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 306, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 265, in process url = save_attachment(mlist, part, dir) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 361, in save_attachment fnext = os.path.splitext(msg.get_filename(''))[1] File "/usr/local/mailman/pythonlib/email/Message.py", line 714, in get_filename return unicode(newvalue[2], newvalue[0] or 'us-ascii') LookupError: unknown encoding: X-UNKNOWN Apr 26 18:27:05 2004 (17449) SHUNTING: 1082996756.746207+e85fdb8b141ccd2a8f0757824f62fbff58 da2ce4 ---------------------------------------------------------------------- Comment By: Ervin N?meth (nemethe) Date: 2003-10-08 12:23 Message: Logged In: YES user_id=768522 It's quite unpleasant to recieve this mail daily. In addition there was a local mailing list to which no mail was delivered until digests to this list was turned off. Last day I have upgraded to mailman 2.1.3 and the last lines of the traceback changed: File "/usr/local/mailman/pythonlib/email/Message.py", line 714, in get_filename return unicode(newvalue[2], newvalue[0] or 'us-ascii') LookupError: unknown encoding: X-UNKNOWN ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=803729&group_id=103 From noreply at sourceforge.net Mon Apr 26 14:03:28 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Mon Apr 26 14:03:59 2004 Subject: [ mailman-Bugs-803729 ] LookupError: unknown encoding: X-UNKNOWN Message-ID: Bugs item #803729, was opened at 2003-09-10 15:31 Message generated for change (Comment added) made by nemethe You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=803729&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ervin N?meth (nemethe) Assigned to: Nobody/Anonymous (nobody) Summary: LookupError: unknown encoding: X-UNKNOWN Initial Comment: Our site encounters the following problem. mailman-2.1.2 installed from OpenBSD ports. Traceback (most recent call last): File "/usr/local/mailman/cron/senddigests", line 94, in ? main() File "/usr/local/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/usr/local/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 257, in process url = save_attachment(mlist, part, dir) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 348, in save_attachment fnext = os.path.splitext(msg.get_filename(''))[1] File "/usr/local/mailman/pythonlib/email/Message.py", line 707, in get_filename return unicode(newvalue[2], newvalue[0]) LookupError: unknown encoding: X-UNKNOWN ---------------------------------------------------------------------- >Comment By: Ervin N?meth (nemethe) Date: 2004-04-26 20:03 Message: Logged In: YES user_id=768522 As far as I recognised mailman copies Message.py from the python libraries so I also reported it for python (id 854102). As a workaround replace the line in question: return unicode(newvalue[2], newvalue[0] or 'us-ascii') with try: return unicode(newvalue[2], newvalue[0] or 'us-ascii') except LookupError: return unicode(newvalue[2], 'us-ascii', 'replace') ---------------------------------------------------------------------- Comment By: Gregor Maier (maiergre) Date: 2004-04-26 18:53 Message: Logged In: YES user_id=38025 Hello, I have the same problem with mailmain-2.1.4 with python-2.3.3 under linux gentoo. Are there any clues where the problem lies or any workarounds? Disableing the digest option works but is not really a solution. Another interesting fact is, that the only some lists show this problem and that the prolbem just "occurs" and then it doesn't go away.. Here's a part of my error log: Apr 26 18:27:05 2004 (17449) Uncaught runner exception: unknown encoding: X-UNKNOWN Apr 26 18:27:05 2004 (17449) 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/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 91, in process send_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 132, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 306, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 265, in process url = save_attachment(mlist, part, dir) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 361, in save_attachment fnext = os.path.splitext(msg.get_filename(''))[1] File "/usr/local/mailman/pythonlib/email/Message.py", line 714, in get_filename return unicode(newvalue[2], newvalue[0] or 'us-ascii') LookupError: unknown encoding: X-UNKNOWN Apr 26 18:27:05 2004 (17449) SHUNTING: 1082996756.746207+e85fdb8b141ccd2a8f0757824f62fbff58 da2ce4 ---------------------------------------------------------------------- Comment By: Ervin N?meth (nemethe) Date: 2003-10-08 14:23 Message: Logged In: YES user_id=768522 It's quite unpleasant to recieve this mail daily. In addition there was a local mailing list to which no mail was delivered until digests to this list was turned off. Last day I have upgraded to mailman 2.1.3 and the last lines of the traceback changed: File "/usr/local/mailman/pythonlib/email/Message.py", line 714, in get_filename return unicode(newvalue[2], newvalue[0] or 'us-ascii') LookupError: unknown encoding: X-UNKNOWN ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=803729&group_id=103 From noreply at sourceforge.net Wed Apr 28 12:51:47 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Apr 28 12:52:14 2004 Subject: [ mailman-Patches-699199 ] French translation of "cancel" has reverse meaning Message-ID: Patches item #699199, was opened at 2003-03-06 23:54 Message generated for change (Comment added) made by anarcat You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=699199&group_id=103 Category: internationalization Group: Mailman 2.1 >Status: Closed Resolution: Works For Me Priority: 5 Submitted By: The Anarcat (anarcat) Assigned to: Ousmane Wilane (wilane) Summary: French translation of "cancel" has reverse meaning Initial Comment: When confirming a subscribe request via the web, the user is presented with two buttons: - "Cancel my subscription request" - "Subscribe to list %(listname)s" The unfortunate thing is that this is translated as: - "Annuler la requ?te d'abonnement" - "Abonnement ? la liste: %(listname)s" which translates to: - "Confirm my subscription request" - "Subscribtion to list %(listname)s" The correct translation is outlined in the patch. I took the liberty of also removing the extra ":" that was lying there. It is not in the english version, and I don't see how it should be in the french one. ---------------------------------------------------------------------- >Comment By: The Anarcat (anarcat) Date: 2004-04-28 12:51 Message: Logged In: YES user_id=246797 I think this is ok in mailman right now. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-10 10:23 Message: Logged In: YES user_id=34209 Assigning to wilane, who (at least partially) does the French translations. ---------------------------------------------------------------------- Comment By: The Anarcat (anarcat) Date: 2003-03-10 10:07 Message: Logged In: YES user_id=246797 Man, what a bad patch report. :( This bug report should have read: When confirming a subscribe request via the web, the user is presented with two buttons: - "Cancel my subscription request" - "Subscribe to list %(listname)s" The unfortunate thing is that this is translated as: - "Confirmer la requ?te d'abonnement" - "Abonnement ? la liste: %(listname)s" which translates to: - "Confirm my subscription request" - "Subscribtion to list %(listname)s" If you look closer in the actual .po file, it is indeed written "confirmer" where it should be "annuler". I have attached the patch which should take care of all this. Sorry for the confusion. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-10 08:35 Message: Logged In: YES user_id=34209 There is no patch attached, and (though my french isn't what it used to be) I don't see how "Annuler la requ?te d'abonnement" reads as 'confirm my submission request'. Please contact the french translation team directly, if you still think this needs fixing: http://listes.rezo.net/mailman/listinfo/mailman-fr ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=699199&group_id=103 From noreply at sourceforge.net Wed Apr 28 12:57:27 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Wed Apr 28 12:57:33 2004 Subject: [ mailman-Patches-943827 ] true virtual hosting patch for 2.1 Message-ID: Patches item #943827, was opened at 2004-04-28 12: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=943827&group_id=103 Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: The Anarcat (anarcat) Assigned to: Nobody/Anonymous (nobody) Summary: true virtual hosting patch for 2.1 Initial Comment: [copy of the mail sent to -developpers@] We developped a reliable solution for running lists with the same name on different domains on the same Mailman installation. I implemented that on top of the Mailman 2.1.1-5.1 Debian stable package. All that is needed is to patch 2 files (bin/newlist, Mailman/MailList.py) in the mailman install, and here is the patch: http://bugs.koumbit.net/file_download.php?file_id=3&type=bug There's only one caveat right now: Mailman/Cgi/create.py might need to get patched too, but I haven't got around looking at it yet, and it "just works", for now. I don't know what's the current status of virtual hosting support on Mailman, but this patch is a simple hack that should bring joy in the homes of all Mailman admins around the world. :) I got my inspiration and part of the code from: http://mithrandr.moria.org/blog/139.html All it does is to add the domain to the internal_name() of a list. The real_name is kept as is, and the getListAddress() does the Right Thing. This makes Mailman generate aliases like: list-example.com: "|/var/lib/mailman/mail/mailman post list-example.com" Care will have to be taken on the MTA side to map those list-example.com to list@example.com. We are using alternc.org to manage our server, so we are using LDAP, so everything went pretty smoothly. :) But I guess it will require some magic on the Postfix side or something... Cheers, A. PS: for those wanting to see more, you can come to our Wiki: http://koumbit.net/wiki/VirtualMailman You'll probably have a little trouble finding your way if you don't read french though. :) Babelfish might help, haven't tried. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=943827&group_id=103 From noreply at sourceforge.net Thu Apr 29 01:49:35 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Apr 29 01:49:46 2004 Subject: [ mailman-Bugs-229568 ] Pipermail won't resolve author names of aol.com addresses Message-ID: Bugs item #229568, was opened at 2001-01-21 14:53 Message generated for change (Comment added) made by cajela You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=229568&group_id=103 Category: Pipermail Group: 2.1 beta Status: Closed Resolution: Out of Date Priority: 7 Submitted By: Aharon Varady (aharon) Assigned to: Nobody/Anonymous (nobody) Summary: Pipermail won't resolve author names of aol.com addresses Initial Comment: Pipermail does not resolve the "author" of emails sent from aol.com. Instead, Pipermail gives the email address of the listserve. For example: "John" is resolved by pipermail as: listname@foo.com and not as John. This bug only occurs for users of aol.com addresses. ---------------------------------------------------------------------- Comment By: Cath Lawrence (cajela) Date: 2004-04-29 15:49 Message: Logged In: YES user_id=1031650 Of course, it is NOT only for aol.com. I can confirm the same problem with a firstname.lastname@csiro.au address format. ---------------------------------------------------------------------- Comment By: Terri Oda (spot) Date: 2002-07-03 06:00 Message: Logged In: YES user_id=110886 Whoops. Diffed the wrong thing. That's what happens when I try to patch code but haven't slept in a few days. This actually works better: 180c180 < if e is not None: --- > if e is not None and self.email == "": ---------------------------------------------------------------------- Comment By: Terri Oda (spot) Date: 2002-07-02 04:03 Message: Logged In: YES user_id=110886 The problem is that it defaults to using the reply-to address if it's set, and this isn't what we want when the reply-to is always being set by the list. Take a careful look at the rest of your archives and you'll probably note that *everyone's* email address is showing up as listname@foo.com. It's a nice anti-spam feature, perhaps, but probably not what you want. Here's a quick fix for pipermail.py: 180c180 < if e is not None: --- > if e is not None and self.email is None: This just changes it so that it defaults to the From: address (when it's set) rather than the Reply-to address. If there's some particular reason to take the Reply-To over the From, I can make something which actually checks to see if the reply-to is being set by the list, but this should solve your problem for the moment. Terri ---------------------------------------------------------------------- Comment By: Ava Jarvis (katanalynx) Date: 2002-06-11 12:14 Message: Logged In: YES user_id=561110 This bug -- for version 2.0.11 at least -- seems to occur when 'from' only contains the email address. There's some code in pipermail.py (version 2.0.11), line 177: # Figure out the e-mail address and poster's name self.author, self.email = message.getaddr('From') e = message.getheader('Reply-To') if e is not None: self.email = e self.email = strip_separators(self.email) self.author = strip_separators(self.author) if self.author == "": self.author = self.email If reply-to is set, then it is always taken as the author's email address. However, some lists set the reply-to field to be, for instance, the list address.... and you can guess what happens next when there is no name comment/author. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-06-07 02:09 Message: Logged In: NO This comment doesn't directly address the case you report, but it might be related so I thought it worthwhile to submit. I see you are using MM2.0.9. I saw a similar problem with MM2.1b1, which was fixed in MM2.1b2. The problem then was that an address with a name "comment" would be displayed in the archive as the list name, whereas an address with a name comment would be displayed (properly) with the name. Example: "John Doe" jdoe@whereever.com displayed as "John Doe" whereas jdoe@whereever.com displayed as the list name. In your comment, you use an example with a name comment of "John", but in the example you provided there is no name comment field, so perhaps my statements here do apply. ---------------------------------------------------------------------- Comment By: Aharon Varady (aharon) Date: 2002-06-06 11:37 Message: Logged In: YES user_id=139355 Well, this remains (and has always been) a problem for my lists. I have never had a user posting with an aol.com address that this hasn't been the case with. Currently my solution is to replace the wrong address shown (philly_ambient@phobos.serve.com) with a generic or balnk mark. Here is the html source of a typical email from our pipermail archive, and below it the source email with headers. ------------------------------------------------------------- [Philly_ambient] tool!

    [Philly_ambient] tool!

    Posted by . . . .. . . . on Mon Jun 3 23:17:02 2002 

    hey all
a friend can get me some free tickets to see TOOL on monday
august 12 at 
sovereign bank arena in trenton. i know mondays suck, but oh
well. is anyone 
here into going?  if so, contact me privately.  i know it's
not ambient, but 
neither is some of what we discuss here :)
let me know asap, please

gina

  • Previous message: [Philly_ambient] Noise Deafinitions and playlist
  • Next message: [Philly_ambient] Do you hear what I hear? (re: noise deaf)
  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
    • --------------------------------------------------------------------- Here is the original email with headers: --------------------------------------------------------------- >From - Tue Jun 04 01:16:56 2002 X-UIDL: m;n!!9'f!!a2E"!3;D"! X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Return-Path: Delivered-To: aharon@phobos.serve.com Received: from phobos.serve.com (localhost.localdomain [127.0.0.1]) by phobos.serve.com (Postfix) with ESMTP id 6BC4D52D2B; Mon, 3 Jun 2002 23:17:06 -0400 (EDT) Delivered-To: philly_ambient@phobos.serve.com Received: from imo-r06.mx.aol.com (imo-r06.mx.aol.com [152.163.225.102]) by phobos.serve.com (Postfix) with ESMTP id 6F82F52D1D for ; Mon, 3 Jun 2002 23:16:46 -0400 (EDT) Received: from Mistsojorn@aol.com by imo-r06.mx.aol.com (mail_out_v32.5.) id p.d4.184e63f9 (17378) for ; Mon, 3 Jun 2002 23:14:35 -0400 (EDT) From: Mistsojorn@aol.com Message-ID: To: philly_ambient@phobos.serve.com MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 4.0 for Mac - Post-GM sub 66 Subject: [Philly_ambient] tool! Sender: philly_ambient-admin@phobos.serve.com Errors-To: philly_ambient-admin@phobos.serve.com X-BeenThere: philly_ambient@phobos.serve.com X-Mailman-Version: 2.0.9 Precedence: bulk Reply-To: philly_ambient@phobos.serve.com List-Help: List-Post: List-Subscribe: , List-Id: a discussion list relevant to Philadelphia Ambient and Experimental Psychedelic Music Enthusiasts List-Unsubscribe: , List-Archive: X-Original-Date: Mon, 3 Jun 2002 23:14:35 EDT Date: Mon, 3 Jun 2002 23:14:35 EDT X-UIDL: m;n!!9'f!!a2E"!3;D"! hey all a friend can get me some free tickets to see TOOL on monday august 12 at sovereign bank arena in trenton. i know mondays suck, but oh well. is anyone here into going? if so, contact me privately. i know it's not ambient, but neither is some of what we discuss here :) let me know asap, please gina _______________________________________________ Philly_ambient mailing list Philly_ambient@phobos.serve.com Subscribe, Unsubscribe, Edit Options at: http://phobos.serve.com/mailman/listinfo/philly_ambient a PAC(MaN) List http://simpletone.com -------------------------------------------------------------------- I don't know why pipermail would treat my aol subscribers different either. But it is. Aharon ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-04-29 11:11 Message: Logged In: YES user_id=12800 Bizarre. I've never seen this, and I can't see any reason why Pipermail would treat aol.com addresses any different. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=229568&group_id=103 From noreply at sourceforge.net Thu Apr 29 10:59:23 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Apr 29 10:59:42 2004 Subject: [ mailman-Bugs-931861 ] MemoryError when running senddigests Message-ID: Bugs item #931861, was opened at 2004-04-08 17:19 Message generated for change (Comment added) made by steffen_mhl You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=931861&group_id=103 Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Patrick Finnerty (finnertyp) Assigned to: Nobody/Anonymous (nobody) Summary: MemoryError when running senddigests Initial Comment: Using Mailman v2.1.4 & Python v2.3.3. OS = TRU64 5.1a Problem only occurs on one mailing list: /usr/local/bin/python -S /usr/local/mailman/cron/senddigests -l shc.nt Traceback (most recent call last): File "/usr/local/mailman/cron/senddigests", line 94, in ? main() File "/usr/local/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/usr/local/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 132, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 306, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 304, in process t = part.get_payload(decode=True) File "/usr/local/mailman/pythonlib/email/Message.py", line 197, in get_payload return Utils._qdecode(payload) File "/usr/local/lib/python2.3/quopri.py", line 161, in decodestring return a2b_qp(s, header = header) MemoryError ---------------------------------------------------------------------- Comment By: Steffen Muehlnickel (steffen_mhl) Date: 2004-04-29 14:59 Message: Logged In: YES user_id=1031993 Can confirm. I got the same error message (under Tru64 5.1b, mailman 2.1.2) disabling digest helped. ---------------------------------------------------------------------- Comment By: Michael Newlyn Blake (zakureth) Date: 2004-04-20 21:30 Message: Logged In: YES user_id=111909 I to am having this problem on an up to date Suse 9.0 system with Mailman 2.1.2. Messages I'm getting in the error log are: Apr 20 14:14:51 2004 (7447) uncaught archiver exception at filepos: 0 Apr 20 14:14:51 2004 (7447) Uncaught runner exception: Empty module name Apr 20 14:14:51 2004 (7447) Traceback (most recent call last): File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/ArchRunner.py", line 73, in _dispose mlist.ArchiveMail(msg) File "/usr/lib/mailman/Mailman/Archiver/Archiver.py", line 206, in ArchiveMail h.processUnixMailbox(f) File "/usr/lib/mailman/Mailman/Archiver/pipermail.py", line 544, in processUnixMailbox m = mbox.next() File "/usr/lib/python2.3/mailbox.py", line 35, in next return self.factory(_Subfile(self.fp, start, stop)) File "/usr/lib/mailman/Mailman/Mailbox.py", line 89, in scrubber return mailbox.scrub(msg) File "/usr/lib/mailman/Mailman/Mailbox.py", line 109, in scrub return self._scrubber(self._mlist, msg) File "/usr/lib/mailman/Mailman/Handlers/Scrubber.py", line 308, in process t = t.encode(charset, 'replace') File "/usr/lib/python2.3/encodings/__init__.py", line 84, in search_function globals(), locals(), _import_tail) ValueError: Empty module name Apr 20 14:14:51 2004 (7447) SHUNTING: 1082469143.1593151+1674b479f52223bba07f4eda7f29b743c99ae34f And an occasional: Apr 20 14:07:58 2004 (3191) Uncaught runner exception: unknown encoding: big5 Apr 20 14:07:58 2004 (3191) Traceback (most recent call last): File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/CommandRunner.py", line 218, in _dispose res = Results(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/CommandRunner.py", line 75, in __init__ subj = make_header(decode_header(subj)).__unicode__() File "/usr/lib/mailman/pythonlib/email/Header.py", line 144, in make_header h.append(s, charset) File "/usr/lib/mailman/pythonlib/email/Header.py", line 272, in append ustr = unicode(s, incodec, errors) LookupError: unknown encoding: big5 Apr 20 14:07:58 2004 (3191) SHUNTING: 1080098916.48541+a5acb6484d8d579d298079c3ebc3d255953e217c Disabling digest doesn't seem to have any effect. ---------------------------------------------------------------------- Comment By: Patrick Finnerty (finnertyp) Date: 2004-04-15 10:29 Message: Logged In: YES user_id=594846 The list in question is also shunting all posts. Disabling the Digest option allowed posts to come through again and also allowed the posts in te queue to be unshunted. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=931861&group_id=103 From noreply at sourceforge.net Thu Apr 29 18:18:39 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Apr 29 18:18:44 2004 Subject: [ mailman-Bugs-944927 ] Non-Ascii character in e-mail address causes traceback Message-ID: Bugs item #944927, was opened at 2004-04-29 22:18 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=944927&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Joseph Tate (jtate) Assigned to: Nobody/Anonymous (nobody) Summary: Non-Ascii character in e-mail address causes traceback Initial Comment: I fixed the problem without saving a trackback, but if a non-ascii character (>127) somehow makes it into the subscribers list, the admin/members page will not display, and will show a python error on line 870 of Mailman/Cgi/Admin.py. The error says something like not in range(128). Thus user management must be done via command line utility. No error occurs when using list_members. Either no non-ascii character should be allowed in e-mail addresses, or this error should be worked around. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=944927&group_id=103 From noreply at sourceforge.net Fri Apr 30 10:50:32 2004 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Apr 30 10:50:55 2004 Subject: [ mailman-Bugs-945346 ] "Subscription-forwarded" Mail is sent to the wrong address Message-ID: Bugs item #945346, was opened at 2004-04-30 16:50 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=945346&group_id=103 Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Michael Bussmann (bus) Assigned to: Nobody/Anonymous (nobody) Summary: "Subscription-forwarded" Mail is sent to the wrong address Initial Comment: Hi there, I'm not sure whether this is a bug, non-standard behaviour or simply the right way, but I noticed the following: Mail address A sends out an subscription-request to a list (subscribe policy: approval) with the command subscribe address=B. The message "Your subscription request has been forwarded to the list admin" is sent to address A instead of B. The confirmation mail (if the admin approves the request) is sent to address B. >From my point of view even the first piece of email should be sent to address B, but if you think the current behaviour is ok, feel free to trash this report. Cheers, Michael ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=945346&group_id=103