From: Ralf Hildebrandt (Ralf.Hildebrandtcharite.de)
Date: Mon Feb 06 2006 - 10:31:52 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

* Bill Bradford <mrbillmrbill.net>:
> On Mon, Feb 06, 2006 at 07:59:25AM +0100, Ralf Hildebrandt wrote:
> > Useless. Leave smtpd_helo_restrictions empty.
>
> Done.
>
> > > smtpd_sender_restrictions =
> > > permit_mynetworks
> > > reject_unauth_pipelining
> > > reject_unknown_sender_domain
> > > smtpd_recipient_restrictions =
> > > permit_mynetworks
> > > permit_mx_backup
> > > permit_auth_destination
> > > reject_unauth_destination
> > > reject_unknown_recipient_domain
> > > check_policy_service inet:127.0.0.1:6000
> > > check_helo_access dbm:/etc/postfix/helo_checks
> > Why didn't you put these into smtpd_helo_restrictions?
>
> Because I thought where I put them is where they're *supposed* to go...

The logic escapes me. You put client stuff into
smtpd_client_restrictions and now you say "check_helo_access" goes
into smtpd_recipient_restrictions?? WHy?

> So I should move check_helo_access and the check_policy_service to
> smtpd_helo_restrictions? Everything I've seen documentation-wise says
> to put the policy service check under smtpd_recipient_restrictions.

check_helo_access dbm:/etc/postfix/helo_checks
is NOT the policy service!

--
Ralf Hildebrandt (Ralf.Hildebrandtcharite.de) spamtrapcharite.de
Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155
http://www.postfix-buch.com
What goes up, must come down.
Ask any system administrator.

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]