Re: Issue with reject_unknown_client and CNAME Data as per RFC2317

* Michel R Vaillancourt <misha@wolfstar.ca>:

> Hello, to the list. I'm dealing with a similar issue, with a slight twist. I have
> the PERL-based pop-before-smtp implemented per the how-to on Ralf's site and it
> works well. However, it turns out that our up-stream ISP at work has been lazy
> about A records... even though I authenticate to my home mail server with
> pop-before-smtp, I still get get REJECT for relay.
>
> smtpd_client_restrictions = hash:/etc/postfix/access,
> permit_mynetworks,
> check_client_access hash:/etc/postfix/pop-before-smtp,
> reject_rbl_client relays.ordb.org,
> reject_rbl_client dnsbl.njabl.org,
> reject_unknown_sender_domain,
> reject_unknown_client
>
> ....the 'problem' seems to be the "reject_unknown_client" line.

No. Any OK in check_client_access hash:/etc/postfix/pop-before-smtp
ENDS the evaluation of smtpd_client_restrictions

Also, your config makes no sense, since check_client_access
hash:/etc/postfix/pop-before-smtp must go into
smtpd_recipient_restrictions.

--
Ralf Hildebrandt Ralf.Hildebrandt@charite.de
my current spamtrap spamtrap@charite.de
http://www.arschkrebs.de/postfix/ Tel. +49 (0)30-450 570-155
"I have traveled the length and breadth of this country and talked with
the best people, and I can assure you that data processing is a fad that
won't last out the year."
- The editor in charge of business books for Prentice Hall, 1957.