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.
On Wed, Jul 6, 2011 at 4:40 PM, John Hardin wrote:
O
On 06/07/11 09:17, Lars Jørgensen wrote:
I think many people run with tag at 5.0 and discard at 10.0
I should have mentioned that we are running amavisd-new. I thought that was the
de facto way of integrating spamassassin into a mail gateway, but reading this
list reveals that most people pro
"David F. Skoll" wrote:
> On Wed, 06 Jul 2011 08:15:47 +0200
> Andrzej Adam Filip wrote:
>
>> It may improve performance e.g. in case of hundredths mail servers in
>> a data/co-location center using shared forwarder and rejecting on
>> first DNSBL hit. Somehow I doubt buying data for such "resell
> 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.
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 $?
Nothing about the er
Le 06/07/2011 17:44, tonym302 a écrit :
I get an assortment of domain changing high importance spam email (mostly
sales stuff, some hip replacement info LOL) and want to know if it is
possible to block all high priority stuff liek this. It has the red
exclamation point when it arrives. I tried
Hello all,
I get an assortment of domain changing high importance spam email (mostly
sales stuff, some hip replacement info LOL) and want to know if it is
possible to block all high priority stuff liek this. It has the red
exclamation point when it arrives. I tried blocking most of the repeatin
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
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
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 De
On Wed, 6 Jul 2011, Lars Jørgensen wrote:
$sa_tag2_level_deflt = 5.2; # add 'spam detected' headers at that level
$sa_kill_level_deflt = 6.2; # triggers spam evasive actions (e.g. blocks mail)
That seems a little aggressive to me. Personally I'd prefer a larger
margin of error for FPs, and
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 t
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 Spa
On Wed, 06 Jul 2011 08:15:47 +0200
Andrzej Adam Filip wrote:
> It may improve performance e.g. in case of hundredths mail servers in
> a data/co-location center using shared forwarder and rejecting on
> first DNSBL hit. Somehow I doubt buying data for such "reseller"
> configuration is legally en
On 7/6/11 4:17 AM, Lars Jørgensen wrote:
I think many people run with tag at 5.0 and discard at 10.0
I should have mentioned that we are running amavisd-new. I thought that was the
de facto way of integrating spamassassin into a mail gateway, but reading this
list reveals that most people prob
> I think many people run with tag at 5.0 and discard at 10.0
I should have mentioned that we are running amavisd-new. I thought that was the
de facto way of integrating spamassassin into a mail gateway, but reading this
list reveals that most people probably doesn't do that. Makes me wonder if
16 matches
Mail list logo
