You need to setup your trusted_networks and internal_networks values
to get rid of ALL_TRUSTED. These values are usually stored in the
/etc/mail/spamassassin/local.cf file. Read the wiki regarding the
trusted_networks setup.
Trusted_networks is merely a short list of mailers from when you
directly receive email that you can trust not to forge addresses.
That is the only trust involved. I use fetchmail and with the
headers it places in mail my trusted_networks value can be a simple
"127/8". Then I set "internal_networks 192.168/16" as rather large
overkill for the real setup here.
If you receive directly then your smtp server's IP address that it
places in the email Received headers would be appropriate for the
trusted_networks. And if you have a whole Internet block of addresses
they should probably be in your internal_networks values.
Of course, this is a topic we've been talking about for the last
couple days already. So you probably didn't think of the right search
term. {^_-}
{^_^}
----- Original Message -----
From: "Chad" <[EMAIL PROTECTED]>
Hello!
I've been googling and searching this list for a little over 2 hours
now and have yet to find this problem, or a fix for it. If there is
something obvious I'm missing, feel free to point me in that
direction, but here goes:
I recieve Spam from "Doctor" with the subject "Ultimate Online Pharmaceutical"
It's subject gets marked up correctly with my [SPAM] subject_rewrite,
and I have report_safe set to 1, so the message shows the score as:
Content analysis details: (9.2 points, 5.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
2.3 DATE_IN_FUTURE_12_24 Date: is 12 to 24 hours after Received: date
0.1 HTML_40_50 BODY: Message is 40% to 50% HTML
0.0 HTML_MESSAGE BODY: HTML included in message
0.1 RCVD_IN_SORBS_DUL RBL: SORBS: sent directly from dynamic IP address
[217.217.190.99 listed in dnsbl.sorbs.net]
1.8 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net
[Blocked - see <http://www.spamcop.net/bl.shtml?217.217.190.99>]
2.5 RCVD_IN_XBL RBL: Received via a relay in Spamhaus XBL
[217.217.190.99 listed in sbl-xbl.spamhaus.org]
1.7 RCVD_IN_NJABL_DUL RBL: NJABL: dialup sender did non-local SMTP
[217.217.190.99 listed in combined.njabl.org]
0.6 URIBL_SBL Contains an URL listed in the SBL blocklist
[URIs: asciatini.com]
As noted, it's a score of 9.2 points total.
But, when I check the header, it shows:
X-Spam-Level:
X-Spam-Status: No, score=0.5 required=5.0 tests=ALL_TRUSTED,
DATE_IN_FUTURE_12_24,HTML_40_50,HTML_MESSAGE,MIME_HTML_MOSTLY,
URIBL_SBL autolearn=no version=3.0.2-gr1
Which makes procmail NOT do it's job of sorting this into the correct
Spam folder.
The closest thing I've seen is that a server is underpowered (which I
don't think that's my problem) and a work-around for that to call
Spamassassin twice, which I tried but it didn't work.
So, I really don't know what else to tell you guys, but will include
contents of files and version below for additional help. Thanks for
any info!
~/.procmailrc:
## Set to yes when debugging
VERBOSE=no
## I'm assuming that you are using pine, which means that your mail is
## stored in "~/mail". If not, figure out where your mail is stored
## (for example, "~/Mail" or "~/.mail" or "~/.Mail"), and set MAILDIR
## to that directory.
MAILDIR=$HOME/Maildir
## Directory for storing procmail-related files
PMDIR=$HOME/.procmail
## Put '#' before LOGFILE if you want no logging (not recommended)
LOGFILE=$PMDIR/log
## filter spam
INCLUDERC=$PMDIR/spam.rc
~/.procmail/spam.rc:
:0fw: spamassassin.lock
| /usr/bin/spamc
# The following three lines move messages tagged as spam to a folder
# called "spam-folder" If you want mail to stay in your inbox, just
# delete the lines
# Try a second time if SpamC failed
:0fw: spamassassin.lock2
* ! ^X-Spam-Level:.*
| spamc
# Filter Spam with a level of 15 or higher to Trash:
:0:
* ^X-Spam-Level: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
.Trash/
# And finally, filter as noted above:
:0:
* ^X-Spam-Status: Yes
.Spam/
/etc/spam/local.cf:
# This is the right place to customize your installation of SpamAssassin.
#
# See 'perldoc Mail::SpamAssassin::Conf' for details of what can be
# tweaked.
#
###########################################################################
#
# Set this to 0 to disable altering the subject line
# rewrite_subject 1
# The above is commented out, and the below was changed from subject_tag to
# rewrite_header Subject in versions above 3.0
# Set this with whatever string wanted to alter subject line with (see above)
rewrite_header Subject [SPAM]
# This setting is to display the email address to contact for assistance
report_contact [EMAIL PROTECTED]
# This setting is to set the desired language allowed
ok_languages en
# report_safe 1
trusted_networks 192.168.1.1
sa version:
spamassassin --version
SpamAssassin version 3.0.2
running on Perl version 5.8.6
And procmail version:
procmail v3.22
Thanks!
Chad
