On 10/20/04 8:40 AM, "Matt Kettler" wrote: > Mailscanner is inappropriately impatient with SpamAssassin. It's timeouts > were designed in the pre-bayes era, and are not designed to accommodate > bayes housekeeping chores like expiry and journal syncs. > > In the short term, you can help by running a sa-learn --force-expire on > your bayes DB. > > In the longer term, here's some suggestions I use on my own MailScanner > server: (I use all of these together)
Matt I wanted to personally say thanks! We too had time out issues with the new 3.0 and MS. Certain spams happened to sneak in randomly and looking at the headers showed SA timing out. Applying your suggestions works! This morning when I came in to check our servers and mail, no SA time outs on any mail. Kudos' again for a great tip. Needs to be in the FAQ of SA or at the least MS. -- David Thurman The Web Presence Group http://www.the-presence.com Web Development/E-Commerce/CMS/Hosting/Dedicated Servers 800-399-6441/309-679-0774
