Mailman 3 May 2008 - Mailman-coders

[ mailman-Patches-657951 ] Generate RSS summary in archives
by SourceForge.net Aug. 19, 2022

Aug. 19, 2022

Patches item #657951, was opened at 2002-12-23 14:17 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_i… Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 7 Submitted By: A.M. Kuchling (akuchling) Assigned to: Nobody/Anonymous (nobody) Summary: Generate RSS summary in archives Initial Comment: Here's a first-draft patch. Things that need fixing: * The generated RSS feed needs to be validated. (It passed the W3C's RDF validator, but RSS validators still need to be checked.) * The date should be given in YYYY-MM-DD format, which requires parsing the .fromdate attribute. * How do I get the URL for an archived message? The generated RSS currently just uses the filename, which is wrong. How do I get at the PUBLIC_ARCHIVE_URL setting? * Getting the most recent N postings is inefficient; the code loops through all of the archived messages and takes the last N of them. We could add .last() and .prev() methods to the Database class, but that's more ambitious for 2.1beta than I like. (Would be nice to get this into 2.1final...) * The list index page should have a LINK element pointing to the RSS file. Please make any comments you have, and I'll rework the patch accordingly. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-18 18:43 Message: Logged In: YES user_id=12800 Andrew, to get the url for the archived message use mlist.GetBaseArchiveURL(), which knows about private vs. public archives, the host name and the list name. From there you should be able to tack on just the part of the path under "archives/private/listname". See Mailman/Handlers/Scrubber.py for an example. Only other minor comment: NUM_ARTICLES can probably go in Defaults.py.in ---------------------------------------------------------------------- Comment By: Justin Mason (jmason) Date: 2003-03-26 16:49 Message: Logged In: YES user_id=935 big thumbs up from me too. Much better solution than http://taint.org/mmrss/ ;) ---------------------------------------------------------------------- Comment By: Uche Ogbuji (uche) Date: 2003-03-17 20:09 Message: Logged In: YES user_id=38966 I'd like to add my vote to this item. This is a fantastic idea, Andrew. Thanks. --Uche ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 15:42 Message: Logged In: YES user_id=11375 Updated patch: * Dates are now rendered as ISO-8601 (date only, not the time of the message) * By hard-wiring 2002-December, I got the RSS to validate using Mark Pilgrim's validator. ---------------------------------------------------------------------- Comment By: captain larry (captainlarry) Date: 2002-12-23 14:36 Message: Logged In: YES user_id=147905 Just voting for support here. This is *great* thanks for the patch and I hope the maintainers include it as soon as it's appropriate :) Adam. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-23 14:27 Message: Logged In: YES user_id=12800 Deferring until post-2.1 ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 14:21 Message: Logged In: YES user_id=11375 Argh; SF choked on the file upload. Attaching the patch again... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_i…

2 1

[ mailman-Patches-1968679 ] Add more options for subject_prefix
by SourceForge.net May 27, 2008

May 27, 2008

Patches item #1968679, was opened at 2008-05-21 14:39 Message generated for change (Comment added) made by tinheap You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1968679&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: Mailman 2.1 Status: Open Resolution: None Priority: 1 Private: No Submitted By: Benjamin Meyer (tinheap) Assigned to: Nobody/Anonymous (nobody) Summary: Add more options for subject_prefix Initial Comment: This patch was created out of our need to add these to the prefix. I just wanted to share it with the rest of you in the case it is usefull. With patch applyed to CookHeaders.py one can add %D, %M and/or %Y to the prefix, which will be replaced by the current day, month and/or year. ---------------------------------------------------------------------- >Comment By: Benjamin Meyer (tinheap) Date: 2008-05-27 12:22 Message: Logged In: YES user_id=646585 Originator: YES File Added: CookHeaders.py.patch ---------------------------------------------------------------------- Comment By: Benjamin Meyer (tinheap) Date: 2008-05-26 16:23 Message: Logged In: YES user_id=646585 Originator: YES Ok. I goofed that one a bit. There are some issues to be resolved, which were pointed out by a coworker of mine. Sorry for the inconvenience. I'll post an updated patch file, as soon as I have one. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1968679&group_…

1 0

[ mailman-Patches-1968679 ] Add more options for subject_prefix
by SourceForge.net May 26, 2008

May 26, 2008

