OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
RE: Secondary relayhost

From: Aaron Roberts (aarondomicilium.com)
Date: Fri Apr 02 2004 - 04:54:54 CST


owner-postfix-userspostfix.org wrote:
> On Friday, April 02, 2004 at 12:39 CEST,
> Aaron Roberts <aarondomicilium.com> wrote:
>
>> owner-postfix-userspostfix.org wrote:
>>
>>> Why not use content_filter? Anyway, the hostname in relayhost is
>>> subject to MX lookups (unless surrounded by brackets), so setup
>>> suitable MX records in DNS.
>>
>> content_filter sounds good. Presumably all mail would be sent there,
>> and would default to relayhost ?
>
> No. content_filter applies to all mail (even local) and can point to
> any transport defined in master.cf.
>
>
http://www.porcupine.org/postfix-mirror/newdoc/postconf.5.html#content_filter
>
>> I would use MX records, but MX records are already used to direct
>> emails on their way out of the Virus scanner - it seemed easier to
>> hard-route Postfix, rather than create (another) internal DNS view
>> for the same domains.
>
> There is no need to create another view. Just define two MX records in
> whatever zone and view applicable.
>
> virusscan IN MX 10 primary-scanner.domain.com.
> virusscan IN MX 20 secondary-scanner.domain.com.
>
> content_filter = smtp:virusscan.domain.com:25

That is a much better idea - it's so easy to get obsessed with the wrong
solution...

Thanks again,

Aaron