Thank you for replying, Victor. I've had empty subject fields rejected for
years to avoid spam. I mean I had this very basic regexp rule set in my header
checks. It looks like I may have to remove it now and to re-configure it a bit
in combination with procmail, according to this new prefatory /requirement. I
think it will be easier than to put a cart before the horse in my attempts to
use procmail before header_checks. Thanks again.
Den
-----Original Message-----
From: Viktor Dukhovni <postfix-us...@dukhovni.org>
To: postfix-users@postfix.org
Sent: Mon, 10 Jun 2019 21:34
Subject: Re: Regexp Postfix query doesn't stop at the first matching rule
On Mon, Jun 10, 2019 at 03:51:17AM -0700, Den1 wrote:
> Just one teeny tiny comment. Header_checks will trigger before procmail,
> sieve and so on therefore I am pretty much out of luck. Empty subject fields
> will be rejected before either procmail or sieve inserts / replaces the
> subject field (header) in question.
Postfix header checks are by default not enabled, so do not reject
empty subjects by default, and can't reject messages with a missing
subject. You don't have to reject empty subjects.
> Are there any ways to run procmail before header_checks
Only by somehow using procmail as content_filter, for which it is
probably not well suited. So basically, no...
> or is my best bet to move it all to procmail?
You can use a Sieve milter, proxy filter, or defer the processing
to delivery, but then you've already accepted the message, and
should not reject it. You can tag it as spam, and have it delivered
to a suitable sub-folder, or just leave the MUA to deal with the tags.
--
Viktor.
