From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: SMTP question (not quite Gnus-related)
Date: 08 Feb 2001 18:37:42 +0100 [thread overview]
Message-ID: <vafelx9dqjd.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <87lmrhm6tz.fsf@torus.tenzing.com> ("Steven E. Harris"'s message of "08 Feb 2001 09:18:32 -0800")
On 08 Feb 2001, Steven E. Harris wrote:
> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
>
> [...]
>
>> By this reading, "<CRLF>.<CRLF>" is *two* lines: an empty line and
>> a line containing only a dot.
>
> Well, I think that there can be line content before the first <CRLF>
> and still have the <CRLF>.<CRLF> be a valid terminator.
Yes, yes. This misunderstanding is the reason why they included the
first <CRLF>. If you write "foo<CRLF>", do you have a line which
contains the 3 characters "foo" plus an EOL? Well, this depends on
what comes before that. If there is an "x" before this, the line
contains 4 characters plus EOL.
But I hope you understood what I meant: "<CRLF>.<CRLF>" is an empty
line plus a 1-char line only if it is the start of the whole thing, or
follows a line.
>> In "DATA<CRLF>foo<CRLF>.<CRLF>", does the message contain "foo" or
>> "foo<CRLF>"? Or even "<CRLF>foo<CRLF>"?
>
> This is the same question I asked in my previous post a few minutes
> ago. I think that the message just contains "foo," because there
> must be some way for you to send "foo" and get "foo" back out on the
> other side. If you send "foo" and you get back "foo<CRLF>," that
> would seem like an intolerable asymmetry in a "transparency"
> mechanism.
>
> That would then raise another question: If you meant to send
> "foo<CRLF>," then would the SMTP encoding be
> "foo<CRLF><CRLF>.<CRLF>" or just "foo<CRLF>.<CRLF>"? Who owns that
> first <CRLF>?!?
>
> I hope it's clear that I'm not trying to nitpick. I must have
> defined behavior for this stream, and it's supposed to work
> "transparently."
Well, RFC 822 says that the body is a sequence of lines, so the body
always ends with a line, and a line ends with an EOL. So the body
ends with an EOL.
If you want to transmit something which is not a sequence of lines,
you have to add something on top of SMTP. Maybe MIME is your friend?
kai
--
Be indiscrete. Do it continuously.
prev parent reply other threads:[~2001-02-08 17:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-29 18:04 Steven E. Harris
2001-02-07 17:56 ` Kai Großjohann
2001-02-08 1:00 ` Daniel Pittman
2001-02-08 1:18 ` Steven E. Harris
2001-02-08 2:03 ` Daniel Pittman
2001-02-08 13:24 ` Kai Großjohann
2001-02-08 17:11 ` Steven E. Harris
2001-02-08 17:25 ` Paul Jarc
2001-02-08 17:30 ` Paul Jarc
2001-02-08 18:02 ` Steven E. Harris
2001-02-08 18:20 ` Paul Jarc
2001-02-09 12:09 ` Kai Großjohann
2001-02-09 17:33 ` Steven E. Harris
2001-02-08 17:33 ` Kai Großjohann
2001-02-08 18:07 ` Steven E. Harris
2001-02-09 12:11 ` Kai Großjohann
2001-02-09 17:26 ` Steven E. Harris
2001-02-09 0:42 ` Daniel Pittman
2001-02-08 13:22 ` Kai Großjohann
2001-02-08 17:18 ` Steven E. Harris
2001-02-08 17:37 ` Kai Großjohann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vafelx9dqjd.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).