[Mailman-Developers] [Fwd: Thread-SIG member |"nouser" bouncing - NOT disabled]
Greg Stein
gstein@lyra.org
Thu, 03 Dec 1998 09:51:54 -0800
This is a multi-part message in MIME format.
--------------F7A1105FD490855F4A52B7
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Note the erroneous "Content-Type:" in the first line of the message
body.
-g
--
Greg Stein, http://www.lyra.org/
--------------F7A1105FD490855F4A52B7
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Received: from ns1.lyra.org (root@ns1.lyra.org [208.192.43.10])
by svpal.svpal.org (8.9.0/8.9.0) with ESMTP id IAA06959
for <gstein@svpal.org>; Thu, 3 Dec 1998 08:16:49 -0800 (PST)
From: mailman-owner@python.org
Received: from python.org (parrot.python.org [132.151.1.90])
by ns1.lyra.org (8.8.5/8.8.5) with ESMTP id IAA00317
for <gstein@lyra.org>; Thu, 3 Dec 1998 08:16:12 -0800
Received: from python.org (localhost [127.0.0.1])
by python.org (8.9.1a/8.9.1) with ESMTP id LAA25438
for <gstein@lyra.org>; Thu, 3 Dec 1998 11:17:34 -0500 (EST)
Received: from python.org (localhost [127.0.0.1])
by python.org (8.9.1a/8.9.1) with ESMTP id LAA25428
for <thread-sig-admin@python.org>; Thu, 3 Dec 1998 11:17:29 -0500 (EST)
Date: Thu, 3 Dec 1998 11:17:29 -0500 (EST)
Message-Id: <199812031617.LAA25428@python.org>
Subject: Thread-SIG member |"nouser" bouncing - NOT disabled
To: thread-sig-admin@python.org
Errors-To: mailman-owner@python.org
MIME-version: 1.0
Content-type: multipart/mixed; boundary="132.151.1.90.1.25425.912701849.264.14506"
List-Id: SIG on Process Threading in Python <thread-sig.python.org>
X-Mailman-Version: 1.0b7
This MIME message should be readable as plain text.
--132.151.1.90.1.25425.912701849.264.14506
Content-type: text/plain; charset=us-ascii
This is a Mailman mailing list bounce action notice:
List: Thread-SIG
Member: |"nouser"
Action: Subscription not disabled.
Reason: Excessive or fatal bounces.
BUT: User not found.
The triggering bounce notice is attached below.
Questions? Contact the Mailman site administrator at
mailman-owner@python.org.
--132.151.1.90.1.25425.912701849.264.14506
Content-type: text/plain; charset=us-ascii
Received: from koro.off.connect.com.au (koro.off.connect.com.au [192.94.41.1])
by python.org (8.9.1a/8.9.1) with ESMTP id LAA25422
for <thread-sig-admin@python.org>; Thu, 3 Dec 1998 11:17:25 -0500 (EST)
Received: from localhost (localhost) by koro.off.connect.com.au with internal id DAA20027
(8.8.8/IDA-1.6); Fri, 4 Dec 1998 03:17:02 +1100 (EST)
Date: Fri, 4 Dec 1998 03:17:02 +1100 (EST)
From: Mail Delivery Subsystem <MAILER-DAEMON@connect.com.au>
Subject: Returned mail: User unknown
Message-ID: <199812031617.DAA20027@koro.off.connect.com.au>
To: <thread-sig-admin@python.org>
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
boundary="DAA20027.912701822/koro.off.connect.com.au"
Auto-Submitted: auto-generated (failure)
This is a MIME-encapsulated message
--DAA20027.912701822/koro.off.connect.com.au
The original message was received at Fri, 4 Dec 1998 03:17:00 +1100 (EST)
from yarrina.connect.com.au [192.189.54.17]
----- The following addresses had permanent fatal errors -----
|"nouser"
(expanded from: nouser)
----- Transcript of session follows -----
This username is no longer valid at connect.com.au.
If you have a billing enquiry, please send mail to bills@connect.com.au.
If you have a sales enquiry, please send mail to sales@connect.com.au.
If you have a support enquiry, please send mail to support@connect.com.au.
Alternatively, you can call +61 3 9251 3600.
Thankyou.
550 |"nouser"... User unknown
--DAA20027.912701822/koro.off.connect.com.au
Content-Type: message/delivery-status
Reporting-MTA: dns; koro.off.connect.com.au
Received-From-MTA: dns; yarrina.connect.com.au
Arrival-Date: Fri, 4 Dec 1998 03:17:00 +1100 (EST)
Final-Recipient: rfc822; <arb@connect.com.au>
X-Actual-Recipient: rfc822; |nouser@koro.off.connect.com.au
Action: failed
Status: 5.1.1
Last-Attempt-Date: Fri, 4 Dec 1998 03:17:01 +1100 (EST)
--DAA20027.912701822/koro.off.connect.com.au
Content-Type: message/rfc822
Return-Path: <thread-sig-admin@python.org>
Received: from yarrina.connect.com.au (yarrina.connect.com.au [192.189.54.17]) by koro.off.connect.com.au with ESMTP id DAA20025
(8.8.8/IDA-1.6); Fri, 4 Dec 1998 03:17:00 +1100 (EST)
Received: from python.org (parrot.python.org [132.151.1.90]) by yarrina.connect.com.au with ESMTP id DAA25046
(8.8.8/IDA-1.7); Fri, 4 Dec 1998 03:16:58 +1100 (EST)
Received: from python.org (localhost [127.0.0.1])
by python.org (8.9.1a/8.9.1) with ESMTP id LAA25400;
Thu, 3 Dec 1998 11:16:33 -0500 (EST)
Received: from orinoco.cisco.com (orinoco.cisco.com [171.71.125.34])
by python.org (8.9.1a/8.9.1) with ESMTP id LAA25379
for <thread-sig@python.org>; Thu, 3 Dec 1998 11:16:23 -0500 (EST)
Received: from scothrel-pc (dhcp-sat-125-165.cisco.com [171.71.125.165]) by orinoco.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with SMTP id KAA06263; Thu, 3 Dec 1998 10:15:19 -0600 (CST)
Message-ID: <000801be1ed7$e2d1ba30$a57d47ab@scothrel-pc.cisco.com>
From: "Scott Cothrell" <scothrel@cisco.com>
To: "Guido VanRossum" <guido@cnri.reston.va.us>
Cc: <thread-sig@python.org>
Subject: Re: [Thread-SIG] Re: Losing file output in C Python on NT
Date: Thu, 3 Dec 1998 10:13:38 -0600
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3155.0
X-MIMEOLE: Produced By Microsoft MimeOLE V4.72.3155.0
Sender: thread-sig-admin@python.org
List-Id: SIG on Process Threading in Python <thread-sig.python.org>
Errors-To: thread-sig-admin@python.org
X-BeenThere: thread-sig@python.org
X-Mailman-Version: 1.0b7
>Thanks for posting. I bet this was the "unqualified 'except:' clause"
>that I warned you about...
Actually, it wasn't. The global except clause was intentional and was/is
doing what we wanted. It was a mistyped variable name.
>
>I have little to comment on the rest of your post -- I'm not sure why
>having too many threads would close your sockets, although when the
>machine is too heavily loaded, anything can happen -- we've seen this
>at CNRI with stress tests from Python as well.
We are not at all sure whats going on with the sockets shutting down. The
going bet is buffer overflow from too little service time. Its not a big
deal since we can tune to it.
>
>--Guido van Rossum (home page: http://www.python.org/~guido/)
>
_______________________________________________
Thread-SIG maillist - Thread-SIG@python.org
http://www.python.org/mailman/listinfo/thread-sig
--DAA20027.912701822/koro.off.connect.com.au--
--132.151.1.90.1.25425.912701849.264.14506--
--------------F7A1105FD490855F4A52B7--