Mailman-coders August 2008

mailman-coders@python.org

1 participants
15 discussions

[ 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-Bugs-2081096 ] Misleading text
by SourceForge.net 29 Aug '08

29 Aug '08

Bugs item #2081096, was opened at 2008-08-28 13:37 Message generated for change (Comment added) made by m1ss1ontomars You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2081096&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: None Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: m1ss1ontomars (m1ss1ontomars) Assigned to: Mark Sapiro (msapiro) Summary: Misleading text Initial Comment: Mailman is used at UC Berkeley for mailing list management. Unfortunately, many students (not me, obviously) are being confused by what appears to be a standard introductory text: "To post to this list, send your email to:" At least two people thought that they should send their email address to the given address in order to join the mailing list, thus spamming everyone on the list. I suggest that this be changed to: "To post to this list, send the email to:" Or basically anything other than what is currently standard. ---------------------------------------------------------------------- >Comment By: m1ss1ontomars (m1ss1ontomars) Date: 2008-08-28 21:10 Message: Logged In: YES user_id=1976087 Originator: YES Yeah, thanks; that sums it up nicely. At any rate I tried to send an email to whoever maintains Mailman; hopefully someone who can do something knows how to fix it. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2008-08-28 19:53 Message: Logged In: YES user_id=1123998 Originator: NO I assume you are talking about the text in the "welcome" email sent to new members. I will change this to "To post to this list, send your message to:" for Mailman 2.2. In the mean time, note that any list admin can change this text and anything else in the welcome email for the list by going to the list admin -> Edit the public HTML pages and text files link and editing the Welcome email text file. In addition, the Mailman site admin can follow the instructions at <http://wiki.list.org/x/jYA9> and make a site wide version of the subscribeack.txt template (the welcome message). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2081096&group_…

1 0

[ mailman-Bugs-2081096 ] Misleading text
by SourceForge.net 28 Aug '08

28 Aug '08

Bugs item #2081096, was opened at 2008-08-28 13:37 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2081096&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: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: m1ss1ontomars (m1ss1ontomars) >Assigned to: Mark Sapiro (msapiro) Summary: Misleading text Initial Comment: Mailman is used at UC Berkeley for mailing list management. Unfortunately, many students (not me, obviously) are being confused by what appears to be a standard introductory text: "To post to this list, send your email to:" At least two people thought that they should send their email address to the given address in order to join the mailing list, thus spamming everyone on the list. I suggest that this be changed to: "To post to this list, send the email to:" Or basically anything other than what is currently standard. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2008-08-28 19:53 Message: Logged In: YES user_id=1123998 Originator: NO I assume you are talking about the text in the "welcome" email sent to new members. I will change this to "To post to this list, send your message to:" for Mailman 2.2. In the mean time, note that any list admin can change this text and anything else in the welcome email for the list by going to the list admin -> Edit the public HTML pages and text files link and editing the Welcome email text file. In addition, the Mailman site admin can follow the instructions at <http://wiki.list.org/x/jYA9> and make a site wide version of the subscribeack.txt template (the welcome message). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2081096&group_…

1 0

[ mailman-Bugs-2081096 ] Misleading text
by SourceForge.net 28 Aug '08

28 Aug '08

Bugs item #2081096, was opened at 2008-08-28 13:37 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=2081096&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: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: m1ss1ontomars (m1ss1ontomars) Assigned to: Nobody/Anonymous (nobody) Summary: Misleading text Initial Comment: Mailman is used at UC Berkeley for mailing list management. Unfortunately, many students (not me, obviously) are being confused by what appears to be a standard introductory text: "To post to this list, send your email to:" At least two people thought that they should send their email address to the given address in order to join the mailing list, thus spamming everyone on the list. I suggest that this be changed to: "To post to this list, send the email to:" Or basically anything other than what is currently standard. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2081096&group_…

1 0

[ mailman-Bugs-2074653 ] error encoding
by SourceForge.net 25 Aug '08

25 Aug '08

