Hi Noel,
Actually I wanted to use it in production after a successful test,
but as I see now I should change my mind and use a "real" new instance.
But I'm afraid that would cause new problems, look, what I exactly need:
We communicate with some partner companies in an
extranet.
If an email
a) goes to the partner @example_domain1.com (then send it to the 2nd
instance) and
b) this email contains a specific string in the subject ([CR])
then it should be rejected or otherwise delievered to @dst_domain1.com (by 2nd
instance).
All other email should be delievered by the first instance as it does now.
Important: All email should be scanned by trendmicro imss-scanner.
First question: can I use the same ip address for the 2nd instance (with
another port)?
The second question is, do I also need a second instance of imss?
Since I need to use imss from both postfix instances.
How does imss know to which postfix instance ( port number) it should return
the scanned emails?
Does it work automatically by tfhe definition of the content filter loop back
port in the 2nd master.cf?
Thanks for your help
Jannis
--- On Tue, 9/2/08, Noel Jones <[EMAIL PROTECTED]> wrote:
From: Noel Jones <[EMAIL PROTECTED]>
Subject: Re: _checks in a postfix instance?
To: [EMAIL PROTECTED], postfix-users@postfix.org
Date: Tuesday, September 2, 2008, 7:04 AM
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