Patches item #1968679, was opened at 2008-05-21 14:39 Message generated for change (Comment added) made by tinheap You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1968679&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: Mailman 2.1 Status: Open Resolution: None >Priority: 1 Private: No Submitted By: Benjamin Meyer (tinheap) Assigned to: Nobody/Anonymous (nobody) Summary: Add more options for subject_prefix Initial Comment: This patch was created out of our need to add these to the prefix. I just wanted to share it with the rest of you in the case it is usefull. With patch applyed to CookHeaders.py one can add %D, %M and/or %Y to the prefix, which will be replaced by the current day, month and/or year. ---------------------------------------------------------------------- >Comment By: Benjamin Meyer (tinheap) Date: 2008-05-26 16:23 Message: Logged In: YES user_id=646585 Originator: YES Ok. I goofed that one a bit. There are some issues to be resolved, which were pointed out by a coworker of mine. Sorry for the inconvenience. I'll post an updated patch file, as soon as I have one. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1968679&group_…

1 0

[ mailman-Patches-1968679 ] Add more options for subject_prefix
by SourceForge.net May 21, 2008

May 21, 2008

Patches item #1968679, was opened at 2008-05-21 14:39 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1968679&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Benjamin Meyer (tinheap) Assigned to: Nobody/Anonymous (nobody) Summary: Add more options for subject_prefix Initial Comment: This patch was created out of our need to add these to the prefix. I just wanted to share it with the rest of you in the case it is usefull. With patch applyed to CookHeaders.py one can add %D, %M and/or %Y to the prefix, which will be replaced by the current day, month and/or year. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1968679&group_…

1 0

[ mailman-Bugs-1966837 ] Subscribing via e-mail fails.
by SourceForge.net May 19, 2008

May 19, 2008

Bugs item #1966837, was opened at 2008-05-19 10:09 Message generated for change (Comment added) made by berndts You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1966837&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: Fixed Priority: 5 Private: No Submitted By: Stephan Berndts (berndts) Assigned to: Nobody/Anonymous (nobody) Summary: Subscribing via e-mail fails. Initial Comment: Hi, when I try to subscribe to a mailing list by sending an e-mail to listname-join@listserver this fails with the following error: May 13 13:08:54 2008 (14270) Uncaught runner exception: 'NoneType' object has no attribute 'lower' May 13 13:08:54 2008 (14270) Traceback (most recent call last): File "/srv/mailman/Mailman/Queue/Runner.py", line 114, in _oneloop self._onefile(msg, msgdata) File "/srv/mailman/Mailman/Queue/Runner.py", line 185, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/srv/mailman/Mailman/Queue/CommandRunner.py", line 241, in _dispose res.do_command('join') File "/srv/mailman/Mailman/Queue/CommandRunner.py", line 139, in do_command return handler.process(self, args) File "/srv/mailman/Mailman/Commands/cmd_subscribe.py", line 74, in process if digest is None and password.lower() in ('digest', 'nodigest'): AttributeError: 'NoneType' object has no attribute 'lower' May 13 13:08:54 2008 (14270) SHUNTING: 1210676933.788779+8f3f3d5d13ba53d21c00b3731faff2259213e4bf M The error arises as cmd_subscribe.py assumes that the variable "password" is not empty (at line 74) which is not true if neither a password nor an option in {digest,nodigest} was passed as a command-line argument. A patch resolving the error is attached. ---------------------------------------------------------------------- >Comment By: Stephan Berndts (berndts) Date: 2008-05-19 21:51 Message: Logged In: YES user_id=129854 Originator: YES Oops. I actually read it on mailman-announce but forgot about it when I discovered the bug. But: I browsed through the bug tracker and could not find the bug there. Maybe you should open a bug even for bugs you already fixed (and close them instantly). ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2008-05-19 17:37 Message: Logged In: YES user_id=1123998 Originator: NO Thanks for the patch. This is a known issue. See the news item "Important patch for Mailman 2.1.10 2008-04-26" on the project page at <http://sourceforge.net/projects/mailman> and the Mailman_2.1.10.patch file on the download page at <http://sourceforge.net/project/showfiles.php?group_id=103>. Also see <http://mail.python.org/pipermail/mailman-announce/2008-April/000111.html> which was also posted to mailman-developers(a)python.org and mailman-users(a)python.org. Do you have any suggestions as to how the make things like this more visible? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1966837&group_…

1 0

