Mailman 3 September 2004 - 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-1032434 ] make KNOWN_SPAMMERS work for headers appearing mult. times
by SourceForge.net Sept. 24, 2004

Sept. 24, 2004

Patches item #1032434, was opened at 2004-09-22 10:39 Message generated for change (Comment added) made by bergolth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1032434&group_… Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Alexander Bergolth (bergolth) Assigned to: Tokio Kikuchi (tkikuchi) Summary: make KNOWN_SPAMMERS work for headers appearing mult. times Initial Comment: Hi! Currently the header check against the KNOWN_SPAMMERS config option in SpamDetect.py uses msg[header], i.e. __getitem__. This method only checks against the first matching header: Note that if the header appeared multiple times, exactly which occurrance gets returned is undefined. Use getall() to get all the values matching a header field name. I've changed the code to use msg.get_all() instead. --leo ---------------------------------------------------------------------- >Comment By: Alexander Bergolth (bergolth) Date: 2004-09-24 10:11 Message: Logged In: YES user_id=24695 I'm using spamassassin and amavisd to tag spam and viruses. The header lines added by the virus-check look like the following: ---------- snipp! ---------- X-Amavis-Alert: INFECTED, message contains virus: Worm.SomeFool.Gen-1 X-Amavis-Alert: BANNED FILENAME, message contains part named: .exe ---------- snipp! ---------- I.e. there are multiple "X-Amavis-Alert" headers to be considered. --leo ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-09-24 04:20 Message: Logged In: YES user_id=67709 Looks like resonable to me. So, testing in my site. Do you have example to catch spam with this patch enabled. (received: ??) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1032434&group_…

1 0

[ mailman-Patches-1032434 ] make KNOWN_SPAMMERS work for headers appearing mult. times
by SourceForge.net Sept. 23, 2004

Sept. 23, 2004

Patches item #1032434, was opened at 2004-09-22 08:39 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1032434&group_… Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Alexander Bergolth (bergolth) >Assigned to: Tokio Kikuchi (tkikuchi) Summary: make KNOWN_SPAMMERS work for headers appearing mult. times Initial Comment: Hi! Currently the header check against the KNOWN_SPAMMERS config option in SpamDetect.py uses msg[header], i.e. __getitem__. This method only checks against the first matching header: Note that if the header appeared multiple times, exactly which occurrance gets returned is undefined. Use getall() to get all the values matching a header field name. I've changed the code to use msg.get_all() instead. --leo ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-09-24 02:20 Message: Logged In: YES user_id=67709 Looks like resonable to me. So, testing in my site. Do you have example to catch spam with this patch enabled. (received: ??) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1032434&group_…

1 0

[ mailman-Bugs-1033469 ] attachment appears in archive with extension changed to .exe
by SourceForge.net Sept. 23, 2004

Sept. 23, 2004

Bugs item #1033469, was opened at 2004-09-23 17:45 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=1033469&group_… Category: Pipermail Group: None Status: Open Resolution: None Priority: 5 Submitted By: Alexis Dimitriadis (alexis3) Assigned to: Nobody/Anonymous (nobody) Summary: attachment appears in archive with extension changed to .exe Initial Comment: I posted a message with an attached pdf document, which arrived intact to listmembers. But the link in the archived version appears with a somewhat mangled name and the extension .exe (which confuses browsers). The link points to the intact pdf file. >From the way the name was mangled, I suspect that the problem is caused by a space in the filename of the attachment. The bottom of the archived message looks like this:

1 0

[ mailman-Patches-873035 ] subject handling in -request mail
by SourceForge.net Sept. 22, 2004

Sept. 22, 2004

