Talk:Email
From SME Server
Jump to navigationJump to searchPyzor Timeout
See Bugzilla: 5973
This can mitigated by the adding of a template fragment.
Template fragment to set a pyzor_timeout based on a value in the config db. If no value is set, there is no output (so pyzor uses it's internal default).
mkdir -p /etc/e-smith/templates/etc/mail/spamassassin/local.cf/50pyzor_timeout cd /etc/e-smith/templates/etc/mail/spamassassin/local.cf/50pyzor_timeout nano 50pyzor_timeout
Contents of 50pyzor_timeout
{ my $pyzor_timeout = ($spamassassin{PyzorTimeout} || 0); if ($pyzor_timeout ne '0') { return "pyzor_timeout " . ($pyzor_timeout); } }
Then a value can be set using:
config setprop spamassassin PyzorTimeout 15
Then expand the template
expand-template /etc/e-smith/templates/etc/mail/spamassassin/local.cf/50pyzor_timeout