You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@spamassassin.apache.org by Rob Kudyba <rk...@raeinternet.com> on 2005/01/27 22:11:30 UTC

Spamassassin query failed. HTTP code = 400

Using SA 3.02, specifically spamd, in conjunction with another application (MPP) and Postfix...

What might causes these types of responses?

[spamd::query] Write to socket timed out..
[SpamassassinScannerJob] {20050124_162758_233f400.26} Spamassassin query failed. HTTP code = 400

I know that HTTP code = 400 implies a "Bad Request" but what could generate that?

Thanks,

Rob
http://www.messagepartners.com/

Re: Spamassassin query failed. HTTP code = 400

Posted by Matt Kettler <mk...@evi-inc.com>.

At 04:11 PM 1/27/2005, Rob Kudyba wrote:
>Using SA 3.02, specifically spamd, in conjunction with another application 
>(MPP) and Postfix...
>
>What might causes these types of responses?
>
>[spamd::query] Write to socket timed out..
>[SpamassassinScannerJob] {20050124_162758_233f400.26} Spamassassin query 
>failed. HTTP code = 400
>
>I know that HTTP code = 400 implies a "Bad Request" but what could 
>generate that?

Confusion on the part of MPP..

No part of SA, including spamd, uses HTTP as an interface, so to even refer 
to a HTTP error code in conjunction to a SpamAssassin query is bogus.