OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Wietse Venema (wietse_at_porcupine.org)
Date: Thu Nov 14 2002 - 16:02:40 CST

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

    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