Jannis Kafkoulas wrote:
Hi,
we're using postfix 2.3.8-2+b1 on a debian etch box with imss.
I wanted to reject all emails to the company ccc.com or ccc.net with a
subject
containing a specific string ("Subject: [xxx] " in this test. I also
tried different variations).
So I created a new postfix instance on port 10023 where the
subject should be checked against the string of interest.
A filter directs all emails going to ccc.com to this instance.
This is what we call a postfix listener on port 10023. A
postfix "instance" implies a whole separate config of postfix,
with its own queue and config directories.
While this is OK for limited testing, note that if the 10023
instance rejects mail, it will create backscatter.
Not suitable for a production environment.
This instance receives the email but now it seems that the header_check
doesn't work.
The regexp works fine when I'm testing a test file with the postmap command.
header_checks are a property of the postfix cleanup process,
not the postfix smtpd process.
I'm also wandering why I can't see the file
/etc/postfix/header_checks_NR.cf
in the postconf -n output.
"postconf -n" only shows the parameters it knows about.
ad-hoc and custom parameters are not shown.
Can someone help me with this please?
You can either:
- define an alternate cleanup service with your test
header_checks, and tell the 10023 smtpd listener to use that
cleanup.
- you can set up a separate postfix instance.
--
Noel Jones
