How do i get rid of: (see attached file: nnnn.eee) in body?

[toradex]

What does decide in Lotus/Domino about the fact that an email sent by lotus that does not contain any message body apart from attachment (eg a word document)is empty or includes an automatically added sentence: (See attached file: faxcover.doc) ???

When we send an email through one of ours server, the email, its body looks like that:

"Reply-To: john.smith@domain.com
Subject: 8420343
To: peter@domain.com
Message-ID: <OF4D507613.B7589BC0-ONC1257030.002551EC-C1257030.002551FD@domain.com>
From: john.smith@domain.com
Date: Thu, 30 Jun 2005 08:46:44 +0200
Disposition-Notification-To: john.smith@domain.com
X-MIMETrack: Serialize by POP3 Server on nnn/nn/nnnn(Release 6.5|September 26, 2003) at
2005-06-30 08:47:56
MIME-Version: 1.0
Content-type: application/msword;
name="faxcover.doc"
Content-Disposition: attachment; filename="faxcover.doc"
Content-transfer-encoding: base64

0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAACAAAA6QAAAAAAAAAA
EAAA6wAAAAEAAAD+////AAAAAOcAAADoAAAA////////////////////////////////////////
///////////////////////////////////////////..."

- no text, attachment only

And when we send it through another of our domino servers, it looks like that:

"Reply-To: john.smith@domain.com
Subject: 8420343
To: tom@domain.com
Message-ID: <sdfsdfsd.B7589BC0-ONC1257030.002551EC-C1257030.002551FD@domain.com>
From: john.smith@domain.com
Date: Thu, 30 Jun 2005 08:44:06 +0200
Disposition-Notification-To: john.smith@domain.com
X-MIMETrack: Serialize by POP3 Server on ssss/ss/sssss(Release 6.5|September 26, 2003) at
2005-06-30 08:44:34
MIME-Version: 1.0
Content-type: multipart/mixed;
Boundary="0__=4EBBFAA3DFB779828f9e8a93df938690918c4EBBFAA3DFB77982"
Content-Disposition: inline

--0__=4EBBFAA3DFB779828f9e8a93df938690918c4EBBFAA3DFB77982
Content-type: text/plain; charset=ISO-8859-2
Content-transfer-encoding: base64


DQoNCg0KDQooU2VlIGF0dGFjaGVkIGZpbGU6IGZheGNvdmVyLmRvYyk=

--0__=4EBBFAA3DFB779828f9e8a93df938690918c4EBBFAA3DFB77982
Content-type: application/msword;
name="faxcover.doc"
Content-Disposition: attachment; filename="faxcover.doc"
Content-transfer-encoding: base64

0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAACAAAA6QAAAAAAAAAA
EAAA6wAAAAEAAAD+////AAAAAOcAAADoAAAA////////////////////////////////////////
///////////////////////////////////////"

- as you can see apart from the attachment the email includes base64 encoded sentence "(See attached file: faxcover.doc)"