Gary V wrote: > It did work this time. Even with the spamcop error... > > sfa:~# su amavis -c 'sa-learn --dump magic' > 0.000 0 3 0 non-token data: bayes db version > 0.000 0 7 0 non-token data: nspam > [...] > > sfa:~# su amavis -c 'spamassassin -r < email.txt' > [2812] warn: reporter: SpamCop message older than 2 days, not reporting > 1 message(s) examined. > > sfa:~# su amavis -c 'sa-learn --dump magic' > 0.000 0 3 0 non-token data: bayes db version > 0.000 0 8 0 non-token data: nspam > [...]
Bear in mind that if you have auto-learning enabled, some of the spam you're trying to learn and report has already been learned correctly as spam, so SpamAssassin won't try to re-learn it unless its status has changed (e.g. you're now telling it that the mail was ham, not spam). If the auto-learning mechanism made the correct assessment at scan-time, then you won't see any Bayes changes when you try to learn it manually later. In other words, you're not witnessing a bug, you're seeing the designed behaviour at work. Incidentally, this would be the same whether you were using '-r' or '--spam'--the same Bayes training routine gets called in both cases, and the success or failure of the reporting effort has no bearing on this. -- Robert LeBlanc <[EMAIL PROTECTED]> Renaissoft, Inc. Maia Mailguard <http://www.maiamailguard.com/>
signature.asc
Description: OpenPGP digital signature
