Thank you Mr. Stephenson for your reply. Always learning...[:)]

<div style="font-family: Verdana,sans-serif;"> <p>Hi, I'm testing Mercury mail server, and I'm very impressed.</p> <p>I'm using version 4.72 with ClamWall/ClamAV 0.96.5 on Windows XP SP3.</p> <p>I use Mercury for internal mail, also to fetch various POP accounts from my ISP/Mail provider and I relay my outgoing mail thru their SMTP server. I use MercuryS, MercuryC, MercuryP, MercuryD and the default definition in Content Control. The mail clients in use are Outlook Express and Mozilla Thunderbird 3.1.9.</p> <p>All email is working well, but one email with attachment couldn't be correctly displayed on the clients because of an empty line in the header section.</p> <p>I manually deleted the empty line and then I called the mail again from the client and it did correctly displayed and I could save the attachment.</p> <p>This is getting long....Well, the question is: <span style="font-weight: bold;">is Mercury for some reason inserting this empty line? Is there a setting in the configuration causing this?</span></p> <p>Here is the Header of the mail and the beginning of the Body. The problematic part is on red:</p> <p> </p> <p style="color: red;">-------------------- START CODE --------------------</p> </div> <div style="color: blue; font-family: 'Courier New',sans-serif; font-size: 12px;"> <p>Received: from spooler by mydomain.com (Mercury/32 v4.72); 21 Mar 2011 09:00:12 +0100 X-Envelope-To: receiver@mydomain.com X-CLAMWALL: Passed through antiviral test by ClamWall 1.4.0.96 on mydomain.com (64) Received: from POP3D by mydomain.com with MercuryD (v4.72);  21 Mar 2011 09:00:03 +0100 Return-Path: <prvs=sender=0555a2ab0@senderdomain.ch> Delivery-Date: Mon, 21 Mar 2011 08:49:39 +0100 Received: from mailer.senderdomain.ch (mailer.senderdomain.ch [123.123.123.123]) by  mx.kundenserver.ch (node=mxch1) with ESMTP (Nemesis) id  0LaGYE-1MbudY32T4-02lK45 for receiver@mydomain.com;  Mon, 21 Mar 2011 08:49:39 +0100 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap0EAMufhk2SQ5Jm/2dsb2JhbACCYaI0gUy/R4VjBA <span style="color: red;">X-IronPort-AV: E=Sophos;i="4.63,218,1299452400"; X-AC-Weight: [####] (Whitelisted) -9999 X-CC-Diagnostic:    d="xml'?log'?zip'48?scan'48,48,217,208?hlp'48,48,217,208?lcd'48,48,217,208";a="123284858" </span> Received: from mailer22.senderdomain.ch (HELO mailer22.senderdomain.ch)  ([123.123.123.123]) by mailer.senderdomain.ch with ESMTP;  21 Mar 2011 08:49:38 +0100 Received: from mailer-mbx.senderdomain.ch ([72bb::72bb:72bb:72bb:7732]) by  mailer22.senderdomain.ch ([72bb::71bb:71bb:71bb:7731%12]) with mapi;  Mon, 21 Mar 2011 08:49:37 +0100 From: Sender <sender@senderdomain.ch> To: 'Receiver' <receiver@mydomain.com> CC: SomeOne <someone@otherdomain.ch> Disposition-Notification-To: Sender  <sender@senderdomain.ch> Date: Mon, 21 Mar 2011 08:49:37 +0100 Subject: Some problem ID-123 Thread-Topic: Some problem ID-123 Thread-Index: AxxyyLcHEYo5AnwSUQqTf3Pl4Gb5Fh== Message-ID: <2D19B529188C9B41A325D2784802E9630FEEEC2CA7@mailer-mbx.senderdomain.ch> Accept-Language: fr-FR, fr-CH Content-Language: fr-FR X-MS-Has-Attach: yes X-MS-TNEF-Correlator: acceptlanguage: fr-FR, fr-CH x-tm-as-product-ver: SMEX-10.0.0.4152-6.500.1024-18024.005 x-tm-as-result: No--47.011600-0.000000-31 x-tm-as-user-approved-sender: Yes x-tm-as-user-blocked-sender: No Content-Type: multipart/mixed;  boundary="_004_2D19B529188C9B41A325D2784802E9630FEEEC2CA7MAILERMBXabcd_" MIME-Version: 1.0 Envelope-To: receiver@mydomain.com   --_004_2D19B529188C9B41A325D2784802E9630FEEEC2CA7MAILERMBXabcd_ Content-Type: multipart/alternative;  boundary="_000_2D19B529188C9B41A325D2784802E9630FEEEC2CA7MAILERMBXabcd_"   --_000_2D19B529188C9B41A325D2784802E9630FEEEC2CA7MAILERMBXabcd_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable   Hello ...</p> </div> <div style="font-family: Verdana,sans-serif;"> <p style="color: red;">--------------------END CODE --------------------</p> <p> </p> <p>And I edited this way. Note that this is the short version, I left some code behind:</p> <p> </p> <p style="color: red;">-------------------- START CODE --------------------</p> </div> <div style="color: blue; font-family: 'Courier New',sans-serif; font-size: 12px;"> <p>... [here should be some code] <span style="color: red;">X-IronPort-AV: E=Sophos;i="4.63,218,1299452400";  d="xml'?log'?zip'48?scan'48,48,217,208?hlp'48,48,217,208?lcd'48,48,217,208";a="123284858" </span> ... [here should be some code] MIME-Version: 1.0 Envelope-To: receiver@mydomain.com <span style="color: red;">X-AC-Weight: [####] (Whitelisted) -9999 X-CC-Diagnostic: </span>   --_004_2D19B529188C9B41A325D2784802E9630FEEEC2CA7MAILERMBXabcd_ Content-Type: multipart/alternative;  boundary="_000_2D19B529188C9B41A325D2784802E9630FEEEC2CA7MAILERMBXabcd_"   --_000_2D19B529188C9B41A325D2784802E9630FEEEC2CA7MAILERMBXabcd_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable   Hello ...</p> </div> <div style="font-family: Verdana,sans-serif;"> <p style="color: red;">--------------------END CODE --------------------</p> <p> </p> <p>I hope someone could put some light on this subject, thank you!</p> <p> </p> </div>

<blockquote><p>This is getting long....Well, the question is: <span style="font-weight:bold;">is Mercury for some reason inserting this empty line? Is there a setting in the configuration causing this?</span></p><p>Here is the Header of the mail and the beginning of the Body. The problematic part is on red:</p><p> </p><p style="color:red;">-------------------- START CODE --------------------</p></blockquote><blockquote> Received: from spooler by mydomain.com (Mercury/32 v4.72); 21 Mar 2011 09:00:12 +0100 X-Envelope-To: receiver@mydomain.com X-CLAMWALL: Passed through antiviral test by ClamWall 1.4.0.96 on mydomain.com (64) Received: from POP3D by mydomain.com with MercuryD (v4.72);  21 Mar 2011 09:00:03 +0100 Return-Path: <prvs=sender=0555a2ab0@senderdomain.ch> Delivery-Date: Mon, 21 Mar 2011 08:49:39 +0100 Received: from mailer.senderdomain.ch (mailer.senderdomain.ch [123.123.123.123]) by  mx.kundenserver.ch (node=mxch1) with ESMTP (Nemesis) id  0LaGYE-1MbudY32T4-02lK45 for receiver@mydomain.com;  Mon, 21 Mar 2011 08:49:39 +0100 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap0EAMufhk2SQ5Jm/2dsb2JhbACCYaI0gUy/R4VjBA <span style="color: red;">X-IronPort-AV: E=Sophos;i="4.63,218,1299452400";</span> <span style="color: red;"> X-AC-Weight: [####] (Whitelisted) -9999</span> <span style="color: red;"> X-CC-Diagnostic:</span> <span style="color: red;">  </span> <span style="color: red;">  d="xml'?log'?zip'48?scan'48,48,217,208?hlp'48,48,217,208?lcd'48,48,217,208";a="123284858"</span></blockquote><p>I suspect that the Ironport diagnostic is putting in the extra CR/LF into the message.  It's probably it because that the line is greater than the 78 characters with cr/lf and not properly wrapped but that's just a guess. </p><p> </p><blockquote> </blockquote>

<p>It's difficult to say without seeing the original message, but it looks like there was an empty line after the first line of the X-Ironport-AV header, indicating the end of the header section. Mercury has then added its content control headers after that header.</p><p>If you can have the sender resend the message you could temporarily switch off content control and see if the blank line still is there.</p><p>/Rolf </p>

<div style="font-family: Verdana,sans-serif;"> <p>Thank you all for your comments.</p> <p>One more question at Mr. Thomas R. Stephenson:</p> <p>Could you please explain the meaning of "<span style="color: blue;">is greater than the 78 characters with cr/lf and not properly wrapped</span>".</p> <p>Thank you.</p> </div>

2.2.3.  Long Header Fields
   Each header field is logically a single line of characters comprising
   the field name, the colon, and the field body.  For convenience
   however, and to deal with the 998/78 character limitations per line,
   the field body portion of a header field can be split into a
   multiple-line representation; this is called "folding".  The general
   rule is that wherever this specification allows for folding white
   space (not simply WSP characters), a CRLF may be inserted before any
   WSP.

<blockquote><p>Could you please explain the meaning of "<span style="color: blue;">is greater than the 78 characters with cr/lf and not properly wrapped</span>".</p></blockquote><p> The RFC for e-mail limits to header lines to 78 characters and provides instructions on how the longer lines are to be wrapped. </p><pre>2.2.3. Long Header Fields Each header field is logically a single line of characters comprising the field name, the colon, and the field body. For convenience however, and to deal with the 998/78 character limitations per line, the field body portion of a header field can be split into a multiple-line representation; this is called "folding". The general rule is that wherever this specification allows for folding white space (not simply WSP characters), a CRLF may be inserted before any WSP.</pre><p> </p>