no content-filter for authed users

4 msg	Forwards vs aliases ?

no content-filter for authed users
\ Stefan Palme (15 Nov 2007)
. \ mouss (15 Nov 2007)
. . \ Stefan Palme (15 Nov 2007)
. . \ Stefan Palme (16 Nov 2007)

2 msg	postfix does not flush queued mails
1 msg	Re: [dkim-milter-beta] mlfi_negotiate() problem
2 msg	newby Q
14 msg	PAM 'smtp' file question
5 msg	Cyrus SASL2 + Postfix + PAM - part 3
9 msg	transport error?
3 msg	Can't figure out if this rejection is coming fr...
8 msg	Alias with check_recipient_access: /etc/ppostfi...
2 msg	NDR reports
7 msg	Sender-ID and the Hotmail devil...
2 msg	Postifx with IMAP
2 msg	Postfix and procmail
4 msg	destination limits - what is 'destination'
1 msg	Redirect message based on Conditions
1 msg	Cyrus SASL2 + Postfix + PAM - part 2
6 msg	Cyrus SASL2 + Postfix + PAM
5 msg	header_checks and content_filter documentation ...
2 msg	Some problem configuring postfix/procmail with ...

Subject:	no content-filter for authed users
Group:	Postfix-users
From:	Stefan Palme
Date:	15 Nov 2007

Hi,

currently I have the following setup in main.cf:

content_filter = amavis:[127.0.0.1]:10024
smtpd_recipient_restrictions =
permit_mynetworks,
permit_sasl_authenticated,
reject_non_fqdn_recipient,
reject_unknown_recipient_domain,
reject_unauth_destination,
check_policy_service unix:private/postgrey,
permit
smtpd_sasl_auth_enable = yes
...

On 127.0.0.1:10024 is amavis running, which re-injects mails via
127.0.0.1:10025 into the postfix system.

For authenticated users I don't want to use the content-filter:

/etc/postfix/main.cf:
# content-filter = none
smtpd_recipient_restrictions =
permit_mynetworks,
permit_sasl_authenticated,
reject_non_fqdn_recipient,
reject_unknown_recipient_domain,
reject_unauth_destination,
check_policy_service unix:private/postgrey,
check_client_access static:FILTER amavis:[127.0.0.1]:10024,
permit

Is this the right way to achieve what I want?

Currently amavis re-injects the checked mails via 127.0.0.1:10025.
I think when I use the above setup omitting the content filter,
those mails still have to be injected to 127.0.0.1:10025. The cleanup
service used for the :25 smtp server does not do virtual_alias_mapping
- this is done by the cleanup-service used for the 10025-smtp server.

So I must "route" the mails which skip content-filtering into
127.0.0.1:10025 to let the second cleanup service do its work.

How to do this?

Thanks and regards
-stefan-