[this is a debian bug report; I'm cc-ing it to the exim-users list]
On Sun, Jun 21, 1998 at 01:10:33PM -0400, Avery Pennarun wrote:
> Trying 127.0.0.1...
> Connected to localhost.
> Escape character is '^]'.
> 220 insight.worldvisions.ca ESMTP Exim 1.92 #1 Sun, 21 Jun 1998 13:00:07 -0400
> helo localhost
> 250 insight.worldvisions.ca Hello apenwarr at localhost [127.0.0.1]
> mail from: apenwarr@localhost
> 250 <apenwarr@localhost> is syntactically correct
> rcpt to: apenwarr@insight
> 250 <apenwarr@insight> is syntactically correct
> data
> 354 Enter message, ending with "." on a line by itself
> >From apenwarr@insight Sun Jun 21 13:00:56 1998
When it gets this line, exim says "oh, here's something that isn't a header
line, it must be the beginning of the body, I'll invent a header.
> From: apenwarr@insight
> To: apenwarr@insight
> Subject: I am a test.
>
> This is a test.
> .
So all this bit goes into the body.
> 250 OK id=0ynnTl-0001j8-00
> quit
> 221 insight.worldvisions.ca closing connection
>
> ------------ resulting message in my mailbox --------------
>
> >From apenwarr@localhost Sun Jun 21 13:01:29 1998
That's the message separator in your mailbox. It shouldn't really have a >
infront.
> Return-path: <apenwarr@localhost>
> Envelope-to: apenwarr@insight
> Delivery-date: Sun, 21 Jun 1998 13:01:29 -0400
> Received: from localhost [127.0.0.1] (apenwarr)
> by insight.worldvisions.ca with smtp (Exim 1.92 #1 (Debian))
> id 0ynnTl-0001j8-00; Sun, 21 Jun 1998 13:01:17 -0400
> Message-Id: <E0ynnTl-0001j8-00@???>
> From: apenwarr@localhost
> Bcc:
> Date: Sun, 21 Jun 1998 13:01:17 -0400
> Status: RO
> Content-Length: 131
> Lines: 6
That's the header exim invented. note that it got the from: header from the
envelope from, had no idea what the subject was, and didn't add a to header
because it assumed the message was bcc-ed to you.
>
> >From apenwarr@insight Sun Jun 21 13:00:56 1998
> From: apenwarr@insight
> To: apenwarr@insight
> Subject: I am a test.
>
> This is a test.
And that's what you sent as the DATA part of the SMTP session, unaltered.
As far as I can see, exim is doing the best it can with the clearly broken
input it's receiving.
--
*** Exim information can be found at
http://www.exim.org/ ***
