From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: SMTP question (not quite Gnus-related)
Date: 09 Feb 2001 13:11:42 +0100 [thread overview]
Message-ID: <vafofwcm4xt.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <871yt9m4k3.fsf@torus.tenzing.com> ("Steven E. Harris"'s message of "08 Feb 2001 10:07:40 -0800")
On 08 Feb 2001, Steven E. Harris wrote:
> Okay, that sounds reasonable. So an empty body doesn't *need"
> "<CRLF>.<CRLF>" to terminate. It only needs ".<CRLF>" to
> terminate. If the body isn't empty, we leave the first <CRLF> as
> part of the body and discard the ".<CRLF>". That would match the
> behavior I've seen on MTAs I've tested with. This interpretation
> makes sense, but it's not immediately apparent from reading RFC821.
I don't think you should treat the <CRLF> differently for empty
messages. Here's how to send an empty message:
DATA<CRLF>
.<CRLF>
Here's a nonempty message:
DATA<CRLF>
foo<CRLF>
.<CRLF>
The message content is one line, containing the characters "foo" plus
the EOL that comes after it.
kai
--
Be indiscrete. Do it continuously.
next prev parent reply other threads:[~2001-02-09 12:11 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 [this message]
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=vafofwcm4xt.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).