Difference between revisions of "Talk:Email"

From SME Server
Jump to navigationJump to search
 
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
====Pyzor Timeout====
+
* by HF‎
{{Incomplete}}
+
Unnilennium issued a warning on http://wiki.contribs.org/Email#Bayesian_Autolearning
 
+
{{warning box|the properties BayesAutoLearnThresholdSpam BayesAutoLearnThresholdNonspam  seems unavailable on SME8 and SME7.6 as far as I search as 2014/01/24  }}
See [[Bugzilla: 5973]]
+
Please discuss and verify before we alter the main how-to. It could well be the db keys are not there by default, but are taken into consideration once present. If so or suspect so, please raise a bug before disrupting documentation with unconfirmed possible issues. We can not issue warnings just like that.
{{Warning box|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
 

Latest revision as of 22:27, 24 January 2014

  • by HF‎

Unnilennium issued a warning on http://wiki.contribs.org/Email#Bayesian_Autolearning

Warning.png Warning:
the properties BayesAutoLearnThresholdSpam BayesAutoLearnThresholdNonspam seems unavailable on SME8 and SME7.6 as far as I search as 2014/01/24


Please discuss and verify before we alter the main how-to. It could well be the db keys are not there by default, but are taken into consideration once present. If so or suspect so, please raise a bug before disrupting documentation with unconfirmed possible issues. We can not issue warnings just like that.