Gnus development mailing list
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: SMTP question (not quite Gnus-related)
Date: 08 Feb 2001 13:20:59 -0500	[thread overview]
Message-ID: <m3ofwd2fz2.fsf@multivac.student.cwru.edu> (raw)
In-Reply-To: "Steven E. Harris"'s message of "08 Feb 2001 10:02:59 -0800"

"Steven E. Harris" <steven.harris@tenzing.com> writes:
> prj@po.cwru.edu (Paul Jarc) writes:
> > Use a different start state.  I.e., start in the state you're normally
> > in after seeing <CRLF>.  The first <CRLF> in <CRLF>.<CRLF> is, I
> > believe, considered part of the message.
> 
> This is maddening! If the first <CRLF> if part of the body (don't get
> me wrong - I like the idea), then they should not define the
> *terminator* to be "<CRLF>.<CRLF>."

I don't think they intended to say that <CRLF>.<CRLF> is itself the
terminator.  I think the RFC was written by people who already knew
what SMTP looked like, and who didn't try to get inside the heads of
people who didn't.  So it doesn't quite tell you what SMTP is unless
you already know.  If you said that SMTP was badly designed and its
specification confusingly worded, I would agree with you.

> They should say something more like, "The terminator is .<CRLF>, but
> only if immediately preceded by <CRLF> or as the first three bytes
> of the stream."

Yes, that would be clearer, and would match (I think) the *intended*
meaning of the existing words.

> Okay, so then any sending MUA effectively augments your message if
> it's lacking the final <CRLF>? I didn't know that, but it could make
> sense.

Yes.  I don't know that the RFC says a sender must do this, but this
(or perhaps rejection) is the only sane way to handle such a message.


paul



  reply	other threads:[~2001-02-08 18:20 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 [this message]
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

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=m3ofwd2fz2.fsf@multivac.student.cwru.edu \
    --to=prj@po.cwru.edu \
    /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).