On 2021-10-20 at 11:31:48 UTC-0400 (Wed, 20 Oct 2021 17:31:48 +0200) Alessio Cecchi <ales...@skye.it> is rumored to have said:
> Il 20/10/21 16:46, Benny Pedersen ha scritto: >> On 2021-10-20 16:35, Alessio Cecchi wrote: >> >>> How can I configure this timeout to 5 seconds or similar? >> >> perldoc Mail::SpamAssassin::Plugin::DKIM >> >> see section override > > Thanks, I have solved with: > > adsp_override * unknown > > There still a 10 seconds time spents on DKIM check: > > Oct 20 17:19:42.210 [15847] dbg: dkim: using Mail::DKIM version 0.39 > Oct 20 17:19:42.211 [15847] dbg: dkim: performing public key lookup and > signature verification > > [ 10 seconds here] > > Oct 20 17:19:52.211 [15847] dbg: dkim: FAILED DKIM, i=@serverupgrader.xyz, > d=serverupgrader.xyz, s=default, a=rsa-sha1, c=relaxed/relaxed, unknown key > size, invalid, does not match author domain > Oct 20 17:19:52.211 [15847] dbg: dkim: signature verification result: INVALID > (PUBLIC KEY: DNS QUERY TIMEOUT FOR DEFAULT._DOMAINKEY.SERVERUPGRADER.XYZ) > > But seems a dns timeout, not a a dkim_timeout that is 5 seconds by default > (from perldoc Mail::SpamAssassin::Plugin::DKIM ). > > Any suggestion? Don't run SpamAssassin inside a chroot jail or container without working DNS? That's just a random guess since you don't say anything useful about your configuration. Because you appear to have munged relevant domain names, it is impossible to know whether the failed lookup could or should have resulted in anything. You can set default timeouts for DNS queries in /etc/resolv.conf. -- Bill Cole b...@scconsult.com or billc...@apache.org (AKA @grumpybozo and many *@billmail.scconsult.com addresses) Not Currently Available For Hire
