You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Michael Hall <mh...@riverside.org> on 2004/09/10 20:38:33 UTC
DCC error and 3.x
I just thought I'd try enabling DCC again with 'rc4' and also (still)
get the same error message:
Sep 10 11:25:57 ukiah dccproc[43025]: missing message body; fatal error
Has anybody got DCC working with 3.x? Reset my old 2.63 up again and DCC
works fine.
On Wed, Jul 21, 2004 at 03:33:16PM -0400, Jared Priddy wrote:
> Since upgrading to 3.0-pre2 I too am having this issue. Before I had lots
> of messages hitting DCC_CHECK, since upgrading I have none, only the error
> reported by Erik below. Has anyone figured this out yet?
>
> JP
>
> -----Original Message-----
> From: Erik Slooff [mailto:erik@slooff.com]
> Sent: Sunday, June 27, 2004 5:19 PM
> To: spamassassin-users@incubator.apache.org
> Subject: SA 3.0 and DCC error
>
>
> Hi all,
>
> After upgrading from 2.63 to 3.0 pre1 I've seen quite a lot of the following
> errors in my logs (never had them before):
> dccproc[708]: missing message body; fatal error
>
> I've already upgraded to the most recent version of dccproc today...
> FWIW I'm using SA with amavisd-new (latest p9) together with postfix.
>
> Anybody an idea?
--
Honk if you love peace and quiet.
Mike Hall,
System Admin - Rock Island Communications <mi...@rockisland.com>
System Admin - riverside.org, ssdd.org <mh...@riverside.org>
Re: DCC error and 3.x
Posted by Michael Hall <mh...@riverside.org>.
On Fri, Sep 10, 2004 at 02:44:51PM -0400, Theo Van Dinter wrote:
> On Fri, Sep 10, 2004 at 11:38:33AM -0700, Michael Hall wrote:
> > I just thought I'd try enabling DCC again with 'rc4' and also (still)
> > get the same error message:
> >
> > Sep 10 11:25:57 ukiah dccproc[43025]: missing message body; fatal error
> >
> > Has anybody got DCC working with 3.x? Reset my old 2.63 up again and DCC
> > works fine.
>
> Still works fine for me:
>
> 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 16677: ruid=501 euid=501
> debug: DCC: got response: X-DCC-sgs_public_dcc_server-Metrics: eclectic.kluge.net 1199; Body=2 Fuz1=5 Fuz2=many
> debug: leaving helper-app run mode
> debug: DCC: Listed! BODY: 2 of 999999 FUZ1: 5 of 999999 FUZ2: 999999 of 999999
>
> What does your -D output say? Are you running spamd, spamassassin,
> or something else? There aren't any useful details in your message.
Sorry about the delayed reply, I had a family emergency and just got back
into town this weekend and finally getting caught up with my mail :-(
Anyway, I was using 'rc4', perl 5.8.5, and amavisd-new-2.1.2, all under
FreeBSD. Feeding a message directly to spamassassin shows DCC working,
yet running from amavisd-new results in 'missing message body; fatal error'
for every message. After enabling and setting up dccifd it works fine
versus using dccproc.
Enabling debugging in amavisd-new and grepping the output I had:
debug: DCCifd is not available: no r/w dccifd socket found.
debug: DCC is available: /usr/local/bin/dccproc
DCC -> check failed: Died at /usr/local/lib/perl5/site_perl/5.8.5/Mail/SpamAssas
sin/Dns.pm line 802.
debug: DCCifd is not available: no r/w dccifd socket found.
debug: DCC is available: /usr/local/bin/dccproc
debug: DCCifd is not available: no r/w dccifd socket found.
debug: DCC is available: /usr/local/bin/dccproc
debug: DCC -> check timed out after 10 secs.
debug: DCC -> check timed out after 10 secs.
debug: DCCifd is not available: no r/w dccifd socket found.
debug: DCC is available: /usr/local/bin/dccproc
debug: DCC -> check timed out after 10 secs.
debug: DCCifd is not available: no r/w dccifd socket found.
debug: DCC is available: /usr/local/bin/dccproc
debug: DCCifd is not available: no r/w dccifd socket found.
debug: DCC is available: /usr/local/bin/dccproc
debug: DCC -> check timed out after 10 secs.
debug: DCC -> check timed out after 10 secs.
debug: DCCifd is not available: no r/w dccifd socket found.
debug: DCC is available: /usr/local/bin/dccproc
which seems to indicate its actually a timeout issue. Interesting enough
after reading the 3.0 announcement thread regarding 'pyzor' not working
(bugzilla ID 3649) this sounded similar. After applying Mark Martinec's
fix logic for the pyzor issue to dcc it now works (SA 3.0, dccproc,
and amavisd-new). What I did was just uncomment the old line and comment
out the new line(s) in Dns.pm:
sub dcc_lookup
...
my $pid = open(DCC, join(' ', $path, "-H", $opts, "< '$tmpf'", "2>&1", '|'))
|| die "$!\n";
#my $pid = Mail::SpamAssassin::Util::helper_app_pipe_open(*DCC,
# $tmpf, 1, $path, "-H", split(' ', $opts));
...
--
Mike Hall,
System Admin - Rock Island Communications <mi...@rockisland.com>
System Admin - riverside.org, ssdd.org <mh...@riverside.org>
Re: DCC error and 3.x
Posted by Theo Van Dinter <fe...@kluge.net>.
On Fri, Sep 10, 2004 at 11:38:33AM -0700, Michael Hall wrote:
> I just thought I'd try enabling DCC again with 'rc4' and also (still)
> get the same error message:
>
> Sep 10 11:25:57 ukiah dccproc[43025]: missing message body; fatal error
>
> Has anybody got DCC working with 3.x? Reset my old 2.63 up again and DCC
> works fine.
Still works fine for me:
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 16677: ruid=501 euid=501
debug: DCC: got response: X-DCC-sgs_public_dcc_server-Metrics: eclectic.kluge.net 1199; Body=2 Fuz1=5 Fuz2=many
debug: leaving helper-app run mode
debug: DCC: Listed! BODY: 2 of 999999 FUZ1: 5 of 999999 FUZ2: 999999 of 999999
What does your -D output say? Are you running spamd, spamassassin,
or something else? There aren't any useful details in your message.
--
Randomly Generated Tagline:
"I want 'c' students to strive to become great, but I don't actually want
them to get there." - Jennifer Tilly on Politically Incorrect, 2001.05.22
Re: DCC error and 3.x
Posted by Alex S Moore <as...@edge.net>.
On Fri, 2004-09-10 at 13:38, Michael Hall wrote:
> I just thought I'd try enabling DCC again with 'rc4' and also (still)
> get the same error message:
>
> Sep 10 11:25:57 ukiah dccproc[43025]: missing message body; fatal error
>
> Has anybody got DCC working with 3.x? Reset my old 2.63 up again and DCC
> works fine.
No problem here. In the past, I have seen a few 'missing message body'
messages, but not lately. Although it should not matter, I use dccifd
and not dccproc. I have some of these messages until the end of
August. I installed 1.2.51 on Sep 04.
Are you running the latest stable version of dcc?
Alex
RE: DCC error and 3.x
Posted by Erik Slooff <er...@slooff.com>.
> I just thought I'd try enabling DCC again with 'rc4' and also (still)
> get the same error message:
>
> Sep 10 11:25:57 ukiah dccproc[43025]: missing message body;
> fatal error
>
> Has anybody got DCC working with 3.x? Reset my old 2.63 up
> again and DCC
> works fine.
>
> On Wed, Jul 21, 2004 at 03:33:16PM -0400, Jared Priddy wrote:
> > Since upgrading to 3.0-pre2 I too am having this issue.
> Before I had lots
> > of messages hitting DCC_CHECK, since upgrading I have none,
> only the error
> > reported by Erik below. Has anyone figured this out yet?
> >
> > JP
Jared,
I'm still having the same probs, even with sa 3.0rc4 and the latest dccproc
version (1.2.51). No solution yet...
Erik