On 4/27/06, Gary Buckmaster <[EMAIL PROTECTED]> wrote: > I'm giving SpamD and have it all basically configured, although I'm > stuck at the NextMTA setting. This setting appears to assume only a > single MTA behind pfSense. Is this correct? Is there a way to specify > multiple transport mappings for multiple MTAs or would this require me > installing postfix behind the scenes and setting up the transport > mappings from there?
Good question. I'd say right now its hot-wired to one host *BUT* we can make a change to support aliases, then you can add as many MTA's until your heart is content. > Another, semi-related question. How would the spamD package handle a > situation where an MTA or multiple MTAs are sitting behind a bridged DMZ > interface? Does the package set up an interception rule for inbound > tcp-25 traffic? Yep, at the moment it hijacks anything incoming to the firewall with destination port 25. Let me think about how this can be improved, but I have a feeling we may be able to do the same trick with aliases. Scott --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
