Hi,
You are right. Also there is a problem with current p5-FuzzyOcr, it works only
with
Spamassassin 3.1. But in the ports tree p5-Mail-SpamAssassin release is 3.2.X
which is not
compatible with FuzzyOcr older than 3.6.0
There are two options.
1. As RW mentioned, remove p5-FuzzyOcr and
On Sun, 31 May 2009 00:58:30 +0300
Ismail YENIGUL wrote:
> Hi,
>
> I sent an update for this port
> (http://www.freebsd.org/cgi/query-pr.cgi?pr=135065) I also would like
> to be maintainer of this port.
>
It doesn't seem sensible that p5-FuzzyOcr contains an obso
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, May 31, 2009 at 12:58:30AM +0300, Ismail YENIGUL wrote:
> Hi,
>
> I sent an update for this port
> (http://www.freebsd.org/cgi/query-pr.cgi?pr=135065)
> I also would like to be maintainer of this port.
Done
>
> Thanks.
>
>
>
> --
> I
Hi,
I sent an update for this port
(http://www.freebsd.org/cgi/query-pr.cgi?pr=135065)
I also would like to be maintainer of this port.
Thanks.
--
Ismail YENIGUL
Endersys Ltd.
Phone :+90 216-4709423 | Mobile:+90 533 747 36 65
Fax :+90 216-4709508 | web: http://www.endersys.com.tr
Ender
RW wrote:
On Mon, 27 Apr 2009 10:00:29 -0700
pkg_add -r ImageMagick
Fetching
[1]ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7-stable/Latest/ImageM
agick.tbz...
Done.
Fetching
[2]ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7-stable/All/perl-5.8.
9_2.tbz...
Done.
pkg_ad
On Mon, 27 Apr 2009 10:00:29 -0700
> pkg_add -r ImageMagick
> Fetching
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7-stable/Latest/ImageMagick.tbz...
>
> Done.
> Fetching
> ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7-stable/All/perl-5.8.9_2.tbz...
>
> Done.
> pkg_add:
years back i used FuzzyOcr to combat image spam, I stopped using it
after some time went by. Over the last month or 2 I have seen a huge
increase in drug spam, bed event type emails, so I went to install
FuzzyOcr again. I have migrated to the newer perl 5.10, and this is the
first problem I
Garrett
What user are you running spamassassin as?
-Garrett
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Hmm, even modifying it to use /var/log/F
Brian wrote:
Basically the file isn't readable / writable because of permissions
issues, like Shaun said. All of the other 4 error messages are a
biproduct of not being able to open up the file. Did you change the
permissions by accident?
-Garrett
I do not jacking with this file.
-bash-
Basically the file isn't readable / writable because of permissions
issues, like Shaun said. All of the other 4 error messages are a
biproduct of not being able to open up the file. Did you change the
permissions by accident?
-Garrett
___
freebsd-
amassassin/FuzzyOcr.log
I could ln -s it but thats a bandaid, not a fix.
I don't speak enough perl to make sense of the line number errors shown.
/var/db/pkg shows p5-FuzzyOcr-2.3.b_2,1
The log file needs to be writable by the SpamAssassin process (although
it runs as root by default, if I r
pamassassin/FuzzyOcr.log
> I could ln -s it but thats a bandaid, not a fix.
>
> I don't speak enough perl to make sense of the line number errors shown.
>
> /var/db/pkg shows p5-FuzzyOcr-2.3.b_2,1
>
The log file needs to be writable by the SpamAssassin process (althoug
cr.pm
line 431.
The log location is not right, it actually exists in
/usr/local/etc/mail/spamassassin/FuzzyOcr.log
I could ln -s it but thats a bandaid, not a fix.
I don't speak enough perl to make sense of the line number errors shown.
/var/db/pkg shows p5-Fuzzy
I'm running a mail server on FreeBSD 6.2-RELEASE amd64 and want to
use all the cool latest spamassassin stuff, in particular FuzzyOcr
(does OCR on image spam).
I have been doing cvsup on my ports tree to get the latest port updates.
The netpbm devel version is 10.31 dated 05.12.23, not r
I'm running a mail server on FreeBSD 6.2-RELEASE amd64 and want to
use all the cool latest spamassassin stuff, in particular FuzzyOcr
(does OCR on image spam).
I have been doing cvsup on my ports tree to get the latest port updates.
The netpbm devel version is 10.31 dated 05.12.23, not r
On Mon, Nov 27, 2006 at 06:22:46PM -0800, Brian wrote:
>
> >
> >Sorry about this. It seems my last fix was incomplete. I'll update the
> >port again. In the meantime, you can replace the first line (loadplugin
> >FuzzyOcr...) in FuzzyOcr.cf with:
> >
&g
On Mon, Nov 27, 2006 at 02:40:27PM -0800, Brian wrote:
>
> Shaun Amott wrote:
> >On Mon, Nov 27, 2006 at 11:26:46AM -0800, Brian wrote:
> >
> >>Have any of you started getting the below errors with fuzzyocr since the
> >>port updated?
> >>
> &g
Shaun Amott wrote:
On Mon, Nov 27, 2006 at 02:40:27PM -0800, Brian wrote:
Shaun Amott wrote:
On Mon, Nov 27, 2006 at 11:26:46AM -0800, Brian wrote:
Have any of you started getting the below errors with fuzzyocr since the
port updated?
I did have this working manually
Shaun Amott wrote:
On Mon, Nov 27, 2006 at 11:26:46AM -0800, Brian wrote:
Have any of you started getting the below errors with fuzzyocr since the
port updated?
I did have this working manually previously, but now the port has been
updated, and my procmail.log is full of these. The
On Mon, Nov 27, 2006 at 11:26:46AM -0800, Brian wrote:
>
> Have any of you started getting the below errors with fuzzyocr since the
> port updated?
>
> I did have this working manually previously, but now the port has been
> updated, and my procmail.log is full of these.
Have any of you started getting the below errors with fuzzyocr since the
port updated?
I did have this working manually previously, but now the port has been
updated, and my procmail.log is full of these. The corrupt image line
isn't in all of them, but most of the time it is there. I
On Thu, Nov 16, 2006 at 09:21:08AM +, James Seward wrote:
>
> On 11/16/06, Brian <[EMAIL PROTECTED]> wrote:
> >I started using this a few days ago, got a coredump today. Any of you
> >interested in the dumpfile or other debug? I'm tracking 6.stable,
> >currently
> >at the 6.2-PRERELEASE sta
On 11/16/06, Brian <[EMAIL PROTECTED]> wrote:
The relevant corefile is named giftext.core, I'm assuming based on the
name that is a fuzzyocr dependency.
I'd suggest reinstalling your libungif port following step 3 of my
instructions here:
http://jamesoff.net/site/projects/free
ng based on the
name that is a fuzzyocr dependency.
Brian
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On 11/16/06, Brian <[EMAIL PROTECTED]> wrote:
I started using this a few days ago, got a coredump today. Any of you
interested in the dumpfile or other debug? I'm tracking 6.stable, currently
at the 6.2-PRERELEASE stage.
What died? FuzzyOCR's page on the spamassassin wiki mentions patches
for
I started using this a few days ago, got a coredump today. Any of you
interested in the dumpfile or other debug? I'm tracking 6.stable, currently
at the 6.2-PRERELEASE stage.
Brian
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.
26 matches
Mail list logo
