Re: Massive spamruns

[polloxx]

Neil,

I'm sorry but I can't disclose the logs. fortunately 95% of them were
blocked by blacklisting or greylisting. I just wanted to know if other
people see a massive increase of spam the last weeks.


On Wed, Jun 12, 2013 at 9:31 PM, Benny Pedersen  wrote:

> Alex skrev den 2013-06-12 20:25:
>
>
>  John Hardin wrote:
>>
>>> As was suggested earlier: greylisting?
>>>
>>
>> I really don't think my users would tolerate the delay, so I've never
>> implemented it. They would have vendors calling them on the phone
>> complaining, not to mention users. From what I understand the delay
>> can be multiple minutes, correct? I'd imagine there's support for
>> whitelisting an IP after receiving multiple messages over some
>> extended period? Is it something suitable for an environment with a
>> few hundred thousand messages per day?
>>
>
> https://github.com/mmatuska/**sqlgrey/blob/master/sqlgrey
> http://www.hardwarefreak.com/**fqrdns.pcre<
>  used as a discriminatore list, so greylist only this hosts
>
> and if possible patch sqlgreywebui to be pr user, or make it possible for
> each recipient to opt in
>
> with this the most important mails are not delayed at all, else there is
> only sagrey left
>
>
> --
> senders that put my email into body content will deliver it to my own
> trashcan, so if you like to get reply, dont do it
>

Massive spamruns

[polloxx]

Dear list,

We see massive spamruns since begin june. Are other people also similar
runs? They fill our maillog. Fortunately most is blocked.

Re: FuzzyOCR

[polloxx]

On Fri, Jul 15, 2011 at 3:01 PM, John Hardin  wrote:
> On Fri, 15 Jul 2011, polloxx wrote:
>
>>> polloxx, hit this URL; I remember seeing various patches for FuzzyOCR to
>>> address this.
>>>
>>>
>>> http://www.google.com/search?q=fuzzyocr+2048+%22insecure+dependency%22+patch
>>
>> Thanks John, I've read this before I posted my question on the ML.
>>
>>> You said you're using debian squeeze...
>>>
>>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571218
>>>
>>> The debian maintainers claim it's fixed in 3.6.0-2. Did FuzzyOCR get
>>> updated
>>> when you ran your apt-get?
>>
>> This is from februari 2010. My server setup is from beginning of 2011
>> and fuzzyocr is at version 3.6.0-3.
>
> You're still getting the taint errors, so the patch(es) are apparently still
> needed, or they got reverted. You might want to open a bug with debian and
> let them know 571218 is back in 3.6.0-3
>

'aptitude install tesseract-ocr' was the clue.

Re: FuzzyOCR

[polloxx]

> polloxx, hit this URL; I remember seeing various patches for FuzzyOCR to
> address this.
>
> http://www.google.com/search?q=fuzzyocr+2048+%22insecure+dependency%22+patch
>

Thanks John, I've read this before I posted my question on the ML.


> You said you're using debain squeeze...
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571218
>
> The debian maintainers claim it's fixed in 3.6.0-2. Did FuzzyOCR get updated
> when you ran your apt-get?
>

This is from februari 2010. My server setup is from beginning of 2011
and fuzzyocr is at version 3.6.0-3.

Re: FuzzyOCR

[polloxx]

On Mon, Jul 11, 2011 at 8:40 PM, John Hardin  wrote:
> On Mon, 11 Jul 2011, polloxx wrote:
>
>>> Okay, no error with the test message.
>>>
>>> So far we haven't been able to reproduce the error.
>>>
>>> Is it still occurring in the live mail stream?
>>
>> Yes.
>
> Ok.
>
>>> Was this test message menually composed for testing purposes, or was it a
>>> real incoming message that had generated errors when processed?
>>>
>>
>> The testmail (containing a spam image) sent trough the CL produces no
>> error (as you could see).
>> The same image sent as an attachment produces the error I talked about.
>
> Can you capture that message after it's gone through your mail stream and
> run it through the manual test?
>

Mail through mail server does does not recognise the spam image and
generates an error.
Through manual test works fine.

Re: FuzzyOCR

[polloxx]

> Okay, no error with the test message.
>
> So far we haven't been able to reproduce the error.
>
> Is it still occurring in the live mail stream?

Yes.


>
> Was this test message menually composed for testing purposes, or was it a
> real incoming message that had generated errors when processed?
>

The testmail (containing a spam image) sent trough the CL produces no
error (as you could see).
The same image sent as an attachment produces the error I talked about.

Re: FuzzyOCR

[polloxx]

> ...okay. What was the debugging output from that run?
>

See attachment.


> Does normal delivery run as root, or as a different user? If it runs as a
> different user, can that user perform the above manual test successfully?
>

Runs as root.


> Are you still seeing errors for normal mail delivery?
>
> Is your installation running spamd or spamassassin for normal processing?
>

