I've searched the net for solutions and tried them, but they don't seem to work. Unfortunately I only found the solution reinstalling postfix Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Asked 3 years, 9 months ago. Active 2 years, 7 months ago. Atom topic feed.
Arch Linux. Index Rules Search Register Login. You are not logged in. Topics: Active Unanswered. Here's the full list: [root avalon postfix] ls -lah total 64K drwxr-xr-x 16 root root 4. Can you su to postfix and touch a file in that path? The stack shows that it is. These two processes are expected to have the group set to postdrop and the permission include 's' for the group.
Make sure to use ls -l like above to verify that your final changes gave the file the correct permissions. For me, that did not fix anything. That is, all of those permissions were already what they were expected to be.
What else could I do to fix that problem? Just in case, I looked at the queue directory and it is correct:. In my environment, the postdrop tool is being run from my daemon. That service runs as snapwebsites:snapwebsites and it had the NoNewPrivileges set to true.
There is the pertinent part of the snapwatchdog. When it comes to run postdrop , that tool is expected to have the right to write to a directory which allows writing by using a specific group. However, that means your service now has permission to write in that same directory as postdrop and that's probably not something you want.
The other solution is to keep the NoNewPrivileges parameter to false which is the default, but you can also make it explicit :. What we would need, though, is a way to tell systemd which tool we want to allow getting new privileges. In our case that would be the postdrop and our sendmail tools. A site for solving at least some of your technical problems
0コメント