9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Boyd Roberts" <boyd@fr.inter.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] bug in Plan 9 -ms macros?
Date: Mon, 17 Sep 2001 11:19:57 +0200	[thread overview]
Message-ID: <020301c13f59$ebaae7d0$a2b9c6d4@SOMA> (raw)
In-Reply-To: <9nv3ki$218$1@inputplus.demon.co.uk>

> As an aside, is there some problem with the mail<->news gateway?  The
> dots turned up doubled on comp.os.plan9.

could be a blendmail/smtp thing.  there's some option to blendmail (sic)
to double up on leading dots to prevent premature end of the input to
a DATA command.  it's also written up in the smtp rfc [rfc821 / std10]:

4.5.2.  TRANSPARENCY

         Without some provision for data transparency the character
         sequence "<CRLF>.<CRLF>" ends the mail text and cannot be sent
         by the user.  In general, users are not aware of such
         "forbidden" sequences.  To allow all user composed text to be
         transmitted transparently the following procedures are used.

            1. Before sending a line of mail text the sender-SMTP checks
            the first character of the line.  If it is a period, one
            additional period is inserted at the beginning of the line.

            2. When a line of mail text is received by the receiver-SMTP
            it checks the line.  If the line is composed of a single
            period it is the end of mail.  If the first character is a
            period and there are other characters on the line, the first
            character is deleted.

sounds like a bug.  why am i not suprised?

it may also be an issue with nntp.






  reply	other threads:[~2001-09-17  9:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-15  1:50 Mike Haertel
2001-09-17  8:38 ` Ralph Corderoy
2001-09-17  9:19   ` Boyd Roberts [this message]
2001-09-15 11:44 rob pike

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='020301c13f59$ebaae7d0$a2b9c6d4@SOMA' \
    --to=boyd@fr.inter.net \
    --cc=9fans@cse.psu.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).