Re: Issue with reject_unknown_client and CNAME Data as per RFC2317

Hello, to the list. I'm dealing with a similar issue, with a slight twis=
t. 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 bee=
n 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 =3D 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. Other th=
an removing
this line, is there a way to give "priority" to the 'check_client_access'=
statement.
I looked at the docs and tried using classes, but it didn't make a diffe=
rence.

Thanks in advance for any help folks might be able to give!

--Michel

"Poetry is what happens when you are too choked up, too much in love, or =
too pissed
off to write coherent prose"