OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
Re: best approach to filtering one specific case?

From: Mike Ray (mrayxes-inc.com)
Date: Thu Nov 06 2014 - 13:48:22 CST


>----- Original Message -----
>From: "Wietse Venema" <wietseporcupine.org>
>To: "Postfix users" <postfix-userspostfix.org>
>Sent: Thursday, November 6, 2014 1:26:29 PM
>Subject: Re: best approach to filtering one specific case?
>
>Mike Ray:
>> The basic condition I'm trying to deal with is a message that has
>> a certain subject *and* is destined for a particular address.
>
>Hi, I wrote Postfix. Postfix does not do combinations of headers
>and other stuff. Such things are supposed to be "outsourced" to
>external filters such as Amavisd, Milters, and the like.
>
>You might be able to cobble together something with header_checks
>and such, but the solution falls apart when a requirement changes.
>
>> Secondly, I've heard that it is "better" to use milters (before-queue
>> filters?) as opposed to content filters (after-queue filters?),
>
>There is no fundamental difference in functionality between Milters
>and other before-queue filters. The main difference with after-queue
>filters is that an after-queue filter can be chosen dynamically.
>
> Wietse

I should have been more clear.

I understand that header_checks can't be checked together, but do you all think it reasonable to have a header_check for that specific address and then call a filter specific to this situation, one that could analyze the compound condition, or do you all avoid this kind of setup (if so, why)?

E.g.

/etc/postfix/main.cf:
header_checks = /etc/postfix/checkme

/etc/postfix/checkme
/this_one_addressmy.domain/ FILTER foo:bar

Or have I misunderstood: http://www.postfix.org/FILTER_README.html#dynamic_filter ?

-Mike