Wietse Venema:
> Victor.Duchovnimorganstanley.com:
> > On Thu, 14 Nov 2002, Wietse Venema wrote:
> >
> > > Victor.Duchovnimorganstanley.com:
> > > > On Thu, 14 Nov 2002, Wietse Venema wrote:
> > > >
> > > > > Actually, this rewriting of recipient domain to the local hostname
> > > > > is done by the queue manager, but only when the local recipient
> > > > > concurrency limit is set to 1.
> > > > >
> > > >
> > > > So is the queue manager logic duplicated by the trivial-rewrite service
> > > > lookups performed on each address when .forward is expanded?
> > >
> > > It's not. and I wonder if at least part of the logic needs to be
> > > in the resolver: if the domain name matches $mydestination, replace
> > > it by $myhostname.
> >
> > Perhaps. Otherwise one may get some surprises.
>
> This is presently done by the queue manager. If and only if
> local_destination_recipient_limit = 1, which is the default.

This was incorrect. I was confusing the queue name with the recipient.

With the following settings:

    mydestination = {any list of domain names}
    myorigin = one domain listed in mydestination

And with:

    ~test/.forward:
        test, nobody

Sending mail to test{any domain listed in mydestination} results in

    postfix/local[pid]: QID: to=<test$myorigin>, orig_to=<test{any
        domain in mydestination}>, relay=local, delay=dd, status=sent
        (mailbox)
    postfix/local[pid]: QID: to=<wietse$myorigin>,
        orig_to=<test{any domain in mydestination}>, relay=local,
        delay=dd, status=sent (mailbox)

And that makes a lot of sense to me. There is no loop.

        Wietse

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]