Mailman 3 February 2003 - Mailman-coders

[ mailman-Patches-682573 ] qmail-to-mailman.py broken when using --with-var-prefix
by SourceForge.net Feb. 8, 2003

Feb. 8, 2003

Patches item #682573, was opened at 2003-02-07 16:37 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=682573&group_i… Category: mail delivery Group: Mailman 2.1 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Matthias Juchem (brightice) Assigned to: Nobody/Anonymous (nobody) Summary: qmail-to-mailman.py broken when using --with-var-prefix Initial Comment: Hi. Problem: When using --with-var-prefix with configure, contrib/qmail-to-mailman.py gets broken because it does not know about the concept of a second directory. Fix: Instroduce new variable for var-prefix directory. Patch tested in production use. Matthias ---------------------------------------------------------------------- Comment By: Matthias Juchem (brightice) Date: 2003-02-07 16:44 Message: Logged In: YES user_id=60479 Sorry for the spam, I got the diff wrong... stupid me. ---------------------------------------------------------------------- Comment By: Matthias Juchem (brightice) Date: 2003-02-07 16:39 Message: Logged In: YES user_id=60479 Ok. Trying to attach patch a second time... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=682573&group_i…

1 0

[ mailman-Patches-664611 ] Updated README.QMAIL doc patch
by SourceForge.net Feb. 8, 2003

Feb. 8, 2003

Patches item #664611, was opened at 2003-01-08 14:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=664611&group_i… Category: documentation Group: Mailman 2.1 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Ed Lau (edlau) Assigned to: Nobody/Anonymous (nobody) Summary: Updated README.QMAIL doc patch Initial Comment: Main item: distinction between MM2.0 & MM2.1 alias generation scripts. Also, information on VERP ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-02-07 23:38 Message: Logged In: YES user_id=12800 Applied the v2 doc ---------------------------------------------------------------------- Comment By: Ed Lau (edlau) Date: 2003-01-09 02:24 Message: Logged In: YES user_id=675094 Directory paths have changed to reflect new installations vs upgrading from prior installs ---------------------------------------------------------------------- Comment By: Ed Lau (edlau) Date: 2003-01-08 22:50 Message: Logged In: YES user_id=675094 Didn't look like SF got my patch the first time. It's attached now ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=664611&group_i…

1 0

[ mailman-Patches-682573 ] qmail-to-mailman.py broken when using --with-var-prefix
by SourceForge.net Feb. 7, 2003

Feb. 7, 2003

Patches item #682573, was opened at 2003-02-07 22:37 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=682573&group_i… Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Matthias Juchem (brightice) Assigned to: Nobody/Anonymous (nobody) Summary: qmail-to-mailman.py broken when using --with-var-prefix Initial Comment: Hi. Problem: When using --with-var-prefix with configure, contrib/qmail-to-mailman.py gets broken because it does not know about the concept of a second directory. Fix: Instroduce new variable for var-prefix directory. Patch tested in production use. Matthias ---------------------------------------------------------------------- >Comment By: Matthias Juchem (brightice) Date: 2003-02-07 22:44 Message: Logged In: YES user_id=60479 Sorry for the spam, I got the diff wrong... stupid me. ---------------------------------------------------------------------- Comment By: Matthias Juchem (brightice) Date: 2003-02-07 22:39 Message: Logged In: YES user_id=60479 Ok. Trying to attach patch a second time... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=682573&group_i…

1 0

[ mailman-Patches-682573 ] qmail-to-mailman.py broken when using --with-var-prefix
by SourceForge.net Feb. 7, 2003

Feb. 7, 2003

