Mailman 3 July 2003 - Mailman-coders

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

17 Jul '03

Bugs item #759842, was opened at 2003-06-24 16:23 Message generated for change (Comment added) made by karem_lore 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: Anthony Carter (karem_lore) Date: 2003-07-17 15: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 15: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 15: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 15: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-759842 ] Formatting archives that don't have newlines
by SourceForge.net 17 Jul '03

17 Jul '03

Bugs item #759842, was opened at 2003-06-24 16:23 Message generated for change (Comment added) made by karem_lore 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: Anthony Carter (karem_lore) Date: 2003-07-17 15: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 15: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 15: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-759842 ] Formatting archives that don't have newlines
by SourceForge.net 17 Jul '03

17 Jul '03

Bugs item #759842, was opened at 2003-06-24 16:23 Message generated for change (Comment added) made by karem_lore 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: Anthony Carter (karem_lore) Date: 2003-07-17 15: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 15: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-759842 ] Formatting archives that don't have newlines
by SourceForge.net 17 Jul '03

17 Jul '03

Bugs item #759842, was opened at 2003-06-24 16:23 Message generated for change (Comment added) made by karem_lore 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: Anthony Carter (karem_lore) Date: 2003-07-17 15: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-Patches-657951 ] Generate RSS summary in archives
by SourceForge.net 15 Jul '03

15 Jul '03

Patches item #657951, was opened at 2002-12-23 14:17 Message generated for change (Comment added) made by akuchling 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: A.M. Kuchling (akuchling) Date: 2003-07-15 14:55 Message: Logged In: YES user_id=11375 OK, done! This patch is now ready to go in: some people have looked at the RSS and haven't spotted any problems. Barry, can I please get CVS write access to check this in? ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2003-07-10 21:00 Message: Logged In: YES user_id=11375 Attaching correct version of the patch. ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2003-07-10 20:52 Message: Logged In: YES user_id=11375 Here at last is an updated version of the patch that's crawling closer to being complete. There's now a RSS_NUM_ARTICLES setting in Defaults.py, the generated URLs are correct, and I modified the English template to link to the RSS file. Remaining things: check the generated RSS for correctness; edit all of the other language templates to include the RSS file (I may ask for CVS write access to do that). It would be really nice if the Mailman upgrade script could update existing general list information pages to include the LINK element; any suggestion about how to go about that? ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 11:00 Message: Logged In: YES user_id=7830 OK, I've regenerated the patch with some code which works for me. http://rdfweb.org/2003/06/mailman-rss/rsspatch Health warning: * I suspect it may fail in conditions when get_archives() returns a list not a string (does this ever happen?). * See also problems mentioned below, regenerating partial archives seems tricky. Hope this is useful anyways... Dan <danbri(a)w3.org> ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 07:48 Message: Logged In: YES user_id=7830 I thought I'd have a look at this myself, though have modest knowledge of both Python and MailMan. In the course of trying to patch the patch, I tried running the archiver over just the last couple of messages, to speed things along: "../../bin/arch -s 4390 rdfweb-dev". Traceback (most recent call last): File "../../bin/arch", line 187, in ? main() File "../../bin/arch", line 177, in main archiver.close() File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 310, in close self.write_TOC() File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1082, in write_TOC rss.write(self.RSS()) File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 769, in RSS date, msgid = self.database.dateIndex.first() AttributeError: HyperDatabase instance has no attribute 'dateIndex' Not sure what's going on there, but this seemed as good a place of any to keep note of it. Investigating... ---------------------------------------------------------------------- Comment By: Dan Brickley (danbri) Date: 2003-06-22 07:04 Message: Logged In: YES user_id=7830 Does anyone have a patch to remove the hardwiring of "2002-December" and get the appropriate date from mailman somehow? ---------------------------------------------------------------------- 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…

1 0

[ mailman-Bugs-766667 ] failure at mailman/subscribe/{list-name}
by SourceForge.net 15 Jul '03

15 Jul '03

