9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: W B Hacker <wbh@conducive.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] my previous note on vf
Date: Wed,  6 Jun 2007 05:07:24 -0400	[thread overview]
Message-ID: <4666794C.8040308@conducive.org> (raw)
In-Reply-To: <46656533.E70F1036@null.net>

Douglas A. Gwyn wrote:
> W B Hacker wrote:
>> Just obtuse with different semantics.  Ones not seen as often.
>
> No, it is an actual bug.  Instead of refuse(), a different form
> of termination should be used, one that generates an accurate
> diagnostic.  Or, refuse should accept an argument for the
> reason: refuse("can't create temp file");
> Followup-To:
> Distribution:
> Organization: University of Bath Computing Services, UK
> Keywords:
> Cc:
>
>

The *cause* may very well be a bug. Not my area of expertise.

But quite separately, the form of presentation of the response is an smtp RFC
violation.

While the specific text is flexible, the code numbers at beginning of each line
are standard for each type of situation, not optional.

Decently laid-out listing here:

http://www.greenend.org.uk/rjk/2000/05/21/smtp-replies.html

The cited RFC's spell out the 'MAY', 'SHOULD', and 'MUST' rules applicable.

Nothing prevents inventing/defining some other way of messaging - smtp is far
from the only way in use.

But that 'other way' would NOT be 'smtp', nor should a proper smtp server be
expected to interoperate with a non-standard set of codes, or absence therof.

Whatever 'fixing' is to be done should take that into account as well as sorting
the proximal cause of this specific error situation.

Bill





  reply	other threads:[~2007-06-06  9:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-03  3:14 ron minnich
2007-06-03  3:26 ` geoff
2007-06-03  3:32   ` ron minnich
2007-06-03  3:43     ` W B Hacker
2007-06-06  8:49       ` Douglas A. Gwyn
2007-06-06  9:07         ` W B Hacker [this message]
2007-06-03  4:03     ` erik quanstrom
2007-06-03  8:58     ` Steve Simon
2007-06-03  4:29 geoff

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=4666794C.8040308@conducive.org \
    --to=wbh@conducive.org \
    --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).