On Thu, Oct 11, 2012 at 04:05:14PM -0500, Paul Schmehl wrote: > mynetworks = 127.0.0.0/8,IP.Of.Fortimail.Firewall
(BTW the /32 is implied, you do not need to specify it.) This in reply to: > --On October 11, 2012 1:44:04 PM -0700 BeauSanders > <b...@beausanders.org> wrote: > > >I am attempting to configure a Postfix MTA in CentOS 6.3 for our > >school. The Postfix server has to send and receive email through > >a Fortimail firewall. Outgoing email is working fine. Email sent > >locally using the mail command to a local user on the > >CentOS/Postfix server works fine. However, all email coming in to > >the Fortimail firewall addressed to users on the Postfix server > >is NOT being accepted by Postfix. Inbound mail from Fortimail is > >being deferred and ultimately rejected by Postfix. It appears the > >email is being forwarded/relayed from the Fortimail firewall to > >the Postfix server. There are no errors on the Fortimail firewall. And subsequently Paul wondered why this was considered the wrong solution to the problem. One potential problem I see is that of mail loops. Fortimail is allowing Postfix to relay, and is our relayhost. If Fortimail believes Postfix should handle a certain address, but Postfix does not agree, it will loop. With Fortimail in $mynetworks, Postfix allows it to relay. And from the problem description above, it does not sound like relaying is needed. Fortimail wants Postfix to take this mail for final delivery, and $mynetworks won't help with that. I don't think open relay is likely to be the result, but again, there's no reason why a relayhost should EVER be in $mynetworks. The ball is in the OP's court, so to speak, to better define the problem and to share the logs which show it. > >Here is the main.cf file as it is currently configured: snip -- http://rob0.nodns4.us/ -- system administration and consulting Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
