Mailman-coders December 2005

mailman-coders@python.org

1 participants
27 discussions

[ mailman-Patches-933757 ] fix for [815297] signatures break
by SourceForge.net 12 Dec '05

12 Dec '05

Patches item #933757, was opened at 2004-04-12 19:15 Message generated for change (Comment added) made by schoinobates You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=933757&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: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 8 Submitted By: Bernhard Reiter (ber) Assigned to: Nobody/Anonymous (nobody) Summary: fix for [815297] signatures break Initial Comment: Fix attempt for [ 815297 ] Breaking signatures in message/rfc822 attachement! https://sourceforge.net/tracker/?func=detail&aid=815297&group_id=103&atid=1… The patch introduces a new Mailman specific Generator class and only enables header folding for the top object and Mailbox.py and SMTPDirect.py. ---------------------------------------------------------------------- Comment By: Schoinobates Volans (schoinobates) Date: 2005-12-12 17:33 Message: Logged In: YES user_id=41822 A slightly edited version of this patch is at http://bugs.debian.org/cgi-bin/bugreport.cgi/77_header_folding_in_attachmen… ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2004-04-14 19:56 Message: Logged In: YES user_id=113859 My patch was tested with python 2.3.3. Thomas Köster made a patch which also works with python 2.1.x I'll attach it. ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2004-04-12 19:24 Message: Logged In: YES user_id=113859 A bug fix to a priority 8 bug... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=933757&group_i…

1 0

[ mailman-Bugs-1204386 ] check_perms doesn't ensure aliases.db is group-writeable
by SourceForge.net 11 Dec '05

11 Dec '05

Bugs item #1204386, was opened at 2005-05-18 12:01 Message generated for change (Comment added) made by beelzebozo You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1204386&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: configuring/installing Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Graham Klyne (grahamk) Assigned to: Nobody/Anonymous (nobody) Summary: check_perms doesn't ensure aliases.db is group-writeable Initial Comment: Problem reported for mailman 2.1.6rc4 With postfix 2:2.0.16-14.RHEL3 When installing mailman 2.1.6rc1 using postfix MTA and "Integrating Postfix and Mailman" as described inthe installation document, I encountered a problem that the aliases.db file was created without group write capability. This was not detected by check_perms. (Even on re-reading, it's not obvious to me that g+w permissions are required, though that became pretty obvious when I tracked the error log failure report when attempting to create a new mailing list.) Because I messed around a bit with that installation, I've verified the problem with check_perms on a working 2.1.6rc4 installation, by resetting the groupwrite permission, thus: The following is executed as user mailman in dirtectory /var/mailman/data: [[ bash-2.05b$ ls -al total 60 drwxrwsr-x 2 mailman mailman 4096 May 18 14:31 . drwxrwsr-x 9 mailman mailman 4096 Apr 21 18:36 .. -rw-r----- 1 mailman mailman 41 Apr 29 13:54 adm.pw -rw-rw---- 1 mailman mailman 4922 May 4 16:25 aliases -rw-rw---- 1 mailman mailman 12288 May 4 16:25 aliases.db -rw-r----- 1 mailman mailman 41 Apr 22 15:07 creator.pw -rw-r--r-- 1 mailman mailman 10 May 18 14:32 last_mailman_version -rw-rw---- 1 mailman mailman 6 May 12 09:19 master-qrunner.pid -rw-r--r-- 1 mailman mailman 14110 May 18 14:31 sitelist.cfg bash-2.05b$ bash-2.05b$ /home/mailman/bin/check_perms No problems found (This is a normal working configuration from which I started) bash-2.05b$ chmod g-w aliases* bash-2.05b$ /home/mailman/bin/check_perms /var/mailman/data/aliases permissions must be 066x (got 0100640) Problems found: 1 Re-run as mailman (or root) with -f flag to fix (check_perms notices the problem with aliases, but not with aliases.db) bash-2.05b$ ls -al total 60 drwxrwsr-x 2 mailman mailman 4096 May 18 14:31 . drwxrwsr-x 9 mailman mailman 4096 Apr 21 18:36 .. -rw-r----- 1 mailman mailman 41 Apr 29 13:54 adm.pw -rw-r----- 1 mailman mailman 4922 May 4 16:25 aliases -rw-r----- 1 mailman mailman 12288 May 4 16:25 aliases.db -rw-r----- 1 mailman mailman 41 Apr 22 15:07 creator.pw -rw-r--r-- 1 mailman mailman 10 May 18 14:32 last_mailman_version -rw-rw---- 1 mailman mailman 6 May 12 09:19 master-qrunner.pid -rw-r--r-- 1 mailman mailman 14110 May 18 14:31 sitelist.cfg bash-2.05b$ chmod g+w aliases bash-2.05b$ /home/mailman/bin/check_perms No problems found bash-2.05b$ ls -al total 60 drwxrwsr-x 2 mailman mailman 4096 May 18 14:31 . drwxrwsr-x 9 mailman mailman 4096 Apr 21 18:36 .. -rw-r----- 1 mailman mailman 41 Apr 29 13:54 adm.pw -rw-rw---- 1 mailman mailman 4922 May 4 16:25 aliases -rw-r----- 1 mailman mailman 12288 May 4 16:25 aliases.db -rw-r----- 1 mailman mailman 41 Apr 22 15:07 creator.pw -rw-r--r-- 1 mailman mailman 10 May 18 14:32 last_mailman_version -rw-rw---- 1 mailman mailman 6 May 12 09:19 master-qrunner.pid -rw-r--r-- 1 mailman mailman 14110 May 18 14:31 sitelist.cfg (No report from check_perms despite missing group write permission on aliases.db) ]] ---------------------------------------------------------------------- Comment By: Todd (beelzebozo) Date: 2005-12-11 14:57 Message: Logged In: YES user_id=1386166 Patch against CVS (20051211) created. See https://sourceforge.net/tracker/index.php?func=detail&aid=1378270&group_id=… ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1204386&group_…

