Mailing-List: contact users-help@spamassassin.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: local policy)
From: "Sharma, Ashish" <ashish.sharma3@hp.com>
To: "users@spamassassin.apache.org" <users@spamassassin.apache.org>
Date: Thu, 21 Jul 2011 07:53:02 +0100
Subject: RE: Suggest OCR plugin on Spamassassin 3.3.1 for image spam
Thread-Topic: Suggest OCR plugin on Spamassassin 3.3.1 for image spam
Thread-Index: AcxHToiEMxP8L9oIRxumeDOv55IHvQAI3iKg
Message-ID: 
 <3439D88AC8B9534AB0C26F8CA8F055C66D6AD0C1B6@GVW1154EXB.americas.hpqcorp.net>
References: 
 <3439D88AC8B9534AB0C26F8CA8F055C66D6AD0BF27@GVW1154EXB.americas.hpqcorp.net>
 <20110721011848.GH16702@chaosreigns.com> <4E278FBF.5070307@i6ix.com>
In-Reply-To: <4E278FBF.5070307@i6ix.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

All,

The current functionality requires me to receive mails that contains image =
and process them.

So I want a good tool to deal with image spam.

Please suggest some.

Thanks
Ashish Sharma

-----Original Message-----
From: Jason Bertoch [mailto:jason@i6ix.com]=20
Sent: Thursday, July 21, 2011 8:03 AM
To: users@spamassassin.apache.org
Subject: Re: Suggest OCR plugin on Spamassassin 3.3.1 for image spam

On 7/20/2011 9:18 PM, darxus@chaosreigns.com wrote:
> On 07/20, Sharma, Ashish wrote:
>> Can someone suggest some better OCR plugin for Spamassassin 3.3.1 for im=
age spam?
> It still seems strange to me that anybody has ever bothered with using OC=
R
> to deal with image spam, when it's so easy, and for me not problematic, t=
o
> just block all emails that might be image spam - those with an attached
> image that is embedded in the body of an html mail.
>
> Inlined attached images are not a feature that I find anywhere near worth
> having enough to justify needing to OCR image spam.
>

Image spam was a huge deal when it first came out, and there were=20
several sources scrambling to offer a solution, including resources to=20
involve Bayes on the decoded text.  Those worked well enough to deter,=20
for the time-being anyway, that method of spamming.

That said, while I agree with your sentiment toward inline images and=20
HTML mail in general, they are a common business practice and many folks=20
simply can't use the outright block method.

At my last job, I eventually found that image-spam dropped to such a=20
significant low that I didn't need OCR anymore but was still required to=20
allow inline images through.

/Jason