From: Covington, Chris (ccovingtonplusone.com)
Date: Mon Mar 01 2004 - 18:53:12 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi all,

If my MX gateways have loads such as:

 19:38:23 up 120 days, 2:29, 1 user, load average: 0.08, 0.03, 0.01
66 processes: 65 sleeping, 1 running, 0 zombie, 0 stopped
CPU0 states: 0.0% user 0.0% system 0.0% nice 0.0% iowait 100.0%
idle
CPU1 states: 0.1% user 0.0% system 0.0% nice 0.0% iowait 99.0%
idle
Mem: 2064504k av, 1451336k used, 613168k free, 0k shrd, 107640k
buff
                    614100k actv, 555152k in_d, 1264k in_c
Swap: 2044072k av, 0k used, 2044072k free 592680k
cached

Would there be any problems using smtpd_proxy_filter to call amavisd-new
running SA and anti-virus (Other than the amavisd-new logging issue:
"Client broke the connection without a QUIT" of course)?

The average message analysis time is 4 seconds, with it sometimes
reaching 11 or 12 if a SpamAssassin network test is slow.

The ultimate reason is that the existing Postfix content_filter with
amavisd-new D_DISCARD "silenty discard mail judged to be spam" has a
black-hole effect if a not-so-savvy AOL (ie USERNAME_ENDS_IN_NUMS) user
forwards a joke or something like that with weird HTML formatting, etc.
to one of our users and it ends up in the spam quarantine and isn't
manually forwarded until a week or so later (which is a hassle). It
would be preferable that the AOL user would be notified that his message
bounced, though this might cause backscatter for real spam. There's
always a trade-off.

Chris

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]