Yep, you guessed it.  And the patch worked.  Here's a header from one of those weird messages:
 
Return-Path: <>
X-Original-To: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
Received: by mail.mobius-soft.com (Postfix, from userid 417)
 id 19FE228297; Thu,  8 Jan 2004 22:16:03 -0600 (CST)
Received: from mx01.osn.de (mx01.osn.de [194.45.27.123])
 by mail.mobius-soft.com (Postfix) with SMTP id 9330128296
 for <[EMAIL PROTECTED]>; Thu,  8 Jan 2004 22:16:00 -0600 (CST)
Received: (qmail 22291 invoked for bounce); 9 Jan 2004 04:16:20 -0000
Date: 9 Jan 2004 04:16:20 -0000
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: failure notice
Message-Id: <[EMAIL PROTECTED]>
X-Primary-Address: [EMAIL PROTECTED]
X-Sanitizer: Mail Filtered by Anomy Sanitizer and SpamAssassin
X-Spam-Status: No, hits=0.3 required=6.0 tests=HTML_MESSAGE,
 HTML_TAG_BALANCE_BODY autolearn=no version=2.61
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on
 mail.mobius-soft.com
Status:  
 
 
I'm setting my bounce alias back to /dev/null now.  Thanks!
 
Andrea
 

----- Original Message -----
Sent: Thursday, January 08, 2004 1:41 PM
Subject: Re: File "./TMDA/Util.py", line 471, in confirm_append_address

"Andrea Whitlock" <[EMAIL PROTECTED]> writes:

> File "./TMDA/Util.py", line 471, in confirm_append_address
> ValueError: unpack list of wrong size
>
> I'm guessing it has to do with receiving bounced messages.  That's
> the only thing I think of where the envelope sender wouldn't have an
> @ to split on.

Looks like you might have found an obscure bug.  I only see it being
triggered when the incoming message has a null envelope sender (as in
the case of a bounce), AND it also contains an X-Primary-Address
header, which is just strange.

Can you apply the attached patch to your Util.py and see if that
helps?  Also, if this works, allowing the message to be delivered, can
you look at the headers and verify my above assumption?  Thanks.

_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users

Reply via email to