What method are you connecting to your CygWin SpamD?
Perhaps the problem is not with SpamD, but with SpamC. I noticed that the
new SA3.0 doesn't always fill the incoming TCP for your SpamC calling
application buffer... I use 1024 byte buffers. This may be throwing
whichever SpamC you are using
@spamassassin.apache.org
Subject: RE: Cygwin SA3.0 Problems
It seems something in the Cygwin packages may be causing the problem. I
have version 3.0 working here and at work under cygwin, however, I
installed cygwin wyyy back when 2.62 was just released. If I do a
copy install (install cygwin
Here are CygWin instructions that I wrote a few months ago that worked for
me and others up to and including SA-3.0.0-rc2... at which point I moved to
a dedicated SuSE Linux 9.1 server for SpamD and then wrote a custom SpamC
client on windows for XMail Server.
Feel free to take whatever info you
:[EMAIL PROTECTED]
Sent: Sunday, September 26, 2004 4:46 AM
To: 'JamesDR'; users@spamassassin.apache.org
Subject: RE: Cygwin SA3.0 Problems
Here are CygWin instructions that I wrote a few months ago that worked
for
me and others up to and including SA-3.0.0-rc2... at which point I moved