da scheint wohl irgend etwas bei der MIME Conversion schiefgegangen zu sein.
Hab hier mal was aus der Knowledgebase
Domino 5.0.8 SMTP Server Fails Conversion of SMTP/MIME Message with Attachment
Problem:
A Domino 5.0.8 or later SMTP server receives a message with an attachment from the Internet. The Domino server fails in conversion. The same message is received by a Domino 4.6.7 SMTP MTA server, and there is no difficulty converting the message and attachment. Why?
Solution:
This issue has been reported to Lotus Quality Engineering.
In this particular case, a name header wrapped to two lines, the second of which begins with double quotes, appears central to the issue. As a workaround, adding a TAB as a line continuation character on the second line appears to have prevented the conversion issue.
Supporting Information:
------=_NextPart_000_000A_01C1818D.2A155EE0
Content-Type: application/msword;
name="=?iso-2022-jp?B?GyRCRnFHMyVXJWklOSVBJUMlLyU7JV8lSiE8GyhCJw==?=
"
Adding a TAB in the above header, at the left margin before the double quotes, appears to prevent the Domino 5.0.8 or later SMTP server's conversion issue with this particular message. Posed for consideration is if the TAB tells ROUTER that the line beginning with the TAB is part of the line above it. Meanwhile, the original message, processed by a Domino 4.6.7 SMTP MTA server, experiences no conversion issues.
A mail user sends a message with an attachment to an Internet recipient. When the recipient opens the message and launches or views the attachment, the following text displays (including quotation marks):
"
Content-Transfer-Encoding: Base64
Content-Disposition: attachment; filename="=?iso-2022-jp?B?GyRCQmgbKEIxMzkbJEIycxsoQklTTxskQiEmGyhCSklT?=
=?iso-2022-jp?B?GyRCMys6RTBGRmIbKEIuZG9j?="
0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAABAAAAIQAAAAAAAAAA
EAAAIwAAAAEAAAD+////AAAAACAAAAD/////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
Request for Comments (RFC) 822 3.1.1. LONG HEADER FIELDS:
"Each header field can be viewed as a single, logical line of ASCII characters, comprising a field-name and a field-body.
For convenience, the field-body portion of this conceptual entity can be split into a multiple-line representation; this
is called 'folding'. The general rule is that wherever there may be linear-white-space (NOT simply LWSP-chars), a CRLF
immediately followed by AT LEAST one LWSP-char may instead be inserted."
