On Wednesday 30 May 2007 21:36, Justin Mason wrote:
> Guys -- could you open a bugzilla entry about this, attaching
> (a) sample messages that are missed and (b) your relevant configuration
> lines? it sounds like it may have something to do with how the
> bounces are formatted, I'd guess.
Done,
Hi,
I had Justin's VBounce ruleset working fine until I switched to 3.2.0 and I
seem to have bounce messages coming through again. I've checked that
spamassassin is loading the plugin and it is, but testing with both a genuine
bounce (I've commented out the whitelist_bounce_relays entries from
On Saturday 25 November 2006 15:26, Chris wrote:
> I've installed the VBounce Ruleset and it tags bounce messages correctly,
> however, I'm pretty much lost when it comes to writing other than a simple
> procmail recipe. So if someone could lend a hand I'd be very much
>
> appreciative. What I h
On Friday 13 Oct 2006 17:55, Justin Mason wrote:
> I copied the VBounce.pm and 20_vbounce.cf from the rulesrc SVN repository,
> path sandbox/jm, into my 3.1.x "rules" dir, then modified the code for
> have_any_bounce_relays() to output a warning; sure enough, running
> "spamassassin --lint" output
On Friday 13 Oct 2006 15:32, Justin Mason wrote:
> that sounds like the plugin .pm file didn't load correctly.
> Can you check to ensure you have the most recent version (of both
> .pm and .cf)? And post the entire debug log of "spamassassin -D --lint"?
Thanks Justin, I only downloaded the .pm a
On Friday 01 Sep 2006 10:23, Justin Mason wrote:
> There's also a very good ruleset I've been using for a while now, at
>
> http://svn.apache.org/repos/asf/spamassassin/rules/trunk/sandbox/jm/20_vbou
>nce.cf
>
> It catches almost all my unwanted bounces. Requires a little hand-editing
> before it
On Saturday 20 Nov 2004 04:27, Rob Blomquist wrote:
> > X-Spam-Level: **
> > X-Spam-Status: Yes, score=53.2 required=5.0 tests=BAYES_99,DCC_CHECK,
> >
> > I have better than a 99.99% catch rate.
>
> I gotta love it. And I see that you guys are the pr
On Saturday 20 Nov 2004 02:50, alan premselaar wrote:
>I'd suggest changing it to /usr/bin/perl -T -w (instead of
> /usr/bin/perl5.8.5) to prevent the same kind of confusion should you
> ever upgrade perl again.
Thanks Alan, good idea :-)
Bob
On Friday 19 Nov 2004 22:08, Nix wrote:
> > Yes, I know what it means, but see below (I'm not sure exactly where the
> > request for /usr/bin/perl5.8.3 is coming form or how I fix it) ...
>
> It's on the first line of the sa-learn script (which names the
> interpreter, i.e., perl, to use to inter
On Friday 19 Nov 2004 17:40, you wrote:
> > when I try to sa-learn my ham/spam I get the following:
> > /usr/bin/sa-learn: /usr/bin/perl5.8.3: bad interpreter: No such file
> > or directory
>
> I've always thought that "No such file or directory" was one of the
> clearest messages from a computer,
On Friday 19 Nov 2004 17:40, Michael Barnes wrote:
> > when I try to sa-learn my ham/spam I get the following:
> > /usr/bin/sa-learn: /usr/bin/perl5.8.3: bad interpreter: No such file
> > or directory
>
> I've always thought that "No such file or directory" was one of the
> clearest messages from
On Friday 19 Nov 2004 08:29, alan premselaar wrote:
>what is the actual sa-learn command you're using? I ran into this
> using Maildir format by specifying sa-learn -D --spam
> /path/to/maildir/cur/*
I use one script to move the mails out of my mail directory tree into my
ham/spam folders:
/
I've run into a problem with sa-learn. I'm running SA 3.0.1, and since the
RPMs always seem to lag behind the binaries it's compiled. I call
spamassassin using amavsd. I think the problem has arisen since upgrading my
Mandrake system from 10.0 to 10.1, it looks like 10.1 uses Perl 5.8.5, I
thin
On Tuesday 12 Oct 2004 22:05, Joe Jenkins wrote:
> I am trying to make Spam Assassin 3.0 redirect all tagged spam emails to
> one file in /var/spool/SPAM instead of ever having it show up in the
> individual users email boxes. I've got spamassassin working now (thanks,
> theo and matt) and it see
14 matches
Mail list logo