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.

For local(8) delivery, this must be 1.

It is by default.

Moral: if you don't know what you're changing in main.cf, stay away
from it.

        Wietse

Wietse Venema:
> Victor.Duchovnimorganstanley.com:
> > On Thu, 14 Nov 2002, Wietse Venema wrote:
> >
> > > What is the minimum example that reproduces the problem? For example,
> > > suppose I have:
> > >
> > > mydestination = localhost.$mydomain $myhostname
> > > myorigin = $myhostname
> > >
> > > what .forward file and what initial recipient address would loop?
> > >
> >
> > OK, here is my chance to have egg on my face:
> >
> > I predict that mail to userlocalhost.$mydomain loops once and bounces (if
> > untouched by canonical/virtual) with a .forward file of the form:
> >
> > ~user/.forward:
> > user, nobody
> >
> > The first recipient in been_here is presumably userlocalhost.$mydomain,
> > the second is user$myhostname and the two are different so the one hop
> > forwarding loop is not detected.
>
> The trivial-rewrite resolver replaces $mydestination recipient
> domains by $myhostname, to avoid such loops:
>
> Nov 14 16:48:10 bristle postfix/local[17444]: 04A3928E70:
> to=<userbristle.domain.tld>, orig_to=<userlocalhost>,
> relay=local, delay=1, status=sent (mailbox)
> Nov 14 16:48:10 bristle postfix/local[17444]: 04A3928E70:
> to=<wietsebristle.domain.tld>, orig_to=<userlocalhost>,
> relay=local, delay=1, status=sent (mailbox)
>
> On this particular machine, nobody is aliased to me.
>
> I tried it with other domain names listed in mydestination,
> and got the same result as with sending to userlocalhost.
>
> Note, this is with post-1.1 snapshots. The stable Postfix release
> uses a different address resolver that pre-dates transport map
> wild-card and userdomain patterns.
>
> Wietse
>
>

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