wt., 17 gru 2024 o 11:45 Jeremy Harris via Exim-users < exim-users@lists.exim.org> napisał(a):
> On 16/12/2024 16:22, Marcin Owsiany via Exim-users wrote: > > What could it be? It would have been helpful if the error message > > mentioned what was the attempted operation... > > It's the open for the -D file for a message. Is it the open() call for writing or reading? > It could have been > in the main spool directory or a split-spool subdir (which are > checked even when not running split-spool, to handle leftovers > from a changeover). If something is creating what looks like > a split-spool-dir occasionally, that would confuse the issue. > The path mentioned in the message does not seem like a split-spool one, right? Or are you saying that the message would still include the non-split path even if the error was encountered on the split-spool file? > Given the errno "permission denied", something is messed-up > with permissions or ownerships on your systems. > I tried sending a message with "mail -s test root < /dev/null" after "sudo su - netdata" and this does not trigger the error. I suspect there might be some kind of restriction set on the context of the netdata daemon process, which gets inherited by the exim binary when run as /usr/lib/sendmail, that causes this error. But it's weird that it can write to the spool file, but not reopen it! > Check also in system logs - /var/log/messages, systemd journal > and so on - in case there's anything there, > I already had, nothing out of the ordinary. Marcin -- ## subscription configuration (requires account): ## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/ ## unsubscribe (doesn't require an account): ## exim-users-unsubscr...@lists.exim.org ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