spamd
Jul 11 14:55:34.257 [14578] dbg: FuzzyOcr: focr_bin_helper: 
'pnmnorm,pnminvert,ppmtopgm'
Jul 11 14:55:34.258 [14578] info: FuzzyOcr: Adding <3> new helper apps
Jul 11 14:55:34.258 [14578] dbg: FuzzyOcr: focr_bin_helper: 'tesseract'
Jul 11 14:55:34.258 [14578] info: FuzzyOcr: Adding <1> new helper apps
Jul 11 14:55:34.259 [14578] info: FuzzyOcr: Starting preprocessor parser for 
file "/etc/mail/spamassassin/FuzzyOcr.preps"...
Jul 11 14:55:34.259 [14578] dbg: FuzzyOcr: line: preprocessor normalize {
Jul 11 14:55:34.259 [14578] dbg: FuzzyOcr: line: command = pnmnorm
Jul 11 14:55:34.259 [14578] dbg: FuzzyOcr: line: }
Jul 11 14:55:34.259 [14578] dbg: FuzzyOcr: line: preprocessor invert {
Jul 11 14:55:34.259 [14578] dbg: FuzzyOcr: line: command = pnminvert
Jul 11 14:55:34.259 [14578] dbg: FuzzyOcr: line: }
Jul 11 14:55:34.259 [14578] dbg: FuzzyOcr: line: preprocessor ppmtopgm {
Jul 11 14:55:34.259 [14578] dbg: FuzzyOcr: line: command = ppmtopgm
Jul 11 14:55:34.259 [14578] dbg: FuzzyOcr: line: }
Jul 11 14:55:34.259 [14578] dbg: FuzzyOcr: line: preprocessor maketiff {
Jul 11 14:55:34.259 [14578] dbg: FuzzyOcr: line: command = pnmtotiff
Jul 11 14:55:34.259 [14578] dbg: FuzzyOcr: line: args = -color -truecolor
Jul 11 14:55:34.259 [14578] dbg: FuzzyOcr: line: }
Jul 11 14:55:34.260 [14578] info: FuzzyOcr: Starting scanset parser for file 
"/etc/mail/spamassassin/FuzzyOcr.scansets"...
Jul 11 14:55:34.260 [14578] dbg: FuzzyOcr: line scanset ocrad {
Jul 11 14:55:34.260 [14578] dbg: FuzzyOcr: line command = $ocrad
Jul 11 14:55:34.260 [14578] dbg: FuzzyOcr: line args = -s5 $input
Jul 11 14:55:34.260 [14578] dbg: FuzzyOcr: line }
Jul 11 14:55:34.260 [14578] dbg: FuzzyOcr: line scanset ocrad-invert {
Jul 11 14:55:34.260 [14578] dbg: FuzzyOcr: line command = $ocrad
Jul 11 14:55:34.260 [14578] dbg: FuzzyOcr: line args = -s5 -i $input
Jul 11 14:55:34.260 [14578] dbg: FuzzyOcr: line }
Jul 11 14:55:34.260 [14578] dbg: FuzzyOcr: line scanset ocrad-decolorize-invert 
{
Jul 11 14:55:34.260 [14578] dbg: FuzzyOcr: line preprocessors = ppmtopgm
Jul 11 14:55:34.260 [14578] dbg: FuzzyOcr: line command = $ocrad
Jul 11 14:55:34.260 [14578] dbg: FuzzyOcr: line args = -s5 -i $input
Jul 11 14:55:34.260 [14578] dbg: FuzzyOcr: line }
Jul 11 14:55:34.260 [14578] dbg: FuzzyOcr: line scanset ocrad-decolorize {
Jul 11 14:55:34.260 [14578] dbg: FuzzyOcr: line preprocessors = ppmtopgm
Jul 11 14:55:34.260 [14578] dbg: FuzzyOcr: line command = $ocrad
Jul 11 14:55:34.260 [14578] dbg: FuzzyOcr: line args = -s5 $input
Jul 11 14:55:34.261 [14578] dbg: FuzzyOcr: line }
Jul 11 14:55:34.261 [14578] dbg: FuzzyOcr: line scanset gocr {
Jul 11 14:55:34.261 [14578] dbg: FuzzyOcr: line command = $gocr
Jul 11 14:55:34.261 [14578] dbg: FuzzyOcr: line args = -i $input
Jul 11 14:55:34.261 [14578] dbg: FuzzyOcr: line }
Jul 11 14:55:34.261 [14578] dbg: FuzzyOcr: line scanset gocr-180 {
Jul 11 14:55:34.261 [14578] dbg: FuzzyOcr: line command = $gocr
Jul 11 14:55:34.261 [14578] dbg: FuzzyOcr: line args = -l 180 -d 2 -i $input
Jul 11 14:55:34.261 [14578] dbg: FuzzyOcr: line }
Jul 11 14:55:34.261 [14578] dbg: FuzzyOcr: line scanset tesseract {
Jul 11 14:55:34.261 [14578] dbg: FuzzyOcr: line preprocessors = maketiff
Jul 11 14:55:34.261 [14578] dbg: FuzzyOcr: line command = $tesseract
Jul 11 14:55:34.261 [14578] dbg: FuzzyOcr: line args = $input $output
Jul 11 14:55:34.261 [14578] dbg: FuzzyOcr: line force_output_in = $output.txt
Jul 11 14:55:34.261 [14578] dbg: FuzzyOcr: line }
Jul 11 14:55:34.821 [14578] info: FuzzyOcr: Searching in: /usr/local/netpbm/bin
Jul 11 14:55:34.822 [14578] info: FuzzyOcr: Searching in: /usr/local/bin
Jul 11 14:55:34.822 [14578] info: FuzzyOcr: Searching in: /usr/bin
Jul 11 14:55:34.822 [14578] info: FuzzyOcr: Using gifsicle => /usr/bin/gifsicle
Jul 11 14:55:34.822 [14578] info: FuzzyOcr: Using giffix => /usr/bin/giffix
Jul 11 14:55:34.822 [14578] info: FuzzyOcr: Using giftext => /usr/bin/giftext
Jul 11 14:55:34.822 [14578] info: FuzzyOcr: Using gifinter => /usr/bin/gifinter
Jul 11 14:55:34.822 [14578] info: FuzzyOcr: Using giftopnm => /usr/bin/giftopnm
Jul 11 14:55:34.822 [14578] info: FuzzyOcr: Using jpegtopnm => 
/usr/bin/jpegtopnm
Jul 11 14:55:34.822 [14578] info: FuzzyOcr: Using pngtopnm => /usr/bin/pngtopnm
Jul 11 14:55:34.822 [14578] info: FuzzyOcr: Using bmptopnm => /usr/bin/bmptopnm
Jul 11 14:55:34.822 [14578] info: FuzzyOcr: Using tifftopnm => 
/usr/bin/tifftopnm
Jul 11 14:55:34.822 [14578] info: FuzzyOcr: Using ppmhist => /usr/bin/ppmhist
Jul 11 14:55:34.822 [14578] info: FuzzyOcr: Using pamfile => /usr/bin/pamfile
Jul 11 14:55:34.822 [14578] info: Fuzzy

