From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Mon, 28 Sep 2009 01:07:59 -0400 To: 9fans@9fans.net Message-ID: In-Reply-To: <> References: <> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] upas aliases Topicbox-Message-UUID: 7907cd38-ead5-11e9-9d60-3106f5b1d025 > 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