Re: message sent by detector has duplicate Message-Id header, rejected by SMTP server

----- Original Message -----
> From: "Cédric Krier" <[email protected]>
> To: [email protected]
> Sent: Thursday, August 20, 2015 11:53:20 PM
> Subject: Re: [Roundup-users] message sent by detector has duplicate Message-Id header, rejected by SMTP server
> 
> On 2015-08-20 16:01, Dan Tenenbaum wrote:
> > Hi,
> > 
> > (First of all, is this list still up? I saw some discussion of
> > moving it, and very little traffic. If the list is elsewhere,
> > please let me know where to go.)
> > 
> > OK, I am trying to switch to a new SMTP email server, one provided
> > by Amazon Simple Email Service (SES).
> > 
> > Messages sent by roundup to this server bounce back to me with the
> > error:
> > 
> > DetectorError: Error: couldn't send email: (554, "Transaction
> > failed: Duplicate header 'Message-ID'.")
> > 
> > If I instead arrange to have the same email sent to a mailcatcher
> > app so I can inspect the email, it does indeed have two
> > (identical) Message-Id headers (note the difference in case
> > between the actual headers and the error message (Message-Id vs.
> > Message-ID); not sure if it is significant).
> > 
> > Here is an example of the kind of email (with headers) that causes
> > this error, in between dashed lines. I've lightly edited some of
> > the identifying information.
> > 
> > You can see that the Message-Id header, with identical value,
> > appears twice.
> > 
> > This message is sent by the detector called nosyreaction.py which I
> > guess is a detector that is supplied with roundup. It may have
> > been modified slightly since we started using it.
> > 
> > I notice that the detector code has references to 'msgid' so I
> > wonder if this gets translated to a Message-Id header at some
> > point. This is the code for the unmodified version:
> > 
> > http://sourceforge.net/p/roundup/code/ci/default/tree/website/issues/detectors/nosyreaction.py
> > 
> > Any ideas for suppressing these duplicate headers?
> > 
> > This is with roundup 1.5.0.
> 
> I think it was fixed by
> http://issues.roundup-tracker.org/issue2550869
> 

I can confirm that fixes it.
Thanks,
Dan


> --
> Cédric Krier - B2CK SPRL
> Email/Jabber: [email protected]
> Tel: +32 472 54 46 59
> Website: http://www.b2ck.com/
> 
> ------------------------------------------------------------------------------
> 
> _______________________________________________
> Roundup-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/roundup-users
> 

------------------------------------------------------------------------------
_______________________________________________
Roundup-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/roundup-users