Mailman 3 April 2005 - Mailman-coders

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

19 Aug '22

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-Feature Requests-1192175 ] provide filtered log access via web
by SourceForge.net 30 Apr '05

30 Apr '05

Feature Requests item #1192175, was opened at 2005-04-29 14:33 Message generated for change (Comment added) made by yaseppochi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1192175&group_… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Stephen J. Turnbull (yaseppochi) Assigned to: Nobody/Anonymous (nobody) Summary: provide filtered log access via web Initial Comment: ... and queuefile summary data, too! Suggested interface: new toplevel menu item for a TROUBLESHOOTING page. The page would contain query boxes for (a) logfiles and (b) queue summaries. The LOG QUERY would have a checkbox (not radio button) interface listing the available logs. Filters would include (a) timestamp range (b) general Python regexp at least. The QUEUE QUERY would have a checkbox listing the queues. Rather than have filters (at least at first) the QUEUE QUERY might just provide age distributions, say < 1 hour, < 5 hours, < 1 day, > 1 day for each requested queue. I'm of two minds as to whether an interface to access data about individual messages would be useful. The thing is, generally to do anything useful about the queues you need shell and privileged access to the host. It might be useful to have a MiniFAQ on this page that just points to the MFAQs on the FAQWizard. ---------------------------------------------------------------------- >Comment By: Stephen J. Turnbull (yaseppochi) Date: 2005-04-30 16:12 Message: Logged In: YES user_id=88738 As pointed out by Brad Knowles, Mailman can't unilaterally provide access to MTA queues. That will depend on the privileges the host gives to the list admins. It would be useful on the troubleshooting page to point to FAQs that help the list admins provide the MTA admins with the info they need to troubleshoot problems on the MTA side. For newbie list+MTA admins, pointers to the MTA mailing lists. ---------------------------------------------------------------------- Comment By: Stephen J. Turnbull (yaseppochi) Date: 2005-04-30 16:10 Message: Logged In: YES user_id=88738 As pointed out by Brad Knowles, Mailman can't unilaterally provide access to MTA queues. That will depend on the privileges the host gives to the list admins. It would be useful on the troubleshooting page to point to FAQs that help the list admins provide the MTA admins with the info they need to troubleshoot problems on the MTA side. For newbie list+MTA admins, pointers to the MTA mailing lists. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1192175&group_…

1 0

[ mailman-Feature Requests-1192175 ] provide filtered log access via web
by SourceForge.net 30 Apr '05

30 Apr '05

Feature Requests item #1192175, was opened at 2005-04-29 14:33 Message generated for change (Comment added) made by yaseppochi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1192175&group_… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Stephen J. Turnbull (yaseppochi) Assigned to: Nobody/Anonymous (nobody) Summary: provide filtered log access via web Initial Comment: ... and queuefile summary data, too! Suggested interface: new toplevel menu item for a TROUBLESHOOTING page. The page would contain query boxes for (a) logfiles and (b) queue summaries. The LOG QUERY would have a checkbox (not radio button) interface listing the available logs. Filters would include (a) timestamp range (b) general Python regexp at least. The QUEUE QUERY would have a checkbox listing the queues. Rather than have filters (at least at first) the QUEUE QUERY might just provide age distributions, say < 1 hour, < 5 hours, < 1 day, > 1 day for each requested queue. I'm of two minds as to whether an interface to access data about individual messages would be useful. The thing is, generally to do anything useful about the queues you need shell and privileged access to the host. It might be useful to have a MiniFAQ on this page that just points to the MFAQs on the FAQWizard. ---------------------------------------------------------------------- >Comment By: Stephen J. Turnbull (yaseppochi) Date: 2005-04-30 16:10 Message: Logged In: YES user_id=88738 As pointed out by Brad Knowles, Mailman can't unilaterally provide access to MTA queues. That will depend on the privileges the host gives to the list admins. It would be useful on the troubleshooting page to point to FAQs that help the list admins provide the MTA admins with the info they need to troubleshoot problems on the MTA side. For newbie list+MTA admins, pointers to the MTA mailing lists. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1192175&group_…

1 0

[ mailman-Patches-1192757 ] Mail Archive mirroring
by SourceForge.net 29 Apr '05

29 Apr '05

