From the looks of it, it's generated by this tool:
http://groups.google.com/groups?q=%22X-Spam-Status:+SpamAssassin+Failed%22+Communigate&hl=en&lr=&selm=list-25424187%40mail.stalker.com&rnum=1
It inserts an X-Spam-Status header, and expects SpamAssassin to over-write it. If for some reason SA doesn't get called, the failed message stays. In this case "failed" is a bit of a misnomer. It could mean SA failed, or that SA was never called at all due to some kind of bypass rule in the CG configuration.
At 11:59 AM 11/2/2004, Chr. von Stuckrad wrote:
On Tue, Nov 02, 2004 at 08:42:34AM -0500, Matt Kettler wrote: ... > >X-Spam-Status: SpamAssassin Failed ... > >What can give this error?
ON 29th of October "Alexandr Orlov <[EMAIL PROTECTED]>" also wrote a Question to the list, containig the same Header.
He said "I have a linux box with CommunigatePro + spamassasin."
So may be you'll find the same Problem at your site, and that 'CommunigatePro' MTA does not understand spamassassin>2 ?
Just an Idea, because I stumbled upon the older Message while cleaning mailfolders :-)
Stucki
-- Christoph von Stuckrad * * |nickname |<[EMAIL PROTECTED]>\ Freie Universitaet Berlin |/_*|'stucki' |Tel(days):+49 30 838-75 459| Fachbereich Mathematik, EDV|\ *|if online|Tel(else):+49 30 77 39 6600| Arnimallee 2-6/14195 Berlin* * |on IRCnet|Fax(alle):+49 30 838-75454/