[snip]
I think the problem is Postfix is sending using eth0, which in turn
means that it appears to come from n.n.n.186, which in turn means that a
reverse lookup does not resolve to mail.domain.tld. The loop is not
closed and therefor we are suspect.
then why not fix that?
I would like to, unf
Le 15/02/2011 20:21, John a écrit :
> First off I am still a bit green on this stuff.
>
> Both my servers are multi-homed, server A which runs Postfix is
> configured -> eth0 :n.n.n.186 and eth1:n.n.n.187.
> The host name for this server is mail.domain.tld which points to n.n.n.187.
>
> Up unti
On 2/15/2011 7:07 PM, Jeroen Geilman wrote:
On 02/15/2011 08:21 PM, John wrote:
First off I am still a bit green on this stuff.
Both my servers are multi-homed, server A which runs Postfix is
configured -> eth0 :n.n.n.186 and eth1:n.n.n.187.
The host name for this server is mail.domain.tld w
On 02/15/2011 08:21 PM, John wrote:
First off I am still a bit green on this stuff.
Both my servers are multi-homed, server A which runs Postfix is
configured -> eth0 :n.n.n.186 and eth1:n.n.n.187.
The host name for this server is mail.domain.tld which points to
n.n.n.187.
Up until last Fr
First off I am still a bit green on this stuff.
Both my servers are multi-homed, server A which runs Postfix is
configured -> eth0 :n.n.n.186 and eth1:n.n.n.187.
The host name for this server is mail.domain.tld which points to n.n.n.187.
Up until last Friday we did not have any problems. On
