Re: Combining transport and aliases

On Thu, May 26, 2005 8:13 am, Michael Nguyen said:

> From: "Matt Fretwell" <mattf@bauchan.org>
>
> > An access map with DISCARD?
>
> I don't think that this is what I'm looking for, but I could be wrong.
> Could you explain what you had in mind?

smtpd_mumble_restrictions =3D
...
check_recipient_access hash:/path/to/file
...

/path/to/file:
validuser1@example.com DUNNO
validuser2@example.com DUNNO
example.com DISCARD

I strongly advise against this. What if someone misspells the address and
the message just disappears into the bitbucket? What's the problem with
rejecting messages to invalid recipients?

[...]

> How should I set it up so that everything is done in the right order?
> Example:
>
> - Email comes in for user2@twentyten.org
> - transport map is checked -- user has no transport map
> - user table is checked. user2@twentyten.org maps to user1@twentyten.=
org
> - user1@twentyten.org should be sent to europe7.twentyten.org:2525
> - mail is delivered

See ADDRESS_REWRITING_README.

> It would also work if aliases were always checked first, then transport=
....

Transport selection takes place after virtual and canonical address
rewriting.

> Like I said, I can do each step of this individually, but I'm having
> trouble getting the whole thing to work (i.e, having the aliases get
> looked up properly and then having the transport maps looked up properl=
y).

Having virtual aliases and transport tables work together is no different
from having each of them work alone. Are you having actual problems (if
so, which?), or are you just imagining your problems?

--=20
Magnus B=E4ck
magnus@dsek.lth.se