Date: Tue, 24 Oct 2006 21:53:43 +0200 From: Edda Hochstrate <eh@netuse.de> To: mike <mike@coloradosurf.com> Cc: isp@freebsd.org Subject: Re: mimedefang/spamassassin/dcc Message-ID: <20061024195343.GA29404@raysrv3.netuse.de> In-Reply-To: <20061024170801.GA32638@coloradosurf.com> References: <20061024170801.GA32638@coloradosurf.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Oct 24, 2006 at 11:08:01AM -0600, mike wrote: > I am running mimedefang-2.57 w/ p5-Mail-SpamAssassin-3.1.6 on > 6.1-RELEASE-p10 (w/ dcc-dccd-1.3.42). I cannot get spamassassin > to use DCC. It makes me very sad. > > I have : > use_dcc 1 > dcc_timeout 30 > dcc_path /usr/local/bin/dccproc > > > I have verified there is no firewall issue by running dccproc > from the command line in verbose mode (and verified the > output file had the appropriate X-DCC header). just to determine what's your problem, spamassassin or mimedefang have you tried spamassassin in debug mode? /usr/bin/spamassassin -t -D < /usr/share/doc/spamassassin/examples/sample-spam.txt the debug lines for dcc should look like this with your configuration: --- [...] debug: DCCifd is not available: no r/w dccifd socket found. debug: executable for dccproc was found at /usr/local/bin/dccproc debug: DCC is available: /usr/local/bin/dccproc debug: entering helper-app run mode debug: setuid: helper proc 28365: ruid=0 euid=0 debug: DCC: got response: X-DCC-EATSERVER-Metrics: host1 1166; Body=203 Fuz1=203 Fuz2=203 debug: leaving helper-app run mode [...] --- Edda
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061024195343.GA29404>