Received: by 10.68.232.169 with SMTP id tp9mr10020334pbc.6.1333474380296;
        Tue, 03 Apr 2012 10:33:00 -0700 (PDT)
Path: r9ni14493pbh.0!nntp.google.com!news2.google.com!npeer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!csnews.cs.nctu.edu.tw!news.cs.nctu.edu.tw!FreeBSD.cs.nctu.edu.tw!postfix.org!owner-postfix-users
From: dmil...@amfes.com ("Daniel L. Miller")
Newsgroups: mailing.postfix.users
Subject: Re: Address re-writes
Date: Tue, 03 Apr 2012 10:32:39 -0700
Organization: NCTU CS FreeBSD Server
Lines: 23
Sender: n...@FreeBSD.cs.nctu.edu.tw
Message-ID: <mailpost.1333474377.3828699.25312.mailing.postfix.users@FreeBSD.cs.nctu.edu.tw>
References: <3VMcgq3VW5zk2RR@spike.porcupine.org>
NNTP-Posting-Host: localhost
Mime-Version: 1.0
X-Trace: FreeBSD.cs.nctu.edu.tw 1333474377 69467 127.0.0.1 (3 Apr 2012 17:32:57 GMT)
X-Complaints-To: usenet@FreeBSD.cs.nctu.edu.tw
NNTP-Posting-Date: Tue, 3 Apr 2012 17:32:57 +0000 (UTC)
X-Received-Bytes: 1735
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 4/3/2012 10:27 AM, Wietse Venema wrote:
> Daniel L. Miller:
>> and fax-access:
>> mess...@inbound.efax.com        REDIRECT        theal...@amfes.com
> As documented, REDIRECT affects all recipients. It is meant to yank
> mail out of its normal path, and was originally implemented for
> emergencies (that is also why the feature is not subject to canonical,
> virtual alias, or BCC address mappings, and none of this is properly
> documented).
>
> In other words, don't use REDIRECT for routine mail processing.
>
>

Ok - I'm using the wrong tool for the job.  So - please let me rephrase 
my question.

What would be the proper way to redirect inbound mail originally 
destined for a valid user, to an alias which can be expanded/redirected 
through normal handling, based on the sender?
-- 
Daniel