Spamassassin + exim + cygwin
Jason D. Michaelson
jdm@visi.com
Sat Sep 28 20:24:00 GMT 2002
I'm trying to get spamassassin to work with exim under cygwin. I've got
everything up and running fine, except for spamd. Its compiled, but when
I go to run it I end up with an ntvdm process running, using up all
available cpu time. This means that I end up running spamassassin for
each message that is received. When I do this, the following appears in
my exim logs:
2002-09-28 20:22:08 H36EGV-00039W-00 <= jdm@visi.com
H=corb.mc.mpls.visi.com [208.42.156.1] P=esmtp S=2831
id=Pine.GSO.4.10.10209282021580.10237-100000@isis.visi.com
2002-09-28 20:22:16 SMTP connection from jason lost while reading
message data (header)
2002-09-28 20:22:16 H36EGV-00039W-00 == jason@the-four-horsemen.org
R=spamcheck_router T=spamcheck defer (-24): Filter process failure
In the routers section of exim.conf I have:
# Spam Assassin
spamcheck_router:
no_verify
check_local_user
# When to scan a message :
# - it isn't already flagged as spam
# - it isn't already scanned
condition = "${if and { {!def:h_X-Spam-Flag:} {!eq
{$received_protocol}{spam-scanned}}} {1}{0}}"
driver = accept
transport = spamcheck
In the transports section I have:
# Spam Assassin
spamcheck:
driver = pipe
command = /usr/bin/exim -oMr spam-scanned -bS
use_bsmtp = true
transport_filter = /usr/bin/spamassassin
home_directory = "/tmp"
current_directory = "/tmp"
log_output = true
return_fail_output = true
return_path_add = false
message_prefix =
message_suffix =
Is there a command line option or something to spamassassin that I'm
missing that's causing the smtp connection back to exim to fail?
Thanks
jdm
---------
Jason D. Michaelson | Debian GNU/ o http://www.debian.org
Jason.Michaelson@veritas.com | __
VERITAS Software | / / __ _ _ _ _ __ __
2815 Cleveland Ave - ROS2-4 | / /__ / / / \// //_// \ \/ /
Roseville, MN 55113 | /____/ /_/ /_/\/ /___/ /_/\_\
Voice: (651)746-7263 |
Cell: (612)812-2459 | ...because lockups are for
convicts...
Getting a SCSI chain working is perfectly simple if you remember that
there must be exactly three terminations: one on one end of the cable,
one
on the other end, and the goat, terminated over the SCSI chain with
a silver-handled knife whilst burning *black* candles. --- Anthony
DeBoer
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
More information about the Cygwin
mailing list