The weird thing is I don’t have a /etc/procmail file?

I did edit the squirrelmail config to the following so far:

rewrite_subject 1
subject_tag [SPAM] Score: _HITS_/_REQD_ -
required_hits 5.0

required_hits 5.0
rewrite_subject 1
subject_tag [SPAM] Score: _HITS_/_REQD_ -

auto_learn 1

#Black Listing#

blacklist_from abmtiu@yahoo.com
blacklist_from *@netcom.com
blacklist_from *@porschezone.com
blacklist_from muuext@yahoo.com
blacklist_from *@atonement9529pirrs.com
blacklist_from *@industrialac.com
blacklist_from *@isp.knotwork.com


# End SpamAssassin Configuration File


Does this make sense so far? I think the .procmailrc file is not even being used? Is there a rule that I can put in the squirrelmail config to automatically delete spam?

Ahh I see. I use procmail and that's why it works for me and not you. I don't know off the top of my head about squirrelmail, but I imagine there's something in the docs or forums about it that would help. I'll do some research and see what I can find.

Travis

I use Outlook to access my mail all the time. And only use squirrelmail every once in while when I'm out of town. But I did do apt-get install procmail and when I do a search on my HD I find /usr/bin/procmail so I take it it's installed? Now I don't know if procmail is reading the .procmailrc files in the home directory? i see this in the logs:

Sep 12 19:13:03 localhost spamd[12657]: processing message <1095045334.010318-18208-slash-slashdot-nfs-1.osdn.net@slashdot.org> for USER:50$
Sep 12 19:13:14 localhost spamd[12657]: clean message (3.3/5.0) for USER:500 in 12.0 seconds, 25562 bytes.
Sep 12 19:13:14 localhost postfix/local[12651]: 694C33F334: to=<EMAIL>, relay=local, delay=13, status=sent ("|/usr/bin/procmail)

Yep, sounds like it's reading the procmailrc file. Also, webmin (www.webmin.com) has a module built in that's called Usermin. It allows you to check your mail and take care of stuff with your account if you want. I use it at home for my webmail needs. Just a thought. Glad to see you've got it up and running though! It does take some time, but once you get Linux up and running, almost nothing will bring it down (except power failure, hardware issues, alien attack, etc.)

Travis

Well it's finally working Here are my configs!

/home/USER/.procmailrc

# SpamAssassin sample procmailrc
#
# Pipe the mail through spamassassin (replace 'spamassassin' with 'spamc'
# if you use the spamc/spamd combination)
#
# The condition line ensures that only messages smaller than 250 kB
# (250 * 1024 = 256000 bytes) are processed by SpamAssassin. Most spam
# isn't bigger than a few k and working with big messages can bring
# SpamAssassin to its knees.
#
# The lock file ensures that only 1 spamassassin invocation happens
# at 1 time, to keep the load down.
#

:0fw: spamassassin.lock
* < 256000
| spamassassin

# Mail spam to the spamuser e-mail account

:0:
* ^X-Spam-Status: Yes
! spamuser@Domain.com

# Work around procmail bug: any output on stderr will cause the "F" in "From"
# to be dropped. This will re-add it.
:0
* ^^rom[ ]
{
LOG="*** Dropped F off From_ header! Fixing up. "

:0 fhw
| sed -e '1s/^/F/'
}

~~~~~~~~~~~~~~~~~~~~~~~~~~~

/etc/mail/spamassassin/local.cf

~~~~~~~~~~~~~~~~~~~~~~~~~~~

# These values can be overridden by editing ~/.spamassassin/user_prefs.cf
# (see spamassassin(1) for details)

# These should be safe assumptions and allow for simple visual sifting
# without risking lost emails.

# 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 5.0

# Whether to change the subject of suspected spam
rewrite_subject 1

# 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 1

# Enable or disable network checks
skip_rbl_checks 0
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.
# - english
ok_languages en

# Mail using locales used in these country codes will not be marked
# as being possibly spam in a foreign language.
ok_locales en


#Black Listing#

blacklist_from abmtiu@yahoo.com
blacklist_from *@netcom.com
blacklist_from *@porschezone.com
blacklist_from muuext@yahoo.com
blacklist_from *@atonement9529pirrs.com
blacklist_from *@industrialac.com
blacklist_from *@isp.knotwork.com
blacklist_from *@cyberis.fr
blacklist_from *@wizard.net
blacklist_from *@directresponseback.com
blacklist_from *@irol.net
blacklist_from *@howlermonkey.net
blacklist_from *@pop.com.br


# End SpamAssassin Configuration File


tbeehler thanks again for your help.

Hopefully this will help other newbies out there!!!!

Perfect! Glad to hear you got it up and running! If you have any further problems or questions, come on back and we'll get you all hooked up!!!

Travis