you read the bug history, shown
now as Status: RESOLVED, Resolution: FIXED.
However, a CPAN installation attempted a few moments ago failed as
per the original bug report.
Presumably, Justin's committed patch of 18 Jun 2007 hasn't yet made
its way to the CPAN servers?
--
Anthony Edwards
[EMAIL PROTECTED]
On Thu, May 24, 2007 at 01:12:42PM +0200, Robert Schetterer wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Anthony Edwards schrieb:
> > On Sun, May 06, 2007 at 02:37:34PM +0100, Stephen Carter wrote:
> >> Hi guys,
> >>
> >> I've
Not found: status = X-Spam-Status: Yes, score=
> # Failed test 9 in t/SATest.pm at line 633 fail #8
> Output can be examined in: log/d.spamc_z/out.1
> t/spamc_z...FAILED tests 2-9
> Failed 8/9 tests, 11.11% okay
Same result here, attempting to update via cpan on Ubuntu 6.06.1 LTS.
--
Anthony Edwards
[EMAIL PROTECTED]
fact, explained at:
http://thread.gmane.org/gmane.mail.spam.spamassassin.general/56501
If you edit /etc/init.d/spamd to change the line:
SPAMD_BIN=/usr/sbin/spamd
To read:
SPAMD_BIN=/usr/bin/spamd
Then stop and restart spamd and use the YaST Runlevel Editor to
configure spamd to automatically start in runlevels 3 & 5, that should
provide a resolution for you.
--
Anthony Edwards
[EMAIL PROTECTED]
er "topflite" password "***"
limit 10
[EMAIL PROTECTED]:~> cat .mailfilter
DEFAULT="Mail/inbox"
logfile ".maildroplog"
`reformail -D 8192 .duplicate.cache`
if ( $RETURNCODE == 0 )
exit
if ($SIZE < 10)
xfilter "spamc"
if (/^X-Spam-Flag: YES/)
to Mail/junk
(etc)
--
Anthony Edwards
[EMAIL PROTECTED]
l of
false positives. In our opinion these lists are best used
as part of a scoring system, such as spamassassin and not
for outright blocking of email.
http://dsbl.org/usage
--
Anthony Edwards
[EMAIL PROTECTED]
On Fri, Sep 24, 2004 at 06:12:53PM +0100, Anthony Edwards wrote:
> On Fri, Sep 24, 2004 at 03:04:58AM +0100, Anthony Edwards wrote:
>
> > I removed all SpamAssassin files earlier this evening and re-installed
> > using cpan. With hindsight, I believe I could have simply done
then subsequently upgrading one's SpamAssassin using cpan has benefits
there too.
--
Anthony Edwards
[EMAIL PROTECTED]
On Fri, Sep 24, 2004 at 03:04:58AM +0100, Anthony Edwards wrote:
> I removed all SpamAssassin files earlier this evening and re-installed
> using cpan. With hindsight, I believe I could have simply done what
> you have suggested above. I run a SuSE 8.2 system, and persuading
ent in that file.
Alternatively, perhaps the released version could be amended so
that spamd is installed in /usr/sbin rather than /usr/bin, which
is I understand what the Debian package maintainers have done (that
wouldn't assist users who have already upgraded, of course).
--
Anthony Edwards
[EMAIL PROTECTED]
for the time being.
Incidentally, a co-worker who runs a Debian system tells me that the
Debian package maintainer has overcome the issue by creating the Debian
SpamAssassin 3.0.0 package in such a way that spamd is installed in
/usr/sbin/ rather than /usr/bin, as with previous versions.
--
Anthony Edwards
[EMAIL PROTECTED]
On Thu, Sep 23, 2004 at 01:51:54PM +0100, Anthony Edwards wrote:
> I have also been unable to persuade spamd to add spamassassin headers,
> as per my posting of last night to the list. Running spamassassin, in
> contrast, seems to work properly (which seems to rule out it being
ist. Running spamassassin, in
contrast, seems to work properly (which seems to rule out it being a
local configuration issue?).
--
Anthony Edwards
[EMAIL PROTECTED]
--1 anthony users2184 2004-09-22 23:49
1095894767.4440_1.ultra:2,S
-rw-r--r--1 anthony users2184 2004-09-23 01:01 test
This is preventing the use of SpamAssassin to filter mail, of course.
What is needed to get SpamAssassin to add its usual tags and headers, as
before?
TI
14 matches
Mail list logo