This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Spamassassin + exim + cygwin

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 <= [] P=esmtp S=2831
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 ==
R=spamcheck_router T=spamcheck defer (-24): Filter process failure

In the routers section of exim.conf I have:

# Spam Assassin
  # 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
  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?



Jason D. Michaelson             | Debian GNU/  o    |         __
VERITAS Software                |        / /    __  _  _  _  _ __  __
2815 Cleveland Ave - ROS2-4     |       / /__  / / / \// //_// \ \/ /
Roseville, MN 55113             |      /____/ /_/ /_/\/ /___/  /_/\_\
Voice: (651)746-7263            |
Cell: (612)812-2459             |   ...because lockups are for

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,
on the other end, and the goat, terminated over the SCSI chain with
a silver-handled knife whilst burning *black* candles. --- Anthony

Unsubscribe info:
Bug reporting:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]