Mailman-coders July 2003

mailman-coders@python.org

1 participants
39 discussions

[ mailman-Bugs-780171 ] "unknown encoding" in senddigests
by SourceForge.net 30 Jul '03

30 Jul '03

Bugs item #780171, was opened at 2003-07-30 14: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=780171&group_i… Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ervin Németh (nemethe) Assigned to: Nobody/Anonymous (nobody) Summary: "unknown encoding" in senddigests Initial Comment: Traceback (most recent call last): File "/usr/local/mailman/cron/senddigests", line 94, in ? main() File "/usr/local/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/usr/local/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 123, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 295, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 257, in process url = save_attachment(mlist, part, dir) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 348, in save_attachment fnext = os.path.splitext(msg.get_filename(''))[1] File "/usr/local/mailman/pythonlib/email/Message.py", line 689, in get_filename return unicode(newvalue[2], newvalue[0]) LookupError: unknown encoding ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=780171&group_i…

1 0

[ mailman-Bugs-780051 ] senddigests crashes when a whole message is discarded
by SourceForge.net 30 Jul '03

30 Jul '03

Bugs item #780051, was opened at 2003-07-30 16:25 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=780051&group_i… Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: senddigests crashes when a whole message is discarded Initial Comment: Traceback (most recent call last): File "/usr/local/mailman/cron/senddigests", line 94, in ? main() File "/usr/local/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/usr/local/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 179, in process raise DiscardMessage Mailman.Errors.DiscardMessage ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=780051&group_i…

1 0

[ mailman-Bugs-759842 ] Formatting archives that don't have newlines
by SourceForge.net 28 Jul '03

28 Jul '03

Bugs item #759842, was opened at 2003-06-24 09:23 Message generated for change (Comment added) made by phelim_gervase You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=759842&group_i… Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Pug Bainter (phelim_gervase) Assigned to: Nobody/Anonymous (nobody) Summary: Formatting archives that don't have newlines Initial Comment: I have a problem (mostly with M$ Outlook users) that when a user sends a message without newlines in it (because their email client auto-displays it "properly" for them), the message gets stored just like this in the archives as expected. The problem is that when the message gets pulled up in the webpages, they will appear as one long line instead of being formatted to the size of the browser width. ---------------------------------------------------------------------- >Comment By: Pug Bainter (phelim_gervase) Date: 2003-07-28 18:59 Message: Logged In: YES user_id=484284 Please note that the <PRE Width=80> doesn't seem to work for many Internet Explorer users. I think it is supported in IE 6.x and later. ---------------------------------------------------------------------- Comment By: Anthony Carter (karem_lore) Date: 2003-07-17 08:37 Message: Logged In: YES user_id=201573 Found the solution! In the file HyperArch.py in $mailmanhome/Mailman/Archiver search for <PRE> and replace it with <PRE Width=80> (change 80 to whatever you want). Anthony ---------------------------------------------------------------------- Comment By: Anthony Carter (karem_lore) Date: 2003-07-17 08:28 Message: Logged In: YES user_id=201573 Right, well removing the <PRE></PRE> tags in the file $mailman/Mailman/Archiver/HyperArch.py does not fix the problem. In fact, it makes it worse. However, I have yet to see if it is possible to substitute it with a tag that will dictate the width of the text. Will keep you posted. Anthony ---------------------------------------------------------------------- Comment By: Anthony Carter (karem_lore) Date: 2003-07-17 08:19 Message: Logged In: YES user_id=201573 I notice that the archiver uses a <PRE> and </PRE> around the article (from mailmanhome/templates/en/article.html. The PRE tag says that no formatting should occur as it is preformatted...I wonder what would happen if that PRE disappeared somehow... the text comes from whatever defines %(body)s in the Python code somewhere. This mus also defines the PRE tag as it is not in the template. Anthony ---------------------------------------------------------------------- Comment By: Anthony Carter (karem_lore) Date: 2003-07-17 08:06 Message: Logged In: YES user_id=201573 Yep, I have this too. Did you get any possible resolution to this? I guess it should not be too difficult to add this functionality (maybe within the mail2html part of the conversion) to add a limit on width (I think there may be a HTML possibility to enforce this). I don't know python, unfortunately, to go trapsing through the mailman code. I'll take a look though... Anthony Carter ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=759842&group_i…

1 0

[ mailman-Bugs-779230 ] SBC/SWBell bounces not being caught
by SourceForge.net 28 Jul '03

28 Jul '03

