On Thu, 2005-06-09 at 11:05 -0400, Steven Dickenson wrote:
Peter Guhl wrote:
Well, still... somehow I don't get why the software is running as spamd
and tries to write into /root. I wouldn't say anything if the sofware
inwvolved wasn't designed to cooperate (spamd, spamass-milter
--
Peter Guhl [EMAIL PROTECTED]
NetzWerkCenter GmbH
On Thu, 2005-06-09 at 13:03 +0200, Peter Guhl wrote:
Cannot write to /root/.spamassassin/user_prefs: Permission denied
/root/.spamassassin/ is world-writable (of course I can't leave it like
this, but apparently this error message points me to the wrong
direction.
Nope, it was right
On Sun, 2005-03-13 at 05:09, John Andersen wrote:
On Saturday 12 March 2005 02:47 pm, jdow wrote:
The canonical way to do it is something like:
rewrite_header Subject *SPAM* _SCORE(00)_ **
That gives headers that look like:
Subject: *SPAM* 027.3 ** spoo is best for
Hello all
Our Mailclient handles * in filter rules as wildcards. Now I tried to
change the subject tagging to # (as I have seen it at other
spamassassins-results) but this is the comment character (-- --lint
fails). Experimenting with escaping resulted in \\#SPAM\\# (using
\#SPAM\# in local.cf)
Hello
Mails ending in Novell GroupWise don't seem to be useful for sa-learn.
Does somebody have some experience or solutions to that problem? Could
the same POP3-Solution described in sa-learn with lotus notes do it's
job here too?
More for GroupWise professionals would be the question how to
Hello
Mails ending in Novell GroupWise don't seem to be useful for sa-learn.
Does somebody have some experience or solutions to that problem? Could
the same POP3-Solution described in sa-learn with lotus notes do it's
job here too?
More for GroupWise professionals would be the question how to
On Fri, 2005-01-21 at 10:56, Jon Gerdes wrote:
*** Before acting on this email or opening any attachment you are advised to
read the disclaimer at the end of this email ***
http://wiki.apache.org/spamassassin/ResendingMailWithHeaders?action=highlightvalue=groupwise
Hello all
We have got some customers who want to get their mails in Chinese. Now
the bayes filter happened to block them because the only Chinese mails
it ever saw where spam (Chinese customers, but no Chinese employees...).
Now I am looking for a way to control the treatment of Chinese mails (a
