I'm getting this mysterious message when I send mail to the list. Contrary to what the message indicates, the mail still gets through. This may be the source of some double postings. I know it was for one of mine. Someone may want to look into this...
Thanks, Corey -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 02, 2002 2:00 AM To: [EMAIL PROTECTED] Subject: failure notice Hi. This is the qmail-send program at nagoya.betaversion.org. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. <[EMAIL PROTECTED]>: ezmlm-send: fatal: message already has a Mailing-List header (maybe I should be a sublist) (#5.7.2) ezmlm-gate: fatal: Fatal error from child --- Below this line is a copy of the message. Return-Path: <[EMAIL PROTECTED]> Received: (qmail 25622 invoked by uid 98); 2 Oct 2002 07:00:00 -0000 Delivered-To: [EMAIL PROTECTED] X-Antivirus: nagoya (v4218 created Aug 14 2002) Received: (qmail 25556 invoked from network); 2 Oct 2002 06:59:58 -0000 Received: from daedalus.apache.org (HELO apache.org) (63.251.56.142) by nagoya.betaversion.org with SMTP; 2 Oct 2002 06:59:58 -0000 Received: (qmail 51248 invoked by uid 500); 2 Oct 2002 06:59:04 -0000 Delivered-To: [EMAIL PROTECTED] Received: (qmail 51225 invoked from network); 2 Oct 2002 06:59:03 -0000 Received: from dialin-c1-35.129.187.keyaccess.nl (HELO topicus.nl) (195.35.129.187) by daedalus.apache.org with SMTP; 2 Oct 2002 06:59:03 -0000 Received: from pop.vuurwerk.nl ([62.250.3.109]) by topicus.nl ([]) with DomainPOP (MDaemon.PRO.v6.0.4.R) for <[EMAIL PROTECTED]>; Wed, 02 Oct 2002 08:58:43 +0200 Delivered-To: [EMAIL PROTECTED] Received: (qmail 51996 invoked by uid 25); 1 Oct 2002 20:21:02 -0000 Delivered-To: [EMAIL PROTECTED] X-Envelope-To: [EMAIL PROTECTED] Received: (qmail 51983 invoked from network); 1 Oct 2002 20:21:02 -0000 Received: from host-131-49-18-192.iplanet.com (HELO nagoya.betaversion.org) (192.18.49.131) by lust.vuurwerk.nl with SMTP; 1 Oct 2002 20:21:02 -0000 Received: (qmail 477 invoked by uid 97); 1 Oct 2002 20:21:40 -0000 Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm Precedence: bulk List-Unsubscribe: <mailto:[EMAIL PROTECTED]> List-Subscribe: <mailto:[EMAIL PROTECTED]> List-Help: <mailto:[EMAIL PROTECTED]> List-Post: <mailto:[EMAIL PROTECTED]> List-Id: "OJB Users List" <ojb-user.jakarta.apache.org> Reply-To: "OJB Users List" <[EMAIL PROTECTED]> Delivered-To: mailing list [EMAIL PROTECTED] Received: (qmail 465 invoked by uid 98); 1 Oct 2002 20:21:40 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <D1D9F6D8C301D411BA1C009027B211CA182C67@KCNT1> From: Corey Klaasmeyer <[EMAIL PROTECTED]> To: 'OJB Users List' <[EMAIL PROTECTED]> Subject: [OJBException] NestableException Not Serializable... Date: Tue, 1 Oct 2002 15:23:38 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-MDRemoteIP: 62.250.3.109 X-MDRcpt-To: [EMAIL PROTECTED] X-MDaemon-Deliver-To: [EMAIL PROTECTED] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N OJBExceptions never seem to make it back to the client, because they're not Serializable. Maybe Nestable classes in common-lang need to be Serializable? Corey -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