1 0

[ mailman-Bugs-1378270 ] make check_perms ensure aliases.db is group-writeable
by SourceForge.net 11 Dec '05

11 Dec '05

Bugs item #1378270, was opened at 2005-12-11 14:54 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=1378270&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: None Status: Open Resolution: None Priority: 5 Submitted By: Todd (beelzebozo) Assigned to: Nobody/Anonymous (nobody) Summary: make check_perms ensure aliases.db is group-writeable Initial Comment: checkperms in the Postfix module doesn't ensure that both aliases and aliases.db are group writable. The attached patch against CVS (20051211) fixes this by copying the check for aliases to also check aliases.db. It also patches mailman-install.tex to make it clear that both files should be group writable. See Tracker 1204386[1] and Mailman FAQ 6.9[2] for reports on this problem. [1] https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1204386&group_… [2] http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq06.009.htp ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1378270&group_…

1 0

[ mailman-Bugs-1152953 ] Cancelling a subscription confirmation throws assertion
by SourceForge.net 10 Dec '05

10 Dec '05

Bugs item #1152953, was opened at 2005-02-27 09:15 Message generated for change (Settings changed) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1152953&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: Closed >Resolution: Fixed Priority: 5 Submitted By: Geoff Mottram (gmottram) Assigned to: Nobody/Anonymous (nobody) Summary: Cancelling a subscription confirmation throws assertion Initial Comment: When you use the web interface to confirm a subscription and select the "Cancel my subscription request", Mailman throws an assertion. The problem can be fixed by replacing line 312 in Mailman/Cgi/confirm.py which currently reads: userdesc = mlist.pend_confirm(cookie)[1] With the following code: mlist.Lock() try: userdesc = mlist.pend_confirm(cookie)[1] finally: mlist.Unlock() More detailed information on this fix can be found here: http://www.minaret.biz/tips/mailman2.html Geoff Mottram ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2005-12-10 13:43 Message: Logged In: YES user_id=1123998 This is a duplicate of 981188, fixed in Mailman 2.1.6. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1152953&group_…

1 0

[ mailman-Bugs-971957 ] Uncaught runner exception
by SourceForge.net 08 Dec '05

08 Dec '05

