Re: DSpam Content Filter via Header_Checks

Am Donnerstag, den 05.05.2005, 11:25 +0200 schrieb Magnus B=E4ck:
> On Thursday, May 05, 2005 at 11:12 CEST,
> Jens Mittag <jens.mittag@prime23.de> wrote:
>=20
> > I thought, let's decide that in the header_checks... to prevent "too
> > many hops", I first check if the mails was already scanned by DSpam
> > (X-DSPAM-Result Header) and if not, check if the mail is for my local
> > domains and whether or not, send it through DSpam.
> >=20
> > ## main.cf
> > header_checks =3D pcre:/etc/postfix/header_checks
> >=20
> > ## /etc/postfix/header_checks (version 1)
> > if !/^X-DSPAM-Result/
> > /for <.*@(domain1.tld|domain2.tld|domain3.tld)>/ FILTER dspam:
> > endif
>=20
> That's not how header_checks works. One line is inspected at a time.
> The above means "if this line does not match /^X-DSPAM-Result/ and
> THE SAME LINE matches /for <.*@(domain1.tld|domain2.tld|domain3.tld)>/
> then apply the FILTER action".
>=20
> There is no need to use something that complex. Example:
>=20
> smtpd_client_restrictions =3D
> check_client_access cidr:/path/to/file
>=20
> /path/to/file:
> # Your local subnet(s)
> 1.2.3.0/24 OK
>=20
> # A catch-all for the rest
> 0.0.0.0/0 FILTER dspam:
>=20
> [...]
>=20

Sounds nice, but doesn't fit in my environment, because my mailserver is
not "local", but in some computer center. So, I cannot differentiate
between two networks - incoming and outgoing mails are accepted over the
same ip address. The users which are allowed to send mails via postfix
authenticate via SASL.

Thanks anyway.
Jens
--=20
Jens Mittag <jens.mittag@prime23.de>