Bugs item #2074653, was opened at 2008-08-25 17:57 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2074653&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: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Liu Junmin (openread) >Assigned to: Mark Sapiro (msapiro) Summary: error encoding Initial Comment: At /mailman-2.1.11rc2/templates/zh_CN/ have four file is gb2312 encoding, but correct encoding is UTF-8.The files is postack.txt postauth.txt postheld.txt unsub.txt This files can be using send wrong encoding message to user. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2008-08-25 20:12 Message: Logged In: YES user_id=1123998 Originator: NO Fixed in the Bazaar repository on Launchpad for the 2.1 and 2.2 branches. Thank you for your help. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2074653&group_…

1 0

[ mailman-Bugs-2074653 ] error encoding
by SourceForge.net 25 Aug '08

25 Aug '08

Bugs item #2074653, was opened at 2008-08-26 08:57 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=2074653&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: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Liu Junmin (openread) Assigned to: Nobody/Anonymous (nobody) Summary: error encoding Initial Comment: At /mailman-2.1.11rc2/templates/zh_CN/ have four file is gb2312 encoding, but correct encoding is UTF-8.The files is postack.txt postauth.txt postheld.txt unsub.txt This files can be using send wrong encoding message to user. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2074653&group_…

1 0

[ mailman-Bugs-2074453 ] allow message display to wrap (simple HTML provided)
by SourceForge.net 25 Aug '08

25 Aug '08

Bugs item #2074453, was opened at 2008-08-25 14:58 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2074453&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: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: S Page (skierpage) Assigned to: Nobody/Anonymous (nobody) Summary: allow message display to wrap (simple HTML provided) Initial Comment: I browse the archives of many mailing lists created by Mailman. I love its ASCII preformatted display, but many messages to mailing lists are not word-wrapped and so each paragraph appears as a few unreadably long lines. For example, http://lists.freedesktop.org/archives/xorg/2008-August/038178.html, and resize your browser window wider and narrower. Modern browsers support the CSS "white-space" property to display long lines wrapped to fit the window, see http://archivist.incutio.com/viewlist/css-discuss/55677 I modified the <pre> tag in that Mailman message to use this CSS style and it now displays fine (in Firefox 3.1a2 and MSIE7 on Windows XP), see http://www.skierpage.com/moz_bugs/pre_wrap_test.html , resize your browser window wider and narrower, and view its source. This *does not* affect copy and paste of long lines and does not involve processing or changing the text within the pre tag in any way. It just makes many more messages readable! The new pre tag is <pre style=" white-space: pre-wrap; /* css-3 should we be so lucky... */ white-space: -moz-pre-wrap; /* Mozilla, since 1999 */ white-space: -pre-wrap; /* Opera 4-6 ?? */ white-space: -o-pre-wrap; /* Opera 7 ?? */ word-wrap: break-word; /* Internet Explorer 5.5+ */ _white-space: pre; /* IE only hack to re-specify in addition to word-wrap */ "> Please consider making the change in a future Mailman release. In appreciation of your consideration I donated $10 to GNU Mailman. P.S. In order to pass strict validation, adding a style means you have to specify the HTML 4.01 Transitional DOCTYPE. I did in my modified file and passes 100%. According to validator.w3.org, the original DOCTYPE in Mailman's HTML output ( <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> ) is invalid anyway. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2008-08-25 17:32 Message: Logged In: YES user_id=1123998 Originator: NO Thank you for the suggested style. It looks promising. It is not clear to me whether you operate a Mailman site or are just a member of lists, but a site can easily accomplish what you've done by making site/language versions of the article.html template per <http://wiki.list.org/x/jYA9> with the following changes: Change the doctype declaration to <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> and add the following style in the <head> section <style type="text/css"> pre { white-space: pre-wrap; /* css-3 */ white-space: -moz-pre-wrap; /* Mozilla, since 1999 */ white-space: -pre-wrap; /* Opera 4-6 */ white-space: -o-pre-wrap; /* Opera 7 */ word-wrap: break-word; /* Internet Explorer 5.5+ */ _white-space: pre; /* IE only hack to re-specify in addition to word-wrap */ } </style> Of course the browser specific parts of the style don't pass validation at <http://jigsaw.w3.org/css-validator/> but that's not unexpected. Note however that the valid style <style type="text/css"> pre { white-space: pre-wrap; /* css-3 */ } </style> alone appears sufficient in Firefox 3.0.1, Opera 9.51 and Safari 3.1.2, but not in Camino 1.6.3 or MSIE 7.0 and adding white-space: -moz-pre-wrap; works in Camino. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2074453&group_…

