Loading ...
Sorry, an error occurred while loading the content.
 

RE: Order of parameters for smtpd_recipient_restrictions

Expand Messages
  • Justin Pasher
    ... Ahhh... Something so simple. That seems to have fixed the problem. Now I can remove relay_transport without breaking anything. Thanks! Justin Pasher
    Message 1 of 9 , Jun 30, 2008
      > -----Original Message-----
      > From: owner-postfix-users@... [mailto:owner-postfix-
      > users@...] On Behalf Of mouss
      > Sent: Sunday, June 29, 2008 6:30 AM
      > Cc: postfix-users@...
      > Subject: Re: Order of parameters for smtpd_recipient_restrictions
      >
      > Justin Pasher wrote:
      > > [snip]
      > >
      > > I tried removing the relay_transport directive and now I remember why I
      > set
      > > it (it was because it was the only way I could figure out how to get it
      > > working). Luckily my setup only relays mail to 10.205.154.91, so it
      > didn't
      > > cause a problem.
      > >
      > > Here's the scenario that breaks when I remove relay_transport. I
      > probably
      > > made the mistake of previously removing lines from transport_maps that I
      > > thought were not important. :(
      > >
      > > This postfix filtering server: server1.relay1-example.com
      > >
      > > /etc/postfix/transport_maps
      > > --------------------
      > > server1.relay1-example.com local:
      > > .relay1-example.com smtp:
      > >
      > > /etc/aliases
      > > --------------------
      > > root: admin@...
      > >
      > > Send email to root@...1-example.com. It will be delivered
      > through
      > > the local: transport. It is then mapped over to admin@relay1-
      > example.com,
      > > according to the aliases file. I then get a warning in the logs about a
      > mail
      > > loop.
      > >
      > > Jun 28 11:53:39 nmgapps postfix/smtp[15689]: 4571B70809D:
      > > to=<admin@...>, orig_to=<root@...1-
      > example.com>,
      > > relay=none, delay=0.01, delays=0/0.01/0/0, dsn=4.4.6, status=SOFTBOUNCE
      > > (mail for relay1-example.com loops back to myself)
      > >
      >
      > you have no transport for relay1-example.com but your postfix is an MX
      > for this domain. you need to add a transport for this domain. see below.
      > > Basically, server1.relay1-example.com relays all mail for relay1-
      > example.com
      > > and relay2-example.com. This server's name is on the same domain name as
      > the
      > > relay domain (relay1-example.com). Could this possibly be related to the
      > > gotcha you previously mentioned (receive_override_options =
      > > no_address_mappings)?
      > >
      > > I also tried changing the line in transport_maps to read the following
      > (with
      > > no luck)
      > >
      > > .relay1-example.com relay:[10.205.154.91]
      > >
      > >
      >
      > This matches subdomains, but not the domain itself:
      >
      > add the entry for the domain as well:
      >
      > relay1-example.com relay:[10.205.154.91]

      Ahhh... Something so simple. That seems to have fixed the problem. Now I can
      remove relay_transport without breaking anything. Thanks!

      Justin Pasher
    Your message has been successfully submitted and would be delivered to recipients shortly.