Mailman-coders April 2004

mailman-coders@python.org

1 participants
57 discussions

[ mailman-Patches-810675 ] Add 'Discard all messages marked "Defer"' option t
by SourceForge.net 25 Apr '04

25 Apr '04

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_i… 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_i…

1 0

[ mailman-Bugs-940497 ] substitute poster's address but keep name
by SourceForge.net 23 Apr '04

23 Apr '04

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_i… 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 <l.e.vator(a)otis.com> To: foo(a)bar.baz should become From: Ellie Vator <foo(a)bar.baz> To: foo(a)bar.baz and From: l.e.vator(a)otis.com (Ellie Vator) should become From: foo(a)bar.baz (Ellie Vator) . ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=940497&group_i…

1 0

[ mailman-Bugs-940386 ] Mail with no Subject line causes DOS
by SourceForge.net 23 Apr '04

23 Apr '04

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_i… 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_i…

1 0

[ mailman-Bugs-940106 ] Characters incorrectly replaced with HTML entities
by SourceForge.net 22 Apr '04

22 Apr '04

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_i… 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_i…

1 0

[ mailman-Bugs-660733 ] pipermail date handling
by SourceForge.net 21 Apr '04

21 Apr '04

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_i… 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_i…

1 0

[ mailman-Bugs-936432 ] python name generators?
by SourceForge.net 20 Apr '04

20 Apr '04

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_i… 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_i…

1 0

[ mailman-Bugs-931861 ] MemoryError when running senddigests
by SourceForge.net 20 Apr '04

20 Apr '04

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_i… 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_i…

1 0

[ mailman-Bugs-936432 ] python name generators?
by SourceForge.net 20 Apr '04

20 Apr '04

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_i… 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_i…

1 0

[ mailman-Patches-850805 ] Aggressive anti email address harvesting measure
by SourceForge.net 20 Apr '04

20 Apr '04

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_i… 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_i…

1 0

[ mailman-Patches-938301 ] Fix for bug 740457
by SourceForge.net 20 Apr '04

20 Apr '04

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_i… 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_i…

1 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

Mailman-coders April 2004