Re: [exim] tainted filname issue

Pàgina inicial
Delete this message
Reply to this message
Autor: Dan Egli
Data:  
A: exim-users
Assumpte: Re: [exim] tainted filname issue
On 5/5/2021 4:04 AM, Heiko Schlittermann via Exim-users wrote:
>   # determine the domain to be used for signing (use the rfc5322.From
>      # or schlittermann.de as a fallback
>      dkim_domain = ${lookup{${domain:${address:$h_from:}}}dsearch{$config_dir/dkim}{$value}{schlittermann.de}}
>      dkim_selector = ${lookup{$dkim_domain}lsearch{$config_dir/dkim/selector}}

>
>      # use the found signing domain and it's selector to get
>      # the private key
>      dkim_private_key = $config_dir/dkim/$dkim_domain/$dkim_selector.pem

Okay, I changed my dkim_private_key line to:
    dkim_domain =
${lookup{${domain:${address:$h_from:}}}dsearch{/etc/exim/DKIM/}{$value}{newideatest.site}}

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 exim conks out saying I passed a bad or incomplete
argument:

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 exim_new.conf -d=0xf7795cfd -MCd
daemon-accept-delivery -Mc 1leOFn-000466-HW
exim abandoned: unknown, malformed, or incomplete option -MCd
15754 SMTP<< QUIT


So how do I figure out what the heck is going on here?

--

Dan Egli
From my Test Server