Bugs item #766667, was opened at 2003-07-06 15:28 Message generated for change (Comment added) made by iku You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=766667&group_i… Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ivan Kurmanov (iku) Assigned to: Nobody/Anonymous (nobody) Summary: failure at mailman/subscribe/{list-name} Initial Comment: Traceback (most recent call last): File "/var/lib/mailman/scripts/driver", line 87, in run_main main() File "/usr/lib/mailman/Mailman/Cgi/subscribe.py", line 96, in main process_form(mlist, doc, cgidata, language) File "/usr/lib/mailman/Mailman/Cgi/subscribe.py", line 176, in process_form mlist.AddMember(userdesc, remote) File "/var/lib/mailman/Mailman/MailList.py", line 831, in AddMember text=text, lang=lang) File "/var/lib/mailman/Mailman/Message.py", line 206, in __init__ errors='replace') TypeError: __init__() got an unexpected keyword argument 'errors' This is when I entered my email address, name, password, and clicked [subscribe]. This might be a misconfiguration, but it would be nice to know what exactly is wrong. Mailman version 2.1.2 ---------------------------------------------------------------------- >Comment By: Ivan Kurmanov (iku) Date: 2003-07-15 18:03 Message: Logged In: YES user_id=320488 Looks like this problem is *unstable* python problem. In my case fixed by installing a stable python version. ---------------------------------------------------------------------- Comment By: Bernhard Kuemel (darsie) Date: 2003-07-14 01:43 Message: Logged In: YES user_id=559942 The debian/unstable package 2.1.2-6 fixes both bugs. ---------------------------------------------------------------------- Comment By: Bernhard Kuemel (darsie) Date: 2003-07-14 01:27 Message: Logged In: YES user_id=559942 appearently the same bug exists for unsubscribing or requesting a password reminder. e.g. at http://bksys.at/mailman/listinfo/test I'll see if there is already an update for debian/testing that fixes the bug. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=766667&group_i…

1 0

[ mailman-Bugs-766667 ] failure at mailman/subscribe/{list-name}
by SourceForge.net 13 Jul '03

13 Jul '03

Bugs item #766667, was opened at 2003-07-06 14:28 Message generated for change (Comment added) made by darsie You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=766667&group_i… Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ivan Kurmanov (iku) Assigned to: Nobody/Anonymous (nobody) Summary: failure at mailman/subscribe/{list-name} Initial Comment: Traceback (most recent call last): File "/var/lib/mailman/scripts/driver", line 87, in run_main main() File "/usr/lib/mailman/Mailman/Cgi/subscribe.py", line 96, in main process_form(mlist, doc, cgidata, language) File "/usr/lib/mailman/Mailman/Cgi/subscribe.py", line 176, in process_form mlist.AddMember(userdesc, remote) File "/var/lib/mailman/Mailman/MailList.py", line 831, in AddMember text=text, lang=lang) File "/var/lib/mailman/Mailman/Message.py", line 206, in __init__ errors='replace') TypeError: __init__() got an unexpected keyword argument 'errors' This is when I entered my email address, name, password, and clicked [subscribe]. This might be a misconfiguration, but it would be nice to know what exactly is wrong. Mailman version 2.1.2 ---------------------------------------------------------------------- Comment By: Bernhard Kuemel (darsie) Date: 2003-07-14 00:43 Message: Logged In: YES user_id=559942 The debian/unstable package 2.1.2-6 fixes both bugs. ---------------------------------------------------------------------- Comment By: Bernhard Kuemel (darsie) Date: 2003-07-14 00:27 Message: Logged In: YES user_id=559942 appearently the same bug exists for unsubscribing or requesting a password reminder. e.g. at http://bksys.at/mailman/listinfo/test I'll see if there is already an update for debian/testing that fixes the bug. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=766667&group_i…

1 0

[ mailman-Bugs-766667 ] failure at mailman/subscribe/{list-name}
by SourceForge.net 13 Jul '03

13 Jul '03

Bugs item #766667, was opened at 2003-07-06 14:28 Message generated for change (Comment added) made by darsie You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=766667&group_i… Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ivan Kurmanov (iku) Assigned to: Nobody/Anonymous (nobody) Summary: failure at mailman/subscribe/{list-name} Initial Comment: Traceback (most recent call last): File "/var/lib/mailman/scripts/driver", line 87, in run_main main() File "/usr/lib/mailman/Mailman/Cgi/subscribe.py", line 96, in main process_form(mlist, doc, cgidata, language) File "/usr/lib/mailman/Mailman/Cgi/subscribe.py", line 176, in process_form mlist.AddMember(userdesc, remote) File "/var/lib/mailman/Mailman/MailList.py", line 831, in AddMember text=text, lang=lang) File "/var/lib/mailman/Mailman/Message.py", line 206, in __init__ errors='replace') TypeError: __init__() got an unexpected keyword argument 'errors' This is when I entered my email address, name, password, and clicked [subscribe]. This might be a misconfiguration, but it would be nice to know what exactly is wrong. Mailman version 2.1.2 ---------------------------------------------------------------------- Comment By: Bernhard Kuemel (darsie) Date: 2003-07-14 00:27 Message: Logged In: YES user_id=559942 appearently the same bug exists for unsubscribing or requesting a password reminder. e.g. at http://bksys.at/mailman/listinfo/test I'll see if there is already an update for debian/testing that fixes the bug. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=766667&group_i…

1 0

[ mailman-Bugs-770506 ] bounce mail not included in bounce action notification
by SourceForge.net 13 Jul '03

13 Jul '03

Bugs item #770506, was opened at 2003-07-13 14: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=770506&group_i… Category: bounce detection Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Bernhard Kuemel (darsie) Assigned to: Nobody/Anonymous (nobody) Summary: bounce mail not included in bounce action notification Initial Comment: Hi! Instead of the usual bounce message which tells the reason for the bounce (e.g. 'user over quota') on which a list moderator can decide whether to remove a user or not, this bounce action notification only includes the original list mail that was sent to the user. Since I have received proper bounce action notifications later this problem may occur only in a german setup or my mailman upgrade happened after this incident. I tried to provoke a bounce action notification with my test list but apperantly there must be bounces for some while before that happens. I only sent a number of mails within some 20 minutes. Return-path: <mailman-bounces(a)rainbow.hn.org> Envelope-to: bernhard(a)rainbow.bksys.at Delivery-date: Wed, 09 Jul 2003 12:01:10 +0200 Received: from mx0.gmx.de ([213.165.64.100] helo=mx0.gmx.net) by rainbow.bksys.at with smtp (Exim 3.36 #1 (Debian)) id 19aBl7-00063W-00 for <bernhard(a)rainbow.bksys.at>; Wed, 09 Jul 2003 12:01:09 +0200 Received: (qmail 22835 invoked by alias); 9 Jul 2003 10:00:39 -0000 Delivered-To: GMX delivery to darsie(a)gmx.at Received: (qmail 22648 invoked by uid 65534); 9 Jul 2003 10:00:38 -0000 Received: from rainbow.bksys.at (EHLO rainbow.bksys.at) (212.41.248.75) by mx0.gmx.net (mx004) with SMTP; 09 Jul 2003 12:00:38 +0200 Received: from s ([127.0.0.1] helo=rainbow.bksys.at ident=ident-is-useless) by rainbow.bksys.at with esmtp (Exim 3.36 #1 (Debian)) id 19aBk9-00063N-00 for <darsie(a)gmx.at>; Wed, 09 Jul 2003 12:00:09 +0200 Received: from s ([127.0.0.1] helo=rainbow.bksys.at ident=ident-is-useless) by rainbow.bksys.at with esmtp (Exim 3.36 #1 (Debian)) id 19aBk7-00063F-00 for <ac-owner(a)rainbow.bksys.at>; Wed, 09 Jul 2003 12:00:07 +0200 Subject: =?iso-8859-1?q?Bounce_action_notification?= From: mailman(a)rainbow.bksys.at To: ac-owner(a)rainbow.bksys.at MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============76570886680946471==" Message-ID: <mailman.1.1057744806.403.ac(a)rainbow.bksys.at> Date: Wed, 09 Jul 2003 12:00:06 +0200 Precedence: bulk X-BeenThere: ac(a)rainbow.bksys.at X-Mailman-Version: 2.1.1 List-Id: =?iso-8859-1?q?Austria_Circle_-_=D6sterreic?= =?iso-8859-1?q?hische_Rainbow_mailing_list?= <ac.rainbow.bksys.at> X-List-Administrivia: yes Sender: mailman-bounces(a)rainbow.hn.org Errors-To: mailman-bounces(a)rainbow.hn.org X-GMX-Antispam: 0 (Mail was not recognized as spam) X-Resent-By: Forwarder <forwarder(a)gmx.at> X-Resent-For: darsie(a)gmx.at X-Resent-To: bernhard(a)rainbow.bksys.at X-Spam-Status: No, hits=0.8 required=5.0 tests=MAILTO_WITH_SUBJ,NO_REAL_NAME version=2.55 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) --===============76570886680946471== Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Dies ist eine Mailman-Verst=E4ndigung betreffend die Unzustellbarkeit von Emails an eine bestimmte Adresse ("bounce"). Liste: AC Abonnent: c.vonwiller(a)utanet.at Vorgang: Abonnement disabled. Grund: Zu viele oder fatale Bounces = Die ausl=F6sende Nachricht ist weiter unten angeh=E4ngt. Fragen? Kontaktieren Sie den Mailman Systemverwalter unter mailman(a)rainbow.bksys.at. --===============76570886680946471== Content-Type: message/rfc822 MIME-Version: 1.0 From: ac-request(a)rainbow.bksys.at Subject: =?iso-8859-1?q?AC_Nachrichtensammlung=2C_Band_2=2C_Eintrag_5?= To: ac(a)rainbow.bksys.at Reply-To: ac(a)rainbow.bksys.at MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-BeenThere: ac(a)rainbow.bksys.at X-Mailman-Version: 2.1.1 Precedence: list List-Id: =?iso-8859-1?q?Austria_Circle_-_=D6sterreic?= =?iso-8859-1?q?hische_Rainbow_mailing_list?= <ac.rainbow.bksys.at> List-Unsubscribe: <http://rainbow.bksys.at/mailman/listinfo/ac>, <mailto:ac-request@rainbow.bksys.at?subject=unsubscribe> List-Archive: <http://rainbow.bksys.at/mailman/private/ac> List-Post: <mailto:ac@rainbow.bksys.at> List-Help: <mailto:ac-request@rainbow.bksys.at?subject=help> List-Subscribe: <http://rainbow.bksys.at/mailman/listinfo/ac>, <mailto:ac-request@rainbow.bksys.at?subject=subscribe> Sender: ac-bounces(a)rainbow.bksys.at Errors-To: ac-bounces(a)rainbow.bksys.at Um Emails an die Liste AC zu schicken, schicken Sie diese an die Adresse ac(a)rainbow.bksys.at Um sich via Web von der Liste zu entfernen oder draufzusetzen: http://rainbow.bksys.at/mailman/listinfo/ac oder, via Email, schicken Sie eine Email mit dem Wort 'help' in Subject/Betreff oder im Text an ac-request(a)rainbow.bksys.at Sie koennen den Listenverwalter dieser Lister unter der Adresse ac-owner(a)rainbow.bksys.at erreichen Wenn Sie antworten, bitte editieren Sie die Subject/Betreff auf einen sinnvollen Inhalt der spezifischer ist als "Re: Contents of AC digest..." Meldungen des Tages: 1. Re: AC Nachrichtensammlung, Band 2, Eintrag 4 (Hela Sattler) ---------------------------------------------------------------------- Message: 1 Date: Tue, 8 Jul 2003 12:07:20 +0200 From: "Hela Sattler" <hela(a)chello.at> Subject: [AC] Re: AC Nachrichtensammlung, Band 2, Eintrag 4 To: <ac(a)rainbow.bksys.at> Message-ID: <001d01c34538$b8672b40$c3adb23e@Hela> Content-Type: text/plain; charset=3D"iso-8859-1" Lieber Bernie! Es wird immer geheimnisvoller. Diese Mail habe ich heute erhalten: >----- Original Message ----- >From: <ac-request(a)rainbow.bksys.at> >To: <ac(a)rainbow.bksys.at> >Sent: Tuesday, July 08, 2003 12:00 PM >Subject: AC Nachrichtensammlung, Band 2, Eintrag 4 ---------------------------------------------------------------------------- ---- >Meldungen des Tages: >1. August (Raphael Wegmann) >2. Re: AC Nachrichtensammlung, Band 2, Eintrag 3 (earth1) ---------------------------------------------------------------------------- ---- ...Welchen Eintrag habe ich da gemacht??? Gr=FC=DFe an Sherlock Holmes Hela ------------------------------ -- = Die oesterreichische Rainbow Mailingliste: ac(a)rainbow.bksys.at http://rainbow.hn.org/mailman/listinfo/ac Ende AC Nachrichtensammlung, Band 2, Eintrag 5 ********************************************** --===============76570886680946471==-- ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=770506&group_i…

1 0

[ mailman-Bugs-769484 ] Creating mailman failure
by SourceForge.net 10 Jul '03

10 Jul '03

Bugs item #769484, was opened at 2003-07-11 00:44 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=769484&group_i… Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Barry Fawthrop (brif8) Assigned to: Nobody/Anonymous (nobody) Summary: Creating mailman failure Initial Comment: Bug in Mailman version 2.1.2 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/create.py", line 55, in main process_request(doc, cgidata) File "/usr/local/mailman/Mailman/Cgi/create.py", line 217, in process_request sys.modules[modname].create(mlist, cgi=1) File "/usr/local/mailman/Mailman/MTA/Postfix.py", line 232, in create _update_maps() File "/usr/local/mailman/Mailman/MTA/Postfix.py", line 53, in _update_maps raise RuntimeError, msg % (acmd, status, errstr) RuntimeError: command failed: /usr/sbin/postalias /usr/local/mailman/data/aliases (status: 1, Operation not permitted) Python information: ------------------------------- What is going on?? MTA = postfix ./configure --with-mail-gid=postfix --with-cgi-gid=nobody install went fine, followed all docs upto create list, and this failure?? Thanks Barry ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=769484&group_i…

1 0