You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Sao31113 <sa...@terra.com.br> on 2004/08/23 18:48:29 UTC
*** SpamAssassin x MailScanner
Hi:
I - My Environment:
Linux Server - Fedora Core 2
Apache - 2.0.50
Sendmail - 8.12.11
MailScanner - 4.31.6-1
SpamAssassin - 2.63
II - My /etc/procmailrc:
DROPPRIVS=yes
#Uncomment the following lines to allow for logging
LOGFILE=/var/log/procmail
VERBOSE=ON
:0fw
* < 256000
| spamc
:0e
{
EXITCODE=$?
}
:0:
* ^X-Spam-Flag: YES
/var/spool/mail/lixo
Note: All flagged Spam emails are written to this /var/spool/mail/lixo folder.
III - My /etc/mail/spamassassin/local.cf:
# SpamAssassin config file for version 2.5x
# generated by http://www.yrex.com/spam/spamconfig.php (version 1.01)
# How many hits before a message is considered spam.
required_hits 6.0
# Whether to change the subject of suspected spam
rewrite_subject 0
# Text to prepend to subject if rewrite_subject is used
subject_tag *****SPAM*****
# Encapsulate spam in an attachment
report_safe 1
# Use terse version of the spam report
use_terse_report 0
# Enable the Bayes system
use_bayes 1
# Enable Bayes auto-learning
auto_learn 0
# Enable or disable network checks
skip_rbl_checks 1
use_razor2 1
use_dcc 1
use_pyzor 1
# Mail using languages used in these country codes will not be marked
# as being possibly spam in a foreign language.
ok_languages all
# Mail using locales used in these country codes will not be marked
# as being possibly spam in a foreign language.
ok_locales all
IV - My Problem
I had all this stuff working without any problem. Until Yesterday. So,
whenever SpamAssassin flagged one email as Spam, it just wrote it to a
folder called "/var/spool/mail/lixo", as you can see configured above at
"procmailrc file", and put there all that pontuation / rules, etc
All of a sudden, it stopped doing so, that is:
a) SpamAssassin, although it seems it keeps on scanning emails, it stopped
writing them to "/var/spool/mail/lixo" directory.
b) In the other hand we realized that SpamAssassin started, at the same
time, to write them to a directory called "spam", at a path
"/var/spool/MailScanner/quarantine/2004/0823/spam". And it writes them
there with no pontuation / rules , etc.
c) The third remark is that we also realized that SpamAssassin stopped
writing Spam emails to the "/var/spool/mail/lixo" and instead writes them
to "/var/spool/MailScanner/quarantine/2004/0823/spam", but only when we
start MailScanner.
V - My Questions:
1) Why did SpamAssassin, which was working fine, all of a sudden, start
writing to "/var/spool/MailScanner/quarantine/2004/0823/spam" instead of to
"/var/spool/mail/lixo" ?
2) Why does MailScanner affect it and how to solve this, that is, how to
have SpamAssassin and Mailscanner as well, working normally together again?
I thank a lot to anyone who could help us with this.
Mario./
Re: *** SpamAssassin x MailScanner
Posted by Matt Kettler <mk...@evi-inc.com>.
At 12:48 PM 8/23/2004, Sao31113 wrote:
>a) SpamAssassin, although it seems it keeps on scanning emails, it stopped
>writing them to "/var/spool/mail/lixo" directory.
SpamAssassin never wrote mail there in the first place.. your MDA did that
(presumably procmail).
>b) In the other hand we realized that SpamAssassin started, at the same
>time, to write them to a directory called "spam", at a path
>"/var/spool/MailScanner/quarantine/2004/0823/spam". And it writes them
>there with no pontuation / rules , etc.
MailScanner does do this. SpamAssassin doesn't write mail to files at all.
>c) The third remark is that we also realized that SpamAssassin stopped
>writing Spam emails to the "/var/spool/mail/lixo" and instead writes them
>to "/var/spool/MailScanner/quarantine/2004/0823/spam", but only when we
>start MailScanner.
>1) Why did SpamAssassin, which was working fine, all of a sudden, start
>writing to "/var/spool/MailScanner/quarantine/2004/0823/spam" instead of
>to "/var/spool/mail/lixo" ?
This is a MailScanner behavior.. see your mailscanner.conf, spam action is
probably set to "quarantine".
Spamassassin itself does not, and can not, write mail anywhere, so what
directory mail gets written to is entirely out of it's control. Although
tools like MailScanner, procmail, etc can be influenced by SpamAssassin's
decisions, SA itself has no direct control over such things.
>2) Why does MailScanner affect it and how to solve this, that is, how to
>have SpamAssassin and Mailscanner as well, working normally together again?
-set up your mailscanner.conf the way you want it
-enable the "use spamassassin" option in mailscanner.
-disable any other references to spamassassin (ie: in procmail)
follow up any problems with mailscanner configuration on the
mailscanner mailing list (see www.mailscanner.info for details on the list
under the heading "
Mailing Lists"
).
RE: *** SpamAssassin x MailScanner
Posted by "Michele Neylon :: Blacknight Solutions" <mi...@blacknightsolutions.com>.
It sounds like you are trying to do two things at once and hurting yourself
in the process :)
Stop spamc/spamd and make sure they are off
MailScanner.conf has all the configuration elements you need to get your
mail tagged/delivered/deleted etc and you can tweak it your heart's content.
DO NOT try running Spam Assassin AND Mailscanner at the same time. Let MS
call SA internally.
If you are confused I would recommend you download the mailscanner manual
from:
http://www.fsl.com/support/MailScanner-Manual-Version-1.0.1.pdf
HTH
Michele
Mr Michele Neylon
Blacknight Internet Solutions Ltd
http://www.blacknight.ie/
Tel. +353 59 9137101
Re: *** SpamAssassin x MailScanner
Posted by Martin Hepworth <ma...@solid-state-logic.com>.
Hi
why use spamc AND Mailscanner?? Mailscanner can call SA from within
itself and alter headers as required so procmail can then process as
needed..
--
Martin Hepworth
Snr Systems Administrator
Solid State Logic
Tel: +44 (0)1865 842300
Sao31113 wrote:
> Hi:
>
> I - My Environment:
>
> Linux Server - Fedora Core 2
> Apache - 2.0.50
> Sendmail - 8.12.11
> MailScanner - 4.31.6-1
> SpamAssassin - 2.63
>
> II - My /etc/procmailrc:
>
> DROPPRIVS=yes
> #Uncomment the following lines to allow for logging
> LOGFILE=/var/log/procmail
> VERBOSE=ON
> :0fw
> * < 256000
> | spamc
>
> :0e
> {
> EXITCODE=$?
> }
>
> :0:
> * ^X-Spam-Flag: YES
> /var/spool/mail/lixo
>
> Note: All flagged Spam emails are written to this /var/spool/mail/lixo
> folder.
>
> III - My /etc/mail/spamassassin/local.cf:
>
> # SpamAssassin config file for version 2.5x
> # generated by http://www.yrex.com/spam/spamconfig.php (version 1.01)
> # How many hits before a message is considered spam.
> required_hits 6.0
> # Whether to change the subject of suspected spam
> rewrite_subject 0
> # Text to prepend to subject if rewrite_subject is used
> subject_tag *****SPAM*****
> # Encapsulate spam in an attachment
> report_safe 1
> # Use terse version of the spam report
> use_terse_report 0
> # Enable the Bayes system
> use_bayes 1
> # Enable Bayes auto-learning
> auto_learn 0
> # Enable or disable network checks
> skip_rbl_checks 1
> use_razor2 1
> use_dcc 1
> use_pyzor 1
> # Mail using languages used in these country codes will not be marked
> # as being possibly spam in a foreign language.
> ok_languages all
> # Mail using locales used in these country codes will not be marked
> # as being possibly spam in a foreign language.
> ok_locales all
>
> IV - My Problem
>
> I had all this stuff working without any problem. Until Yesterday. So,
> whenever SpamAssassin flagged one email as Spam, it just wrote it to a
> folder called "/var/spool/mail/lixo", as you can see configured above at
> "procmailrc file", and put there all that pontuation / rules, etc
>
> All of a sudden, it stopped doing so, that is:
>
> a) SpamAssassin, although it seems it keeps on scanning emails, it
> stopped writing them to "/var/spool/mail/lixo" directory.
>
> b) In the other hand we realized that SpamAssassin started, at the same
> time, to write them to a directory called "spam", at a path
> "/var/spool/MailScanner/quarantine/2004/0823/spam". And it writes them
> there with no pontuation / rules , etc.
>
> c) The third remark is that we also realized that SpamAssassin stopped
> writing Spam emails to the "/var/spool/mail/lixo" and instead writes
> them to "/var/spool/MailScanner/quarantine/2004/0823/spam", but only
> when we start MailScanner.
>
> V - My Questions:
>
> 1) Why did SpamAssassin, which was working fine, all of a sudden, start
> writing to "/var/spool/MailScanner/quarantine/2004/0823/spam" instead of
> to "/var/spool/mail/lixo" ?
>
> 2) Why does MailScanner affect it and how to solve this, that is, how to
> have SpamAssassin and Mailscanner as well, working normally together again?
>
> I thank a lot to anyone who could help us with this.
>
> Mario./
>
>
> ------------------------------------------------------------------------
>
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.742 / Virus Database: 495 - Release Date: 19/8/2004
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote confirms that this email message has been swept
for the presence of computer viruses and is believed to be clean.
**********************************************************************