Patches item #682573, was opened at 2003-02-07 22:37 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=682573&group_i… Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Matthias Juchem (brightice) Assigned to: Nobody/Anonymous (nobody) Summary: qmail-to-mailman.py broken when using --with-var-prefix Initial Comment: Hi. Problem: When using --with-var-prefix with configure, contrib/qmail-to-mailman.py gets broken because it does not know about the concept of a second directory. Fix: Instroduce new variable for var-prefix directory. Patch tested in production use. Matthias ---------------------------------------------------------------------- >Comment By: Matthias Juchem (brightice) Date: 2003-02-07 22:39 Message: Logged In: YES user_id=60479 Ok. Trying to attach patch a second time... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=682573&group_i…

1 0

[ mailman-Patches-682573 ] qmail-to-mailman.py broken when using --with-var-prefix
by SourceForge.net Feb. 7, 2003

Feb. 7, 2003

Patches item #682573, was opened at 2003-02-07 22:37 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=682573&group_i… Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Matthias Juchem (brightice) Assigned to: Nobody/Anonymous (nobody) Summary: qmail-to-mailman.py broken when using --with-var-prefix Initial Comment: Hi. Problem: When using --with-var-prefix with configure, contrib/qmail-to-mailman.py gets broken because it does not know about the concept of a second directory. Fix: Instroduce new variable for var-prefix directory. Patch tested in production use. Matthias ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=682573&group_i…

1 0

[ mailman-Bugs-671147 ] ValueError on admin of upgraded list
by SourceForge.net Feb. 7, 2003

Feb. 7, 2003

Bugs item #671147, was opened at 2003-01-20 08:11 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=671147&group_i… Category: None Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: seb bacon (sebbacon) Assigned to: Nobody/Anonymous (nobody) Summary: ValueError on admin of upgraded list Initial Comment: This is a dupe of bug 668664, but I'm darned if I can see how you can upload a file as a comment to an already existing bug. I looked at this bug for a friend and there appear to be a couple of obvious bugs that cause this ValueError to happen. I don't use mailman, so I didn't bother checking that this fix works, but hopefully it's helpful ;-) ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-02-07 11:28 Message: Logged In: YES user_id=12800 There was no attachment, probably because you didn't check the upload box (yes, this is SF's suckage). No matter, I believe this will be fixed for 2.1.1 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=671147&group_i…

1 0

[ mailman-Patches-640518 ] SpamAssassin handler
by SourceForge.net Feb. 7, 2003

Feb. 7, 2003

Patches item #640518, was opened at 2002-11-19 05:26 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=640518&group_i… Category: list administration Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Jon Parise (jparise) Assigned to: Nobody/Anonymous (nobody) Summary: SpamAssassin handler Initial Comment: I've updated the existing SpamAssassin patch (534577) for Mailman 2.1. ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2003-02-07 07:23 Message: Logged In: YES user_id=81797 I can't get this code to work with Mailman 2.1. A message that triggers the hold for moderator starts bouncing messages from the list owner and just sits in a mail loop until I remove SpamAssassin from the filter chain, delivering a message for every loop to the admin interface. I spent a couple of hours looking at it, but I can't see why it is doing this. It's defeinitely in the Hold.hold_for_whatever, but I don't know why that's failing. Just thought I'd mention it. I guess we'll stay with 2.0 where it's working fine with the other patch-set. Sean ---------------------------------------------------------------------- Comment By: Jon Parise (jparise) Date: 2003-02-03 02:39 Message: Logged In: YES user_id=485579 Yes, use the version with the "footsie" code. I don't appear to have permission to delete the older version from this patch tracker. It doesn't make any special exceptions with regard to the list owner, but I'll have a look at making that part of the logic smarter. ---------------------------------------------------------------------- Comment By: Shamanic Acid (shamanicacid) Date: 2003-01-28 07:18 Message: Logged In: YES user_id=698712 I am a bit confused in which SpamAssassin.py file to use. There does not seem to be an embedded version number in the download links. The diff I see is as follows: $ diff SpamAssassin.1.py SpamAssassin.py 62,65d61 < # First, play footsie with _ so that the following are marked as translated, < # but aren't actually translated until we need the text later on. < def _(s): < return s 71,73d66 < reason = _('SpamAssassin identified this message as spam') < rejection = _('You message was identified as spam.') < 78,80d70 < reason = _('SpamAssassin identified this message as spam') < rejection = _('You message was identified as spam.') < Question # 1. Do I want to use the SpamAssassin.py file with the "footsie" code? Question # 2. Does the SpamAssassin.py code allow for exceptions when the e-mail is from the $list-owner ( bounces to moderator ) ? I ask because I ran into a problem with a mailer-loop occuring when SpamAssassin errantly tagged the $list-owner moderator bounces as spam. ( spamassasin marks pending e-mails from $list-owner with score 7.6 ) I have not read through all the code, I am curious if mlist.isMember(sender) includes the owner alias? Many Thanks in Advance ---------------------------------------------------------------------- Comment By: Jon Parise (jparise) Date: 2003-01-12 16:01 Message: Logged In: YES user_id=485579 I've updated the SpamAssassin handler to report a more detailed reason when a DiscardMessage and HoldMessage exception is raised. ---------------------------------------------------------------------- Comment By: Jon Parise (jparise) Date: 2003-01-01 00:33 Message: Logged In: YES user_id=485579 The attached patch adds the SpamAssassin handler to Mailman's mail processing pipelines. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-11-27 16:13 Message: Logged In: YES user_id=12800 I'm only moving this to the MM2.2/3.0 group so I can concentrate on patches for 2.1. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=640518&group_i…

