Script agent creates MIME part for outbound email, then Router adds another set of SMTP headers

Script agent running on server creates a document Form=“Memo” and creates a field Set body = outMemo.CreateMIMEEntity(“body”)

Headers are created:

Set thishead = body.CreateHeader(hn)

values are set:

Call thishead.SetHeaderValAndParams(hv)

The body gets some content:

Call body.SetContentFromText(stream, “text/html;charset=”+EMmimecs, ENC_NONE)

The email is sent:

Call outMemo.send(False)

Viewed in the server’s mail.box the headers are OK:

The first “blob” or “body” item is:

Content-Transfer-Encoding: 7bit

To: dontspamme@cbdweb.net

Subject: Quote - Joint Venture

Date: Thu, 2 Oct 2008 11:14:13 +1000

Message-ID: 31c701c9242c$2e691790$1e1ea8c0@ACI.Internal

From: V@a.com.au

Content-Class: urn:content-classes:message

MIME-Version: 1.0

Thread-Index: AckkLC5kOVVopss2T8GZCoIhNNpz2w==

ReplyTo: V@A.com.au

X-Notes-Item: Memo; name=FORM

Content-Type: multipart/mixed;

boundary=“emailSMARTs-z65Bey”

This is a multi-part message in MIME format.

Then we have text/html part, other parts etc.

Once the router gets hold of it and sends the email out to the internet, it looks like this (on our outbound relay server - a@a.com.au is the agent signer’s internet address)

Return-Path: a@a.com.au

Delivered-To: bad-header-quarantine

X-Envelope-From: a@a.com.au

X-Envelope-To: dontspamme@cbdweb.net

X-Quarantine-ID: <1vpVaeu-5BNf>

X-Amavis-Alert: BAD HEADER Duplicate header field: “Date”

Received: from mx.a.com.au ([127.0.0.1])

    by localhost (mx.a.com.au [127.0.0.1]) (amavisd-new, port 10024)

    with ESMTP id 1vpVaeu-5BNf for <dontspamme@cbdweb.net>;

    Thu,  2 Oct 2008 11:29:00 +1000 (EST)

Received: from melbnotes01.ACI.Internal (m.a.internal [192.168.30.31])

    by mx.a.com.au (Postfix) with ESMTP id AF8591D8492

    for <dontspamme@cbdweb.net>; Thu,  2 Oct 2008 11:28:59 +1000 (EST)

Subject: Quote - Joint Venture

Content-Class: urn:content-classes:message

MIME-Version: 1.0

Thread-Index: AckkLC5kOVVopss2T8GZCoIhNNpz2w==

ReplyTo: V@A.com.au

From: A Mail a@a.com.au

To: dontspamme@cbdweb.net

Message-ID: OF985E9F7D.FA19CEEF-ONCA2574D6.00074AB4-CA2574D6.00074BBF@a.com.au

Date: Thu, 2 Oct 2008 11:19:41 +1000

X-MIMETrack: Itemize by Agent Manager on melbnotes01/Agricola(Release 7.0.3|September 26, 2007) at

02/10/2008 11:19:41 AM,

Serialize by Router on melbnotes01/Agricola(Release 7.0.3|September 26, 2007) at 02/10/2008 11:29:00 AM

Content-Transfer-Encoding: 7bit

To: dontspamme@cbdweb.net

Subject: Quote - Joint Venture

Date: Thu, 2 Oct 2008 11:14:13 +1000

Message-ID: 31c701c9242c$2e691790$1e1ea8c0@ACI.Internal

From: V@a.com.au

Content-Class: urn:content-classes:message

MIME-Version: 1.0

Thread-Index: AckkLC5kOVVopss2T8GZCoIhNNpz2w==

ReplyTo: V@A.com.au

X-Notes-Item: Memo; name=FORM

Content-Type: multipart/mixed;

     boundary="emailSMARTs-z65Bey"

–emailSMARTs-z65Bey

Content-Type: text/html;charset=iso-8859-1

You can see the headers created by the agent are there, but they are preceded by a different set of headers apparently created by the Router. The mail relay removes most of the duplicate headers which is saving us some pain, but the headers left in are not always the ones put there by the agent.

This appears to be a bug, unless someone can tell me what is being done wrongly.

Subject: Here’s what it looks like after the email has been cleaned up a bit by the relay server:

Received: from mx.a.com.au ([203.34.145.43]) by n.cbdweb.net (Lotus Domino Release 7.0.3)

      with ESMTP id 2008100211291654-1065 ;

      Thu, 2 Oct 2008 11:29:16 +1000 

Received: from localhost (localhost [127.0.0.1])

	 by mx.a.com.au (Postfix) with ESMTP id E2EAA1D8508

	 for <dontspamme@cbdweb.net>; Thu,  2 Oct 2008 11:29:08 +1000 (EST)

X-Quarantine-ID: <1vpVaeu-5BNf>

X-Virus-Scanned: Debian amavisd-new at a.com.au

X-Amavis-Alert: BAD HEADER, Duplicate header field: “Date”

Received: from mx.a.com.au ([127.0.0.1])

	 by localhost (mx.a.com.au [127.0.0.1]) (amavisd-new, port 10024)

	 with ESMTP id 1vpVaeu-5BNf for <dontspamme@cbdweb.net>;

	 Thu,  2 Oct 2008 11:29:00 +1000 (EST)

Received: from m.A.Internal (m.a.internal [192.168.30.31])

	 by mx.a.com.au (Postfix) with ESMTP id AF8591D8492

	 for <dontspamme@cbdweb.net>; Thu,  2 Oct 2008 11:28:59 +1000 (EST)

From: Agricola Mail a@a.com.au

X-MIMETrack: Itemize by Agent Manager on m/A(Release 7.0.3|September 26, 2007) at

02/10/2008 11:19:41 AM,

	 Serialize by Router on m/A(Release 7.0.3|September 26, 2007) at

02/10/2008 11:29:00 AM,

	 Itemize by SMTP Server on n/cbdweb(Release 7.0.3|September 26, 2007) at

02/10/2008 11:29:17,

	 Serialize by Notes Client on Nicholas Dow/cbdweb(Release 7.0.3|September 26, 2007) at

02/10/2008 12:52:27 PM

Subject: Quote - Joint Venture

Date: Thu, 2 Oct 2008 11:14:13 +1000

Message-ID: 31c701c9242c$2e691790$1e1ea8c0@A.Internal

MIME-Version: 1.0

Thread-Index: AckkLC5kOVVopss2T8GZCoIhNNpz2w==

ReplyTo: V@A.com.au

To: dontspamme@cbdweb.net

Content-Transfer-Encoding: 7bit

Content-Class: urn:content-classes:message

Content-Class: urn:content-classes:message

Content-Type: multipart/mixed;

	  boundary="emailSMARTs-z65Bey"

–emailSMARTs-z65Bey

Content-Type: text/html;charset=iso-8859-1

Subject: Same problem

I also had this issue. We begin scanning outbound SMTP e-mail with Amavis. We discovered that with bad-header checking enabled all e-mail originating from DWA were being deleted. We have since disabled bad-header checking and luckily we had copies of this e-mails that we could release. Its still a concern because external domains may be rejecting this e-mails as well and we would never know.

It was confirmed that DWA generates duplicate MIME-Version header fields in ND6, ND7 and ND8. A SPR was created SPR#SRNS7L3QMQ requesting the DWA be changed so that this does not occur in future releases. IBM Support referenced the following RFCs: RFC 2045 and RFC 2822, and said that they do not seem to clearly indicate any limits for this header field.