Bugs item #971957, was opened at 2004-06-12 20:36 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=971957&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: mail delivery Group: 2.1 (stable) Status: Closed Resolution: Fixed Priority: 5 Submitted By: John Distler (jd_waverly) Assigned to: Nobody/Anonymous (nobody) Summary: Uncaught runner exception Initial Comment: In 2.1.5 Apparently some email message characters can crash the Runner.py. I have inserted $mailman in place of my mailman path in the message below from $mailman/logs/error Jun 12 01:25:48 2004 (16604) Uncaught runner exception: ASCII decoding error: ordinal not in range (128) Jun 12 01:25:48 2004 (16604) Traceback (most recent call last): File "$mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File $mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "$mailman/Mailman/Queue/CommandRunner.py", line 223, in _dispose res = Results(mlist, msg, msgdata) File "$mailman/Mailman/Queue/CommandRunner.py", line 77, in __init__ subj = make_header(decode_header (subj)).__unicode__() File "$mailman/pythonlib/email/Header.py", line 144, in make_header h.append(s, charset) File "$mailman/pythonlib/email/Header.py", line 272, in append ustr = unicode(s, incodec, errors) UnicodeError: ASCII decoding error: ordinal not in range (128) ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2005-12-08 08:16 Message: Logged In: YES user_id=1123998 A few remarks with regard to the 2005-12-08 comment from doctorchd: 1) Posting new information to a Closed/Fixed Bug report is not too useful. It would be better to generate a new report. 2) The Traceback and error reported by doctorchd is not at all the same error as the one originnaly reported in this report. The only thing they have in common is they both generate uncaught UnicodeError exceptions. 3) The error reported by doctorchd is fixed by patch 1246003 which has been accepted and is in CVS. ---------------------------------------------------------------------- Comment By: chd (doctorchd) Date: 2005-12-08 02:12 Message: Logged In: YES user_id=1400126 mailman 2.1.6 on FreeBSD (default installation from ports collection) python-2.4.2 A letter with charset=ISO-2022-JP stopped a maillist. New letters are added to the digest but not get sent. logs/error: Dec 08 11:12:05 2005 (8832) Uncaught runner exception: ISO-2022-JP decoding error: invalid designation Dec 08 11:12:05 2005 (8832) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 92, in process send_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 133, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 331, in send_i18n_digests payload = unicode(payload, mcset, 'replace' UnicodeError: ISO-2022-JP decoding error: invalid designation Dec 08 11:12:05 2005 (8832) SHUNTING: 1134033124.1110449+22e27c8eb18c70264c17eb27d07146812a8c656c I can present the letter that causes this error (I didn't find how is it possible to attach a file here). ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2005-11-22 22:00 Message: Logged In: YES user_id=1123998 gray-john wrote: > >I'm seeing this in 2.1.6 as well. We are running Debian >Sarge. Any word on getting this resolved? This error was fixed in source in 2.1.6 by catching and passing the UnicodeError exception. See bug 909490 which is the same problem. If you are seeing this error in 2.1.6, it must be coming from somewhere other than CommandRunner calling make_header. I suggest you try to get a resolution by posting your specific error trace to mailman-users(a)python.org. I'm closing this report. ---------------------------------------------------------------------- Comment By: John Gray (gray-john) Date: 2005-11-22 15:31 Message: Logged In: YES user_id=392368 I'm seeing this in 2.1.6 as well. We are running Debian Sarge. Any word on getting this resolved? ---------------------------------------------------------------------- Comment By: Tommi Tervo (tomtervo) Date: 2004-07-30 06:42 Message: Logged In: YES user_id=1094436 Do you need some additional information for debugging this one, I've over 200 mails stuck on shunts. AFAIK this is quite fatal bug, emails just disappear and nobody gets notification. UnicodeDecodeError: 'ascii' codec can't decode byte 0xf6 in position 10: ordinal not in range(128) Mailman 2.1.5 and python 2.3.4 on Solaris 8. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=971957&group_i…

1 0

[ mailman-Bugs-971957 ] Uncaught runner exception
by SourceForge.net 08 Dec '05

08 Dec '05