1 0

[ mailman-Bugs-2074453 ] allow message display to wrap (simple HTML provided)
by SourceForge.net 25 Aug '08

25 Aug '08

Bugs item #2074453, was opened at 2008-08-25 14: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=2074453&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: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: S Page (skierpage) Assigned to: Nobody/Anonymous (nobody) Summary: allow message display to wrap (simple HTML provided) Initial Comment: I browse the archives of many mailing lists created by Mailman. I love its ASCII preformatted display, but many messages to mailing lists are not word-wrapped and so each paragraph appears as a few unreadably long lines. For example, http://lists.freedesktop.org/archives/xorg/2008-August/038178.html, and resize your browser window wider and narrower. Modern browsers support the CSS "white-space" property to display long lines wrapped to fit the window, see http://archivist.incutio.com/viewlist/css-discuss/55677 I modified the <pre> tag in that Mailman message to use this CSS style and it now displays fine (in Firefox 3.1a2 and MSIE7 on Windows XP), see http://www.skierpage.com/moz_bugs/pre_wrap_test.html , resize your browser window wider and narrower, and view its source. This *does not* affect copy and paste of long lines and does not involve processing or changing the text within the pre tag in any way. It just makes many more messages readable! The new pre tag is <pre style=" white-space: pre-wrap; /* css-3 should we be so lucky... */ white-space: -moz-pre-wrap; /* Mozilla, since 1999 */ white-space: -pre-wrap; /* Opera 4-6 ?? */ white-space: -o-pre-wrap; /* Opera 7 ?? */ word-wrap: break-word; /* Internet Explorer 5.5+ */ _white-space: pre; /* IE only hack to re-specify in addition to word-wrap */ "> Please consider making the change in a future Mailman release. In appreciation of your consideration I donated $10 to GNU Mailman. P.S. In order to pass strict validation, adding a style means you have to specify the HTML 4.01 Transitional DOCTYPE. I did in my modified file and passes 100%. According to validator.w3.org, the original DOCTYPE in Mailman's HTML output ( <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> ) is invalid anyway. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2074453&group_…

1 0

[ mailman-Bugs-2068642 ] 2.1.11.rc2 crash
by SourceForge.net 22 Aug '08

22 Aug '08

