From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: SMTP question (not quite Gnus-related)
Date: 07 Feb 2001 18:56:58 +0100 [thread overview]
Message-ID: <vafelxav0k5.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <87y9vujkvd.fsf@torus.tenzing.com> ("Steven E. Harris"'s message of "29 Jan 2001 10:04:06 -0800")
On 29 Jan 2001, Steven E. Harris wrote:
> ,----[ RFC821 4.1.1 ]
>| The mail data is terminated by a line containing only a period,
>| that is the character sequence "<CRLF>.<CRLF>" (see Section 4.5.2
>| on Transparency). This is the end of mail data indication
> `----
Actually, there is a contradiction right here, because `a line
containing only a period' and the character sequence "<CRLF>.<CRLF>"
are not the same thing.
I presume that the first part is the relevant part and the
"<CRLF>.<CRLF>" thing is just an explanation. Maybe the explanation
makes it clear that there is no whitespace either before or after the
period. If they had said the character sequence ".<CRLF>", then
"foo.<CRLF>" might be a valid suffix for a message, which is not what
the standard intends.
kai
--
Be indiscrete. Do it continuously.
next prev parent reply other threads:[~2001-02-07 17:56 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 [this message]
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
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=vafelxav0k5.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).