Re: [EXIM] problem with MIME attachments

At 19:20 22/05/98 +0100, you wrote:
>On Fri 22 May, comms wrote:
>
>> I traced an imcoming e-mail with a MIME attachment and compared the headers
>> present in the trace file to the headers present in the message in the
>> user's mailbox on the server.
>>
>> Our mail server had added the following headers at the beginning of the
message:
>>

>> > From comms@??? Fri May 22 16:43:02 1998
>> > Return-path: <comms@???>
>> > Envelope-to: simon.king@???
>> > Delivery-date: Fri, 22 May 1998 16:43:02 +0100
>> > Received: from host65.cis1.u-net.com [194.119.156.66] 
>> >    by mail.cis.co.uk with esmtp (Exim 1.82 #1)
>> >    id 0yctyI-0007b9-00; Fri, 22 May 1998 16:43:02 +0100
>> 23,28c16
>> > Message-Id: <E0yctyI-0007b9-00@???>
>> > From: comms@???
>> < Bcc:
>> > Date: Fri, 22 May 1998 16:43:02 +0100

>> >
>> > >From comms@??? Fri May 22 16:41:32 1998
>> ---
>> < From comms@??? Fri May 22 16:41:32 1998
>>
>>
>> The last couple of lines are where it has inserted a '>' before the original
>> 'From' header.
>
>There shouldn't have been a 'From' header at the start of a message
received by
>Exim. RFC822 messages that come over the wire must contain only RFC822
headers,
>which have names ending in colons. That 'From' line is a UUCP thing, which is
>also used as a message separator in Berkeley-style mailboxes. Exim will treat
>any line that doesn't start with a name followed by a colon as the start of
the
>message body.
>
>It looks to me as though host65.cis1.u-net.com [194.119.156.66] is sending out
>non-conforming messages, starting with a UUCP-style 'From' line. What follows
>that last 'From' line? That's part of the body of the message, not the headers,
>since there is a separator line after 'Date:'.
>

We have an ISDN connection to our ISP. They hold some of our mail accounts.
Mail for any other users in our domain is dumped in a default mailbox. We
use a pullmail routine to initiate an smtp transfer of mail in this default
mailbox to our mail server.

I assume that all these extra headers are created when the mail message is
delivered to the default mailbox on our ISP's mail server.

Anyway, to answer your question, the complete header listing goes as follows
(I've copied from the beginning of the mailbox file to the attachment itself)::




>From MAILER-DAEMON Fri May 22 10:43:40 1998
Date: Fri, 22 May 1998 10:43:40 +0100 (BST)
From: Mail System Internal Data <MAILER-DAEMON@???>
Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA
X-IMAP: 891338039 27
Status: RO

This text is part of the internal format of your mail folder, and is not
a real message. It is created automatically by the mail system software.
If deleted, important folder data will be lost, and it will be re-created
with the data reset to initial values.

>From comms@??? Fri May 22 13:57:09 1998

Return-path: <comms@???>
Envelope-to: simon.king@???
Delivery-date: Fri, 22 May 1998 13:57:09 +0100
Received: from host65.cis1.u-net.com [194.119.156.66]
    by mail.cis.co.uk with esmtp (Exim 1.82 #1)
    id 0ycrNl-0007Q9-00; Fri, 22 May 1998 13:57:09 +0100
Received: from mail.u-net.net (unverified [195.102.240.137]) by
host65.cis1.u-net.com
 (Integralis SMTPRS 2.04) with SMTP id <B0000002434@???>;
 Fri, 22 May 1998 14:00:00 +0100
Message-Id: <E0ycrNl-0007Q9-00@???>
From: comms@???
Bcc:
Date: Fri, 22 May 1998 13:57:09 +0100

>From comms@??? Fri May 22 13:51:01 1998

Return-path: <comms@???>
Envelope-to: simon.king@???
Delivery-date: Fri, 22 May 1998 13:51:01 +0100
Received: from (serv1.is1.u-net.net) [194.119.130.9]
    by mserv1b.u-net.net with smtp (Exim 1.82 #2)
    id 0ycrHo-0007lF-00; Fri, 22 May 1998 13:51:00 +0100
Received: from cis.u-net.com [193.119.188.89]
    by serv1.is1.u-net.net with smtp (Exim 1.62 #2)
    id 0ycrMg-0000fd-00; Fri, 22 May 1998 13:56:03 +0100
X-Sender: comms-cis@??? (Unverified)
X-Mailer: Windows Eudora Light Version 1.5.2
MIME-Version: 1.0
To: simon.king@???
From: comms <comms@???>
Subject: test attachment
X-Attachments: C:\DOWNLOAD\VIZ(2).JPG;
Message-Id: <E0ycrMg-0000fd-00@???>
Date: Fri, 22 May 1998 13:56:03 +0100
Content-Type: multipart/mixed; boundary="=====================_895870252==_"

--=====================_895870252==_
Content-Type: text/plain; charset="us-ascii"



--=====================_895870252==_
Content-Type: application/octet-stream; name="VIZ(2).JPG";
x-mac-type="42494E41"; x-mac-creator="6D646F73"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="VIZ(2).JPG"

/9j/4AAQSkZJRgABAgEASABIAAD/7RdMUGhvdG9zaG9wIDMuMAA4QklNA+0AAAAAABA
ASAAAAAEA
AgBIAAAAAQACOEJJTQPzAAAAAAAIAAAAAAAAAAA4QklNBAoAAAAAAAEAADhCSU0n
EAAAAAAACgAB
AAAAAAAAAAI4QklNA/UAAAAAAEgAL2ZmAAEAbGZmAAYAAAAAAAEAL2ZmAAEAoZma
AAYAAAAAAAEA
MgAAAAEAWgAAAAYAAAAAAAEANQAAAAEALQAAAAYAAAAAAAE4QklNA/gAAAAAAH
AAAP//////////
//////////////////8D6AAAAAD/////////////////////////////A+gAAAAA////////////
/////////////////wPoAAAAAP////////////////////////////8D6AAAOEJJTQQIAAAAAAAQ
AAAAAQAAAkAAAAJAAAAAADhCSU0ECQAAAAAV2wAAAAEAAACAAAAATAAAAYAAAH
IAAAAVvwAYAAH/
2P/gABBKRklGAAECAQBIAEgAAP/+ACdGaWxlIHdyaXR0ZW4gYnkgQWRvYmUgUGhvdG
9zaG9wqCA0
LjAA/+4ADkFkb2JlAGSAAAA




I experimented a bit more and found that it wasn't the '>From' header which
was causing the problem, it's the blank line that precedes it. If I remove
the blank line by editing the mailbox directly then the attachment is
received normally.

Is there anything I can do to get round this problem?


--
*** Exim information can be found at http://www.exim.org/ ***