On Mon, Mar 16, 2015 at 02:39:15AM +0000, Viktor Dukhovni wrote: > > Then there are the built-in inet services, smtpd(8), postscreen(8) > or qmqpd(8). These can be cloned to create custom TCP service > endpoints. Most common: > > smtp inet n - n - - smtpd
It's my understanding that with "inet", the name of the service is one from /etc/services, and you can use an IP address there if you want. But it's not really clear from the documentation. The documentation also says that for "unix" it listens on the unix socket with that name. And I guess "smtp unix" is what it looks up talk to the process that sends mail. It's confusing to see "smtp inet" with smtpd as command, and "smtp unix" with smtp as command. You would expect both of them to be about incomming connections. But then there can be things like "smtpd pass", and I have no clue what that things does. Is smtpd the name of the unix socket that postscren looks up to hand of the request? > You can build new transports with the pipe(8) delivery agent. I've seen people use pipe for doing things like filtering spam. That is, use a smtpd content_filter, and then have a service with that name that uses pipe. The documentation says it's send to a "transport:destination", most of the examples I've seen don't have a destination while postfix's documentation has ":dummy" there. But then the services has "unix" in it's line. And what is "transport", the name of a service? Kurt