Patches item #1192757, was opened at 2005-04-29 14:59 Message generated for change (Comment added) made by marshman You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1192757&group_… Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Jeff Marshall (marshman) Assigned to: Nobody/Anonymous (nobody) Summary: Mail Archive mirroring Initial Comment: New third party archiving option that uses The Mail Archive. The implementation subscribes or unsubscribes the archive(a)mail-archive.com address from the subscriber list. This gives list admins an easy setup option to provide mirroring and searchable public archives. Patch is based on branch Release_2_1-maint version 2.1.6rc3. ---------------------------------------------------------------------- >Comment By: Jeff Marshall (marshman) Date: 2005-04-29 15:24 Message: Logged In: YES user_id=118832 Updated the patch to account for existing mailing lists that are still using the old archive(a)jab.org address, rather than the archive(a)mail-archive.com address. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1192757&group_…

1 0

[ mailman-Patches-1192757 ] Mail Archive mirroring
by SourceForge.net 29 Apr '05

29 Apr '05

Patches item #1192757, was opened at 2005-04-29 14:59 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=1192757&group_… Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Jeff Marshall (marshman) Assigned to: Nobody/Anonymous (nobody) Summary: Mail Archive mirroring Initial Comment: New third party archiving option that uses The Mail Archive. The implementation subscribes or unsubscribes the archive(a)mail-archive.com address from the subscriber list. This gives list admins an easy setup option to provide mirroring and searchable public archives. Patch is based on branch Release_2_1-maint version 2.1.6rc3. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1192757&group_…

1 0

[ mailman-Bugs-871050 ] Uncought runner exception: Empty module name
by SourceForge.net 29 Apr '05

29 Apr '05

Bugs item #871050, was opened at 2004-01-05 09:03 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=871050&group_i… Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Fernando Barajas (fbarajas) Assigned to: Nobody/Anonymous (nobody) Summary: Uncought runner exception: Empty module name Initial Comment: Hi! I run several lists on mailman, and all of the lists are working OK, but suddently one of them (named fc_general) stopped working, and I get the following in logs/error every time I try to post to the fc_general list: Jan 05 11:03:48 2004 (8451) Uncaught runner exception: Empty module name Jan 05 11:03:48 2004 (8451) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 89, in process send_digests(mlist, mboxfp) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests send_i18n_digests(mlist, mboxfp) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_dige sts msg = scrubber(mlist, msg) File "/home/mailman/Mailman/Handlers/Scrubber.py", line 308, in process t = t.encode(charset, 'replace') File "/var/tmp/python2-2.2.3- root/usr/lib/python2.2/encodings/__init__.py", li ne 51, in search_function ValueError: Empty module name Jan 05 11:03:48 2004 (8451) SHUNTING: 1073322225.130398+2e61b88872c9af343bce1927 de7443b7500f2622 The rest of my lists work correctly. I was using 2.1.2, but today I upgraded to 2.1.4 and it's still failing. What can I do? Thanks! ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2005-04-29 14:27 Message: Logged In: NO I also experienced a similar problem, but was able to fix it. In my case, it appears to have been related to a python version number: the qrunner program was running against one python version, but was actually using features defined in a later version. In my case, I had Python 2.2 installed with the operating system, but had subsequently installed version 2.4.1. I fixed the problem by re-installing mailman with an explicit reference to the later python version (./configure --with-python=...), and then rebooting the system. After that, it was fine. (The reboot was to get qrunner running against the later python version: it seemed the old version was running whatever I might do with chkconfig or /etc/init.d/mailman. Rebooting was maybe a sledgehammer to crack a nut.) ---------------------------------------------------------------------- Comment By: James Hammett (james968) Date: 2005-03-14 07:32 Message: Logged In: YES user_id=310971 Running version 2.1.2. I get : Mar 14 09:30:49 2005 (28471) Traceback (most recent call last): File "/usr/share/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/share/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/share/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/share/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/share/mailman/Mailman/Handlers/ToDigest.py", line 89, in process send_digests(mlist, mboxfp) File "/usr/share/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/share/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/share/mailman/Mailman/Handlers/Scrubber.py", line 308, in process t = t.encode(charset, 'replace') File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/ python2.3/encodings/__init__.py", line 84, in search_function globals(), locals(), _import_tail) ValueError: Empty module name ---- I've attempted removing the digest files and cleaning them up, but this hasn't helped. ---------------------------------------------------------------------- Comment By: Charles Hall (hallcp) Date: 2004-08-02 10:34 Message: Logged In: YES user_id=747417 In my case the quick fix was to delete the existing "digest.mbox" file. (Look in ~mailman/lists/your_list/digest.mbox) I guess a bogus email snuck in there that breaks Python's character handling. Your digest subscribers will be unhappy but at least your list is up again. ---------------------------------------------------------------------- Comment By: Dan Langille (junkmale) Date: 2004-02-05 08:10 Message: Logged In: YES user_id=27858 I am having a simlar problem. Mail comes in, but never goes out to the list. Everthing is shunted. I found this "patch" http://www.mail-archive.com/mailman-developers@python. org/msg06317.html and applied it. Then I ran unshunt. That's when this appeared in mailman/logs/error Feb 05 07:57:07 2004 (27060) Dequeuing message destined for missing list: planners Feb 05 07:57:07 2004 (27060) Uncaught runner exception: Empty module name Feb 05 07:57:07 2004 (27060) 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/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 90, in process send_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 131, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 304, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 311, in process t = t.encode(charset, 'replace') File "/usr/local/lib/python2.3/encodings/__init__.py", line 84, in search_function globals(), locals(), _import_tail) ValueError: Empty module name ---------------------------------------------------------------------- Comment By: Jochen Witte (zebaoth) Date: 2004-01-27 03:09 Message: Logged In: YES user_id=565663 I use 2.1.3 and have the same problem. Any solution in sight? ---------------------------------------------------------------------- Comment By: Marcel Meyer (meyerm) Date: 2004-01-14 02:56 Message: Logged In: YES user_id=66911 Hi, was this somehow resolved?? I just found to have the same problems! What can I do that the messages (the shunt directory is now 1,5 MB big! [not the contents of the dir, but the dir inode itself...!!] ) are written into the archives without loosing anything? unshunt just puts them back into the shunt directory. Is there some patch - anything? Thanks a lot Marcel ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=871050&group_i…