1 0

[ mailman-Bugs-668664 ] ValueError processing held messages
by SourceForge.net Feb. 7, 2003

Feb. 7, 2003

Bugs item #668664, was opened at 2003-01-15 14:05 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=668664&group_i… Category: None Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Bryan Fullerton (fehwalker) Assigned to: Nobody/Anonymous (nobody) Summary: ValueError processing held messages Initial Comment: I've seen this problem both with cron/checkdbs and now with the admindb CGI. I'm submitting this one because it has lots of detail. I've had some luck playing with try/except in checkdbs, but that just skips the entry that's having problems, doesn't actually deal with it. Jan 14 18:21:47 2003 admin(54023): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(54023): [----- Mailman Version: 2.1 -----] admin(54023): [----- Traceback ------] admin(54023): Traceback (most recent call last): admin(54023): File "/home/mailman-2.1/scripts/driver", line 87, in run_main admin(54023): main() admin(54023): File "/home/mailman-2.1/Mailman/Cgi/admindb.py", line 226, in main admin(54023): num = show_pending_subs(mlist, form) admin(54023): File "/home/mailman-2.1/Mailman/Cgi/admindb.py", line 287, in show_pending_subs admin(54023): time, addr, fullname, passwd, digest, lang = mlist.GetRecord(id) admin(54023): ValueError: unpack tuple of wrong size admin(54023): [----- Python Information -----] admin(54023): sys.version = 2.2.2 (#1, Dec 1 2002, 11:44:59) [GCC 2.95.3 20010315 (release) [FreeBSD]] admin(54023): sys.executable = /usr/local/bin/python admin(54023): sys.prefix = /usr/local admin(54023): sys.exec_prefix = /usr/local admin(54023): sys.path = /usr/local admin(54023): sys.platform = freebsd4 admin(54023): [----- Environment Variables -----] admin(54023): PATH_INFO: /wnet admin(54023): HTTP_ACCEPT: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-powerpoint, application/vnd.ms-excel, application/msword, */* admin(54023): CONTENT_TYPE: application/x-www-form-urlencoded admin(54023): HTTP_REFERER: http://lists.samurai.com/mailman/admindb/wnet admin(54023): SERVER_SOFTWARE: Apache/1.3.27 (Unix) admin(54023): PYTHONPATH: /home/mailman-2.1 admin(54023): SCRIPT_FILENAME: /home/mailman-2.1/cgi-bin/admindb admin(54023): SERVER_ADMIN: webmaster(a)samurai.com admin(54023): SCRIPT_NAME: /mailman/admindb admin(54023): SCRIPT_URI: http://lists.samurai.com/mailman/admindb/wnet admin(54023): SERVER_SIGNATURE: <ADDRESS>Apache/1.3.27 Server at lists.samurai.com Port 80</ADDRESS> admin(54023): admin(54023): REQUEST_METHOD: POST admin(54023): HTTP_HOST: lists.samurai.com admin(54023): SCRIPT_URL: /mailman/admindb/wnet admin(54023): SERVER_PROTOCOL: HTTP/1.1 admin(54023): QUERY_STRING: admin(54023): HTTP_CACHE_CONTROL: no-cache admin(54023): REQUEST_URI: /mailman/admindb/wnet admin(54023): CONTENT_LENGTH: 18 admin(54023): PATH_TRANSLATED: /usr/local/www/data/wnet admin(54023): HTTP_USER_AGENT: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; Q312461) admin(54023): HTTP_CONNECTION: Keep-Alive admin(54023): SERVER_NAME: lists.samurai.com admin(54023): REMOTE_ADDR: 65.93.181.251 admin(54023): REMOTE_PORT: 4749 admin(54023): HTTP_ACCEPT_LANGUAGE: en-ca admin(54023): UNIQUE_ID: PiSbis3PHE8AAKK7eCk admin(54023): SERVER_PORT: 80 admin(54023): GATEWAY_INTERFACE: CGI/1.1 admin(54023): REMOTE_HOST: sherbrooke-hse-ppp3609836.sympatico.ca admin(54023): HTTP_ACCEPT_ENCODING: gzip, deflate admin(54023): SERVER_ADDR: 205.207.28.81 admin(54023): DOCUMENT_ROOT: /usr/local/www/data Bryan ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-02-07 01:30 Message: Logged In: YES user_id=12800 I believe I've finally fixed this in MM2.1+ (cvs) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=668664&group_i…