Bugs item #779230, was opened at 2003-07-28 18:39 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=779230&group_i… Category: bounce detection Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Pug Bainter (phelim_gervase) Assigned to: Nobody/Anonymous (nobody) Summary: SBC/SWBell bounces not being caught Initial Comment: This was reported in 2.0.x and closed. It is still a problem in 2.1.x. The two styles I've seen that aren't caught are: ========================================== Message from sbcglobal.net. Unable to deliver message to the following address(es). <morganavandya(a)sbcglobal.net>: Sorry, your message to morganavandya(a)sbcglobal.net cannot be delivered. This account is over quota. ========================================== and: ========================================== Message from swbell.net. Unable to deliver message to the following address(es). <khemail(a)swbell.net>: This user doesn't have a swbell.net account (khemail(a)swbell.net) [-9] ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=779230&group_i…

1 0

[ mailman-Bugs-778728 ] mm-handler: addresses are case-sensitive
by SourceForge.net 28 Jul '03

28 Jul '03

Bugs item #778728, was opened at 2003-07-28 04:00 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=778728&group_i… Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: mm-handler: addresses are case-sensitive Initial Comment: A message to List-request@listhost (capitalized) causes error message "Returned mail: List unknown": > Your mail for List-request@listhost could not be sent: > no list named "List" is known by listhost <<snip>> ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-07-28 17:14 Message: Logged In: YES user_id=75166 The Python version is see MM patch #644810 (not see MM patch #64481); sorry for the typo ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-07-28 17:10 Message: Logged In: YES user_id=75166 Changing line 200 of the mm-handler Perl script from: $list = $addr; to read: $list = lc $addr; will fix this problem. mm-handler is an unsupported contribution and has other potential problems which can lead to mail loss. There is an alernative Python implementation of this approach which is more tightly integrated with MM and does not have the same defects: see MM patch #64481 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=778728&group_i…

1 0

[ mailman-Bugs-778728 ] mm-handler: addresses are case-sensitive
by SourceForge.net 28 Jul '03

28 Jul '03

Bugs item #778728, was opened at 2003-07-28 04:00 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=778728&group_i… Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: mm-handler: addresses are case-sensitive Initial Comment: A message to List-request@listhost (capitalized) causes error message "Returned mail: List unknown": > Your mail for List-request@listhost could not be sent: > no list named "List" is known by listhost <<snip>> ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-07-28 17:10 Message: Logged In: YES user_id=75166 Changing line 200 of the mm-handler Perl script from: $list = $addr; to read: $list = lc $addr; will fix this problem. mm-handler is an unsupported contribution and has other potential problems which can lead to mail loss. There is an alernative Python implementation of this approach which is more tightly integrated with MM and does not have the same defects: see MM patch #64481 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=778728&group_i…

1 0

[ mailman-Patches-778929 ] templates/cs/listinfo.html: Small grammar fix
by SourceForge.net 28 Jul '03

28 Jul '03

Patches item #778929, was opened at 2003-07-28 13:44 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=778929&group_i… Category: internationalization Group: None Status: Open Resolution: None Priority: 5 Submitted By: Rudolf Cejka (cejkar) Assigned to: Nobody/Anonymous (nobody) Summary: templates/cs/listinfo.html: Small grammar fix Initial Comment: Changed prohlédnou to prohlédnout. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=778929&group_i…

1 0

[ mailman-Feature Requests-778815 ] Hide "other subscriptions" of members from owner
by SourceForge.net 28 Jul '03

28 Jul '03

Feature Requests item #778815, was opened at 2003-07-28 18:18 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=778815&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: Hide "other subscriptions" of members from owner Initial Comment: On Mailman-2.1.2, list owner(s) can view "List of other subscriptions" of list members accessing members' option pages. This seems not to be allowed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=778815&group_i…

1 0

[ mailman-Bugs-778728 ] mm-handler: addresses are case-sensitive
by SourceForge.net 28 Jul '03

28 Jul '03

Bugs item #778728, was opened at 2003-07-28 13:00 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=778728&group_i… Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: mm-handler: addresses are case-sensitive Initial Comment: A message to List-request@listhost (capitalized) causes error message "Returned mail: List unknown": > Your mail for List-request@listhost could not be sent: > no list named "List" is known by listhost <<snip>> ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=778728&group_i…

1 0

[ mailman-Bugs-778237 ] Invitations/Confirmations need expire info
by SourceForge.net 26 Jul '03

26 Jul '03

Bugs item #778237, was opened at 2003-07-26 17:58 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=778237&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: John A. Martin (jamux) Assigned to: Nobody/Anonymous (nobody) Summary: Invitations/Confirmations need expire info Initial Comment: Both subscription invitations and subscription confirmation messages fail to indicate when they will expire. Folks get confused when stale confirmations don't work. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=778237&group_i…

1 0

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

Mailman-coders July 2003