Thanks to everyone that replied to my question and my apologies, since the
answer was so obvious. But sometimes, after a long day, one starts to see
right through the obvious...
The messages in questions were really quite long and my size limit was too
small, so spamc didn't touch them, because it
- Original Message -
From: "Ralf Guenthner" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, May 28, 2003 6:35 PM
Subject: [SAtalk] Strange spamc problem with SA 2.54 and qmail
> Hello list
>
> I call spamc via a script called /var/qmail/bin/q
Ralf,
Did you see my recent thread titled "Some observations on doing more with
less"?
I ran some tests trying different cut off points. I think it's possible
that 1 will work for you, but you need to send the first and the last
parts of the message off to spamc, rather than just the first part
I've seen this, if you had absolutely no SpamAssassin headers, it could
mean that something happened between spamc and spamd. I'd go looking for
cores or any other error that would have kept spamd from responding.
On Wed, 28 May 2003, Ralf Guenthner wrote:
> Hello list
>
> I call spamc via a sc
A question: was the entire mail (header + body) longer than 1 chars. in
length? If so, then the first spamc call only passes the first 10K of the
message. The spamassassin call passes the entire message. Perhaps there was
info in the remaining part of the truncated message that would've helped
Hello list
I call spamc via a script called /var/qmail/bin/qmail-queue with the
following content:
spamc -s1 | /var/qmail/bin/qmail-queue.orig
(the latter, as the name says, is the original program )
It worked fine, or at least I thought it did, until a colleague showed me a
spam mail that s
