virtual domain + '@domain user' + relocated table

[Adam Hirsch]

The short version: using '@domain user' in the virtual table allows rewrite
to grab mail early that I'd like to match (and bounce) later in the
relocated table. I can make it work with a fictitious specific local user,
but that changes the bounce message to refer to $myorigin rather than the
virtual domain concerned.

The actual scenario:

I've got a virtual domain (foo.org) on my machine, and a user who currently
receives all mail sent to that virtual domain, like so:

foo.org foo
@foo.org jeffrey

Now, jeffrey acquired this domain from someone else who had a working
address in foo.org for a bit. The address (quux) still receives mail from
time to time, and jeffrey would like mail to qu...@foo.org to get a
relocated message, but all other mail to still file through to him.

"A-ha," say I, "I can do this using the relocated table, like so!"

qu...@foo.org qu...@home.com

Problem is, rewrite consults the virtual table before the relocated table,
so jeffrey still gets the mail for quux.

"Okay," sez I, "I'll set up the virtual table like so:"

foo.org foo
qu...@foo.org quux
@foo.org jeffrey

"and then I'll have my relocated table like so:"

quux qu...@home.com

This *almost* works the way I want it -- jeffrey gets all the mail for the
domain except that for quux, which gets a relocated message... except the
system now sends mail saying that qu...@baz.org (which is $myorigin) has
moved, which isn't quite true.

I figure this must be doable and that I've just missed the permutation to
do it... any thoughts?

A

--
Life and love are life and love, a bunch of violets is a bunch of violets,
and to drag in the idea of a point is to ruin everything. Live and let
live, love and let love, flower and fade, and follow the natural
curve, which flows on, pointless. -D.H.Lawrence <ad...@baz.org>

[Wietse Venema]

For now, Use the SMTPD access map feature.

Wietse

Adam Hirsch: