9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] upas aliases
Date: Mon, 28 Sep 2009 01:42:10 -0400	[thread overview]
Message-ID: <f6140d81ef9d8fb90371099b6b03a05e@ladd.quanstro.net> (raw)
In-Reply-To: <<dd6fe68a0909272228y7e141beavf1a3fc4fb02f7fbd@mail.gmail.com>>

> I don't think there's a software bug here.
> The system is behaving exactly as you configured it to:
> it can expand the alias but not deliver the mail.

i don't think there's a bug either.  i had intended the original
email to be an illustration of what not to do and why.

it is a little bit problematic, however, when smtp ping
believes that successful alias expantion is the same thing
as deliverability.  send does take the edge off by checking
that /mail/box/$boxname exists.

the orginal problem i was looking at was the fact that
smtp ping was succeeding for unwritable mail boxes.
i had thought that removing the write bits would disable
a mail box.

it seems like it would be better if send -x would finish the
job and verifiy deliverability or just expand aliases and
leave the question of deliverability to someone else.

- erik



       reply	other threads:[~2009-09-28  5:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<dd6fe68a0909272228y7e141beavf1a3fc4fb02f7fbd@mail.gmail.com>
2009-09-28  5:42 ` erik quanstrom [this message]
2009-09-28  5:54   ` Russ Cox
     [not found] <<dd6fe68a0909272125n6b907dd0g459c4a587f66b372@mail.gmail.com>
2009-09-28  5:07 ` erik quanstrom
2009-09-28  5:28   ` Russ Cox
2009-09-28  4:00 erik quanstrom
2009-09-28  4:25 ` Russ Cox

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=f6140d81ef9d8fb90371099b6b03a05e@ladd.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    /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).