Hello, We are running SpamAssassin version 3.1.7-deb running on Perl version 5.8.4 on a Debian Sarge box with exim4.
I am using the following router: ====================================================================== sa_router: no_verify check_local_user # When to scan a message : # - it isn't already flagged as spam from Spamassassin # - it isn't already scanned # - it isn't local # - it isn't from one internal domain user to another condition = "${if and { \ {!eq {$received_protocol}{spam-scanned}} \ {!eq {$received_protocol}{local}} \ {!eq {$sender_address_domain}{$domain}} \ } \ {1}{0}}" driver = accept transport = sa_spamcheck local_parts = /etc/spamassassinUsers ====================================================================== and the following transport: ====================================================================== sa_spamcheck: driver = pipe command = /usr/sbin/exim4 -oMr spam-scanned -bS use_bsmtp = true transport_filter = /usr/bin/spamc home_directory = "/tmp" current_directory = "/tmp" user = spamcheck group = spamcheck log_output = true return_fail_output = true return_path_add = false message_prefix = message_suffix = ====================================================================== This always used to work perfectly until i upgraded spamassassin using apt-get to the version above (which was done in order to give us access to the "sa-update" command). Now, on some emails spamd eats up 99% CPU and doesn't return until i kill it, at which point the email is delivered as non-spam, whether it is spam or not. Does anyone know why this is happening? It's destroying the use of our mail server, lol! Also, FYI, here is a copy of /etc/spamassassin/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. # # Only a small subset of options are listed below # ########################################################################### rewrite_subject 1 # Add *****SPAM***** to the Subject header of spam e-mails # rewrite_header Subject ****SPAM**** (_HITS_/_REQD_): # Save spam messages as a message/rfc822 MIME attachment instead of # modifying the original message (0: off, 2: use text/plain instead) # report_safe 1 # Set which networks or hosts are considered 'trusted' by your mail # server (i.e. not spammers) # # trusted_networks 212.17.35. trusted_networks 192.168.3. trusted_networks 193.128.142. # Set file-locking method (flock is not safe over NFS, but is faster) # # lock_method flock # Set the threshold at which a message is considered spam (default: 5.0) # required_score 2.5 # Use Bayesian classifier (default: 1) # # use_bayes 1 # Bayesian classifier auto-learning (default: 1) # # bayes_auto_learn 1 # Set headers which may provide inappropriate cues to the Bayesian # classifier # # bayes_ignore_header X-Bogosity # bayes_ignore_header X-Spam-Flag # bayes_ignore_header X-Spam-Status # WHITELIST whitelist_from [EMAIL PROTECTED] whitelist_from [EMAIL PROTECTED] whitelist_from [EMAIL PROTECTED] whitelist_from [EMAIL PROTECTED] whitelist_from [EMAIL PROTECTED] whitelist_from [EMAIL PROTECTED] whitelist_from [EMAIL PROTECTED] ====================================================================== Thanks in advance for any assistance! It's greatly appreciated! Richard. -- Richard Hobbs (Systems Administrator) Toshiba Research Europe Ltd. - Speech Technology Group Email: [EMAIL PROTECTED] Web: http://www.toshiba-europe.com/research/ Tel: +44 1223 376964 Mobile: +44 7811 803377