[ mailman-Bugs-1966837 ] Subscribing via e-mail fails.
by SourceForge.net May 19, 2008

May 19, 2008

Bugs item #1966837, was opened at 2008-05-19 01:09 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1966837&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: (un)subscribing Group: 2.1 (stable) Status: Open >Resolution: Fixed Priority: 5 Private: No Submitted By: Stephan Berndts (berndts) Assigned to: Nobody/Anonymous (nobody) Summary: Subscribing via e-mail fails. Initial Comment: Hi, when I try to subscribe to a mailing list by sending an e-mail to listname-join@listserver this fails with the following error: May 13 13:08:54 2008 (14270) Uncaught runner exception: 'NoneType' object has no attribute 'lower' May 13 13:08:54 2008 (14270) Traceback (most recent call last): File "/srv/mailman/Mailman/Queue/Runner.py", line 114, in _oneloop self._onefile(msg, msgdata) File "/srv/mailman/Mailman/Queue/Runner.py", line 185, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/srv/mailman/Mailman/Queue/CommandRunner.py", line 241, in _dispose res.do_command('join') File "/srv/mailman/Mailman/Queue/CommandRunner.py", line 139, in do_command return handler.process(self, args) File "/srv/mailman/Mailman/Commands/cmd_subscribe.py", line 74, in process if digest is None and password.lower() in ('digest', 'nodigest'): AttributeError: 'NoneType' object has no attribute 'lower' May 13 13:08:54 2008 (14270) SHUNTING: 1210676933.788779+8f3f3d5d13ba53d21c00b3731faff2259213e4bf M The error arises as cmd_subscribe.py assumes that the variable "password" is not empty (at line 74) which is not true if neither a password nor an option in {digest,nodigest} was passed as a command-line argument. A patch resolving the error is attached. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2008-05-19 08:37 Message: Logged In: YES user_id=1123998 Originator: NO Thanks for the patch. This is a known issue. See the news item "Important patch for Mailman 2.1.10 2008-04-26" on the project page at <http://sourceforge.net/projects/mailman> and the Mailman_2.1.10.patch file on the download page at <http://sourceforge.net/project/showfiles.php?group_id=103>. Also see <http://mail.python.org/pipermail/mailman-announce/2008-April/000111.html> which was also posted to mailman-developers(a)python.org and mailman-users(a)python.org. Do you have any suggestions as to how the make things like this more visible? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1966837&group_…

1 0

[ mailman-Bugs-1966837 ] Subscribing via e-mail fails.
by SourceForge.net May 19, 2008

May 19, 2008

Bugs item #1966837, was opened at 2008-05-19 10:09 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1966837&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Stephan Berndts (berndts) Assigned to: Nobody/Anonymous (nobody) Summary: Subscribing via e-mail fails. Initial Comment: Hi, when I try to subscribe to a mailing list by sending an e-mail to listname-join@listserver this fails with the following error: May 13 13:08:54 2008 (14270) Uncaught runner exception: 'NoneType' object has no attribute 'lower' May 13 13:08:54 2008 (14270) Traceback (most recent call last): File "/srv/mailman/Mailman/Queue/Runner.py", line 114, in _oneloop self._onefile(msg, msgdata) File "/srv/mailman/Mailman/Queue/Runner.py", line 185, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/srv/mailman/Mailman/Queue/CommandRunner.py", line 241, in _dispose res.do_command('join') File "/srv/mailman/Mailman/Queue/CommandRunner.py", line 139, in do_command return handler.process(self, args) File "/srv/mailman/Mailman/Commands/cmd_subscribe.py", line 74, in process if digest is None and password.lower() in ('digest', 'nodigest'): AttributeError: 'NoneType' object has no attribute 'lower' May 13 13:08:54 2008 (14270) SHUNTING: 1210676933.788779+8f3f3d5d13ba53d21c00b3731faff2259213e4bf M The error arises as cmd_subscribe.py assumes that the variable "password" is not empty (at line 74) which is not true if neither a password nor an option in {digest,nodigest} was passed as a command-line argument. A patch resolving the error is attached. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1966837&group_…

1 0

[ mailman-Patches-1483446 ] Daily mbox files for list mbox archives
by SourceForge.net May 17, 2008

May 17, 2008