Re: FuzzyOCR

[polloxx]

On Thu, Jul 7, 2011 at 5:18 PM, John Hardin  wrote:
> On Thu, 7 Jul 2011, polloxx wrote:
>
>> On Wed, Jul 6, 2011 at 6:33 PM, John Hardin  wrote:
>>>
>>> OK. Just to be clear, you took a jpeg-format image file and used
>>> jpegtopnm
>>> to convert it to a pnm file, and got a correct .pnm image file out? Did
>>> you
>>> do this to verify the exit code from jpegtopnm:
>>>
>>>    echo $?
>>
>> $ /usr/bin/jpegtopnm ./spam1.jpg > spam1.pnm
>> jpegtopnm: WRITING PPM FILE
>>
>> spam1.pnm is created.
>
> Please run this:
>
>     /usr/bin/jpegtopnm ./spam1.jpg > spam1.pnm ; echo $?
>
> The return code is likely zero, but let's be _sure_.
>

Yes, zero.


>>> It would be useful to see the debugging output of spamassassin where it's
>>> talking about fuzzyocr. Do you know how to run spamassassin in debug mode
>>> against a test message?
>>
>> # spamassassin --debug FuzzyOCR < ./spam1.jpg > /dev/null
>
> Your input there needs to be a complete email message with the image as an
> attachment, not the image itself:
>

The example eml from Spamassassin works fine:

# spamassassin --debug FuzzyOCR > output

# cat output

Spam detection software, running on the system "xxx.xxx.xxx", has
identified this incoming email as possible spam.  The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email.  If you have any questions, see
the administrator of that system for details.

Content preview:  Langdon looked again at the fax an ancient myth confirmed
  in black and white. The implications were frightening. He gazed
absently through
   the bay window. The first hint of dawn was sifting through the birch trees
   in his backyard, but the view looked somehow different this morning. As an
   odd combination of fear and exhilaration settled over him, Langdon knew he
   had no choice The man led Langdon the length of the hangar. They rounded
  the corner onto the runway. [...]

Content analysis details:   (24.6 points, 5.0 required)

 pts rule name  description
 -- --
 3.6 RCVD_IN_PBLRBL: Received via a relay in Spamhaus PBL
[58.186.156.15 listed in zen.spamhaus.org]
 1.6 RCVD_IN_BRBL_LASTEXT   RBL: RCVD_IN_BRBL_LASTEXT
[58.186.156.15 listed in bb.barracudacentral.org]
 0.0 FSL_HELO_NON_FQDN_1FSL_HELO_NON_FQDN_1
 3.6 HELO_LOCALHOST HELO_LOCALHOST
 4.4 KB_RATWARE_OUTLOOK_MID KB_RATWARE_OUTLOOK_MID
 0.8 DKIM_ADSP_NXDOMAIN No valid author signature and domain not in DNS
 2.5 DATE_IN_FUTURE_12_24   Date: is 12 to 24 hours after Received: date
 0.0 HTML_MESSAGE   BODY: HTML included in message
 0.0 MIME_QP_LONG_LINE  RAW: Quoted-printable line longer than 76 chars
 0.2 SHORT_HELO_AND_INLINE_IMAGE Short HELO string, with inline image
 1.3 RDNS_NONE  Delivered to internal network by a host with no rDNS
 0.0 T_DOS_OUTLOOK_TO_MX_IMAGE Direct to MX with Outlook headers and an