1 0

[ mailman-Patches-674401 ] ToDigest.py i18n subject
by SourceForge.net Feb. 7, 2003

Feb. 7, 2003

Patches item #674401, was opened at 2003-01-24 20:08 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=674401&group_i… Category: internationalization Group: Mailman 2.1 >Status: Closed Resolution: Accepted Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: ToDigest.py i18n subject Initial Comment: ToDigestl.py (v2.23) was considerably improved but there remain some oddities in digested message subject representation. Specificaly, MIME subject is not wrapped with the lheader() propperly. Please examine the files I am going to attach. 1. Test program to examine the behaviour of lheader() and improbed (but lengthy) header_in_a_line() which removes excessive CRLF and adjust folding white spaces. It simulates the subject-prefix which will be added in CookHeaders.py. 2. Result of test program. You will notice incompatiblity when the subject is once MIME encoded. 3. New patch which use header_in_a_line() and Utils.wrap() ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-02-07 00:14 Message: Logged In: YES user_id=12800 Looks like this is working for python.org at least, so I'm closing the issue. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-02-06 23:24 Message: Logged In: YES user_id=12800 I'm accepting and applying this patch -- with two differences. One the line that says "return oneline.encode()" I want to pass the argument "replace" so that there's more chance that much of the header decoding can actually happen. Without this, iso-8859-1 encoded Subject: headers posted to an English list leave the RFC 2047 encodings in the header, which looks ugly. The second change is to replace the bare except (bad! :) in oneline() with a qualified except. I believe only UnicodeError and LookupError can occur here, although with the first change above, maybe not even UnicodeError. Now I want to see if this fixes the problem I've been having with the spambayes list. Thanks! :) ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-06 22:28 Message: Logged In: YES user_id=67709 Sorry, I have uploaded intermediate version. This is final, I hope. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-06 19:37 Message: Logged In: YES user_id=67709 updating patch for fixing new unicode-related error reported by Dan Mick. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-04 02:15 Message: Logged In: YES user_id=67709 This is my final patch. And, I like no blank line in TOC. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-31 02:01 Message: Logged In: YES user_id=67709 OK, Barry. I will compromise. Use u''.join() not u' '.join(). This eliminate extra space added when joining. Remember that all-ASCII header will get double space after the prefix for English text while the spaces after the prefix is removed for Japanese text. I think __unicode__() joining in the email package should take care the difference in RFC2822/2047 headers. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-31 00:55 Message: Logged In: YES user_id=67709 Looks like good for english text (may be for western) but folding white space should be treated as null string ('') in iso-2022-jp encoded japanese (and other RFC 2047 encoded MIME subject, I believe). u' '.join() must be u''.join() in these languages. You must alway check if the part of the header is mime encoded or not when joining. :-( ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-01-31 00:17 Message: Logged In: YES user_id=12800 Tell me what you think of the hial() function in the attached file. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-24 20:16 Message: Logged In: YES user_id=67709 Forget to note: This patch is revise of #668819 which was closed and differently applied in recent CVS. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=674401&group_i…

