|
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
porcupine.org)
Date: Fri Jun 18 2010 - 07:50:28 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Carlos Velasco:
> > I think this is a mistake, in the sense that it is a crude work-around.
> > The right solution is keep the "inet_interfaces" settings of Postfix
> > instances *disjoint*, and to never forward mail to port 25 *within*
> > an instance. This keeps things clear and predictable.
> >
> > - Each instance "owns" a separate pool of IPs
> >
> > - Internal forwarding is never to port 25, that's
> > where outside mail comes in, and you never loop
> > it back-in again.
> >
> > - Loop detection is not disabled.
> >
> > Don't fight the system, work within the design.
> >
>
> Sorry, but I don't see your point here.
> I understand the check as to stop a mail bouncing to itself, but this is
> not the case, mail is going from one instance to another. This is,
Then,
- Give each instance its own IP address (use main.cf:inet_interfaces)
- Give each instance its own name (use main.cf:myhostname)
Work WITH the system, or else stop complaining.
Wietse
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]