On 04.09.14 07:51, Geoff Soper wrote:
References:
<1014212314.119.1394801251166.JavaMail.TPIWEB$@virus.tw.shuttle.com>,<6d30dd2234165a4fb52082d093514b87132b0...@tpiex04.shuttle.corp>
<16437ca7e285c5498f501fae7eeb7d131323f...@tpiex04.shuttle.corp>,<53282f7c.9010...@alphaworks.co.uk>
<16437ca7e285c5498f501fae7eeb7d131323f...@tpiex04.shuttle.corp>
In-Reply-To: <16437ca7e285c5498f501fae7eeb7d131323f...@tpiex04.shuttle.corp>
Hello,
please, if you are writing a new post, send it as new mail and not
as reply/followup on old mail. It makes people with threading clients
angry and they can also in such case miss your e-mail.
Thank you.
I've got an issue whereby spam messages seem to be somehow bypassing SA and
getting into my inbox. I call SA via procmail as per
https://wiki.apache.org/spamassassin/UsedViaProcmail
The exact procmail file that calls SA is as follows:
# The condition line ensures that only messages smaller than 250 kB
# (250 * 1024 = 256000 bytes) are processed by SpamAssassin. Most spam
# isn't bigger than a few k and working with big messages can bring
# SpamAssassin to its knees.
#
# The lock file ensures that only 1 spamassassin invocation happens
# at 1 time, to keep the load down.
#
:0fw: spamassassin.lock
* < 400000
| spamc -x
at first, this causes messages over 400k not to be sent into spamc.
at second, spamc itself will ignore messages over 256K.
at third, when you alreway use 'w' flag, you should check for failures and
exit with tempfail..
at fourth, can't you plug SA directly in your MTA?
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
I wonder how much deeper the ocean would be without sponges.
