SMTP Security Server Does Not Deliver to Lower Precedence MXs

[roadrunner]

SMTP Security Server Does Not Deliver to Lower Precedence MXs
The NG Release of FireWall-1 supports using MX records to deliver mail. This is defined on a per-resource basis.

In 4.1 and earlier releases, the way around this would be to use a "Smart" SMTP server. This SMTP Server can either be inside or outside your firewall, but you have to make sure that any SMTP traffic from this host does not get processed by any SMTP resources. To insure this doesn't happen when your mail server is inside the firewall, you need to craft your SMTP rules according to the following order:

Source Destination Service Action
Smart-SMTP-Server Any SMTP Accept
Any Internal-SMTP-Server SMTP->Inbound_Resource Accept
Internal-SMTP-Server Any SMTP->Outbound_Resource Accept


The "Smart SMTP Server" rule above your other SMTP rules with resources will insure the SMTP Security Server does not get invoked. The Inbound_Resource will be configured per your tastes. The Outbound_Resource will be configured to forward all outbound email to your "smart" SMTP server. You can do this by setting the "Mail Server" part of the resource to your smart SMTP server's IP address. This will force all outbound email to be forwarded to the Smart SMTP Server, regardless of the actual destination.

-- PhoneBoy - 01 Jan 2004


FAQForm
FAQs.Class: ContentSecurityFAQs
FAQs.OperatingSystem:
FAQs.Version: