The mailing list for listmasters using Sympa

[David Verdin <address@concealed>]

You can tell Sympa to delete headers from outgoing or incoming messages. 
but the deletion is definitive. this is done using the remove_headers 
and remove_outgoing_headers list parameters.
If you remove it from outgoing messages, it is likely that these headers 
won't appear in the bounces anymore.

But there is probably a real bug in the way we are looking for the From: 
field in the bounced daemon.

I added a bug report regarding that in our tracker: 
http://sourcesup.cru.fr/tracker/index.php?func=detail&aid=6538&group_id=23&atid=167

I'll porcess it ASAP.

Regards,

David

Queen Brown a écrit :
> Ok, we received another occurrence of this behavior.  Following is the 
> bounce report that's triggering the issue.  The From field contains no 
> value. But the string in the X-header begins with the word "FROM".  
> Perhaps this is the conflict???
> -Queen
>
> ---------------------------
> X-Sympa-To: address@concealed
> Return-Path: <>
> X-Original-To: address@concealed
> Delivered-To: address@concealed
> Received: from mta.simmons.edu
>        by sympa.simmons.edu (Postfix) with ESMTP id ADD43AD60FE
>        for <address@concealed>; Tue, 27 Oct 2009 
> 16:50:17 -0400 (EDT)
> Received: from mta.simmons.edu (localhost.localdomain [127.0.0.1])
>        by localhost (Postfix) with SMTP id 9F984168473
>        for <address@concealed>; Tue, 27 Oct 2009 
> 16:50:17 -0400 (EDT)
> Received: from mail.necc.org
>        by mta.simmons.edu (Postfix) with SMTP id 49D75168442
>        for <address@concealed>; Tue, 27 Oct 2009 16:50:17 
> -0400 (EDT)
> X-CheckPoint: {4AE75D00-10B-3018C86-7B6}
> From: <>
> To: address@concealed
> Subject: Returned mail: unreachable recipients:address@concealed
> Date: Tue, 27 Oct 2009 16:46:20 -0400
> MIME-Version: 1.0
> Content-Type: multipart/mixed;
>        boundary="----=_NextPart_1256676380"
> Message-Id: <address@concealed>
> X-PMX-Version: 5.5.8.383112, Antispam-Engine: 2.7.2.376379, 
> Antispam-Data: 2009.10.27.203924
> X-PerlMx-Spam: Gauge=XIIIIIIIII, Probability=19%, Report='
> FROM_NO_USER 2.1, BODY_SIZE_5000_5999 0, BODY_SIZE_7000_LESS 0, 
> BOUNCE_ENVELOPE 0, BOUNCE_FROM_NULL 0, BOUNCE_GENERIC 0,
> BOUNCE_NDR 0, BOUNCE_RFC822_ATTACH 0, BOUNCE_RFC822_ATTACH_COMBINED 0, 
> TO_NO_NAME 0, __BOUNCE_NDR_BODY_HIGH 0, __BOUNCE_ND
> R_SUBJECT_CONTAINS 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, 
> __CTYPE_MULTIPART 0, __CTYPE_MULTIPART_MIXED 0, __HAS_MSGID 0, __MIM
> E_VERSION 0, __RFC822_ATTACH 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, 
> __URI_NS '
>
> This is a multi-part message in MIME format.
>
> ------=_NextPart_1256676380
> Content-Type: text/plain;
>        charset="us-ascii"
> Content-Transfer-Encoding: 7bit
>
> The original message was received at Tue Oct 27 16:46:20 2009
>
> Likely reason for failure: 550 5.1.1 User unknown
> _____________________________________________________________
>
>
>
> David Verdin wrote:
> > Hi Queen,
> >
> > Sympa should not takt that X-headeer into account at all to define 
> > the sender of a messagee. Only the From field.
> > Could you please send us an example of message that produced such a log?
> >
> > Regards,
> >
> > David
> >
> > Queen Brown a écrit :
> > > Hi,
> > >
> > > We are running Sympa 5.4.3 and are having issues with extensive 
> > > logging by the Sympa bounced deamon.  Our logs are growing to 
> > > several Gigs every week.  The logs show that Sympa seems to be 
> > > attempting to create a file called:
> > >
> > > /home/sympa/bounce/<listname>/OTHER/FROM_NO_USER<String>
> > >
> > > where <String> contains the value of an X-header in the message.  
> > > This X-header is generated by our PureMessage antispam engine.  I'm 
> > > guessing that Sympa is interpreting this value as a recipient email 
> > > address and is trying to create the bounce directory containing the 
> > > name of the recipient/string.
> > > Is there any way to configure Sympa bounced to ignore this X-header 
> > > when determining recipient addresses?
> > > Following is more specific logging:
> > >
> > > Sep 20 04:23:05 sympa bounced[10746]: Cannot create 
> > > /address@concealed
> > > /OTHER/FROM_NO_USER%202.1%2c%20HTML_70_90%200.1%2c%20BODY_SIZE_10000_PLUS%200%2c%20BOUNCE_ENVELOPE% 
> > >
> > > 200%2c%20BOUNCE_FROM_NULL%200%2c%20BOUNCE_GENERIC%200%2c%20BOUNCE_NDR%200%2c%20BOUNCE_RFC822_ATTACH 
> > >
> > > %200%2c%20BOUNCE_RFC822_ATTACH_COMBINED%200%2c%20TO_NO_NAME%200%2c%20__BOUNCE_NDR_BODY_HIGH%200%2c% 
> > >
> > > 20__BOUNCE_NDR_SUBJECT_CONTAINS%200%2c%20__C230066_P5%200%2c%20__CT%200%2c%20__CTYPE_HAS_BOUNDARY%2 
> > >
> > > 00%2c%20__CTYPE_MULTIPART%200%2c%20__CTYPE_MULTIPART_MIXED%200%2c%20__FRAUD_419_CONTACT_NUM%200%2c% 
> > >
> > > 20__HAS_HTML%200%2c%20__HAS_MSGID%200%2c%20__HTML_FONT_BLUE%200%2c%20__HTML_MSWORD%200%2c%20__MIME_ 
> > >
> > > VERSION%200%2c%20__PHISH_SPEAR_GREETING%200%2c%20__RFC822_ATTACH%200%2c%20__SANE_MSGID%200%2c%20__S 
> > >
> > > TYLE_RATWARE_2%200%2c%20__TAG_EXISTS_HTML%200%2c%20__TO_MALFORMED_2%200%27 
> > >
> > >
> > >
> > > Sep 20 04:23:05 sympa bounced[10746]: error: no address found in 
> > > message from FROM_NO_USER 2.1, HTML_70_90 0.1, BODY_SIZE_10000_PLUS 
> > > 0, BOUNCE_ENVELOPE 0, BOUNCE_FROM_NULL 0, BOUNCE_GENERIC 0, 
> > > BOUNCE_NDR 0, BOUNCE_RFC822_ATTACH 0, BOUNCE_RFC822_ATTACH_COMBINED 
> > > 0, TO_NO_NAME 0, __BOUNCE_NDR_BODY_H
> > > IGH 0, __BOUNCE_NDR_SUBJECT_CONTAINS 0, __C230066_P5 0, __CT 0, 
> > > __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __CTYPE_MULTIPART_MIXED 
> > > 0, __FRAUD_419_CONTACT_NUM 0, __HAS_HTML 0, __HAS_MSGID 0, 
> > > __HTML_FONT_BLUE 0, __HTML_MSWORD 0, __MIME_VERSION 0, 
> > > __PHISH_SPEAR_GREETING 0, __RFC822_ATTACH 0, __SANE_MSGID 0, 
> > > __STYLE_RATWARE_2 0, __TAG_EXISTS_HTML 0, __TO_MALFORMED_2 0' for 
> > > list listname
> > >
> > > thanks,  Queen

--
David Verdin
Comité réseau des universités