[SC.LUG] Spamassassin

Ben Whyte ben at whyte-systems.co.uk
Thu Nov 3 19:51:42 GMT 2005


Simeon

Any reason why your using sa-exim rather than the included eximscan way 
of using spamassasin.  We use eximscan and use an acl to process the 
mail through spamassasin and antivirus

The second batch of results shows a successful scan by spamassassin.

Any question give us a shout.

Ben

Simeon W Farrington wrote:

>Hi Folks
>
>Having all sorts of fun trying to persuade spamassassin to work with
>exim4 at the moment. I thought I'd got it all sussed last night once I
>installed sa-exim, but when I switched the machine on tonight, although
>things seem to be working (well, I didn't get any junk mail!) the logs
>seem to suggest something isn't quite right (log extract below).
>
>Any ideas why spamc is being denied?
>
>I had thought about getting procmail up and running again, but it seems
>to be that evolution really seems to muck around with where it stores
>it's mail :( More work required methinks, but it never used to be this
>complicated when I last had this set up!
>
>Cheers
>
>Simeon
>
>Nov  3 18:06:07 gandalf spamd[3755]: spamd starting
>Nov  3 18:06:13 gandalf spamd[3757]: server started on port 783/tcp
>(running version 3.0.3)
>Nov  3 18:06:13 gandalf spamd[3757]: server successfully spawned child
>process, pid 3926
>Nov  3 18:06:13 gandalf spamd[3757]: server successfully spawned child
>process, pid 3927
>Nov  3 18:06:13 gandalf spamd[3757]: server successfully spawned child
>process, pid 3928
>Nov  3 18:06:13 gandalf spamd[3757]: server successfully spawned child
>process, pid 3929
>Nov  3 18:06:13 gandalf spamd[3757]: server successfully spawned child
>process, pid 3930
>Nov  3 18:23:43 gandalf spamc[4901]: connect(AF_INET) to spamd at
>127.0.0.1 failed, retrying (#1 of 3): Connection refused
>Nov  3 18:23:44 gandalf spamc[4901]: connect(AF_INET) to spamd at
>127.0.0.1 failed, retrying (#2 of 3): Connection refused
>Nov  3 18:23:45 gandalf spamc[4901]: connect(AF_INET) to spamd at
>127.0.0.1 failed, retrying (#3 of 3): Connection refused
>Nov  3 18:23:46 gandalf spamc[4901]: connection attempt to spamd aborted
>after 3 retries
>Nov  3 18:23:46 gandalf spamd[4902]: spamd starting
>Nov  3 18:23:47 gandalf spamd[4904]: server started on port 7830/tcp
>(running version 3.0.3)
>Nov  3 18:23:47 gandalf spamd[4906]: connection from gandalf [127.0.0.1]
>at port 32962
>Nov  3 18:23:47 gandalf spamd[4904]: server successfully spawned child
>process, pid 4906
>Nov  3 18:23:47 gandalf spamd[4904]: server successfully spawned child
>process, pid 4907
>Nov  3 18:23:47 gandalf spamd[4904]: server successfully spawned child
>process, pid 4908
>Nov  3 18:23:47 gandalf spamd[4904]: server successfully spawned child
>process, pid 4909
>Nov  3 18:23:47 gandalf spamd[4904]: server successfully spawned child
>process, pid 4910
>Nov  3 18:23:47 gandalf spamd[4906]: processing message (unknown) for
>simeon:1000.
>Nov  3 18:23:47 gandalf spamd[4906]: clean message (-1.3/5.0) for
>simeon:1000 in 0.1 seconds, 19 bytes.
>Nov  3 18:23:47 gandalf spamd[4906]: result: . -1 -
>ALL_TRUSTED,MISSING_SUBJECT
>scantime=0.1,size=19,mid=(unknown),autolearn=unavailable
>Nov  3 18:23:47 gandalf spamd[4907]: connection from gandalf [127.0.0.1]
>at port 32963
>Nov  3 18:23:47 gandalf spamd[4907]: checking message <04a401c5e08f
>$5d06d080$50c1a00a at rtdom.com> for simeon:1000.
>Nov  3 18:23:47 gandalf spamd[4907]: clean message (-2.3/5.0) for
>simeon:1000 in 0.2 seconds, 2876 bytes.
>
>
>  
>




More information about the SC mailing list