Peter wrote:
I ran 'sa-update' as root and the directory
/var/amavisd/var/spamassassin/3.001004/updates_spamassassin_org was
created and populated with rules. Yet before that I had
/var/amavisd/usr/local/share/spamassassin containing my rules. How do
I get SA to look in the right place?
Gary V wrote:
Peter wrote:
I ran 'sa-update' as root and the directory
/var/amavisd/var/spamassassin/3.001004/updates_spamassassin_org was
created and populated with rules. Yet before that I had
/var/amavisd/usr/local/share/spamassassin containing my rules. How do
I get SA to look in the
... but I see no evidence of it, in the headers.
I can run spamassassin in debug mode as the amavis user and it appears
to me that razor2 is configured properly and being checked. So far,
none of the mail that's come through since I set it up has been spam,
so razor hasn't had a hit yet. Is it
Hi all,
is possible customize the header rows:
X-Spam-Flag:
X-Spam-Score:
X-Spam-Level:
X-Spam-Status:
as the header
X-Virus-Scanned:
(with the $X_HEADER_TAG directive in amavisd-new.conf file)?
I.E.
How i can put in the header mail
X-mystring-SPAM-Flag
in place of
X-SPAM-Flag
???
Thanks
If running 2.4.2, and SA 3.1.4, add LOCAL_STATE_DIR = '/var/lib', here:
# LOCAL_RULES_DIR = '/etc/mail/spamassassin',
LOCAL_STATE_DIR = '/var/lib',
#see man Mail::SpamAssassin for other options
stop amavisd and run amavisd debug-sa, see if it now reads the rules
from the new
Shaun T. Erickson wrote:
... but I see no evidence of it, in the headers.
I can run spamassassin in debug mode as the amavis user and it appears
to me that razor2 is configured properly and being checked. So far,
none of the mail that's come through since I set it up has been spam,
so razor
--- Gary V [EMAIL PROTECTED] wrote:
Peter wrote:
I ran 'sa-update' as root and the directory
/var/amavisd/var/spamassassin/3.001004/updates_spamassassin_org was
created and populated with rules. Yet before that I had
/var/amavisd/usr/local/share/spamassassin containing my rules. How
techlist06 wrote:
If running 2.4.2, and SA 3.1.4, add LOCAL_STATE_DIR = '/var/lib', here:
# LOCAL_RULES_DIR = '/etc/mail/spamassassin',
LOCAL_STATE_DIR = '/var/lib',
#see man Mail::SpamAssassin for other options
stop amavisd and run amavisd debug-sa, see if it now reads the rules
Peter wrote:
If running 2.4.2, and SA 3.1.4, add LOCAL_STATE_DIR = '/var/lib',
here:
# LOCAL_RULES_DIR = '/etc/mail/spamassassin',
LOCAL_STATE_DIR = '/var/lib',
#see man Mail::SpamAssassin for other options
stop amavisd and run amavisd debug-sa, see if it now reads the rules
Hallo und Guten Morgen AMaViS-user,
Unfortunately, I cannot see whether the FuzzyOcr works. How
can I test it? I have seen - with amavisd-new debug-sa - that
FuzzyOcr.pm was loaded.
P.S. OS Debian Sarge, amavisd-new-2.4.4-pre1.
ImageInfo is also loaded.
Thanks in advance.
--
Viele Gruesse,
Gary wrote:
sa-update --nogpg --updatedir /var/amavisd/usr/local/share/spamassassin
'amavisd debug-sa' picks up the rules. I set the above command to run
as cronjob once a week.
Read the warning:
http://marc.theaimsgroup.com/?l=spamassassin-usersm=11546111299
Myself, I would be more
--- Gary V [EMAIL PROTECTED] wrote:
Peter wrote:
If running 2.4.2, and SA 3.1.4, add LOCAL_STATE_DIR = '/var/lib',
here:
# LOCAL_RULES_DIR = '/etc/mail/spamassassin',
LOCAL_STATE_DIR = '/var/lib',
#see man Mail::SpamAssassin for other options
stop amavisd and run
Jim Knuth wrote:
Hallo und Guten Morgen AMaViS-user,
Unfortunately, I cannot see whether the FuzzyOcr works. How
can I test it? I have seen - with amavisd-new debug-sa - that
FuzzyOcr.pm was loaded.
Put it in debug mode (log level 2), and send the samples through that are
included with the
It says it can't find:
Mail::DKIM
Mail::DKIM::Verifier
Mail::SpamAssassin::BayesStore::PgSQL
Mail::SpamAssassin::Plugin::DKIM
Mail::SpamAssassin::Plugin::URIDetail
Yet two of them exist on my system:
/usr/lib/perl5/vendor_perl/5.8.5/Mail/SpamAssassin/BayesStore/PgSQL.pm
14 matches
Mail list logo