Re: Advanced content filter with Unix sockets

2022-02-05 Thread Nick Tait
On 31/01/22 07:36, Wietse Venema wrote: Viktor Dukhovni: So I was wondering whether the directory currently named "public" should remain (permission-wise) protected, with the new (permission-wise) unprotected directly named something else? It could become mode 755, with dedicated per-app subdir

Re: Advanced content filter with Unix sockets

2022-01-30 Thread Wietse Venema
Viktor Dukhovni: > On Sun, Jan 30, 2022 at 12:28:06PM -0500, Wietse Venema wrote: > > > > > We could redesign the master.cf 'private' field, so that for > > > > UNIX-domain sockets: > > > > > > > > master.cf directory mode > > > > y private 0700 (no change) > > >

Re: Advanced content filter with Unix sockets

2022-01-30 Thread Viktor Dukhovni
On Sun, Jan 30, 2022 at 12:28:06PM -0500, Wietse Venema wrote: > > > We could redesign the master.cf 'private' field, so that for > > > UNIX-domain sockets: > > > > > > master.cf directory mode > > > y private 0700 (no change) > > > n protected

Re: Advanced content filter with Unix sockets

2022-01-30 Thread Wietse Venema
Viktor Dukhovni: > On Sun, Jan 30, 2022 at 12:14:30PM -0500, Wietse Venema wrote: > > > Perhaps the time has come to get away from giving non-Postfix > > programs access to a directory with Postfix internal sockets. > > > > We could redesign the master.cf 'private' field, so that for > > UNIX-dom

Re: Advanced content filter with Unix sockets

2022-01-30 Thread Viktor Dukhovni
On Sun, Jan 30, 2022 at 12:14:30PM -0500, Wietse Venema wrote: > Perhaps the time has come to get away from giving non-Postfix > programs access to a directory with Postfix internal sockets. > > We could redesign the master.cf 'private' field, so that for > UNIX-domain sockets: > > master.cf

Re: Advanced content filter with Unix sockets

2022-01-30 Thread Wietse Venema
Viktor Dukhovni: > On Sun, Jan 30, 2022 at 03:33:16PM +0100, Christoph Pleger wrote: > > > > You're mistaken. On input, Postfix provides no LMTP server, and no > > > support for receiving messages from external programs via unix-domain > > > sockets. > > > > I have the following line in master.c

Re: Advanced content filter with Unix sockets

2022-01-30 Thread Viktor Dukhovni
On Sun, Jan 30, 2022 at 03:33:16PM +0100, Christoph Pleger wrote: > > You're mistaken. On input, Postfix provides no LMTP server, and no > > support for receiving messages from external programs via unix-domain > > sockets. > > I have the following line in master.cf: > > usmtp unix n

Re: Advanced content filter with Unix sockets

2022-01-30 Thread Christoph Pleger
Hello, > > The other way round, passing from the filter to postfix only using UNIX > > sockets, is working. > > You're mistaken. On input, Postfix provides no LMTP server, and no > support for receiving messages from external programs via unix-domain > sockets. I have the following line in mast

Re: Advanced content filter with Unix sockets

2022-01-30 Thread Viktor Dukhovni
On Sun, Jan 30, 2022 at 02:39:32PM +0100, Christoph Pleger wrote: > the advanced content filter documentation in > http://www.postfix.org/FILTER_README.html describes how an email is > passed to a content filter listening on a TCP port on localhost, but > how is the email passed if the content fil

Advanced content filter with Unix sockets

2022-01-30 Thread Christoph Pleger
Hello, the advanced content filter documentation in http://www.postfix.org/FILTER_README.html describes how an email is passed to a content filter listening on a TCP port on localhost, but how is the email passed if the content filter is listening on a unix socket? I have tried the following in m