I have been waiting to install SA on my xserve, but cannot until 3.2.2
is released with the 'tests' fix.
Fyi, the 32x svn branch (atm, 3.2.2-r547235) builds & execs without
apparent error on both osx 10.4.10 & freebsd 6.2p6.
--
Thanks,
JTDeLys
"Login required for download."
Heh. There's a surprise ... Marketing wizards at work!
--
Thanks,
JTDeLys
Given the numerous, ongoing discussions about the various anti-pdf-spam
tools, /does/ a quantitative comparison of their relative efficacies (I
suppose, measured by SA scores?) exist somewhere?
If not (yet), /is/ there a reference collection (in parlance, "corpus"?) of
pdf spam that could be used
So, although our goal is just, and I don't believe we are "copying" the
PDF against the spirit of this feature, I don't feel I can point out which
lines to delete in the pdftotext.cc file before recompiling it :(.
Maybe others can offer this info, or Google can help. For example :
http://www.cs.
It depends on the versions you have, both FuzzyOcr and perl.
The "use POSIX" is what FO 3.5.1 currently has, and it works fine with
perl
5.8.7 and 5.8.8, but from my experience, it didn't work with 5.8.6 so I
needed
to add the "use POSIX qw(SIGTERM)" ... but don't make much of what I say,
the
SI
Simple fix here was to compile a _special_ pdftotext to be used for
SpamAssassin that would allow parsing of these files :).
could you share what you did that was 'special'?
config options? other?
--
Thanks,
JTDeLys
Hi,
or you can update from SVN that module
sorry, i'm a little confused ...
iiuc, the fix applies -- at least -- to the NON-svn release.
but does it ALSO apply to the svn co? is it needed there?
currently, i have:
svn up
At revision 132.
but, still have 'just'
grep -i posix Fuzz
Hi,
FuzzyOCR
>-- no PDF capabilities
>
wrong, latest dev has code for PDF, but you need few other programs to
work with PDFs and there is a problem:
I couldn`t setup them right :( , I`ve "pstopnm died with signal 8" and
I think that problem with pdftops
because pstopnm works great with p
> Hrm. It works fine on my install, and you seem to be having issues
> specifically with mimeheader rules. Are you sure your installation is
> ok, at
> least the MIMEHeader plugin part?
Sure? Of course not.
But, I can confirm that the install /was/ --lint'ing without error
immediately prior
I can see that downloaded last night - but I can't see a score
associated with it? Will it actually do anything?
I can't say, at the moment :-/
Since the latest sa-update my install not longer --lint's error-free; I'd
forwarded that info to Theo in a split off this thread .
I'm rebuilding/r
Hrm. It works fine on my install, and you seem to be having issues
specifically with mimeheader rules. Are you sure your installation is ok,
at
least the MIMEHeader plugin part?
Sure? Of course not.
But, I can confirm that the install /was/ --lint'ing without error
immediately prior to the
On 7/16/07, Theo Van Dinter <[EMAIL PROTECTED]> wrote:
On Mon, Jul 16, 2007 at 10:25:17AM -0700, JT DeLys wrote:
> >I published the rule to 3.2 the other day, btw.
>
> By 'published', which do you mean: on the website, @ the wiki, in the
src
> tree, etc?
As
When PDFText2 is loaded, it's rendered text will be tested for the word
stock just like everything else that SpamAssassin offers for your tests to
match against. You might consider it to be the more SpamAssassin natural way
of matching against PDF text :).
Clear. Thanks.
Well, I am going to
Hi,
With PDFText2, the found text is added (rendered) to the main tests that
SpamAssassin does.
Do you mean to those tests defined in 80_additional.cf? or others?
PDFText2 can also use gocr to do OCR on any PDF images. I'm not sold on that
as the first one I tested it on gave back :
Is t
third party virus definitions
I wasn't even aware that there *were* 3rd party virus definitions for
ClamAV. Will take an additional look.
--
Thanks,
JTDeLys
Hi Jerry,
I noticed that sa-update last night pulled in something new, but I
don't know which of the files changed since they all have today's
date on them. Maybe that was it.
i don't know if it's the /only/ place that it's available, but, you're
correct -- a manual sa-update pulled the
Hi,
80_additional.cf
> -- not available for v3.2
I published the rule to 3.2 the other day, btw.
By 'published', which do you mean: on the website, @ the wiki, in the src
tree, etc?
Or should an 'update' find it?
--
Thanks,
JTDeLys
Hi,
Could someone perhaps succinctly summarize the various & sundry
anti-pdf-image-spam tools that are currently in play?
My goal is, simply, to cut down on the PDF spam we're seeing; the same goal
as others share.
My hope is that there's a tool that's (1) publicly available, and (2) works
in b
FYI -- trunk/3.3.0 updates are now working.
Thanks :-)
Although, I think I'll also take earlier advice & 'stay here' (a stable &
working 3.2.x) for a bit.
--
Thanks,
JTDeLys
It depends on the version that the 3.2-branch announces itself as, I
think, since that determines the DNS name that's checked within the
SA channel.
Good point.
Then, just FYI, here (for the moment),
> spamassassin --version
SpamAssassin version 3.2.2-r547235
running on Perl version 5
FYI.
After chatting in #irc, checking execution with DEBUG enabled
spamassassin --debug --remove-addr-from-whitelist ...
clearly shows the problem,
[24453] dbg: auto-whitelist: tie-ing to DB file of type DB_File R/W in
/var/root/.spamassassin/auto-whitelist
Checking the documentatio
The same thing is true if you install from the 3.2-branch, or at least
it was in the 3.2.0 days
I'm currently running a build from svn 3.2-branch, and it /seems/ to
be working correctly. There are, at least, files being pulled into my
LOCALSTATEDIR for both SARE & SA-Distrib rules.
--lint pass
I'm trying to /remove/ an address from my current AWL.
Here's the active whitelist,
% cd /usr/local/etc/spamassassin/.spamassassin/
% ls -al auto-whitelist
-rw-rw 1 saadmin saadmin 10248192 Jun 26 16:04 auto-whitelist
It contains this address,
% check_whitelist auto-whitelist | grep car
If you were to use 3.2 it would work.
I've already 'downgraded' to svn 3.2-branch, and you're right - It works!
Reverting the changes that broke 3.3 updates is on my list of things to do.
Great. Thanks.
--
Thanks,
JTDeLys
I still use the broken one in production. It only actually causes the
error _sometimes_, and it doesn't appear to be fatal to the scanning
process.
Good enough!
--
Thanks,
JTDeLys
For awhile, I've not had spf-whitelisting working correctly.
So, some messages have been getting "too high" spam scores, despite
being spf-OK'd.
Now, spf-whitelisting is working again.
For a couple of messages from the spf-whitelisted domain, I got the
expected bunch-of-hits , 'plus' ~100 pts f
Sorry, I've been having some issues at work for the last 6 or 7 months,
that have kept me from working on the next version of Botnet.
It's fixed in the version... I just haven't been able to get the new
version out the door :-}
I understand. Thanks.
In the meantime, is Botnet /with/ these err
felicity has faster fingers.
He beat me to the puchline.
Thanks
JTDeLys
I'm not sure what the problem is you are attempting to demonstrate...
the update from updates.spamassassin.org contains everything you need
from the default DATADIR.
The issue parallels a discussion I've been having in IRC.
The problem is that I'm not seeing any SPF checks being done, despit
Exploring some problems I've been having, I have uploaded the latest
SpamAssassin SVN source code.
I'm specifying 'custom' locations for SpamAssassin local, distribution &
update files.
Despite being correctly 'told' where to pick up the files, SA seems to
ignore the DATADIR spec (where the Dist
In debugging some Spamassassin configuration problems, I've found lots of
Botnet-plugin-related errors in my logs -
" Use of uninitialized value in string eq at
/var/spamassassin/local/Botnet.pm line 564."
I found a January 17th, 2007 post on this @
http://archives.devshed.com/forums/networkin
... you're usually OK ... debug might tell you why ... might be able to
tell you why ... it probably did.
Haha. Now that we've cleared THAT up ;-)
Kidding aside ... I understand.
Thanks,
JTDeLys
This is normal, some regexes can't be optimized. They're still used
though.
> What do I do about these?
Nothing.
That's good. And, thanks.
(Re-enabling loadplugin Mail::SpamAssassin::Plugin::Rule2XSBody now).
One comment that I'll share: After reading the list, wiki, general web, etc
I go
After reading a bunch of typical posts on the user list, is THIS issue/topic
(sa-compile related) better reported to the Developer list or the Bug
Reporting tools?
Thanks,
JTDeLys
I've installed Spamassassin version 3.2.1, and have enabled
loadplugin Mail::SpamAssassin::Plugin::Rule2XSBody
in 'init.pre'.
After downloading the latest rule updates using sa-update, when I compile
the rules using
sa-compile --sudo -D
It finishes "correctly" at
COMPILE DONE
Checking
35 matches
Mail list logo
