Mike Morris:
[ Charset ISO-8859-1 unsupported, converting... ]
> On 08/01/2010 09:29 AM, Wietse Venema wrote:
> > Mike Morris:
> >> Hi,
> >>
> >> I'm working on a mail server deployment that will only have one server
> >> for MX and SASL submission purposes. Generally I like to have separate
> >> Postfix instances to handle a specific task. In this case I'm running
> >> in to problems when the submission instance uses the same IP address as
> >> the MX instance. (Due to a limited IP address pool there is currently
> >> only one routable IP address assigned to this server.)
> >>
> >> Using the submission instance to send a message to a recipient address
> >> for which the server is also the MX host triggers Postfix' loop
> >> detection. Mail for foreign addresses is relayed correctly. I realize
> >> this can be done easily enough without using multiple instances. Is
> >> there a way to work around this so that an MX instance and submission
> >> instance can share single IP address? I've gotten used to the queue,
> >
> > If you use different MTAs, then use different myhostname AND
> > different inet_interfaces settings. Otherwise it is just too easy
> > to screw up and have a high-speed mail system meltdown/explosion/etc.
> >
> > Postfix is not just about "secure" for some vague definition of
> > secure, it is about making a safe to use, so that it does not rip
> > off your arms and legs when you make a trivial mistake.
> >
> > Wietse
>
>
> Fair enough. I'll see what can be done about a second IP address.
Or enable the commented-out submission service (port 587) in the
default master.cf file. With this, use port 587 for submission,
and port 25 for final delivery.
Wietse
