We just replaced our old qmail-scanner + spamd system with a fresh install,
and we had a concurrency incoming of about 150. The old single processor
PIII 800 handled this just fine.
The new dual PIII 1Ghz would supposedly work much better. With
qmail-scanner 1.20 and spamd 2.60 it managed to run
This managed to get through twice today.
Here is the entire header (message below):
(btw: I have two separate qmail-scanner instances. One runs virus scanning,
one runs SA)
Return-Path: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
Received: (qmail 580 invoked from network); 2 Jan 2003
What are the appropriate flags to run spamd for qmail-scanner?
I'm getting qmail-scanner header response that say "Clear:." but I can't get
the test-spam message to generate any X-Spam- style inserts. Does
qmail-scanner
cause spamd not to inject headers?
Am I missing something in the docume
I have a feeling someone may have already thought of this, but I've been
tossing this idea around in my head lately.
If you're scanning on a domain basis (or just one account) and you drop a copy
of every identified spam into a place for later review, couldn't we somehow
extract the IP address o
Can someone point out to me where spamc/spamd identifies the recipient of a
message when comparing it to all/more_spam_to entries in local.cf ?
I've found a bug in SA where if the recipient is not listed in the To: or cc:
line of the message SA is ignorant of the true recipient. This causes it
I've implemented spamd/spamc in a system with about 950+ users. As many of
you
are probably aware or have experienced, a select group of people can't handle
changes. They don't like to see the words "Likely Spam" in their subjects,
they can't handle technical thoughts, and they think my proacti
