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:07:59 -0400	[thread overview]
Message-ID: <ef1e18d95c941e89114c3a018b849fbd@ladd.quanstro.net> (raw)
In-Reply-To: <<dd6fe68a0909272125n6b907dd0g459c4a587f66b372@mail.gmail.com>>

> a1: local!a2
> a3: local!a1

the alias were in this form
a1:	local!a2
a2:	local!a3

where a3 was a "real user."  the rewrite rules were standard,
except that the appropriate domain name was subsituted in.
someone had created /mail/box/a2.  this was the confusing bit.

> Local is *not* analogous to builtin in rc.
> Rc's builtin has special meaning to rc.
> Local has no special meaning at all to upas;
> the rules apply to local!a1 the same as they
> do to any other string; there's just a rule that
> handles local!(.*).

isn't that that like saying /fd or /dev have no special
meaning in plan 9? the kernel may not care, but
convention is important.

> Because you switched names halfway through
> you didn't say what was working and what was not.
> In terms of the above two lines, what is it that
> is behaving a different way than you expect?

mail -x a1 -> local!a2
mail a1 -> dead.letter (no /mail/box/a2/mbox)

so it's confusing that mailing a2 works but the a1
does not.  the problem is with my misuse of local in
the aliases, not with upas or the default rules.

although send could check mailboxes a bit more
carefully for deliverability.

- erik



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

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