From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: [9fans] upas aliases
Date: Mon, 28 Sep 2009 00:00:49 -0400 [thread overview]
Message-ID: <47ff785949f474506048701186b50f22@ladd.quanstro.net> (raw)
i don't know if anyone else has fallen into this
trap, but i don't see it on the archives. i had
been following along and mindlessly using aliases
like
red.forman: local!red
this is fine until you slip up and have
oldguy: local!red.forman
which doesn't work if you're using a somewhat
standard rewrite rule set. this is because local!
is analogous to "builtin" in rc. it disables further
alias expansion. the wierd bit is that mail
somealias will work while a smtp ping, which
uses upas/send -x will not. that is unless you
create the directory /mail/box/somealias. it's
all quite peculiar. and i believe sending to
that alias should always fail.
does anyone think differently?
- erik
next reply other threads:[~2009-09-28 4:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-28 4:00 erik quanstrom [this message]
2009-09-28 4:25 ` Russ Cox
[not found] <<dd6fe68a0909272125n6b907dd0g459c4a587f66b372@mail.gmail.com>
2009-09-28 5:07 ` erik quanstrom
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
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=47ff785949f474506048701186b50f22@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).