On Mon, 4 Oct 2004, David Brodbeck wrote:
I've seen this problem. I avoid it by bypassing SpamAssassin for all mail
larger than 1 megabyte. Very little spam is this large, since it'd be
inefficient to send.
I'm already bypassing it for anything over 256000 bytes.
Mojo
--
Morris Jones
Morris Jones wrote:
On Mon, 4 Oct 2004, David Brodbeck wrote:
I've seen this problem. I avoid it by bypassing SpamAssassin for all mail
larger than 1 megabyte. Very little spam is this large, since it'd be
inefficient to send.
I'm already bypassing it for anything over 256000 bytes.
Mojo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Brodbeck writes:
On Sun, 3 Oct 2004 12:00:51 -0700, Potato Chip wrote
It's happened to me about 3 times, where an email will be sent to my
server that specifically causes the problem. Killing the spamd process
causes the sending MTA to
On Mon, 04 Oct 2004 10:29:38 -0700, Justin Mason [EMAIL PROTECTED] said:
Please note that pretty much *all* our documentation notes that this is
the case. You should NOT scan very large messages.
We configure our spamd client to only pass spamd up to the first 50KB of
a message. Definitely
I've been calling this the Email Scud problem. I've been hoping for a
patriot missle for a long time. I have noticed the same problem with
v2.63 and v2.64. I upgraded to v3.0 hoping that the problem would go
away but it's still there.
It's happened to me about 3 times, where an email will be sent