Patches item #873035, was opened at 2004-01-08 12:32 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=873035&group_i… Category: mail delivery Group: Mailman 2.1 >Status: Closed Resolution: None Priority: 7 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: subject handling in -request mail Initial Comment: Since spammers get one of our '-request' mail command address as target, we frequently get following error log and many such messages shunted. Jan 08 10:17:02 2004 (11705) Uncaught runner exception: ASCII decoding error: ordinal not in range(128) Jan 08 10:17:02 2004 (11705) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 110, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 160, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 223, in _dispose res = Results(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 77, in __init__ subj = make_header(decode_header(subj)).__unicode__() File "/usr/local/mailman/pythonlib/email/Header.py", line 144, in make_header h.append(s, charset) File "/usr/local/mailman/pythonlib/email/Header.py", line 272, in append ustr = unicode(s, incodec, errors) UnicodeError: ASCII decoding error: ordinal not in range(128) Jan 08 10:17:02 2004 (11705) SHUNTING: 1073506489.162806+2102abfa360c02ffb7bebbce12c1b9f09d8139f9 Apparently, following patch to Queue/CommandRunner.py may solve this problem. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-09-23 00:44 Message: Logged In: YES user_id=67709 Fixed in CVS revision: 2.26.2.5 ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-03-04 02:32 Message: Logged In: YES user_id=67709 Ok, I double-posted this item. So, raise the priority. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=873035&group_i…

1 0

[ mailman-Bugs-1014750 ] need to sort by domain before submitting to MTA
by SourceForge.net Sept. 22, 2004

Sept. 22, 2004

Bugs item #1014750, was opened at 2004-08-23 17:39 Message generated for change (Comment added) made by jaredmauch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1014750&group_… Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: jared mauch (jaredmauch) Assigned to: Nobody/Anonymous (nobody) Summary: need to sort by domain before submitting to MTA Initial Comment: I have a number of (large) lists that have a number of users at the same domain, but are submitted to the MTA in chunks of 10 to insure the list performs reasonably. The users at the same domain end up in different queue files of my MTA, and spark a large number of SMTP connections to their SMTP servers that could be minimized if the <user>@<domain> that is passed to the MTA is sorted by domain. Then I could have one SMTP transaction with them that delivers 10 messages. I'm no python expert, but figure sorting of this type should be fairly simple, and will reduce the amount my SMTP server abuses these other SMTP servers, which will be a good thing(tm), as well as save bandwidth.. ---------------------------------------------------------------------- >Comment By: jared mauch (jaredmauch) Date: 2004-09-22 10:59 Message: Logged In: YES user_id=131445 that should be recips not r.sort fyi ---------------------------------------------------------------------- Comment By: jared mauch (jaredmauch) Date: 2004-09-22 10:44 Message: Logged In: YES user_id=131445 SMTPDirect.py def domsort(uida, uidb): ## sort by domain ## usage foo.sort(domsort) i = uida.rfind('@') if i >= 0: doma = uida[i+1:] i = uidb.rfind('@') if i >= 0: domb = uidb[i+1:] return cmp(doma, domb) } # Need to sort by domain name. if we split to chunks it is possible # some well-known domains will be interspersed as we sort by # userid by default instead of by domain. (jared mauch) r.sort(domsort) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1014750&group_…

1 0

[ mailman-Bugs-953320 ] bad handling From header in archiver
by SourceForge.net Sept. 22, 2004

Sept. 22, 2004

