You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by KelvinTang <ke...@namespro.ca> on 2008/05/15 23:17:51 UTC
DCC Warning
I am currently using SpamAssassin 3.2.4 on cygwin.
All is good, except DCC.
When I call dcc alone, the result is good:
================================================
$ dccproc -C -i sample-spam.txt
X-DCC-Rhyolite-Metrics: ns2 104; Body=many Fuz1=many Fuz2=many
reported: 1 checksum server
From: ba807b1f 901b88b4 59688582 cf417dd4
Message-ID: 08d1475a 0103776d 23f5e639 58dd6deb
Body: 13f72fc1 f640a327 b6f6ba3c 76e8a7e5 many
Fuz1: 13f6c01c 03133760 bd468b03 4109bc7a many
Fuz2: 9cf42e99 eff6c33d c49b523b c7ae4ba6 many
================================================
However, for some reason, DCC failed when calling within SpamAssassin. The
following is the debug information from SpamAssassin:
================================================
[2900] dbg: dcc: dccifd is not available: no r/w dccifd socket found
[2900] dbg: dcc: dccproc is available: /usr/local/bin/dccproc
[2900] dbg: info: entering helper-app run mode
[2900] dbg: dcc: opening pipe: /usr/local/bin/dccproc -H -x 0 -d <
/tmp/.spamassassin2900M3ReCotmp
[3500] dbg: util: setuid: ruid=500 euid=500
[2900] dbg: dcc: [3500] finished: exit=0x8000
[2900] dbg: info: leaving helper-app run mode
[2900] warn: dcc: check failed: failed to read header
================================================
Pyzor and Razor are both running accordingly.
Any help will be appreciated!!
--
View this message in context: http://www.nabble.com/DCC-Warning-tp17262741p17262741.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
Re: DCC Warning
Posted by Matus UHLAR - fantomas <uh...@fantomas.sk>.
On 15.05.08 14:17, KelvinTang wrote:
> All is good, except DCC.
>
> When I call dcc alone, the result is good:
>
> ================================================
> $ dccproc -C -i sample-spam.txt
> X-DCC-Rhyolite-Metrics: ns2 104; Body=many Fuz1=many Fuz2=many
> reported: 1 checksum server
> From: ba807b1f 901b88b4 59688582 cf417dd4
> Message-ID: 08d1475a 0103776d 23f5e639 58dd6deb
> Body: 13f72fc1 f640a327 b6f6ba3c 76e8a7e5 many
> Fuz1: 13f6c01c 03133760 bd468b03 4109bc7a many
> Fuz2: 9cf42e99 eff6c33d c49b523b c7ae4ba6 many
> ================================================
>
> However, for some reason, DCC failed when calling within SpamAssassin. The
> following is the debug information from SpamAssassin:
>
> ================================================
> [2900] dbg: dcc: dccifd is not available: no r/w dccifd socket found
> [2900] dbg: dcc: dccproc is available: /usr/local/bin/dccproc
> [2900] dbg: info: entering helper-app run mode
> [2900] dbg: dcc: opening pipe: /usr/local/bin/dccproc -H -x 0 -d <
> /tmp/.spamassassin2900M3ReCotmp
> [3500] dbg: util: setuid: ruid=500 euid=500
> [2900] dbg: dcc: [3500] finished: exit=0x8000
> [2900] dbg: info: leaving helper-app run mode
> [2900] warn: dcc: check failed: failed to read header
I have no idea what does this mean, but have you tried running dccifd? That
might help...
--
Matus UHLAR - fantomas, uhlar@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Your mouse has moved. Windows NT will now restart for changes to take
to take effect. [OK]