[EMAIL PROTECTED] wrote:
Hello,
I have 2 postfix mail relays (similar postfix configuration) which
forward my incoming emails to an Exchange Server, and I have problems
after Exchange reboots. One mail relay (Relay2) “hooks” Exchange and
starts over sending mails and one (Relay1) keeps timing out though the
Exchange server is up and the connections can be established on TCP 25
with a telnet connection.
My Postfix version : 2.3.8-2
My OS : Ubuntu Feisty
My network topology is :
- Relay1 has a public IP and forwards incoming mail to a NATed firewall
(pfsense) which forwards TCP 25 to the internal IP of my Exchange server
- Relay2 has a public IP and forwards incoming mail without NAT and only
with its routes to the internal IP of my Exchange server
During the reboot of the Exchange server, the logs on Relay are similar
to :
Sep 15 12:13:33 relay postfix/qmgr[10428]: 65E2F3C03F: to=<
[EMAIL PROTECTED]>, relay=none, delay=0.28, delays=0.18/0.1/0/0, dsn=4.4.1,
status=defe
rred (delivery temporarily suspended: connect to
192.168.0.250[192.168.0.250]: Connection timed out)
This entry was logged by the postfix/qmgr program. The
message is deferred because postfix has marked the destination
as unreachable due to previous failures. No connection was
actually attempted at this time. Once a destination is marked
unreachable, postfix won't attempt a new connection to that
same destination for at least $minimal_backoff_time.
Read the QSHAPE_README to understand how postfix uses the
different queues.
If you've changed minimal_backoff_time, maximal_backoff_time,
and queue_run_delay, you should probably set them back to the
sensible default values.
http://www.postfix.org/QSHAPE_README.html
http://www.postfix.org/TUNING_README.html
If you need more help, please tell us the version of postfix
you are using (the controls available depend on your postfix
version) and show "postconf -n" output.
--
Noel Jones