Bugs item #953320, was opened at 2004-05-13 07:32 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=953320&group_i… Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 8 Submitted By: Tibor Pittich (phuture) Assigned to: Nobody/Anonymous (nobody) Summary: bad handling From header in archiver Initial Comment: 2.1.4 mailman version - there is problem with archiver. when body of message contains blank line and continued with text 'From ' at beggining of line, then archiver thing that this is a new message and split it. i see, there is a cleanarch script, which can escape non-header From line but why i must change original post adding "escape character"? is there possibility to check only header of message instead of whole message including body? ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2004-09-22 07:52 Message: Logged In: YES user_id=1123998 I had this problem on 2.1.4 after importing a large archive from another service. I then fixed the "^From .*$" lines that were in the bodies of a few messages and ran "bin/arch --wipe" to rebuild the archive and that absolutely DID fix the problem. ---------------------------------------------------------------------- Comment By: David A. Desrosiers (desrod) Date: 2004-09-22 07:04 Message: Logged In: YES user_id=3078 I can confirm that this affects the public/stable release version of 2.1.5. Running bin/cleanarch on the suspect mbox DOES NOT fix the problem. I have a list with messages back in 2002, which have "parts" showing up at the end of my September 2004 archives. The messages contain "parts" of the body, and are missing most of the headers. Every time arch runs, it reduplicates the trashed/truncated messages from 2002 onto the end of the September 2004 archive. This is a MAJOR MAJOR MAJOR MAJOR blocker, and cleanarch is not a proper solution. There are reasons why valid messages can start with the word "From" at the beginning of a line, and not be part of the "From:" header. Here are two examples: http://lists.pilot-link.org/pipermail/pilot-link-general/2002-September/016… http://lists.pilot-link.org/pipermail/pilot-link-general/2002-June/016144.h… I haven't yet found a fix for this, and adding the > in front of the "From" words at the beginning of the lines, DOES NOT fix the problem. In fact, deleting those messages (remember, they're from TWO YEARS AGO) from the .mbox, rm'ing the .html files, and re-running arch on the list, DOES NOT fix the problem. ---------------------------------------------------------------------- Comment By: David A. Desrosiers (desrod) Date: 2004-05-13 10:04 Message: Logged In: YES user_id=3078 I can confirm this bug in 2.1.4, and that it is also in 2.1.5c2.. MAJOR BLOCKER! Please assign to someone and fix! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=953320&group_i…

1 0

[ mailman-Bugs-1014750 ] need to sort by domain before submitting to MTA
by SourceForge.net Sept. 22, 2004

Sept. 22, 2004

Bugs item #1014750, was opened at 2004-08-23 17:39 Message generated for change (Comment added) made by jaredmauch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1014750&group_… Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: jared mauch (jaredmauch) Assigned to: Nobody/Anonymous (nobody) Summary: need to sort by domain before submitting to MTA Initial Comment: I have a number of (large) lists that have a number of users at the same domain, but are submitted to the MTA in chunks of 10 to insure the list performs reasonably. The users at the same domain end up in different queue files of my MTA, and spark a large number of SMTP connections to their SMTP servers that could be minimized if the <user>@<domain> that is passed to the MTA is sorted by domain. Then I could have one SMTP transaction with them that delivers 10 messages. I'm no python expert, but figure sorting of this type should be fairly simple, and will reduce the amount my SMTP server abuses these other SMTP servers, which will be a good thing(tm), as well as save bandwidth.. ---------------------------------------------------------------------- >Comment By: jared mauch (jaredmauch) Date: 2004-09-22 10:44 Message: Logged In: YES user_id=131445 SMTPDirect.py def domsort(uida, uidb): ## sort by domain ## usage foo.sort(domsort) i = uida.rfind('@') if i >= 0: doma = uida[i+1:] i = uidb.rfind('@') if i >= 0: domb = uidb[i+1:] return cmp(doma, domb) } # Need to sort by domain name. if we split to chunks it is possible # some well-known domains will be interspersed as we sort by # userid by default instead of by domain. (jared mauch) r.sort(domsort) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1014750&group_…

1 0

[ mailman-Bugs-953320 ] bad handling From header in archiver
by SourceForge.net Sept. 22, 2004

Sept. 22, 2004

