On Sat, Jun 06, 2020 at 01:46:14PM -0400, Wietse Venema wrote: > Wietse Venema: > > Ian Evans: > > > Food for thought from the co-author of OAuth and oEmbed. How easy would it > > > be for Postfix/Postscreen configs/docs to, say, refer to allow/deny lists? > > > > Easily, if they can be acessed via DNSBL/DNSWL qeueries. Any 'new' > > lookup mechanism will have to be added through a postscreen policy > > plugin, and that involves new Postfix code. > > > > For context: Postscreen decides if a remote SMTP client is allowed > > to talk to a Postfix SMTP service. The decision is made on (protocol) > > behavior and reputation, plus a static allow/deny list that is > > typically populated with information from major provider SPF records. > > I did not realize this was a suggestion to re-word Postfix documentation > (and presumably, the corresponding program and parameter names). > > Changing 'blacklist' into 'blocklist' or 'blackhole' into 'sinkhole'
There is nothing wrong with the use of the word blacklist and blackhole, or the word black. > seems doable. There is no 'slave' in documentation, program names > or parameter names. Internal identifiers and comments can be udpated > with no visible consequence. Other changes would be difficult. > > Wietse -- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 http://www.nylxs.com - Leadership Development in Free Software http://www2.mrbrklyn.com/resources - Unpublished Archive http://www.coinhangout.com - coins! http://www.brooklyn-living.com Being so tracked is for FARM ANIMALS and extermination camps, but incompatible with living as a free human being. -RI Safir 2013
