DWA7 sents blank line in header

Hi all,

Since two months ago we are facing an odd incident with mails we sent from dwa7 (fp2), our corporative mail client. In many cases they are filtered by antivirus/antispam software as “potential malware”.

It seems that our email contains a blank line in the header, something not admitted by standards, so the are filtered or sent to quarantine.

I have been checking domino configuration (two domino clustered servers in 702 fp2, and two smtp gateways with domino 653, all of them in Spanish version) without results.

I also have an independent test domino platform with same configuration and version 653, and the problem does not appear.

Mails sent by Notes clients have no problems.

Here you have an example of the header of a test mail:

From carlos_cabanas@race.es Fri Dec 14 11:48:19 2007

Return-Path: carlos_cabanas@race.es

Authentication-Results: mta530.mail.mud.yahoo.com from=race.es; domainkeys=neutral (no sig)

Received: from 213.0.41.163 (EHLO raceavas2.race.es) (213.0.41.163)

by mta530.mail.mud.yahoo.com with SMTP; Fri, 14 Dec 2007 03:47:24 -0800

Received: from RACEFEND1 ([172.17.196.6]) by raceavas2 with InterScan

Message Security Suite; Fri, 14 Dec 2007 12:45:41 +0100

Importance: Normal

In-Reply-To:

References:

Subject: prueba

MIME-Version: 1.0

From: carlos_cabanas@race.es

To: carlos_cabanas@yahoo.es

Message-ID: OF594EB804.B9CE218A-ONC12573B1.0040D920-C12573B1.0040D922@race.es

Date: Fri, 14 Dec 2007 12:48:19 +0100

7.0.2FP2|May 14, 2007) at14/12/2007 12:48:19,Serialize complete at 

14/12/2007 12:48:19,Serialize by Router on RACEFEND1/RACE_ES(Release 

6.5.3FP1|December 15, 2004) at14/12/2007 12:43:58

Content-Type: multipart/alternative;

boundary="=_alternative 0040D922C12573B1_="

Content-Length: 5676

Any clue would be apreciated.

Thank you in advance.

Carlos Cabanas

Subject: MIME boundaries

I had similar problem when MIME boundaries in email were not populated as per the standards.

Content-Type: Multipart/Mixed; boundary=" 9:Oct:06:15:04:49Peter_The_Man!"

In my case the boundary value started with a leading space, which is not acceptable as per MIME standards. Fixed the problem by removing the space. This field was populated based on current date, and for days 1 to 9 of each month, we had the problem!

I can see a space in your MIME boundary too.

Content-Type: multipart/alternative; boundary=“=alternative 0040D922C12573B1=”

Try removing that space.

Also ensure MIME boundary does appear again at the end of message or wherever is the MIME entity ending. You have not pasted the entire email message, so I can’t see if MIME is properly closed or not.

Regards,

Byju Joy