upgraded 3.0.4 to 3.1.0, spamassassin --lint produces:
[EMAIL PROTECTED] spamassassin]# spamassassin --lint
[1257] warn: config: SpamAssassin failed to parse line, "/home/bayes/"
is not valid for "bayes_path", skipping: bayes_path _/home/bayes/
[1257] warn: config: failed to parse line, skipping:
Mark Merchant wrote:
upgraded 3.0.4 to 3.1.0, spamassassin --lint produces:
[EMAIL PROTECTED] spamassassin]# spamassassin --lint
[1257] warn: config: SpamAssassin failed to parse line, "/home/bayes/"
is not valid for "bayes_path", skipping: bayes_path _/home/bayes/
[1257] warn: config: failed to
Mark Merchant wrote:
> upgraded 3.0.4 to 3.1.0, spamassassin --lint produces:
>
> [EMAIL PROTECTED] spamassassin]# spamassassin --lint
> [1257] warn: config: SpamAssassin failed to parse line, "/home/bayes/"
> is not valid for "bayes_path", skipping: bayes_path _/home/bayes/
SA is correct, your b
Everyone,
I upgraded from 3.0.3 to 3.1.0 and have had a bunch of problems. I
finally got a good install, but could not do it via cpan. There were
many modules that I had to manually install. I have had it active for
about a week and every night for some reason it stops filtering. When
this hap
On Sat, Oct 08, 2005 at 10:59:43AM -0500, Gregory P. Ennis wrote:
> Here are the results of spamassassin --lint:
>
> [18110] warn: plugin: failed to parse plugin (from @INC): Can't locate
> Mail/DomainKeys/Message.pm in @INC (@INC contains:
You've enabled the DomainKeys plugin, disabled by defaul
On Sat, 2005-10-08 at 12:27 -0400, Theo Van Dinter wrote:
> On Sat, Oct 08, 2005 at 10:59:43AM -0500, Gregory P. Ennis wrote:
> > Here are the results of spamassassin --lint:
> >
> > [18110] warn: plugin: failed to parse plugin (from @INC): Can't locate
> > Mail/DomainKeys/Message.pm in @INC (@INC
On Sat, Oct 08, 2005 at 11:42:13AM -0500, Gregory P. Ennis wrote:
> On Sat, 2005-10-08 at 12:27 -0400, Theo Van Dinter wrote:
> > On Sat, Oct 08, 2005 at 10:59:43AM -0500, Gregory P. Ennis wrote:
> > > Here are the results of spamassassin --lint:
> > >
> > > [18110] warn: plugin: failed to parse p
Gregory P. Ennis schrieb:
Everyone,
I upgraded from 3.0.3 to 3.1.0 and have had a bunch of problems. I
finally got a good install, but could not do it via cpan. There were
many modules that I had to manually install. I have had it active for
about a week and every night for some reason it sto
On Sat, 2005-10-08 at 13:08 -0400, Theo Van Dinter wrote:
>
> Is it in a "normal" location that perl will look for it? (the list of @INC
> dirs from the error message)
>
I have a Red Hat 8.0 system with the plugins stored in :
/usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/Plugin
which is th
On Sat, 2005-10-08 at 18:15 +0100, Patrick von der Hagen wrote:
> Gregory P. Ennis schrieb:
> > Everyone,
> >
> > I upgraded from 3.0.3 to 3.1.0 and have had a bunch of problems. I
> > finally got a good install, but could not do it via cpan. There were
> > many modules that I had to manually in
On Sat, Oct 08, 2005 at 12:19:46PM -0500, Gregory P. Ennis wrote:
> I have a Red Hat 8.0 system with the plugins stored in :
> /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/Plugin
> which is the normal directory for other SA plugins that are working.
Right. The problem isn't finding the plug
On Sat, 2005-10-08 at 13:28 -0400, Theo Van Dinter wrote:
> On Sat, Oct 08, 2005 at 12:19:46PM -0500, Gregory P. Ennis wrote:
> > I have a Red Hat 8.0 system with the plugins stored in :
> > /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin/Plugin
> > which is the normal directory for other SA plugi
On Saturday 08 October 2005 01:20 pm, Gregory P. Ennis wrote:
> On Sat, 2005-10-08 at 13:28 -0400, Theo Van Dinter wrote:
> > On Sat, Oct 08, 2005 at 12:19:46PM -0500, Gregory P. Ennis wrote:
> > > I have a Red Hat 8.0 system with the plugins stored in :
> > > /usr/lib/perl5/site_perl/5.8.0/Mail/Sp
On Sun, 2005-10-09 at 09:41 -0500, Gregory P. Ennis wrote:
> On Sat, 2005-10-08 at 18:15 +0100, Patrick von der Hagen wrote:
> > Gregory P. Ennis schrieb:
> > > Everyone,
> > >
> > > I upgraded from 3.0.3 to 3.1.0 and have had a bunch of problems. I
> > > finally got a good install, but could not
On Sat, Oct 08, 2005 at 01:20:10PM -0500, Gregory P. Ennis wrote:
> [21132] warn: _(Can't locate object method "header" via package
> "Mail::DomainKeys::Message"
Hrm. What version of Mail::DomainKeys are you folks
installing? The error indicates that a function that should be in
Mail::DomainKeys
On Sun, Oct 09, 2005 at 01:44:20PM -0400, Theo Van Dinter wrote:
> I'd open up a bugzilla ticket (http://bugzilla.spamassassin.org) about this.
Oh, in the meantime I'd consider just disabling the plugin to avoid getting
the error message, until a solution is implemented.
--
Randomly Generated Ta
On Sunday 09 October 2005 12:44 pm, Theo Van Dinter wrote:
> On Sat, Oct 08, 2005 at 01:20:10PM -0500, Gregory P. Ennis wrote:
> > [21132] warn: _(Can't locate object method "header" via package
> > "Mail::DomainKeys::Message"
>
> Hrm. What version of Mail::DomainKeys are you folks
> installing?
On Sun, 2005-10-09 at 13:00 -0500, Chris wrote:
> On Sunday 09 October 2005 12:44 pm, Theo Van Dinter wrote:
> > On Sat, Oct 08, 2005 at 01:20:10PM -0500, Gregory P. Ennis wrote:
> > > [21132] warn: _(Can't locate object method "header" via package
> > > "Mail::DomainKeys::Message"
> >
> > Hrm. Wh
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
(argh! what's with sending via gmane? ... sorry if this is a dupe)
hi greg,
Gregory P. Ennis wrote:
>> > > On Sun, 2005-10-09 at 13:00 -0500, Chris wrote:
>> >> On Sunday 09 October 2005 12:44 pm, Theo Van Dinter wrote:
>> >>> >>> On S
OpenMacNews wrote:
[16993] dbg: plugin: registering glue method for check_domainkeys_signall
(Mail::SpamAssassin::Plugin::DomainKeys=HASH(0x5d7060))
[16993] warn: rules: failed to run DK_POLICY_SIGNALL test, skipping:
[16993] warn: _(Can't locate object method "header" via package
"Mail::DomainK
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
hi daryl,
Daryl C. W. O'Shea wrote:
> I don't think anybody bothered opening a bug on it.
fair nuf.
*i* can, of course, but would rather that someone who actually know wtf the
issue is does so =:-)
it's also not clear -- to me, at this junctu
OpenMacNews wrote:
Daryl C. W. O'Shea wrote:
I don't think anybody bothered opening a bug on it.
fair nuf.
*i* can, of course, but would rather that someone who actually know wtf the
issue is does so =:-)
it's also not clear -- to me, at this juncture -- whether its a SA bug, a
DomainKeys
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
hi daryl,
> We'll probably have to adapt to the changed API (which may change again
> before a 1.0 version). I'm not familiar with the API, and haven't
> looked at it, though. I'm just recalling what Theo posted last Sunday.
that said -- i'e,
OpenMacNews wrote:
We'll probably have to adapt to the changed API (which may change again
before a 1.0 version). I'm not familiar with the API, and haven't
looked at it, though. I'm just recalling what Theo posted last Sunday.
that said -- i'e, the "we'll ..." -- could *you*, kindly, (re)rai
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Daryl C. W. O'Shea wrote:
> OpenMacNews wrote:
>>> We'll probably have to adapt to the changed API (which may change again
>>> before a 1.0 version). I'm not familiar with the API, and haven't
>>> looked at it, though. I'm just recalling what Th
In the 3.1.0 upgrade page on the wiki:
http://wiki.apache.org/spamassassin/UpgradeTo310
One will find this text:
-
The SA headers X-Spam-Flag, X-Spam-Checker-Version, X-Spam-Level, and
X-Spam-Status are only added to messages that have been flagged as spam. I have
On Mon, 2005-10-31 at 11:14 -0500, Matt Kettler wrote:
> In the 3.1.0 upgrade page on the wiki:
> http://wiki.apache.org/spamassassin/UpgradeTo310
[...]
> Is it true that 3.1.0 is broken as the wiki indicates, or has someone been
> posting mis-information to the wiki?
misinformation
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Raul Dias writes:
> On Mon, 2005-10-31 at 11:14 -0500, Matt Kettler wrote:
> > In the 3.1.0 upgrade page on the wiki:
> > http://wiki.apache.org/spamassassin/UpgradeTo310
> [...]
> > Is it true that 3.1.0 is broken as th
After upgrading to 3.1, I am receiving a warning about a useless /g regex
modifier in the de-token rules as generated by
http://www.wot.no-ip.com/cgi-bin/detoken.pl
(These are custom-generated rules to look for listwash tokens for your
domain).
The warning is:
[19609] warn: Useless (?g) - use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christopher X. Candreva writes:
> After upgrading to 3.1, I am receiving a warning about a useless /g regex
> modifier in the de-token rules as generated by
> http://www.wot.no-ip.com/cgi-bin/detoken.pl
>
> (These are custom-generated rules to look
30 matches
Mail list logo