Bugs item #971957, was opened at 2004-06-13 06:36 Message generated for change (Comment added) made by doctorchd You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=971957&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: mail delivery Group: 2.1 (stable) Status: Closed Resolution: Fixed Priority: 5 Submitted By: John Distler (jd_waverly) Assigned to: Nobody/Anonymous (nobody) Summary: Uncaught runner exception Initial Comment: In 2.1.5 Apparently some email message characters can crash the Runner.py. I have inserted $mailman in place of my mailman path in the message below from $mailman/logs/error Jun 12 01:25:48 2004 (16604) Uncaught runner exception: ASCII decoding error: ordinal not in range (128) Jun 12 01:25:48 2004 (16604) Traceback (most recent call last): File "$mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File $mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "$mailman/Mailman/Queue/CommandRunner.py", line 223, in _dispose res = Results(mlist, msg, msgdata) File "$mailman/Mailman/Queue/CommandRunner.py", line 77, in __init__ subj = make_header(decode_header (subj)).__unicode__() File "$mailman/pythonlib/email/Header.py", line 144, in make_header h.append(s, charset) File "$mailman/pythonlib/email/Header.py", line 272, in append ustr = unicode(s, incodec, errors) UnicodeError: ASCII decoding error: ordinal not in range (128) ---------------------------------------------------------------------- Comment By: chd (doctorchd) Date: 2005-12-08 12:12 Message: Logged In: YES user_id=1400126 mailman 2.1.6 on FreeBSD (default installation from ports collection) python-2.4.2 A letter with charset=ISO-2022-JP stopped a maillist. New letters are added to the digest but not get sent. logs/error: Dec 08 11:12:05 2005 (8832) Uncaught runner exception: ISO-2022-JP decoding error: invalid designation Dec 08 11:12:05 2005 (8832) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 92, in process send_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 133, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 331, in send_i18n_digests payload = unicode(payload, mcset, 'replace' UnicodeError: ISO-2022-JP decoding error: invalid designation Dec 08 11:12:05 2005 (8832) SHUNTING: 1134033124.1110449+22e27c8eb18c70264c17eb27d07146812a8c656c I can present the letter that causes this error (I didn't find how is it possible to attach a file here). ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2005-11-23 08:00 Message: Logged In: YES user_id=1123998 gray-john wrote: > >I'm seeing this in 2.1.6 as well. We are running Debian >Sarge. Any word on getting this resolved? This error was fixed in source in 2.1.6 by catching and passing the UnicodeError exception. See bug 909490 which is the same problem. If you are seeing this error in 2.1.6, it must be coming from somewhere other than CommandRunner calling make_header. I suggest you try to get a resolution by posting your specific error trace to mailman-users(a)python.org. I'm closing this report. ---------------------------------------------------------------------- Comment By: John Gray (gray-john) Date: 2005-11-23 01:31 Message: Logged In: YES user_id=392368 I'm seeing this in 2.1.6 as well. We are running Debian Sarge. Any word on getting this resolved? ---------------------------------------------------------------------- Comment By: Tommi Tervo (tomtervo) Date: 2004-07-30 16:42 Message: Logged In: YES user_id=1094436 Do you need some additional information for debugging this one, I've over 200 mails stuck on shunts. AFAIK this is quite fatal bug, emails just disappear and nobody gets notification. UnicodeDecodeError: 'ascii' codec can't decode byte 0xf6 in position 10: ordinal not in range(128) Mailman 2.1.5 and python 2.3.4 on Solaris 8. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=971957&group_i…

1 0

[ mailman-Bugs-1363422 ] Valid E-mails Rejected as Invalid
by SourceForge.net 05 Dec '05

05 Dec '05

Bugs item #1363422, was opened at 2005-11-21 21:26 Message generated for change (Comment added) made by krellis You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1363422&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: 7 Submitted By: Tim Wilde (krellis) Assigned to: Nobody/Anonymous (nobody) Summary: Valid E-mails Rejected as Invalid Initial Comment: I ran into a problem recently with sync_members. I was attempting to add a list of addresses that included "---tim---(a)krellis.org", but this address was rejected: bin/sync_members -a=no -f /usr/local/mailinglists/lists/system-status.txt system-status Invalid : ---tim---(a)krellis.org You must fix the preceding invalid addresses first. While this is an ODD address, it is perfectly legal, per section 3.4 of RFC 2822 (http://www.faqs.org/rfcs/rfc2822.html). Rejecting a valid address like this seems like a pretty major problem to me. This was with MailMan 2.1.6 on FreeBSD 4. If there is any more information I can provide, please let me know. Regards, Tim Wilde ---------------------------------------------------------------------- >Comment By: Tim Wilde (krellis) Date: 2005-12-05 15:57 Message: Logged In: YES user_id=1021966 This appears to be a problem with line 210 of Utils.py, in the ValidateEmail function: if _badchars.search(s) or s[0] == '-': raise Errors.MMHostileAddress, s MailMan is explicitly rejecting e-mails that start with a hyphen. Why? This is a perfectly legal e-mail address. If MailMan is using e-mail addresses in such an unsafe way that they could be interpreted as command line arguments, that's just absurd. I can't see any other reason to forbid a leading hyphen, though. Can anyone tell me if I will be safe removing this check, or if MailMan will blow up elsewhere? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1363422&group_…

1 0

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

Mailman-coders December 2005