1 0

[ mailman-Patches-1189243 ] Unhandle exception in Message.get_content_charset()
by SourceForge.net 29 Apr '05

29 Apr '05

Patches item #1189243, was opened at 2005-04-25 00:16 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1189243&group_… Category: None Group: Mailman 2.1 Status: Closed Resolution: Accepted Priority: 5 Submitted By: Jon Parise (jparise) Assigned to: Nobody/Anonymous (nobody) Summary: Unhandle exception in Message.get_content_charset() Initial Comment: Message.get_content_charset() can encounter an unhandled exception "(TypeError: unicode() argument 2 must be string, not None") when charset is None. This can can only occur when the call to email.Message.Message.get_content_charset(self, failobj) itself returns None, but, not being acquainted with the email package, I don't understand the circumstances which can cause this situation. Regardless, when charset is None, the call to unicode() will throw the TypeError exception. The attached patch recognizes this as a valid failure case such that failobj will be returned. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-04-29 09:30 Message: Logged In: YES user_id=12800 Tokio, I don't like having duplicate code, so I think it's best to fix the problem in one place and not keep the workaround in Mailman's copy. I've installed email 2.5.6 now and will release Mailman 2.1.6rc3 in a little while. At my own site, all the shunted messages that were broken because of this problem have now been fixed and properly unshunted. I will be updating python.org hopefully this weekend. Let's give rc3 a couple of weeks to shake out. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-04-28 20:02 Message: Logged In: YES user_id=67709 Barry, TypeError is already avoided in email package by this statement: pcharset = charset[0] or 'us-ascii' I want to keep the latter try/except in Mailman/Message.py to assure the charset is known to mailman so that it can serve as security precaution to future mailman code changes, even after the email package is updated to 2.5.6. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-04-25 13:02 Message: Logged In: YES user_id=12800 If it's not too much trouble. I'd love to have a test case in the email package for the TypeError exception. If you can't, no worries. ---------------------------------------------------------------------- Comment By: Jon Parise (jparise) Date: 2005-04-25 11:46 Message: Logged In: YES user_id=485579 Sorry, I don't. Those messages were unshunted as a result of my fix. I could try to instrument a collection mechanism by trapping that exception and storing a copy of the offensive message, however. Would that still be useful? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-04-25 10:32 Message: Logged In: YES user_id=12800 Is there any possibility that you have a sample message that exhibits this problem? I would /really/ like to add a test case for this to the email package, which is where the patch really belongs. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-04-25 00:50 Message: Logged In: YES user_id=67709 Thank you! I just fixed in CVS. (I'd rather make it bare except ...) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1189243&group_…

