On 06/05/2021 02:31, Dan Egli via Exim-users wrote:
20095 LOG: MAIN PANIC DIE
20095 unable to set gid=12 or uid=8 (euid=1002): system filter
That's a basic syscall failure. My initial guess would be that
your use of symlinks, or maybe of setuid bits on binaries, is
the problem.
--
Cheers,
How that last message got encrypted, I don't know. But this should be an
unencrypted copy.
On 5/5/2021 4:04 AM, Heiko Schlittermann via Exim-users wrote:
Dan Egli via Exim-users (Mi 05 Mai 2021 02:41:38
CEST):
I just upgraded to 4.94.2, and most everything is working fine. But I'm
getting
Dan Egli via Exim-users (Mi 05 Mai 2021 22:45:34 CEST):
> and I THINK it's okay. Problem is that I'm encountering another issue that
> prevents me from saying all is well. I have my updated exim binary as
> exim_new and the updated config as exim_new.conf, but when I try to submit a
> message
On 05/05/2021 21:45, Dan Egli via Exim-users wrote:
2021-05-05 14:35:29.708 cwd=/etc/exim 5 args: exim_new -d -bd -C exim_new.conf
[much deleted for brevity]
15754 Calling SSL_read(0x5573489f8110, 0x5573489f99a0, 4096)
15758 postfork: daemon-accept-delivery
15758 exec /usr/sbin/exim -C
Dan Egli via Exim-users (Mi 05 Mai 2021 02:41:38 CEST):
> I just upgraded to 4.94.2, and most everything is working fine. But I'm
> getting an issue on DKIM signings with tainted filename. I looked over the
> list and tried to apply the same fix I've seen used before, but I guess I'm
> not
On 05/05/2021 01:41, Dan Egli via Exim-users wrote:
dkim_private_key = ${if
exists{/etc/exim/DKIM/${lc:$sender_address_domain}/dkim.private.key.pem}\
{/etc/exim/DKIM/${lc:$sender_address_domain}/dkim.private.key.pem}{0}}
So how do I correct this?
You look up that domain in a trusted
On 05/05/2021 02:41, Dan Egli via Exim-users wrote:
> dkim_private_key = ${if
> exists{/etc/exim/DKIM/${lc:$sender_address_domain}/dkim.private.key.pem}\
> {/etc/exim/DKIM/${lc:$sender_address_domain}/dkim.private.key.pem}{0}}
That's a classic already searchable on the list... use dsearch
I just upgraded to 4.94.2, and most everything is working fine. But I'm
getting an issue on DKIM signings with tainted filename. I looked over
the list and tried to apply the same fix I've seen used before, but I
guess I'm not understanding it. Here's my dkim_private_key statement:
