RE: [exim] SA causing Exim 421 timeout/frozen messages

Pàgina inicial
Delete this message
Reply to this message
Autor: Bradley Walker
Data:  
A: exim-users
Assumpte: RE: [exim] SA causing Exim 421 timeout/frozen messages
Currently most all mail that is coming through that is getting frozen (which
is 85% spam) was around 80k at the largest. The average size I would say is
around 15-30k.

Mail volume is low compared to other servers. I have about a dozen domains,
each with about 5-10 users each so the total volume of email is probably
1000-2000 emails per month.

To answer your question about how Exim/SA is setup, currently it's used via
router/transport. The first reference to SA is in the "Directors
Configuration" as the very first item there with the code below. After
that, the second reference to SA is in the transports configuration, the
code is also listed below.

****************************************************************************
****************************

#***********************
#DIRECTORS CONFIGURATION
#***********************
# Spam Assassin
spamcheck_director:
  driver = accept
  condition = "${if and { \
                        {!def:h_X-Spam-Flag:} \
                        {!eq {$received_protocol}{spam-scanned}} \
                        {!eq {$received_protocol}{local}} \


{exists{/home/${lookup{$domain}lsearch{/etc/virtual/domainowners}{$value}}/.
spamassassin/user_prefs}}$
                } {1}{0}}"
  retry_use_local_part
  transport = spamcheck
  no_verify



****************************************************************************
****************************

#************************
#TRANSPORTS CONFIGURATION
#************************

# Spam Assassin
begin transports

spamcheck:
driver = pipe
batch_max = 100
command = /usr/sbin/exim -oMr spam-scanned -bS
current_directory = "/tmp"
group = mail
home_directory = "/tmp"
log_output
message_prefix =
message_suffix =
return_fail_output
no_return_path_add
transport_filter = /usr/bin/spamc -u
${lookup{$domain}lsearch*{/etc/virtual/domainowners}{$value}}
use_bsmtp
user = mail
# must use a privileged user to set $received_protocol on the way back in!



-----Original Message-----
From: exim-users-bounces@??? [mailto:exim-users-bounces@exim.org] On
Behalf Of Jakob Hirsch
Sent: Sunday, February 26, 2006 5:38 PM
To: bawalker@???
Cc: exim-users@???
Subject: Re: [exim] SA causing Exim 421 timeout/frozen messages

Bradley Walker wrote:

[many things...]

Very nice, but you told very little about your setup.
How is SA used by Exim? exiscan-acl, router/transport ...?
What is the relevant config?

The main reasons for SA timeouts are:

- scanning of large mails. scanning >200k is mostly useless
- excessive SA ruleset, network test timeouts
- overloaded system

You did also not tell much about your system and your mail volume.
Anyway, there's little Exim can do about SA timeouts (default is 300s,
IIRC), and the version of Exim has surely not anything to do with it.

What you can do on the Exim side to help SA is
- don't scan oversized messages. 200k is a conservative limit, most spam
here is below 16k, largest this month was about 77k.
- filter out as much trash as possible before it hits SA. A virus scanner
(even clamav) can help. And use callouts and/or greylisting on suspicious
stuff.



--
## List details at http://www.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://www.exim.org/eximwiki/