RW wrote:
AFAIK though it isn't possible to place a cap on the FuzzyOCR score. I
don't want to, but I detune it purely to reduce the likelyhood of
something hitting my discard threshold by OCR alone.
If you consider this feature so important, then I could implement a
max_score feature that
alex k wrote:
If only FuzzyOCR's developer would read that ;)
Unfortunately he doesn't seem to be interested in his project anymore.
Maybe you could take care of this orphaned code.
Dear Alex,
I am reading exactly everything you write ;)
The code is not orphaned, but also not being
LuKreme wrote:
On 24-May-2009, at 18:40, Henrik K wrote:
I don't know why users are so afraid of words like SVN. You have to
look at the project, not version numbers.
I don't have FuzzyOCR installed, and it's not because of the SVN.
First, I don't think my server can take the processing hit
Hello all,
after quite some time, I've decided to release another version of
FuzzyOcr. This version is only a tag from SVN revision 135 (+ a patch
provided recently which fixes something in one of the sql utilities)
that has been used quite some time with SA 3.2.x and is included in some
LuKreme wrote:
This is an excellent idea, but it also needs rule hits on ham, right?
You're right if you're saying that the method would work better if there
were more ham rules. From what I have seen in my experiments however,
the results are also very precise with the current SA ruleset.
LuKreme wrote:
I don't see any need for the model to be dynamic. Periodic
recalculation of it should be just fine. I bet even daily
reprocessing will prove to be over zealous. Weekly, perhaps even monthly.
This is what I think as well :)
I'm thinking that FPs and FNs are bayes problem
Hi all,
as a result of the recent 2+2 != 4 discussion on the list, here is a
new plugin, which tries to learn ham/spam classification only by knowing
which rules triggered and which did not. This is, so to say, an
automatic meta rule.
The plugin is currently experimental and can only be
AlexB wrote:
Chris
From the README its not quite clear: will this work in autolearn ?
If you mean that the plugin can automatically learn with the autolearn
setting, answer is no.
would it be enough to create the model.* files or is it a must to feed
it?
You create one model file once by
John Hardin wrote:
I assume it learns from full message corpa? And all it cares about is
the rules that hit?
Per my earlier suggestion of learning off the logs + corpa to fix
FP/FN, could there be an option to learn off generated minimal corpa
files, with their structure being just the
John Hardin wrote:
It needs the score, and not just Y/N Spam/Ham (i.e. from which corpa
file it came)?
The SVM does not need the score. However, the evaluation tool needs the
score because it uses it to calculate FP/FN rate.
I was thinking you'd generate a ham file and a spam file from the
Marc Perkel wrote:
So - making any progress? :)
Yes, indeed. I am currently rewriting my code to be more generic and
cleaner (you wouldn't want to see my initial poc code^^). Once I'm done
with that, I can quickly repeat some of the experiments on other mail
sets, such as the one that
John Hardin wrote:
Chris:
Do you have any interest in writing an offline tool that generates
static metarules based on the SA log and FP/FN corpa, as I mentioned?
Running some experiments for this kind of tool is at least on my todo
list :) I don't know however, when I will have time to do
Justin Mason wrote:
Thanks for doing this! couple of q's:
1. I can offer a bigger ham/spam corpus if you'd like to test against
that as well;
corpora from multiple contributors can sometimes expose training set bias.
That would be cool :) Is this corpus already processed by spamassassin
Marc Perkel wrote:
Good work so far but sounds like you need to throw more data at it.
Also even though you indicate over 99% accuracy can you break that
down better? 99.9% is 10 times as accurate as 99%.
What do you mean by more data? Of course, some additional data might
help. One should
Marc Perkel wrote:
I suppose what I was thinking was that you still used the SA result
but added or subtracted from the SA result based on your SVM code,
sort of the way bayes does. Or are you letting SVM make the final
determination?
At the moment, I am only using the SVM answer. What you
John Hardin wrote:
Would there be any benefit to having an offline version - i.e.
something that evaluates the log or a corpus to generate new meta
rules, that could be added onto the default ruleset? For instance:
cron @ 0200:
sa_meta_eval /etc/mail/spamassassin/metarules.cf
Justin Mason wrote:
So you're volunteering to code it up, then? ;)
I was planning to do at least some brainstorming+experiements as to what
learning methods would seem suitable and how well the method performs,
whenever I have time again. Unless someone else did that already?
smime.p7s
Marc Perkel wrote:
Justin Mason wrote:
So you're volunteering to code it up, then? ;)
--j.
I would if I were any good at perl.
I think we should evaluate if the suggested technique works and performs
better or is at least of some benefit, before trying to implement it
properly
decoder wrote:
Justin Mason wrote:
So you're volunteering to code it up, then? ;)
I was planning to do at least some brainstorming+experiements as to
what learning methods would seem suitable and how well the method
performs, whenever I have time again. Unless someone else did
Marc Perkel wrote:
LuKreme wrote:
On Mar 3, 2009, at 10:06, John Wilcock j...@tradoc.fr wrote:
Le 03/03/2009 17:42, Matus UHLAR - fantomas a écrit :
I have been already thinking about possibility to combine every two
rules
and do a masscheck over them. Then, optionally repeating that again,
Hello,
on our private mail server we now have quite some forwards from freemail
providers like yahoo, gmx and such. This wasn't a big problem previously
but there is quite some spam arriving now over those forwards that isn't
tagged as such (mainly I think because RBLs can't strike on
Matt Kettler wrote:
Nearly all positive-score RBLs will check all untrusted hosts in
Received: headers, except the DUL RBLs and XBL which only check the
first untrusted because they are designed to be used in that manner.
ie: SBL will be tested against *ALL* untrusted hosts, including the IP
Matus UHLAR - fantomas wrote:
does it push the extracted text back to SA so it could be used by e.g.
bayes? This is how it imho should be used.
(and imho the same for .pdf and/or .doc - extract text _and_ images from
it, call OCR for images...)
That is a question that was very frequently
Theo Van Dinter wrote:
On Fri, May 02, 2008 at 09:12:12PM +0200, decoder wrote:
Also, the SA plugin architecture is not designed to modify the message
in any way, so you cannot push back the text into the normal processing
line.
Really? Who says? I made very specific modifications
mouss wrote:
he's not the only one... seems there's a lot of backscatter coming in
these days.
I guess the reason is that it is so easy to make a mistake in a
mailserver configuration that enables backscatter...
We recently discovered that even our own mailserver (Postfix) was a
Eddy Beliveau wrote:
- Message d'origine - De : Michael Scheidell
[EMAIL PROTECTED]
À : ram [EMAIL PROTECTED]; spamassassin-users
users@spamassassin.apache.org
Envoyé : 27 mars 2008 10:04
Objet : Re: Spam abuse report plugin
From: ram [EMAIL PROTECTED]
Date: Thu, 27 Mar 2008
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Morton wrote:
On Jul 22, 2007, at 9:43 AM, arni wrote:
Loren Wilton schrieb:
I'm not recieving much of it anymore anyways.
FWIW, about 20% of the spam I got today had either a GIF or PNG
image attached to it. Most advertizing viagra
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello all,
because some people insisted on it, I added an experimental feature to
FuzzyOcr that allows you to scan PDFs as if they were images.
The feature was implemented in the latest SVN revision and is of
course disabled by default.
Personally,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gary V wrote:
Hello,
On the fuzzyocr site I see 3.5.1 version is not SA 3.2.X
compatible ? Is this true, or can I safely ignore :-)
We have an older server with SA 3.2.0 and Fuzzyocr 2.3b and it
works.
Greetings.. Richard
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Russell Galpin wrote:
Hi There
I'm running SA 3.2.1 with the latest version of FuzzyOCR (from svn) and I'm
receiving the same error over and over again in my mail logs:
Jun 25 17:25:56 mta1 spamd[629]: Use of uninitialized value in string eq at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello all,
I've just comitted some changes to our SVN that fixes the ugly
formatting problems that came up with SA 3.1.8 and higher.
The new version should display results with a proper formatting in the
SA report, without screwing up the FuzzyOcr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
after I saw that there are incompatiblities with SA 3.2 and FuzzyOcr,
I decided to try to fix them although I'm still very busy (preparing
for Bachelor thesis).
I made changes and the current SVN version fixes ticket #396 as well
as the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Frank Bures wrote:
On Mon, 15 Jan 2007 20:34:38 +0100, Mark Martinec wrote:
Frank Bures writes:
Since I updated to 3.5.1 from 3.4.2, I am sometimes getting the
following
FuzzyOcr: Error running preprocessor(pamthreshold):
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Len Conrad wrote:
With the severe obfuscation of spam images with:
1) low-contrast between f/g and b/g and
2) random images/edges in the b/g,
... how effective is FuzzyOCR in OCR accuracy?
With these two factors, FuzzyOcr has not much problems
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
jdow wrote:
From: Andy Dills [EMAIL PROTECTED]
On Sun, 7 Jan 2007, Andy Dills wrote:
On Sun, 7 Jan 2007, decoder wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
Hello all,
since 3.5.0 RC1 was released, we fixed many bugs, thanks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ed Kasky wrote:
I just upgraded to 3.5.1 and it seemed that everything was working
until I tried using sa-learn on a few messages. Running
spamassassin -D --lint produces the following errors:
[22986] dbg: plugin: fixed relative path:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello all,
since 3.5.0 RC1 was released, we fixed many bugs, thanks to the many
testers and bug reporters :) so big thanks.
Now, the version seems stable enough to replace the 3.4.x branch, and
I recommend everyone to upgrade to it :)
For those
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Giampaolo Tomassoni wrote:
From: decoder [mailto:[EMAIL PROTECTED]
Hello all,
since 3.5.0 RC1 was released, we fixed many bugs, thanks to the
many testers and bug reporters :) so big thanks.
Excellent work. Thank you for your efforts
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert Nicholson wrote:
Are there any plugins that use String::Approx as used by FuzzyOCR
but used to match non-image spam?
Not that I know of but it would definetly be possible. There are only
problems with some words which are too similar to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Knuth wrote:
Heute (28.12.2006/05:10 Uhr) schrieb Gary V,
Jim, I have been working on a doc for Debian. It is
unfinished but may
help
you through some rough spots at this point. I have no idea
when I'll
have
time to finish it. I have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kelly Jones wrote:
Spammers are starting to put speckles in their images to defeat
OCR-scanning plugins such as FuzzyOCR.
Which images are you refering to? If you can put up a sample, then I
can tell you which scanner setting will catch it :)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kenneth Porter wrote:
--On Saturday, December 23, 2006 12:43 PM +0100 decoder
[EMAIL PROTECTED] wrote:
Which images are you refering to? If you can put up a sample,
then I can tell you which scanner setting will catch it :)
Does the SA wiki
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ronnie Tartar wrote:
I have a Qmail Toaster setup. I have everything working except the
fuzzyocr. Should it have information in the header about being
scanned?
Here is a header but I don't see the fuzzyocr plugin working
*X-Spam-Status:*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
pinoyskull wrote:
decoder wrote:
pinoyskull wrote:
I've been using fuzzyocr plugin for some time now and I think
I noticed is its high cpu/memory usage resulting on delayed
delivery of mails. The server is serving 2000+ clients.
The server
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kelly Jones wrote:
We turned on FuzzyOCR's experimental hashdb function, but had to
turn it off again after it tagged the following images (hashes) as
spam:
8:1:1:1::1:1:1:1:1 14:1:1:1::0:0:0:0:1
These appear to be spacer.gif-like images:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Halid Faith wrote:
I use spamassassin3.1.7 and fuzzyocr3.4.2
Fuzzyocr usually work well. Yet some mails which contains jpeg
can't see. Therefore fuzzyocr don't give any score them as
FUZZY_OCR.
Does the jpeg sample file provided within the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Halid Faith wrote:
I use spamassassin3.1.7 and fuzzyocr-2.3b.
it usually works well.
Although Some mails which contain spam in gif/jpeg, fuzzyocr can't
see them. So it doesn't give them any score as FUZZY_OCR.
I want to add these mails to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
can you provide me the message which triggered the 2 warnings + the
error? Also, are your files unchanged or did you add any
scanset/preprocessor?
Chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ignore that msg... wasn't meant to go here, sorry :)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFgE9rJQIKXnJyDxURAhmgAJwIbRTfUXxcd2xACQXeSDXqcHsZwQCgoXIJ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Rudd wrote:
Michael Schaap wrote:
John Rudd wrote:
The next version of the Botnet plugin for Spam Assassin is
ready. The install instructions are in the Botnet.txt file, and
in the INSTALL file.
Great work!
To Do before 1.0:
(...)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert Fitzpatrick wrote:
I have two gateways that filter using amavisd-new and SA 3.1.7 with
the FuzzyOcr recipes used. On one of these FreeBSD servers, all the
helper applications are present, but on the other, they're all
missing. I just now
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Evan Platt wrote:
Installed FuzzyOCR on my os/x box per
http://fuzzyocr.own-hero.net/wiki/Installation-3.x .
Based on my reading of it, I don't need to do anything other than
put the FuzzyOcr.cf file in my spamassassin directory (which on my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Evan Platt wrote:
At 11:34 AM 11/28/2006, you wrote:
You should try to run spamassassin with -D to see more debug
output. Watch out for FuzzyOcr lines :)
Didn't think of that.. :)
Ok, did that.
Only a few lines have Fuzzy:
I forgot to tell
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Evan Platt wrote:
At 12:37 PM 11/28/2006, you wrote:
I forgot to tell you that you also need to increase the verbosity
factor of the plugin:
focr_verbose 2
will make sure that you see more (i.e. everything ;))
Best regards,
Did that,
Marc Perkel wrote:
OK - trying out the FuzzyOCR plugin. So far it all the default stuff
with minimal installation. I'm running Fedora Core 6. Used the gocr
RPM and didn't patch the source. Everything is default and it doesn't
seem to be complaining so .
If I like this what do I need to
Marc Perkel wrote:
The words file needs a little documentation. Is it limited to single
words or phrases too? What's with the colon and the numbers after the
word?
Phrases are possible too, spaces and numbers are stripped out in both
the wordlist and the OCR output before matching :)
The
Sietse van Zanen wrote:
Ofcourse, save the image, calculate the hash and then use the
fuzzy-find.pl script to delete it from the bad hash db.
Next you’ll have to use a little trick to get it into the good hash
db, as that’s not possible from the fuzzy-find.pl script.
Simply make an empty
Thiago LPS wrote:
On 11/17/06, *Sietse van Zanen* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
To be more exact, the procedure would be:
1. Save the image file, and the message
2. Calculate the hash and delete it from the bad hash db
with the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John D. Hardin wrote:
On the FuzzyOCR list (devel-spam) there was a question about OCR of
remote images vs. embedded images.
I ased there but didn't think to ask here:
Does SA check URIBLs on IMG tags with remote sources?
e.g. IMG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello all,
for those that are not on the devel-spam Mailing list, I'd like to
announce a new development release here.
If you are interested, our new website is located at
http://fuzzyocr.own-hero.net/
The branch has been tested by me and some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Rudd wrote:
decoder wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Rudd wrote:
D.J. wrote:
On 11/10/06, Patrick Sneyers [EMAIL PROTECTED] wrote:
I get this warning: plugin: failed to create instance of plugin
Mail
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
sokka wrote:
Hi,
Can anyone post me URL or PDF of clear documentation of the
FuzzyOcr ?
The current URL for FuzzyOcr is http://fuzzyocr.own-hero.net/
The page (wiki) is still quite under construction, but you'll find
installation instructions
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pascal Maes wrote:
Version 2.3b
1) Here is the ouptut of the scanner (gocr -i) :
_
date Informations
9- 11-lO061O_30 Le __ek-end du 3-4r'11, les adresses de cou
r_er jlectron_que des jtud_ants non
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
decoder wrote:
Pascal Maes wrote:
Version 2.3b
1) Here is the ouptut of the scanner (gocr -i) :
_
date Informations
9- 11-lO061O_30 Le __ek-end du 3-4r'11, les adresses de cou
r_er jlectron_que des
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Rudd wrote:
D.J. wrote:
On 11/10/06, Patrick Sneyers [EMAIL PROTECTED] wrote:
I get this warning: plugin: failed to create instance of plugin
Mail::SpamAssassin::Plugin::RelayChecker: Can't locate object
method new via package
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
James Lay wrote:
On Mon, 30 Oct 2006 07:19:44 -0800 Jeff Chan [EMAIL PROTECTED]
wrote:
Does anyone have any opinions on which of these is better:
http://wiki.apache.org/spamassassin/CustomPlugins
OCR scanner and image validator SA-plugin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Anders Norrbring wrote:
This type of image spam is getting more common, and is not
detected.. At least not here..
Yes, this picture is indeed hard to detect...
I'd need a blackbox like
Input: Animated gif of any kind
Output: NonAnimated gif
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bill wrote:
I just installed FuzzyOCR and have questions about 2 things:
1) I am getting the following errors in the fuzzy.log file. Are these
something I should be concerned about? I have verbose enabled.
FuzzyOcr received timeout after
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Duncan Hill wrote:
On Wednesday 04 October 2006 22:23, Alan Munday wrote:
I've been following your developments and looking at how to
integrate with my (few) systems. But as I don't have a test
environment (until I have built a VMWare one) I was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Loren Wilton wrote:
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in;
} P.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY:
Times New Roman } LI.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in
0pt; FONT-FAMILY: Times
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter wrote:
On Mon, Oct 02, 2006 at 03:18:58PM +0100, Randal, Phil wrote:
undetected). Wouldn't it be better to inject the detected
text back to SA? There should be enough variants of spam
worlds to let SA fuzzily catch the ones from
also
http://wiki.apache.org/spamassassin/FuzzyOcrPlugin ). The FuzzyOCR
mailing list is very helpful too.
What do you mean with adventurous? Those versions published by joval
are all devel.
The stable version is available at
http://users.own-hero.net/~decoder/fuzzyocr/ and works fine
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello all,
since I will have a very tight time schedule in the next 7 weeks for a
project at the university, I will not be able to release any new
versions of FuzzyOcr, fix bugs, reply to questions or give support.
Instead of writing me, you can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
today I saw a strange SPF bug occuring. The original mail header was:
Return-Path: [EMAIL PROTECTED]
Received: from mail.cs.uni-sb.de (mail.cs.uni-sb.de [134.96.254.200])
by wjpserver.cs.uni-sb.de (8.12.11.20060308/8.12.11) with ESMTP id
trust mail.cs.uni-sb.de.
--j.
decoder writes:
today I saw a strange SPF bug occuring. The original mail header
was:
Return-Path: [EMAIL PROTECTED] Received: from
mail.cs.uni-sb.de (mail.cs.uni-sb.de [134.96.254.200]) by
wjpserver.cs.uni-sb.de (8.12.11.20060308/8.12.11) with ESMTP id
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gino Cerullo wrote:
On 1-Sep-06, at 7:18 AM, decoder wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
today I saw a strange SPF bug occuring. The original mail header was:
Return-Path: [EMAIL PROTECTED]
Received: from mail.cs.uni
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ramprasad wrote:
Return-Path: [EMAIL PROTECTED] Received: from
mail.cs.uni-sb.de (mail.cs.uni-sb.de [134.96.254.200]) by
wjpserver.cs.uni-sb.de (8.12.11.20060308/8.12.11) with ESMTP
id k7T8rU6P012050; Tue, 29 Aug 2006 10:53:30 +0200 Received:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- --[ UxBoD ]-- wrote:
How many hits are you getting ?
Database changed mysql select count(*) from maillog where
spamreport like '%FUZZY_OCR%' and date = '2006-08-29'; +--+
| count(*) | +--+ | 385 | +--+ 1 row in set
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Grey wrote:
!-- /* Style Definitions */ p.MsoNormal, li.MsoNormal,
div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:12.0pt;
font-family:Times New Roman;} a:link, span.MsoHyperlink
{color:blue; text-decoration:underline;}
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
decoder wrote:
--[ UxBoD ]-- wrote:
How many hits are you getting ?
Database changed mysql select count(*) from maillog where
spamreport like '%FUZZY_OCR%' and date = '2006-08-29';
+--+ | count(*) | +--+ | 385
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
someone discovered that the DB was not working properly in most cases,
please fix line 492:
It says:
print DB $score::$digest\n;
Should be:
print DB ${score}::${digest}\n;
As a result, the produced hashdb is unusable, please
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Arik Raffael Funke wrote:
Hello,
how does spamassassin handle hashcash? It is turned on by default,
right?
Yes but you still need to define your accept range as you tried to do
above:)
I am using v3.1.2 and have in init.pre loadplugin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Arik Raffael Funke wrote:
decoder wrote:
Arik Raffael Funke wrote:
Hello,
how does spamassassin handle hashcash? It is turned on by
default, right?
Yes but you still need to define your accept range as you tried
to do above:)
I am using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Plenz wrote:
decoder wrote:
gifasm can split them into multiple files, etc.
Thanks, gifasm works very well. Seems that I only have to choose
the biggest one of the output files, it contains the text.
That is what FuzzyOcr does automatically
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello there,
A friend of mine recently received a mail containing an ASCII image
advertising meds. The mail is attached.
Anyone seen this before? Do rules exist already against this kind of spam?
Chris
-BEGIN PGP SIGNATURE-
Version:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Loren Wilton wrote:
Ah. Sig-file format. That is I guess a slight new twist. This
sort of thing was popular for a month or two a couple of years ago.
I suspect they gave up on it then because it was probably done by
hand and not worth the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
jdow wrote:
From: decoder [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
Expertsites, Inc. wrote:
From: decoder [EMAIL PROTECTED]
Hello,
I just uploaded FuzzyOcr 2.3b to the download site. If you
find bugs or run
) eq \x89\x50\x4e\x47 )
The tarball which is available for download has been fixed
already...
Chris
I just downloaded it from
http://users.own-hero.net/~decoder/fuzzyocr/ and line 733 says:
elsif ( substr($picture_data,0,5) eq \x89\x50\x4e\x47 ) {
Gary V
Yea my problem it seems like
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Loren Wilton wrote:
Sure. giftopnm will do it. The FuzzyOCR plugin is using some
other tool that will also do it, I don't recall what just at the
moment.
Loren
giftopnm wont do it as far as I tested it... it only extracts the
first frame...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gary V wrote:
Hello,
I just uploaded FuzzyOcr 2.3b to the download site. If you find
bugs or run into problems, please mail back :)
The jpeg.eml and png.eml samples failed to provide FuzzyOcr hits on
my system because the messages scored
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Plenz wrote:
Today I got animated spam. The first frame only with dots an lines, the
second frame with spam text, the third frame again with dots and lines. The
duration of the text frame is very long, the others are very short.
Is there a
this is to upgrade to 3.1.4. I am still unsure
wether I should add my own timeout stuff with alert() only to support
3.1.0.
Maybe someone else here has a better idea :)
Chris
decoder wrote:
Hello,
I just uploaded FuzzyOcr 2.3b to the download site. If you find
bugs or run into problems, please mail back
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rose, Bobby wrote:
What am I missing? I updated but not png isn't working. If I switch to
debug logging 2 I see in the log when I run the sample thru.
[2006-08-26 18:16:40] Debug mode: Analyzing file with content-type
image/png
[2006-08-26
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Plenz wrote:
Adding a point for corrupted images is sounding better and better.
I disagree. To check out what happens I converted a JPG picture into a GIF
file
and sent it to myself. One time I converted it with IrfanView and the
second
time
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kenneth Porter wrote:
--On Friday, August 25, 2006 12:05 AM -0700 Plenz
[EMAIL PROTECTED] wrote:
I disagree. To check out what happens I converted a JPG picture
into a GIF
file
and sent it to myself. One time I converted it with IrfanView and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Logan Shaw wrote:
On Fri, 25 Aug 2006, enediel gonzalez wrote:
From: decoder [EMAIL PROTECTED] Kenneth Porter wrote:
I completely agree, the problem is, some implementations makes
this impossible. For example MailScanner.
I've heard
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rick Cooper wrote:
-Original Message- From: decoder
[mailto:[EMAIL PROTECTED] Sent: Friday, August 25, 2006 2:24
PM To: users@spamassassin.apache.org Subject: Re: Discourage
broken content
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I just uploaded FuzzyOcr 2.3b to the download site. If you find bugs
or run into problems, please mail back :)
The major changes are:
- - Added a configurable timeout (maximum runtime) for the plugin, to
avoid any lockups/unwanted delays
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Andersen wrote:
On Friday 25 August 2006 13:17, decoder wrote:
Another wish: I'd like to create a database to ship with the
plugin so it can be used out of the box but I do not have much
samples here, so it would be nice if you sent me
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Scheidell wrote:
Now if you could just ocr the whole thing as text, and pass it back to
SA to score!
I explained before why this is not going to happen really soon:
a) It is VERY hard to realize. To preserve the message, you would need
two
1 - 100 of 163 matches
Mail list logo