1 0

[ mailman-Patches-674401 ] ToDigest.py i18n subject
by SourceForge.net Feb. 7, 2003

Feb. 7, 2003

Patches item #674401, was opened at 2003-01-24 20:08 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=674401&group_i… Category: internationalization Group: Mailman 2.1 Status: Open >Resolution: Accepted Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: ToDigest.py i18n subject Initial Comment: ToDigestl.py (v2.23) was considerably improved but there remain some oddities in digested message subject representation. Specificaly, MIME subject is not wrapped with the lheader() propperly. Please examine the files I am going to attach. 1. Test program to examine the behaviour of lheader() and improbed (but lengthy) header_in_a_line() which removes excessive CRLF and adjust folding white spaces. It simulates the subject-prefix which will be added in CookHeaders.py. 2. Result of test program. You will notice incompatiblity when the subject is once MIME encoded. 3. New patch which use header_in_a_line() and Utils.wrap() ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-02-06 23:24 Message: Logged In: YES user_id=12800 I'm accepting and applying this patch -- with two differences. One the line that says "return oneline.encode()" I want to pass the argument "replace" so that there's more chance that much of the header decoding can actually happen. Without this, iso-8859-1 encoded Subject: headers posted to an English list leave the RFC 2047 encodings in the header, which looks ugly. The second change is to replace the bare except (bad! :) in oneline() with a qualified except. I believe only UnicodeError and LookupError can occur here, although with the first change above, maybe not even UnicodeError. Now I want to see if this fixes the problem I've been having with the spambayes list. Thanks! :) ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-06 22:28 Message: Logged In: YES user_id=67709 Sorry, I have uploaded intermediate version. This is final, I hope. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-06 19:37 Message: Logged In: YES user_id=67709 updating patch for fixing new unicode-related error reported by Dan Mick. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-04 02:15 Message: Logged In: YES user_id=67709 This is my final patch. And, I like no blank line in TOC. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-31 02:01 Message: Logged In: YES user_id=67709 OK, Barry. I will compromise. Use u''.join() not u' '.join(). This eliminate extra space added when joining. Remember that all-ASCII header will get double space after the prefix for English text while the spaces after the prefix is removed for Japanese text. I think __unicode__() joining in the email package should take care the difference in RFC2822/2047 headers. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-31 00:55 Message: Logged In: YES user_id=67709 Looks like good for english text (may be for western) but folding white space should be treated as null string ('') in iso-2022-jp encoded japanese (and other RFC 2047 encoded MIME subject, I believe). u' '.join() must be u''.join() in these languages. You must alway check if the part of the header is mime encoded or not when joining. :-( ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-01-31 00:17 Message: Logged In: YES user_id=12800 Tell me what you think of the hial() function in the attached file. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-24 20:16 Message: Logged In: YES user_id=67709 Forget to note: This patch is revise of #668819 which was closed and differently applied in recent CVS. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=674401&group_i…

1 0