Gnus development mailing list
 help / color / mirror / Atom feed
From: Daniel Pittman <daniel@rimspace.net>
Cc: ding@gnus.org
Subject: Re: SMTP question (not quite Gnus-related)
Date: 09 Feb 2001 11:42:59 +1100	[thread overview]
Message-ID: <871yt8hejw.fsf@inanna.rimspace.net> (raw)
In-Reply-To: <vafofwdgvea.fsf@lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "08 Feb 2001 14:24:29 +0100")

On 08 Feb 2001, Kai Großjohann wrote:
> On 08 Feb 2001, Daniel Pittman wrote:
> 
>> It is fine by the fragment you posted. By my reading of it, anyway. 
>> 
>>> ,----
>>> | DATA<CRLF>
>>> | .<CRLF>
>>> `----
>> 
>> That final line is a period on an otherwise empty line, the defined
>> terminator.
> 
> But one message earlier, you said that "<CRLF>.<CRLF>" is the
> terminator.  Now you are saying ".<CRLF>" is the terminator.  Which
> one is it?  (I vote for ".<CRLF>", opposing the example in the RFC.)

Ah. I have the same unclearness as the RFC. So:

DATA <CR> <LF> . <CR> <LF>
--------------                  This is the DATA command.
     ---------------------      This is the end-of-data marker.

> Presumably, an SMTP server reading the DATA command will also read the
> <CRLF> that follows it.  Hence, the <CRLF> is not available for the
> subsequent end of data indication anymore.

That's not how I read the RFC. Specifically, I see the notes on
'<crlf>.<crlf>' as being a hint about what to look for.

Anyway, if you are writing an SMTP sender, avoid sending this (just in
case) and if you write an SMTP receiver, accept it.

Because there *is* ambiguity in the RFC - if there wasn't, we wouldn't
be debating it. ;)

        Daniel

-- 
There is no happiness in having or in getting, but only in giving.
        -- Henry Drummond



  parent reply	other threads:[~2001-02-09  0:42 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 [this message]
2001-02-08 13:22     ` Kai Großjohann
2001-02-08 17:18       ` Steven E. Harris
2001-02-08 17:37         ` Kai Großjohann

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=871yt8hejw.fsf@inanna.rimspace.net \
    --to=daniel@rimspace.net \
    --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).