Need help properly configuring squirrelmail with postfix

I just set up a new install of postfix on Ubuntu Intrepid. I believe it is set up correctly. Users are able to send and recive mail fine.

I also set up squirrelmail on the same server, but anything coming via squirrelmail is getting tagged as spam when we send between schools (Almost all mail destined for our schools runs through our mailscanner with spamassassin). Headers when using squirrelmail look like this:
Received: from ( [])
     by (Postfix) with ESMTP id B2520136139
     for <>; Mon, 9 Feb 2009 15:18:58 -0600 (CST)
Received: from ( [])
     by (Postfix) with ESMTP id AEB72621A5
     for <>; Mon, 9 Feb 2009 15:18:58 -0600 (CST)
Received: from
(SquirrelMail authenticated user admin)
by with HTTP;
Mon, 9 Feb 2009 15:18:58 -0600 (CST)
Message-ID: <28e463676fe39a1d67f29ac5afcbe818.squirrel@>
Date: Mon, 9 Feb 2009 15:18:58 -0600 (CST)
Subject: 5
User-Agent: SquirrelMail/1.4.15
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)

All mail is being marked as spam by the following rules:

ached not  
3 required  
-2.60 BAYES_00 Bayesian spam probability is 0 to 1%
1.91 RCVD_ILLEGAL_IP Received: contains illegal IP address
2.07 RCVD_NUMERIC_HELO Received: contains an IP address used for HELO

I need to know what to shange in squirrelmail, apache, or postfix that will fix this issue.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

There's nothing wrong with SquirrelMail. Your SpamAssassin rules however are triggering on the IP address in the headers. Try using editing your /etc/hosts file, and change this: mail localhost.localdomain localhost

to localhost.localdomain localhost mail

That will fix the headers. Or change your spamassassin rule. Since this is a school district, you may consider using a more accurate managed anti-spam service, which typically has a better ROI. I highly recommend:

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
tamray_techAuthor Commented:
That worked. Thanks for the anti-spam solution. Mailscanner with spamassassin has worked very well for us. We scan for spam and send it to each school. They have the flexibility to scan with other solutions to check for spam we might miss, but we take the first hit, so they don't have to.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Email Servers

From novice to tech pro — start learning today.