header_checks hell

2012-04-25 Thread Patrick Ben Koetter
I'm having trouble with a simple header check running in a pre-queue amavis setup. The filter should DISCARD any Subject that begins with SPAM-Verdacht CUSTOMERNAME: # Pattern Aktion /^Subject:\ (SPAM-Verdacht CUSTOMERNAME:\ .*)$/ DISCARD $1 Postfix may read the

Re: header_checks hell

2012-04-25 Thread Ralf Hildebrandt
* Patrick Ben Koetter p...@state-of-mind.de: I'm having trouble with a simple header check running in a pre-queue amavis setup. The filter should DISCARD any Subject that begins with SPAM-Verdacht CUSTOMERNAME: # Pattern Aktion /^Subject:\ (SPAM-Verdacht

Re: header_checks hell

2012-04-25 Thread Wietse Venema
Patrick Ben Koetter: I'm having trouble with a simple header check running in a pre-queue amavis setup. The filter should DISCARD any Subject that begins with SPAM-Verdacht CUSTOMERNAME: # Pattern Aktion /^Subject:\ (SPAM-Verdacht CUSTOMERNAME:\ .*)$/

Re: header_checks hell

2012-04-25 Thread Patrick Ben Koetter
* Ralf Hildebrandt postfix-users@postfix.org: * Patrick Ben Koetter p...@state-of-mind.de: I'm having trouble with a simple header check running in a pre-queue amavis setup. The filter should DISCARD any Subject that begins with SPAM-Verdacht CUSTOMERNAME: # Pattern

Re: header_checks hell

2012-04-25 Thread Ralf Hildebrandt
Not that I am aware of: # == # service type private unpriv chroot wakeup maxproc command + args # (yes) (yes) (yes) (never) (100) #

Re: header_checks hell

2012-04-25 Thread Christian Rößner
Hi, # == # service type private unpriv chroot wakeup maxproc command + args # (yes) (yes) (yes) (never) (100) # == smtp

Re: header_checks hell

2012-04-25 Thread Patrick Ben Koetter
* Wietse Venema postfix-users@postfix.org: Patrick Ben Koetter: I'm having trouble with a simple header check running in a pre-queue amavis setup. The filter should DISCARD any Subject that begins with SPAM-Verdacht CUSTOMERNAME: # Pattern Aktion

Re: header_checks hell

2012-04-25 Thread Patrick Ben Koetter
* Ralf Hildebrandt postfix-users@postfix.org: Not that I am aware of: # == # service type private unpriv chroot wakeup maxproc command + args # (yes) (yes) (yes) (never) (100) #

Re: header_checks hell

2012-04-25 Thread Wietse Venema
Patrick Ben Koetter: * Ralf Hildebrandt postfix-users@postfix.org: Not that I am aware of: # == # service type private unpriv chroot wakeup maxproc command + args # (yes) (yes) (yes)

Re: header_checks hell

2012-04-25 Thread Christian Rößner
That's the problem. The smtpd shown above never queues the mail, so no cleanup there. Enable them on reentry. Sorry, but I don't believe so. The master.cf I test with has receive_override_options=no_unknown_recipient_checks on re-entry and specifies header_checks for the re-entry instance.

SOLVED: Re: header_checks hell

2012-04-25 Thread Patrick Ben Koetter
* Wietse Venema postfix-users@postfix.org: Patrick Ben Koetter: * Ralf Hildebrandt postfix-users@postfix.org: Not that I am aware of: # == # service type private unpriv chroot wakeup maxproc