Bugs item #2068642, was opened at 2008-08-22 17:40 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2068642&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: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: measl (measl) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1.11.rc2 crash Initial Comment: While I know this *looks* like an error caused by having no space... [root@lists /usr/home/crippen/mailman/bin]# df -h Filesystem Size Used Avail Capacity Mounted on /dev/idad0s1a 14G 6.9G 5.6G 55% / devfs 1.0K 1.0K 0B 100% /dev [root@lists /var/log/mailman]# cat error Aug 22 01:00:00 lists newsyslog[66511]: logfile turned over Aug 22 09:54:05 2008 (72778) No such list "ccm-l<br><br>": Aug 22 17:56:06 2008 (60050) Uncaught runner exception: [Errno 28] No space left on device Aug 22 17:56:06 2008 (60050) Traceback (most recent call last): File "/usr/home/crippen/mailman/Mailman/Queue/Runner.py", line 120, in _oneloop self._onefile(msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/Runner.py", line 191, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/OutgoingRunner.py", line 130, in _dispose self.__retryq.enqueue(msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/Switchboard.py", line 138, in enqueue fp.write(msgsave) IOError: [Errno 28] No space left on device Aug 22 17:56:07 2008 (60050) Uncaught runner exception: [Errno 28] No space left on device Aug 22 17:56:07 2008 (60050) Traceback (most recent call last): File "/usr/home/crippen/mailman/Mailman/Queue/Runner.py", line 136, in _oneloop new_filebase = self._shunt.enqueue(msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/Switchboard.py", line 138, in enqueue fp.write(msgsave) IOError: [Errno 28] No space left on device Aug 22 17:56:07 2008 (60050) SHUNTING FAILED, preserving original entry: 1219445382.26142+9c9610d3ebaeef247239107563d4dc48eb1ca558 Aug 22 18:01:07 2008 (60050) Uncaught runner exception: [Errno 6] Device not configured Aug 22 18:01:07 2008 (60050) Traceback (most recent call last): File "/usr/home/crippen/mailman/Mailman/Queue/Runner.py", line 120, in _oneloop self._onefile(msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/Runner.py", line 191, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/OutgoingRunner.py", line 74, in _dispose self._func(mlist, msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Handlers/SMTPDirect.py", line 160, in process deliveryfunc(mlist, msg, msgdata, envsender, refused, conn) File "/usr/home/crippen/mailman/Mailman/Handlers/SMTPDirect.py", line 392, in bulkdeliver syslog('smtp-failure', 'Low level smtp error: %s, msgid: %s', e, msgid) File "/usr/home/crippen/mailman/Mailman/Logging/Syslog.py", line 43, in write self.write_ex(kind, msg, args, kws) File "/usr/home/crippen/mailman/Mailman/Logging/Syslog.py", line 62, in write_ex logf.write(msg + '\n') File "/usr/home/crippen/mailman/Mailman/Logging/StampedLogger.py", line 73, in write Logger.write(self, "%s %s" % (prefix, msg)) File "/usr/home/crippen/mailman/Mailman/Logging/Logger.py", line 94, in write _logexc(self, msg) File "/usr/home/crippen/mailman/Mailman/Logging/Utils.py", line 22, in _logexc sys.__stderr__.write('Logging error: %s\n' % logger) IOError: [Errno 6] Device not configured Aug 22 18:01:08 2008 (60050) SHUNTING: 1219445385.9258931+e43b5a83d97d6d0d8ab87a585adda24feec4785f Aug 22 18:57:19 2008 (60049) Uncaught runner exception: [Errno 28] No space left on device Aug 22 18:57:19 2008 (60049) Traceback (most recent call last): File "/usr/home/crippen/mailman/Mailman/Queue/Runner.py", line 120, in _oneloop self._onefile(msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/Runner.py", line 191, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/VirginRunner.py", line 38, in _dispose return IncomingRunner._dispose(self, mlist, msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/home/crippen/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Handlers/ToOutgoing.py", line 55, in process outq.enqueue(msg, msgdata, listname=mlist.internal_name()) File "/usr/home/crippen/mailman/Mailman/Queue/Switchboard.py", line 138, in enqueue fp.write(msgsave) admin(81551): ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2008-08-22 18:21 Message: Logged In: YES user_id=1123998 Originator: NO df notwithstanding, how is this a Mailman issue? Is it possible you're running into a user quota? In most of the above tracebacks, Mailman has successfully opened a tempfile to build a queue entry, and is denied by the OS with "[Errno 28] No space left on device". There's not much Mailman can do about that. In the case of the logging error, Mailman is attempting to write to the smtp-failure log and hits an IOError exception (possibly error 28) and tries to fall back to the original stderr which is probably the console that started Mailman and is long since detached from the process and gets the "[Errno 6] Device not configured" and logs that exception to the error log. The OS is not letting Mailman write to some files (but apparently the error log is OK). Mailman can't do anything about that. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2068642&group_…

1 0

[ mailman-Bugs-2068642 ] 2.1.11.rc2 crash
by SourceForge.net 22 Aug '08

22 Aug '08

