assin/user_prefs in my home directory to add
further whitelist_from commands, spamassassin doesn't see them. Is there
any obvious reason why?
Tnx in advance.
--
Alayne McGregor
alayne at twobikes.ottawa.on.ca
"I propose a new standard by which to judge mainstream literature. The
more
of unexpected applications.
--
Alayne McGregor
alayne at twobikes.ottawa.on.ca
"But war's a game, which,
Were their subjects wise,
Kings would not play at." -- William Cowper (1731-1800)
d this problem to the list, but
got very little help.
I was going to try turning Bayes/AWL back on with 3.0.3 next week, but
obviously that's a bad idea.
--
Alayne McGregor
alayne at twobikes.ottawa.on.ca
"But war's a game, which,
Were their subjects wise,
Kings would not play at.&quo
Would it be sufficient to simply not process large messages for that user?
The distro procmailrc.example file shows how set a limit on message size
processed in your .procmailrc:
:0fw:
* < 256000
| spamassassin
sets a limit of 256K, or you could pick a much smaller number.
--
Alayne McGre
r/lib/nobody/.spamassassin -- that
had no effect, either.
Two more quick notes:
The SuSE version is 8.2 (not 9.2) on the server. Perl version is 5.8.0 .
Besides using up almost all the CPU cycles when auto-whitelist was
enabled, spamd was also eating up almost all the memory.
Alayne
On Mon, 7 Mar
vance ...
Alayne
-
debug messages from running spamd before changing local.cf:
# spamd -D
trying to connect to syslog/unix...
no error connecting to syslog/unix
logging enabled:
facility: mail
socket:
