> > 2003-10-08 15:26:46 <message ID> spam acl condition: cannot parse spamd output >
> Are you using SA v2.60? I had to back down from that upgrade because
> exiscan-acl doesn't understand changes in the output of SA. I wish
> they'd take backward compatibility a little more seriously.
My exiscan patch might fix that issue, but be aware that you need to
change the ACL by prepending server and port, as:
spam = 127.0.0.1:783:user:true
I am trying to get that patch, which implements correct spamd header
parsing and allows multiple SA servers, into exiscan since quite a
while. I actually do not run the original SA, but ran into the spamd
response problem when implementing a server that used the SA protocol
specification.