1 0

[ mailman-Feature Requests-1192175 ] provide filtered log access via web
by SourceForge.net 29 Apr '05

29 Apr '05

Feature Requests item #1192175, was opened at 2005-04-29 14:33 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=1192175&group_… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Stephen J. Turnbull (yaseppochi) Assigned to: Nobody/Anonymous (nobody) Summary: provide filtered log access via web Initial Comment: ... and queuefile summary data, too! Suggested interface: new toplevel menu item for a TROUBLESHOOTING page. The page would contain query boxes for (a) logfiles and (b) queue summaries. The LOG QUERY would have a checkbox (not radio button) interface listing the available logs. Filters would include (a) timestamp range (b) general Python regexp at least. The QUEUE QUERY would have a checkbox listing the queues. Rather than have filters (at least at first) the QUEUE QUERY might just provide age distributions, say < 1 hour, < 5 hours, < 1 day, > 1 day for each requested queue. I'm of two minds as to whether an interface to access data about individual messages would be useful. The thing is, generally to do anything useful about the queues you need shell and privileged access to the host. It might be useful to have a MiniFAQ on this page that just points to the MFAQs on the FAQWizard. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1192175&group_…

1 0

[ mailman-Patches-1189243 ] Unhandle exception in Message.get_content_charset()
by SourceForge.net 29 Apr '05

29 Apr '05

Patches item #1189243, was opened at 2005-04-25 04:16 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1189243&group_… Category: None Group: Mailman 2.1 Status: Closed Resolution: Accepted Priority: 5 Submitted By: Jon Parise (jparise) Assigned to: Nobody/Anonymous (nobody) Summary: Unhandle exception in Message.get_content_charset() Initial Comment: Message.get_content_charset() can encounter an unhandled exception "(TypeError: unicode() argument 2 must be string, not None") when charset is None. This can can only occur when the call to email.Message.Message.get_content_charset(self, failobj) itself returns None, but, not being acquainted with the email package, I don't understand the circumstances which can cause this situation. Regardless, when charset is None, the call to unicode() will throw the TypeError exception. The attached patch recognizes this as a valid failure case such that failobj will be returned. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-04-29 00:02 Message: Logged In: YES user_id=67709 Barry, TypeError is already avoided in email package by this statement: pcharset = charset[0] or 'us-ascii' I want to keep the latter try/except in Mailman/Message.py to assure the charset is known to mailman so that it can serve as security precaution to future mailman code changes, even after the email package is updated to 2.5.6. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-04-25 17:02 Message: Logged In: YES user_id=12800 If it's not too much trouble. I'd love to have a test case in the email package for the TypeError exception. If you can't, no worries. ---------------------------------------------------------------------- Comment By: Jon Parise (jparise) Date: 2005-04-25 15:46 Message: Logged In: YES user_id=485579 Sorry, I don't. Those messages were unshunted as a result of my fix. I could try to instrument a collection mechanism by trapping that exception and storing a copy of the offensive message, however. Would that still be useful? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-04-25 14:32 Message: Logged In: YES user_id=12800 Is there any possibility that you have a sample message that exhibits this problem? I would /really/ like to add a test case for this to the email package, which is where the patch really belongs. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-04-25 04:50 Message: Logged In: YES user_id=67709 Thank you! I just fixed in CVS. (I'd rather make it bare except ...) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1189243&group_…

1 0

[ mailman-Bugs-1190404 ] Editing HTML/Text file option sets bad file permissions
by SourceForge.net 26 Apr '05

26 Apr '05

Bugs item #1190404, was opened at 2005-04-26 08:33 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=1190404&group_… Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Chris Candreva (ccandreva) Assigned to: Nobody/Anonymous (nobody) Summary: Editing HTML/Text file option sets bad file permissions Initial Comment: System is Solaris 8, gcc 3.4.0, python 2.4, Apache 1.3.33 On mailman 2.1.6rc1 and rc2, when I use the "Edit the HTML pages and text files" option, the directories and files created are mode 600 , owned by nobody.mailman . After this, subscriptions fail with a permissions error. Since the listname/en directory is unreadable, there is a permissions error for the e-mail script that tries to send a confirmation message back to the user. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1190404&group_…

1 0