image
 9.0 FUZZY_OCR  BODY: Mail contains an image with common
spam text inside
[Words found:]
["levitra" in 1 lines]
["cialis" in 1 lines]
["viagra" in 2 lines]
[(6 word occurrences found)]
-2.3 AWLAWL: From: address is in the auto white-list

The original message was not completely plain text, and may be unsafe to
open with some email clients; in particular, it may contain a virus,
or confirm that your address can receive spam.  If you wish to view
it, it may be safer to save it to a file and open it with an editor.

Re: FuzzyOCR

[polloxx]

On Thu, Jul 7, 2011 at 2:07 AM, Sergey Tsabolov ( aka linuxman )
 wrote:
>
>
> On 06/07/2011 06:34 μμ, polloxx wrote:
>>
>> John,
>>
>> Works fine at the CL.
>> Nothing about the error. (It's a SA error I think)
>> apt-get did not alter jpegtopnm.
>
> I think you need update you Debian repositories to newest and try to update
> packages.

Debian has the latest upgrade.

Re: FuzzyOCR

[polloxx]

On Wed, Jul 6, 2011 at 7:52 PM, Brian Bebeau  wrote:
>> after an apt-get upgrade FuzzyOCR has stopped working. I get the
>> following error in the log:
>>
>> FuzzyOCR: 2011-06-22 17:00:38 [3057] /usr/bin/jpegtopnm: Returned
>> [2048], skipping...
>
> I had this problem too, after upgrading SA to 3.3.x and FuzzyOCR to 3.6.0.
> Upgrading netpbm fixed it for me.
>

netpbm is at the latest version for Squeeze: 2:10.0-12.2+b1


>> System is a Debian Squeeze Running Spamassassin 3.3.1 and FuzzyOCR
>> 3.6.0
>>
>> Any idea?
>>
>
>
> This transmission may contain information that is privileged, confidential, 
> and/or exempt from disclosure under applicable law. If you are not the 
> intended recipient, you are hereby notified that any disclosure, copying, 
> distribution, or use of the information contained herein (including any 
> reliance thereon) is STRICTLY PROHIBITED. If you received this transmission 
> in error, please immediately contact the sender and destroy the material in 
> its entirety, whether in electronic or hard copy format.
>
>

Re: FuzzyOCR

[polloxx]

On Wed, Jul 6, 2011 at 6:33 PM, John Hardin  wrote:
> On Wed, 6 Jul 2011, polloxx wrote:
>
>> Works fine at the CL.
>
> OK. Just to be clear, you took a jpeg-format image file and used jpegtopnm
> to convert it to a pnm file, and got a correct .pnm image file out? Did you
> do this to verify the exit code from jpegtopnm:
>
>    echo $?
>

$ /usr/bin/jpegtopnm ./spam1.jpg > spam1.pnm
jpegtopnm: WRITING PPM FILE

spam1.pnm is created.



>> Nothing about the error. (It's a SA error I think)
>
> It looks to me like SA is just reporting an error code from jpegtopnm. I did
> some brief digging and couldn't find anything about that particular error
> code, it might take a look at the sources to learn what it means.
>
>> apt-get did not alter jpegtopnm.
>
> Bummer, so much for the easy explanation... :)
>
> Do you have a sample message having an image attachment that you can run
> through SA manually to test things? If not, try to get one.
>
> It would be useful to see the debugging output of spamassassin where it's
> talking about fuzzyocr. Do you know how to run spamassassin in debug mode
> against a test message?
>

# spamassassin --debug FuzzyOCR < ./spam1.jpg > /dev/null
Jul  7 13:46:19.889 [4590] dbg: FuzzyOcr: focr_bin_helper:
'pnmnorm,pnminvert,ppmtopgm'
Jul  7 13:46:19.889 [4590] info: FuzzyOcr: Adding <3> new helper apps
Jul  7 13:46:19.889 [4590] dbg: FuzzyOcr: focr_bin_helper: 'tesseract'
Jul  7 13:46:19.890 [4590] info: FuzzyOcr: Adding <1> new helper apps
Jul  7 13:46:19.891 [4590] info: FuzzyOcr: Starting preprocessor
parser for file "/etc/mail/spamassassin/FuzzyOcr.preps"...
Jul  7 13:46:19.891 [4590] dbg: FuzzyOcr: line: preprocessor normalize {
Jul  7 13:46:19.891 [4590] dbg: FuzzyOcr: line: command = pnmnorm
Jul  7 13:46:19.891 [4590] dbg: FuzzyOcr: line: }
Jul  7 13:46:19.891 [4590] dbg: FuzzyOcr: line: preprocessor invert {
Jul  7 13:46:19.891 [4590] dbg: FuzzyOcr: line: command = pnminvert
Jul  7 13:46:19.891 [4590] dbg: FuzzyOcr: line: }
Jul  7 13:46:19.891 [4590] dbg: FuzzyOcr: line: preprocessor ppmtopgm {
Jul  7 13:46:19.891 [4590] dbg: FuzzyOcr: line: command = ppmtopgm
Jul  7 13:46:19.891 [4590] dbg: FuzzyOcr: line: }
Jul  7 13:46:19.891 [4590] dbg: FuzzyOcr: line: preprocessor maketiff {
Jul  7 13:46:19.891 [4590] dbg: FuzzyOcr: line: command = pnmtotiff
Jul  7 13:46:19.891 [4590] dbg: FuzzyOcr: line: args = -color -truecolor
Jul  7 13:46:19.891 [4590] dbg: FuzzyOcr: line: }
Jul  7 13:46:19.891 [4590] info: FuzzyOcr: Starting scanset parser for
file "/etc/mail/spamassassin/FuzzyOcr.scansets"...
Jul  7 13:46:19.891 [4590] dbg: FuzzyOcr: line scanset ocrad {
Jul  7 13:46:19.892 [4590] dbg: FuzzyOcr: line command = $ocrad
Jul  7 13:46:19.892 [4590] dbg: FuzzyOcr: line args = -s5 $input
Jul  7 13:46:19.892 [4590] dbg: FuzzyOcr: line }
Jul  7 13:46:19.892 [4590] dbg: FuzzyOcr: line scanset ocrad-invert {
Jul  7 13:46:19.892 [4590] dbg: FuzzyOcr: line command = $ocrad
Jul  7 13:46:19.892 [4590] dbg: FuzzyOcr: line args = -s5 -i $input
Jul  7 13:46:19.892 [4590] dbg: FuzzyOcr: line }
Jul  7 13:46:19.892 [4590] dbg: FuzzyOcr: line scanset ocrad-decolorize-invert {
Jul  7 13:46:19.892 [4590] dbg: FuzzyOcr: line preprocessors = ppmtopgm
Jul  7 13:46:19.892 [4590] dbg: FuzzyOcr: line command = $ocrad
Jul  7 13:46:19.892 [4590] dbg: FuzzyOcr: line args = -s5 -i $input
Jul  7 13:46:19.892 [4590] dbg: FuzzyOcr: line }
Jul  7 13:46:19.892 [4590] dbg: FuzzyOcr: line scanset ocrad-decolorize {
Jul  7 13:46:19.892 [4590] dbg: FuzzyOcr: line preprocessors = ppmtopgm
Jul  7 13:46:19.892 [4590] dbg: FuzzyOcr: line command = $ocrad
Jul  7 13:46:19.892 [4590] dbg: FuzzyOcr: line args = -s5 $input
Jul  7 13:46:19.892 [4590] dbg: FuzzyOcr: line }
Jul  7 13:46:19.893 [4590] dbg: FuzzyOcr: line scanset gocr {
Jul  7 13:46:19.893 [4590] dbg: FuzzyOcr: line command = $gocr
Jul  7 13:46:19.893 [4590] dbg: FuzzyOcr: line args = -i $input
Jul  7 13:46:19.893 [4590] dbg: FuzzyOcr: line }
Jul  7 13:46:19.893 [4590] dbg: FuzzyOcr: line scanset gocr-180 {
Jul  7 13:46:19.893 [4590] dbg: FuzzyOcr: line command = $gocr
Jul  7 13:46:19.893 [4590] dbg: FuzzyOcr: line args = -l 180 -d 2 -i $input
Jul  7 13:46:19.893 [4590] dbg: FuzzyOcr: line }
Jul  7 13:46:19.893 [4590] dbg: FuzzyOcr: line scanset tesseract {
Jul  7 13:46:19.893 [4590] dbg: FuzzyOcr: line preprocessors = maketiff
Jul  7 13:46:19.893 [4590] dbg: FuzzyOcr: line command = $tesseract
Jul  7 13:46:19.893 [4590] dbg: FuzzyOcr: line args = $input $output
Jul  7 13:46:19.893 [4590] dbg: FuzzyOcr: line force_output_in = $output.txt
Jul  7 13:46:19.893 [4590] dbg: FuzzyOcr: line }
Jul  7 13:46:20.439 [4590] info: FuzzyOcr: Searching in: /usr/local/netpbm/bin
Jul  7 13:46:20.440 [4590] info: FuzzyOcr: Searching in: /usr/local/bin
Jul  7 13:46:20.440 [4590] info: FuzzyOcr: Searching in: /usr/bin
Jul  7 

Re: FuzzyOCR

[polloxx]

John,

Works fine at the CL.
Nothing about the error. (It's a SA error I think)
apt-get did not alter jpegtopnm.

On Wed, Jul 6, 2011 at 4:40 PM, John Hardin  wrote:
> On Wed, 6 Jul 2011, polloxx wrote:
>
>> nobody?
>>
>> On Thu, Jun 23, 2011 at 1:56 PM, polloxx  wrote:
>>>
>>> Dear,
>>>
>>> after an apt-get upgrade FuzzyOCR has stopped working. I get the
>>> following error in the log:
>>>
>>> FuzzyOCR: 2011-06-22 17:00:38 [3057] /usr/bin/jpegtopnm: Returned
>>> [2048], skipping...
>>>
>>> System is a Debian Squeeze Running Spamassassin 3.3.1 and FuzzyOCR 3.6.0
>>>
>>> Any idea?
>
> What happens when you try to run /usr/bin/jpegtopnm from the command line?
>
> What does the jpegtopnm man page say about that return code?
>
> Did apt-get change the jpegtopnm program?
>
> --
>  John Hardin KA7OHZ                    http://www.impsec.org/~jhardin/
>  jhar...@impsec.org    FALaholic #11174     pgpk -a jhar...@impsec.org
>  key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C  AF76 D822 E6E6 B873 2E79
> ---
>  [People] are socialists because they are blinded by envy and
>  ignorance.                -- economist Ludwig von Mises (1881-1973)
> ---
>  Tomorrow: Robert Heinlein's 104th birthday
>

Re: FuzzyOCR

[polloxx]

Sergey,

reinstall fuzzyocr did not help.
What should I see in the OSSpecificNotes?

On Wed, Jul 6, 2011 at 4:08 PM, Sergey Tsabolov (aka linuxman)
 wrote:
> Στις 06/07/2011 04:53 μμ, ο/η polloxx έγραψε:
>
> nobody?
>
> You are try to reinstall it ?
> See the notes here http://fuzzyocr.own-hero.net/wiki/OSSpecificNotes
>
> On Thu, Jun 23, 2011 at 1:56 PM, polloxx  wrote:
>
> Dear,
>
> after an apt-get upgrade FuzzyOCR has stopped working. I get the
> following error in the log:
>
> FuzzyOCR: 2011-06-22 17:00:38 [3057] /usr/bin/jpegtopnm: Returned
> [2048], skipping...
>
> System is a Debian Squeeze Running Spamassassin 3.3.1 and FuzzyOCR 3.6.0
>
> Any idea?
>
>
> --
> ---
> Don't send me documents in .doc , .docx, .xls, .ppt , .pptx .
> Send it with ODF format : .odt , .odp , .ods or .pdf .
> Try to use Open Document Format : http://el.libreoffice.org
> Save you money and use GNU/Linux Distro http://distrowatch.com/
> --
> First they ignore you, then they ridicule you, then they fight you,then you
> win!!!
>
> Filipino - detected
> Afrikaans
> Albanian
> Arabic
> Belarusian
> Bulgarian
> Catalan
> Chinese
> Chinese (Simplified)
> Chinese (Traditional)
> Croatian
> Czech
> Danish
> Dutch
> English
> Estonian
> Filipino
> Finnish
> French
> Galician
> German
> Greek
> Hebrew
> Haitian Creole
> Hindi
> Hungarian
> Icelandic
> Indonesian
> Irish
> Italian
> Japanese
> Korean
> Latvian
> Lithuanian
> Macedonian
> Malay
> Maltese
> Norwegian
> Persian
> Polish
> Portuguese
> Portuguese (Portugal)
> Romanian
> Russian
> Serbian
> Slovak
> Slovenian
> Spanish
> Swahili
> Swedish
> Thai
> Turkish
> Ukrainian
> Vietnamese
> Welsh
> Yiddish
>
> Afrikaans
> Albanian
> Arabic
> Belarusian
> Bulgarian
> Catalan
> Chinese
> Chinese (Simplified)
> Chinese (Traditional)
> Croatian
> Czech
> Danish
> Dutch
> English
> Estonian
> Filipino
> Finnish
> French
> Galician
> German
> Greek
> Hebrew
> Haitian Creole
> Hindi
> Hungarian
> Icelandic
> Indonesian
> Irish
> Italian
> Japanese
> Korean
> Latvian
> Lithuanian
> Macedonian
> Malay
> Maltese
> Norwegian
> Persian
> Polish
> Portuguese
> Portuguese (Portugal)
> Romanian
> Russian
> Serbian
> Slovak
> Slovenian
> Spanish
> Swahili
> Swedish
> Thai
> Turkish
> Ukrainian
> Vietnamese
> Welsh
> Yiddish

Re: FuzzyOCR

[polloxx]

nobody?

On Thu, Jun 23, 2011 at 1:56 PM, polloxx  wrote:
> Dear,
>
> after an apt-get upgrade FuzzyOCR has stopped working. I get the
> following error in the log:
>
> FuzzyOCR: 2011-06-22 17:00:38 [3057] /usr/bin/jpegtopnm: Returned
> [2048], skipping...
>
> System is a Debian Squeeze Running Spamassassin 3.3.1 and FuzzyOCR 3.6.0
>
> Any idea?
>

FuzzyOCR

[polloxx]

Dear,

after an apt-get upgrade FuzzyOCR has stopped working. I get the
following error in the log:

FuzzyOCR: 2011-06-22 17:00:38 [3057] /usr/bin/jpegtopnm: Returned
[2048], skipping...

System is a Debian Squeeze Running Spamassassin 3.3.1 and FuzzyOCR 3.6.0

Any idea?

Re: problem in using FuzzyOcr with spamassassin

[polloxx]

On Tue, Jun 22, 2010 at 9:47 PM, Sharma, Ashish  wrote:
> Hi,
>
> I have deployed an mail receiving postfix server combined with amavisd (with 
> clamAV and spamassassin) by using the reference: 
> http://wiki.centos.org/HowTos/Amavisd
>
> on a CentOS 5.5(64 bit) machine.
>
> Now I have deployed the FuzzyOCR module for image spam, but the test cases as 
> provided for fuzzy OCR are not getting passed.
>
> spamassassin version : 3.3.1
> Perl version: 5.8.8
> FuzzyOcr version: 3.6.0
> Postfix version: 3.6.5
>
> Following is one such debug output that I am getting:
>
> $ spamassassin --debug FuzzyOcr < 
> /mnt/fuzzyOCR/FuzzyOcr-3.6.0/samples/ocr-wrongext.eml > /dev/null
>
> Jun 22 15:44:48.653 [12849] dbg: FuzzyOcr: focr_bin_helper: 
> 'pnmnorm,pnminvert,convert,ppmtopgm,tesseract'
> Jun 22 15:44:48.653 [12849] info: FuzzyOcr: Adding <5> new helper apps
> Jun 22 15:44:48.665 [12849] info: FuzzyOcr: Starting preprocessor parser for 
> file "/etc/mail/spamassassin/FuzzyOcr.preps"...
> Jun 22 15:44:48.665 [12849] dbg: FuzzyOcr: line: preprocessor normalize {
> Jun 22 15:44:48.665 [12849] dbg: FuzzyOcr: line: command = pnmnorm
> Jun 22 15:44:48.665 [12849] dbg: FuzzyOcr: line: }
> Jun 22 15:44:48.665 [12849] dbg: FuzzyOcr: line: preprocessor invert {
> Jun 22 15:44:48.665 [12849] dbg: FuzzyOcr: line: command = pnminvert
> Jun 22 15:44:48.665 [12849] dbg: FuzzyOcr: line: }
> Jun 22 15:44:48.665 [12849] dbg: FuzzyOcr: line: preprocessor ppmtopgm {
> Jun 22 15:44:48.665 [12849] dbg: FuzzyOcr: line: command = ppmtopgm
> Jun 22 15:44:48.665 [12849] dbg: FuzzyOcr: line: }
> Jun 22 15:44:48.665 [12849] dbg: FuzzyOcr: line: preprocessor pamtopnm {
> Jun 22 15:44:48.665 [12849] dbg: FuzzyOcr: line: command = pamtopnm
> Jun 22 15:44:48.666 [12849] dbg: FuzzyOcr: line: }
> Jun 22 15:44:48.666 [12849] dbg: FuzzyOcr: line: preprocessor pamthreshold {
> Jun 22 15:44:48.666 [12849] dbg: FuzzyOcr: line: command = pamthreshold
> Jun 22 15:44:48.666 [12849] dbg: FuzzyOcr: line: args = -simple -threshold 0.5
> Jun 22 15:44:48.666 [12849] dbg: FuzzyOcr: line: }
> Jun 22 15:44:48.666 [12849] dbg: FuzzyOcr: line: preprocessor maketiff {
> Jun 22 15:44:48.666 [12849] dbg: FuzzyOcr: line: command = pnmtotiff
> Jun 22 15:44:48.666 [12849] dbg: FuzzyOcr: line: args = -color -truecolor
> Jun 22 15:44:48.666 [12849] dbg: FuzzyOcr: line: }
> Jun 22 15:44:48.666 [12849] info: FuzzyOcr: Starting scanset parser for file 
> "/etc/mail/spamassassin/FuzzyOcr.scansets"...
> Jun 22 15:44:48.666 [12849] dbg: FuzzyOcr: line scanset ocrad {
> Jun 22 15:44:48.666 [12849] dbg: FuzzyOcr: line command = $ocrad
> Jun 22 15:44:48.666 [12849] dbg: FuzzyOcr: line args = -s5 $input
> Jun 22 15:44:48.667 [12849] dbg: FuzzyOcr: line }
> Jun 22 15:44:48.667 [12849] dbg: FuzzyOcr: line scanset ocrad-invert {
> Jun 22 15:44:48.667 [12849] dbg: FuzzyOcr: line command = $ocrad
> Jun 22 15:44:48.667 [12849] dbg: FuzzyOcr: line args = -s5 -i $input
> Jun 22 15:44:48.667 [12849] dbg: FuzzyOcr: line }
> Jun 22 15:44:48.667 [12849] dbg: FuzzyOcr: line scanset 
> ocrad-decolorize-invert {
> Jun 22 15:44:48.667 [12849] dbg: FuzzyOcr: line preprocessors = ppmtopgm, 
> pamthreshold, pamtopnm
> Jun 22 15:44:48.667 [12849] dbg: FuzzyOcr: line command = $ocrad
> Jun 22 15:44:48.667 [12849] dbg: FuzzyOcr: line args = -s5 -i $input
> Jun 22 15:44:48.667 [12849] dbg: FuzzyOcr: line }
> Jun 22 15:44:48.667 [12849] dbg: FuzzyOcr: line scanset ocrad-decolorize {
> Jun 22 15:44:48.667 [12849] dbg: FuzzyOcr: line preprocessors = ppmtopgm, 
> pamthreshold, pamtopnm
> Jun 22 15:44:48.667 [12849] dbg: FuzzyOcr: line command = $ocrad
> Jun 22 15:44:48.667 [12849] dbg: FuzzyOcr: line args = -s5 $input
> Jun 22 15:44:48.667 [12849] dbg: FuzzyOcr: line }
> Jun 22 15:44:48.668 [12849] dbg: FuzzyOcr: line scanset gocr {
> Jun 22 15:44:48.668 [12849] dbg: FuzzyOcr: line command = $gocr
> Jun 22 15:44:48.668 [12849] dbg: FuzzyOcr: line args = -i $input
> Jun 22 15:44:48.668 [12849] dbg: FuzzyOcr: line }
> Jun 22 15:44:48.668 [12849] dbg: FuzzyOcr: line scanset gocr-180 {
> Jun 22 15:44:48.668 [12849] dbg: FuzzyOcr: line command = $gocr
> Jun 22 15:44:48.668 [12849] dbg: FuzzyOcr: line args = -l 180 -d 2 -i $input
> Jun 22 15:44:48.668 [12849] dbg: FuzzyOcr: line }
> Jun 22 15:44:49.009 [12849] info: FuzzyOcr: Searching in: 
> /usr/local/netpbm/bin
> Jun 22 15:44:49.009 [12849] info: FuzzyOcr: Searching in: /usr/local/bin
> Jun 22 15:44:49.009 [12849] info: FuzzyOcr: Searching in: /usr/bin
> Jun 22 15:44:49.010 [12849] info: FuzzyOcr: Using gifsicle => 
> /usr/bin/gifsicle
> Jun 22 15:44:49.010 [12849] info: FuzzyOcr: Using giffix => /usr/bin/giffix
> Jun 22 15:44:49.010 [12849] info: FuzzyOcr: Using giftext => /usr/bin/giftext
> Jun 22 15:44:49.010 [12849] info: FuzzyOcr: Using gifinter => 
> /usr/bin/gifinter
> Jun 22 15:44:49.010 [12849] info: FuzzyOcr: Using giftopnm => 
> /usr/bin/giftopnm
> Jun 22 15:44:49.010 [12849] info: FuzzyOcr: Using jpegtopnm => 
> /usr/bin/jpegtopnm
> Jun 22 15:44:49.0

Re: FozzyOcr logging

[polloxx]

For future readers: rsyslog has it all:
http://www.rsyslog.com/doc/imfile.html


On Thu, Mar 24, 2011 at 5:07 PM, polloxx  wrote:
> Dear,
>
> Is it possible to log FuzzyOcr logs to syslog? As default config is
> using focr_logfile.
>
> Thx,
> P.
>

FozzyOcr logging

[polloxx]

Dear,

Is it possible to log FuzzyOcr logs to syslog? As default config is
using focr_logfile.

Thx,
P.

Development dead

[polloxx]

Hi,

Is the spamassassin development dead?
On the website there's: 2008-06-12: SpamAssassin 3.2.5 has been released.

Bayes database

[polloxx]

Hi,

Your Bayesian database has become dirty: too mush ham mails get a
score of BAYES_99, certainly for one of your customer domains.
Is there a way to sanitize the database without clear the whole thing?

What are the best practices to keep your Bayes database clean?

Thanks,
P.

ocr plugin

[polloxx]

Hi,

Am I right to say that picture spam has dropped dramatically since the
last months?
Is it still reasonable to run an orc plugin? I see the latest FuzzyORC
version is
not SA 3.2.x compatible. Are there more recent product compatible to 3.2.x?
Are you guys still running an ocr plugin on production servers?

Thanks for your answers,
P.

yet another FuzzyOcr version question

[polloxx]

I have another question concerning FozzyOcr 2.3b versus FuzzyOcr 3.5.1:
A spam picture like this: http://213.146.165.18/spam2.gif does generate
a SA FuzzyOcr score of 19 with version 2.3b (and gocr 0.40). With version 3.5.1
(and gocr 0.44)  does not generate a score at all. I'm sure the
systems works because
other picture spam messages are generating a score.
Both are running SA 3.1.7-2 on debian etch. How can I solve this?

P.