Ville Walveranta wrote: > I was under the impression that `permit_inet_interfaces' in > smtpd_client_restrictions would've allowed requests coming *through* > the inet_interfaces (currently defined as 127.0.0.1, 192.168.1.99 – > still in the testing environment) but not from the additional > interface created in master.cf as 192.168.1.97.
The documentation *is* quite clear on this point: http://www.postfix.org/postconf.5.html#permit_inet_interfaces > But apparently this is > not the case; apparently permit_inet_interfaces allows the request > when its IP matches that _of_ the interface, i.e. in this case > 127.0.0.1 or 192.168.1.99. When would a request match one of those? > What, in other words, is the use for permit_inet_interfaces? I've not seen permit_inet_interfaces used before, but an instance where it might be useful is an application running on the same machine. If the application uses a DNS lookup to get the address (eg. mail.example.com maps to 192.168.1.99) then this might be useful. That said, the client in this case would often (but obviously not always) be in $mynetworks. > ...any other client is allowed on the "public" interface > but not one of the spam filtering service Another access table should do the job if you want it.
signature.asc
Description: OpenPGP digital signature