Bugs item #953320, was opened at 2004-05-13 16:32 Message generated for change (Settings changed) made by phuture You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=953320&group_i… Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None >Priority: 8 Submitted By: Tibor Pittich (phuture) Assigned to: Nobody/Anonymous (nobody) Summary: bad handling From header in archiver Initial Comment: 2.1.4 mailman version - there is problem with archiver. when body of message contains blank line and continued with text 'From ' at beggining of line, then archiver thing that this is a new message and split it. i see, there is a cleanarch script, which can escape non-header From line but why i must change original post adding "escape character"? is there possibility to check only header of message instead of whole message including body? ---------------------------------------------------------------------- Comment By: David A. Desrosiers (desrod) Date: 2004-09-22 16:04 Message: Logged In: YES user_id=3078 I can confirm that this affects the public/stable release version of 2.1.5. Running bin/cleanarch on the suspect mbox DOES NOT fix the problem. I have a list with messages back in 2002, which have "parts" showing up at the end of my September 2004 archives. The messages contain "parts" of the body, and are missing most of the headers. Every time arch runs, it reduplicates the trashed/truncated messages from 2002 onto the end of the September 2004 archive. This is a MAJOR MAJOR MAJOR MAJOR blocker, and cleanarch is not a proper solution. There are reasons why valid messages can start with the word "From" at the beginning of a line, and not be part of the "From:" header. Here are two examples: http://lists.pilot-link.org/pipermail/pilot-link-general/2002-September/016… http://lists.pilot-link.org/pipermail/pilot-link-general/2002-June/016144.h… I haven't yet found a fix for this, and adding the > in front of the "From" words at the beginning of the lines, DOES NOT fix the problem. In fact, deleting those messages (remember, they're from TWO YEARS AGO) from the .mbox, rm'ing the .html files, and re-running arch on the list, DOES NOT fix the problem. ---------------------------------------------------------------------- Comment By: David A. Desrosiers (desrod) Date: 2004-05-13 19:04 Message: Logged In: YES user_id=3078 I can confirm this bug in 2.1.4, and that it is also in 2.1.5c2.. MAJOR BLOCKER! Please assign to someone and fix! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=953320&group_i…

1 0

[ mailman-Bugs-953320 ] bad handling From header in archiver
by SourceForge.net Sept. 22, 2004

Sept. 22, 2004

Bugs item #953320, was opened at 2004-05-13 14:32 Message generated for change (Comment added) made by desrod You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=953320&group_i… Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Tibor Pittich (phuture) Assigned to: Nobody/Anonymous (nobody) Summary: bad handling From header in archiver Initial Comment: 2.1.4 mailman version - there is problem with archiver. when body of message contains blank line and continued with text 'From ' at beggining of line, then archiver thing that this is a new message and split it. i see, there is a cleanarch script, which can escape non-header From line but why i must change original post adding "escape character"? is there possibility to check only header of message instead of whole message including body? ---------------------------------------------------------------------- Comment By: David A. Desrosiers (desrod) Date: 2004-09-22 14:04 Message: Logged In: YES user_id=3078 I can confirm that this affects the public/stable release version of 2.1.5. Running bin/cleanarch on the suspect mbox DOES NOT fix the problem. I have a list with messages back in 2002, which have "parts" showing up at the end of my September 2004 archives. The messages contain "parts" of the body, and are missing most of the headers. Every time arch runs, it reduplicates the trashed/truncated messages from 2002 onto the end of the September 2004 archive. This is a MAJOR MAJOR MAJOR MAJOR blocker, and cleanarch is not a proper solution. There are reasons why valid messages can start with the word "From" at the beginning of a line, and not be part of the "From:" header. Here are two examples: http://lists.pilot-link.org/pipermail/pilot-link-general/2002-September/016… http://lists.pilot-link.org/pipermail/pilot-link-general/2002-June/016144.h… I haven't yet found a fix for this, and adding the > in front of the "From" words at the beginning of the lines, DOES NOT fix the problem. In fact, deleting those messages (remember, they're from TWO YEARS AGO) from the .mbox, rm'ing the .html files, and re-running arch on the list, DOES NOT fix the problem. ---------------------------------------------------------------------- Comment By: David A. Desrosiers (desrod) Date: 2004-05-13 17:04 Message: Logged In: YES user_id=3078 I can confirm this bug in 2.1.4, and that it is also in 2.1.5c2.. MAJOR BLOCKER! Please assign to someone and fix! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=953320&group_i…

1 0