Patches item #1483446, was opened at 2006-05-07 18:14 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1483446&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Daily mbox files for list mbox archives Initial Comment: The daily mbox patch changes the way Mailman does its archive-to-mbox archiving, if that is enabled. The standard Mailman system single .mbox file per list used for mbox archiving can, over time, become very unwieldy, presenting problems for disk space management. The mailman daily mbox patch modifies Mailman's behaviour so that a sparse series of daily mbox files is used for archiving rather than a single mbox file. Each archived message is normally appended to a daily mbox file for the UTC date when the message is first archived. For more information, download the patch and check out the file README.dailymbox or visit the URL http://www.openinfo.co.uk/mm/ patches/dailymbox/ Apply the patch from within the Mailman build directory using the command: patch -p1 < path-to-patch-file ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2008-05-17 16:06 Message: Logged In: YES user_id=75166 Originator: YES File Added: dailymbox-2.1.10-0.1.patch.gz ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2006-10-03 11:58 Message: Logged In: YES user_id=75166 Uae dailymbox-2.1.8-0.1.patch.gz for MM 2.1.9 ---------------------------------------------------------------------- Comment By: Jim Popovitch (jimpop) Date: 2006-05-28 21:10 Message: Logged In: YES user_id=3142 Working very well on a production system. Nice addition to Mailman, makes file management and backups MUCH easier. Thanks!! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1483446&group_…

1 0

[ mailman-Patches-1442025 ] List Specialisation for Support Groups
by SourceForge.net May 17, 2008

May 17, 2008

Patches item #1442025, was opened at 2006-03-02 20:32 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1442025&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: List Specialisation for Support Groups Initial Comment: This patch modifies Mailman to address the following scenario: 1. A Mailman list to be used as the means by which a closed set of list subcribers (support staff) can provide responses to requests for support made by non-subscribers (customers) posting messages to the list. 2. Requirement that the incoming posts from customers (both original and follow up) and consequential responses from support staff should be entirely list-centric: a. The customer should see the response to a posting to the list as coming from the list, not the support person that responded. b. Any subsequent reply by the customer to a message from the list should go back to the list. c. Replies to customers by support staff should automatically be distributed to the the list. d. This should all happen by use of the basic features of typical MUAs by both support staff and customers; use of the MUA GUI's "Reply" button should do all that is necessary. e. Using the list in the way described should require no or minimal explanation to support staff and absolutely no explanation to customers. f. The e-mail addresses of support staff should remain hidden behind the list address. For more detail of implementation see: http://www.openinfo.co.uk/mm/patches/supportlist/index.html ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2008-05-17 16:04 Message: Logged In: YES user_id=75166 Originator: YES File Added: response-2.1.10-0.1.patch.gz ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2006-10-03 11:53 Message: Logged In: YES user_id=75166 response-2.1.9-0.1.patch.gz is a MM 2.1.9 compatible version of the patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2006-04-20 06:15 Message: Logged In: YES user_id=75166 Use response-2.1.7-0.1.patch.gz for both MM 2.1.7 and MM 2.1.8 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1442025&group_…

1 0

[ mailman-Patches-850805 ] Aggressive anti email address harvesting measure
by SourceForge.net May 17, 2008

May 17, 2008

Patches item #850805, was opened at 2003-11-28 16:23 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=850805&group_i… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Pipermail Group: Mailman 2.1 Status: Open Resolution: Postponed Priority: 5 Private: No 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: Richard Barrett (ppsys) Date: 2008-05-17 16:02 Message: Logged In: YES user_id=75166 Originator: YES File Added: antispam-2.1.10-0.1.patch.gz ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2006-10-03 11:14 Message: Logged In: YES user_id=75166 antispam-2.1.9-0.1.patch.gz is a MM 2.1.9 compatible version of the patch ---------------------------------------------------------------------- Comment By: O.S. (olaf) Date: 2004-11-14 00:41 Message: Logged In: YES user_id=11209 please, make these harvesting prevention measures per list configurable. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-11-14 00:28 Message: Logged In: YES user_id=67709 Sorry, patch itself is for 2.1 (not 3.0). ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-11-14 00:27 Message: Logged In: YES user_id=67709 It looks nice but it may be too much for 2.1.x where the archives are generated static. Also, I'm a little bit anxious writing such a function in Defaults.py. It would be better to include this feature in 3.0 or later. ---------------------------------------------------------------------- Comment By: Martin Mokrejs (mmokrejs) Date: 2004-04-20 09: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 00: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 07: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