Mitch (WebCob) writes:

Now I have a problem that maybe is related to enabling badmime? Not sure...
I think this goes beyond badmime and is just badmessage - incomplete mail
part of a bad spam engine? I get messages like these:

Received: from adsl-67-118-200-105.dsl.sktn01.pacbell.net ([67.118.200.105])
  by slim1.bitblock.com with esmtp; Thu, 29 Apr 2004 22:58:19 +0000
Received: from 143.161.104.57 by 67.118.200.105; Thu, 29 Apr 2004
18:50:12 -0500
Message-ID: <H[20
To: undisclosed-recipients: ;

Known spam engine. bofhbadmime won't really help, unless the random crap included 8-bit binary garbage.

The problem is that the clients machines hang when reading the mail.

Any suggestions on how to eliminate these kinds of mails?

A global maildrop recipe might do the trick; however the correct solution is to fix the broken clients that can't deal with it.



Attachment: pgp00000.pgp
Description: PGP signature

Reply via email to