On Wed, Jul 20, 2011 at 01:49:20PM +0200, Lars T??uber wrote:
> using this leads me into this error message:
> mail.err:
> [...] postfix/smtpd[29046]: fatal: open lock file pid/unix.../world/sname:
> cannot create file exclusively: No such file or directory
>
> I couldn't find locking options for
Hello everybody,
Am Wed, 20 Jul 2011 08:43:29 -0400 (EDT)
Wietse Venema schrieb:
> Lars T?uber:
> > > $ ls -ld /var/spool/postfix/private/ /var/spool/postfix/public/
> > > drwx-- 2 postfix root 4096 Jun 7
> > > 17:59 /var/spool/postfix/private/ drwx--x--- 2 postfix postdrop 4096
> > >
Lars T?uber:
> > $ ls -ld /var/spool/postfix/private/ /var/spool/postfix/public/
> > drwx-- 2 postfix root 4096 Jun 7 17:59 /var/spool/postfix/private/
> > drwx--x--- 2 postfix postdrop 4096 Jun 7 17:59 /var/spool/postfix/public/
> >
> > > Am I doing something wrong?
> >
> > To run an
Hi Victor,
Am Tue, 19 Jul 2011 11:37:56 -0400
Victor Duchovni schrieb:
> On Tue, Jul 19, 2011 at 05:02:34PM +0200, Lars T??uber wrote:
>
> > The unix socket can't be used by other users than root or postfix.
> > Is there a way to configure ownership and/or permissions for the socket?
>
> No, th
Sorry I had the automatic linebreaking activated in my mail program.
The correct command line was this:
# sudo -u postfix /usr/bin/socat - UNIX-CONNECT:/var/spool/postfix/dspam/filter
220 DSPAM LMTP 3.6.8 Ready
quit
221 2.0.0 OK
Best wishes
Lars
Hello Victor,
Am Tue, 19 Jul 2011 11:37:56 -0400
Victor Duchovni schrieb:
> On Tue, Jul 19, 2011 at 05:02:34PM +0200, Lars T??uber wrote:
>
> > The unix socket can't be used by other users than root or postfix.
> > Is there a way to configure ownership and/or permissions for the socket?
>
> No,
On Tue, Jul 19, 2011 at 05:29:57PM +0200, Lars T??uber wrote:
> > If that's indeed the situation, review the security implications; you
> > can either use ACLs to permit the dspam user execute permission fix that
> > up (if supported and enabled on your /var filesystem), or you can
> > consider ma
On Tue, Jul 19, 2011 at 05:11:57PM +0200, Matthias Andree wrote:
> If that's indeed the situation, review the security implications; you
> can either use ACLs to permit the dspam user execute permission fix that
> up (if supported and enabled on your /var filesystem), or you can
> consider making
On Tue, Jul 19, 2011 at 05:02:34PM +0200, Lars T??uber wrote:
> The unix socket can't be used by other users than root or postfix.
> Is there a way to configure ownership and/or permissions for the socket?
No, the parent directory: $queue_directory/private, must be protected
from users other than
Hi Matthias,
Am Tue, 19 Jul 2011 17:11:57 +0200
Matthias Andree schrieb:
> Am 19.07.2011 17:02, schrieb Lars Täuber:
> > Hi Wietse,
> >
> > the unix socket can't be used by other users than root or postfix.
> > Is there a way to configure ownership and/or permissions for the socket?
> >
> > I t
Am 19.07.2011 17:02, schrieb Lars Täuber:
> Hi Wietse,
>
> the unix socket can't be used by other users than root or postfix.
> Is there a way to configure ownership and/or permissions for the socket?
>
> I thought under Linux the filesystem permissions reflect the permissions to
> the unix socke
Hi Wietse,
the unix socket can't be used by other users than root or postfix.
Is there a way to configure ownership and/or permissions for the socket?
I thought under Linux the filesystem permissions reflect the permissions to
the unix socket.
Here is my config and the socket:
master.cf:
backdoo
Lars T?uber:
> Hello Wietse,
>
> Am Thu, 14 Jul 2011 12:08:34 -0400 (EDT)
> Wietse Venema schrieb:
> > If the connection is not AF_INET or AF_INET6, Postfix pretends it
> > is localhost[127.0.0.1].
>
> thanks. This helps a lot!
> I just had a quick scan over the docs and couldn't find this info.
Hello Wietse,
Am Thu, 14 Jul 2011 12:08:34 -0400 (EDT)
Wietse Venema schrieb:
> If the connection is not AF_INET or AF_INET6, Postfix pretends it
> is localhost[127.0.0.1].
thanks. This helps a lot!
I just had a quick scan over the docs and couldn't find this info.
Thanks
Lars
Wietse Venema:
> Lars T?uber:
> > Now I translated this into unix socket:
> > backdoor
> > unix - - n - 3 smtpd
> > -o content_filter=
>
> That may work, but I wonder what the SMTP client hostname and
> address look like. That will ultimately determine wh
Lars T?uber:
> Now I translated this into unix socket:
> backdoor
> unix - - n - 3 smtpd
> -o content_filter=
That may work, but I wonder what the SMTP client hostname and
address look like. That will ultimately determine what you
can use in your access
Hello,
our mail server does local content_filtering via lmtp over unix socket.
This filter is capable of reinjecting the result via unix socket too.
I'd like to use this.
But I come across a problem.
The inet-way of reinjection is defined in our master.cf as follows:
127.0.0.1:10026
in
17 matches
Mail list logo