Re: reject_unknown_client with pop-before-smtp

Milen wrote:

> I have a running Postfix with pop-before-smtp needed for authorising=20
> several clients, which use laptops with mobile connection (their IP=20
> addresses deffer each time they connect to the web).

s/web/internet/

> I want to apply 'reject_unknown_client' in 'smtp_client_restrictions'=20
> and 'reject_invalid_hostname' in 'smtpd_helo_restrictions' but this=20
> rejects my mobile users as their IP's are not correctly resolved. Is=20
> there a way to tell postfix that the IP's in the pop-before-smtp's db=20
> are part of mynetworks and if there is, how is this done?

I believe mynetworks can contain lookup maps (such as your p-b-s hash),=20
but anyway you can simply list the check_client_access restriction ahead=20
of the reject_invalid_hostname restriction. All restrictions are=20
evaluated in order. Simpler still, list all restrictions under=20
smtpd_recipient_restrictions. It avoids redundancy and makes it easier=20
to understand the order of evaluation.

smtpd_recipient_restrictions =3D
permit_mynetworks
check_client_access hash:/path/to/p-b-s.db
reject_unauth_destination
reject_unknown_client
reject_invalid_hostname

[...]

--=20
Magnus B=E4ck
magnus@dsek.lth.se