Bugs item #2068642, was opened at 2008-08-22 19:40 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=2068642&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: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: measl (measl) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1.11.rc2 crash Initial Comment: While I know this *looks* like an error caused by having no space... [root@lists /usr/home/crippen/mailman/bin]# df -h Filesystem Size Used Avail Capacity Mounted on /dev/idad0s1a 14G 6.9G 5.6G 55% / devfs 1.0K 1.0K 0B 100% /dev [root@lists /var/log/mailman]# cat error Aug 22 01:00:00 lists newsyslog[66511]: logfile turned over Aug 22 09:54:05 2008 (72778) No such list "ccm-l<br><br>": Aug 22 17:56:06 2008 (60050) Uncaught runner exception: [Errno 28] No space left on device Aug 22 17:56:06 2008 (60050) Traceback (most recent call last): File "/usr/home/crippen/mailman/Mailman/Queue/Runner.py", line 120, in _oneloop self._onefile(msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/Runner.py", line 191, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/OutgoingRunner.py", line 130, in _dispose self.__retryq.enqueue(msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/Switchboard.py", line 138, in enqueue fp.write(msgsave) IOError: [Errno 28] No space left on device Aug 22 17:56:07 2008 (60050) Uncaught runner exception: [Errno 28] No space left on device Aug 22 17:56:07 2008 (60050) Traceback (most recent call last): File "/usr/home/crippen/mailman/Mailman/Queue/Runner.py", line 136, in _oneloop new_filebase = self._shunt.enqueue(msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/Switchboard.py", line 138, in enqueue fp.write(msgsave) IOError: [Errno 28] No space left on device Aug 22 17:56:07 2008 (60050) SHUNTING FAILED, preserving original entry: 1219445382.26142+9c9610d3ebaeef247239107563d4dc48eb1ca558 Aug 22 18:01:07 2008 (60050) Uncaught runner exception: [Errno 6] Device not configured Aug 22 18:01:07 2008 (60050) Traceback (most recent call last): File "/usr/home/crippen/mailman/Mailman/Queue/Runner.py", line 120, in _oneloop self._onefile(msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/Runner.py", line 191, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/OutgoingRunner.py", line 74, in _dispose self._func(mlist, msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Handlers/SMTPDirect.py", line 160, in process deliveryfunc(mlist, msg, msgdata, envsender, refused, conn) File "/usr/home/crippen/mailman/Mailman/Handlers/SMTPDirect.py", line 392, in bulkdeliver syslog('smtp-failure', 'Low level smtp error: %s, msgid: %s', e, msgid) File "/usr/home/crippen/mailman/Mailman/Logging/Syslog.py", line 43, in write self.write_ex(kind, msg, args, kws) File "/usr/home/crippen/mailman/Mailman/Logging/Syslog.py", line 62, in write_ex logf.write(msg + '\n') File "/usr/home/crippen/mailman/Mailman/Logging/StampedLogger.py", line 73, in write Logger.write(self, "%s %s" % (prefix, msg)) File "/usr/home/crippen/mailman/Mailman/Logging/Logger.py", line 94, in write _logexc(self, msg) File "/usr/home/crippen/mailman/Mailman/Logging/Utils.py", line 22, in _logexc sys.__stderr__.write('Logging error: %s\n' % logger) IOError: [Errno 6] Device not configured Aug 22 18:01:08 2008 (60050) SHUNTING: 1219445385.9258931+e43b5a83d97d6d0d8ab87a585adda24feec4785f Aug 22 18:57:19 2008 (60049) Uncaught runner exception: [Errno 28] No space left on device Aug 22 18:57:19 2008 (60049) Traceback (most recent call last): File "/usr/home/crippen/mailman/Mailman/Queue/Runner.py", line 120, in _oneloop self._onefile(msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/Runner.py", line 191, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/VirginRunner.py", line 38, in _dispose return IncomingRunner._dispose(self, mlist, msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/home/crippen/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/home/crippen/mailman/Mailman/Handlers/ToOutgoing.py", line 55, in process outq.enqueue(msg, msgdata, listname=mlist.internal_name()) File "/usr/home/crippen/mailman/Mailman/Queue/Switchboard.py", line 138, in enqueue fp.write(msgsave) admin(81551): ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=2068642&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 August 2008