Difference between revisions of "Talk:Email"

From SME Server
Jump to navigationJump to search
Line 9: Line 9:
  
 
  /etc/e-smith/templates/etc/mail/spamassassin/local.cf/50pyzor_timeout
 
  /etc/e-smith/templates/etc/mail/spamassassin/local.cf/50pyzor_timeout
 +
 +
{
 +
  my $pyzor_timeout = ($spamassassin{PyzorTimeout} || 0);
 +
  if ($pyzor_timeout ne '0')
 +
  {
 +
      return "pyzor_timeout " . ($pyzor_timeout);
 +
  }
 +
}
 +
  
 
Template fragment to set a pyzor_timeout based on a value in the config db.
 
Template fragment to set a pyzor_timeout based on a value in the config db.

Revision as of 03:47, 22 January 2013

Pyzor Timeout

Incomplete.png Incomplete:
This article or section needs to be expanded. Please help to fill the gaps or discuss the issue on the talk page


See Bugzilla: 5973

Warning.png Warning:
SME server 7.# users be aware of an issue that can appear in the /var/log/spamd/current logs

" pyzor: [5281] error: TERMINATED, signal 15 (000f)".


This can mitigated by the adding of a custom template fragment see below

/etc/e-smith/templates/etc/mail/spamassassin/local.cf/50pyzor_timeout
{
  my $pyzor_timeout = ($spamassassin{PyzorTimeout} || 0);
  if ($pyzor_timeout ne '0')
  {
     return "pyzor_timeout " . ($pyzor_timeout);
  }
}


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). If a value is set using eg: config setprop spamassassin PyzorTimeout 10