Re: How to output Debugged Lint to file

Is it possible that this --allowplugins was somehow disrupting the sa-update as now that I have removed it my rules are being used again (which may mean that they are back up to day?) Kate Theo Van Dinter wrote: On Thu, May 22, 2008 at 09:57:49AM +1200, Kathryn Kleinschafer wrote: Any re

Re: How to output Debugged Lint to file

Theo Van Dinter wrote: On Thu, May 22, 2008 at 09:57:49AM +1200, Kathryn Kleinschafer wrote: Any reason for the non-default --allowplugins? One of the channels - Open Protect required it "If you use SA versions 3.2.0 or above, use the following command: *sa-update --allowplugins --

Re: How to output Debugged Lint to file

On Thu, May 22, 2008 at 09:57:49AM +1200, Kathryn Kleinschafer wrote: > >Any reason for the non-default --allowplugins? > > > One of the channels - Open Protect required it > "If you use SA versions 3.2.0 or above, use the following command: > *sa-update --allowplugins --gpgkey > D1C035168C1EBC0

Re: How to output Debugged Lint to file

Karsten Bräckelmann wrote: On Thu, 2008-05-15 at 10:01 +1200, Kathryn Kleinschafer wrote: I run sa-update from the crontab daily which I believe should update the rules. (i'm relatively new to this so could have it completely wrong) The command I use in crontab is 00 01 * * * sa-update

Re: How to output Debugged Lint to file

[quote] Does it actually read the files in the update channel dirs? Something like this, below the point where the debugging output has been snipped. [/quote] Yes I think it does - the relevant output is below. [5153] dbg: config: fixed relative path: /var/lib/spamassassin/3.002002/sought_rules

Re: How to output Debugged Lint to file

On Thu, 2008-05-15 at 10:46 +1200, Kathryn Kleinschafer wrote: > I run the update via a crontab entry (set when logged in as root) how do > I specify who its done by and what the umask is? Edit the crontab as the user you want it to be run. Alternatively, have a look at 'man crontab'. > spamassa

Re: How to output Debugged Lint to file

On Thu, 2008-05-15 at 10:01 +1200, Kathryn Kleinschafer wrote: > I run sa-update from the crontab daily which I believe should update the > rules. (i'm relatively new to this so could have it completely wrong) > The command I use in crontab is > 00 01 * * * sa-update --allowplugins --channelfile

Re: How to output Debugged Lint to file

I run the update via a crontab entry (set when logged in as root) how do I specify who its done by and what the umask is? spamassassin is run by postfix user - all this part of the setup should be fine as I haven't played with the config files and it had all been running well. I run the test a

Re: How to output Debugged Lint to file

On Thu, 15 May 2008, Kathryn Kleinschafer wrote: > Hi, > > Pastebin for email: http://pastebin.ca/1018368 > Pastebin for spam check results: http://pastebin.ca/1018373 > > Thanks > Kate > > Karsten Bräckelmann wrote: > > On Wed, 2008-05-14 at 16:25 +1200, Kathryn Kleinschafer wrote: > > > >> which

Re: How to output Debugged Lint to file

I run sa-update from the crontab daily which I believe should update the rules. (i'm relatively new to this so could have it completely wrong) The command I use in crontab is 00 01 * * * sa-update --allowplugins --channelfile /etc/mail/spamassassin/update-channels.txt --gpgkeyfile /etc/mail/spa

Re: How to output Debugged Lint to file

On Thu, 2008-05-15 at 09:09 +1200, Kathryn Kleinschafer wrote: > > Pastebin for email: http://pastebin.ca/1018368 > Pastebin for spam check results: http://pastebin.ca/1018373 OK. And what about my questions above? Err, wait, they are actually below your reply. ;) > Karsten Bräckelmann wrote:

Re: How to output Debugged Lint to file

Hi, Pastebin for email: http://pastebin.ca/1018368 Pastebin for spam check results: http://pastebin.ca/1018373 Thanks Kate Karsten Bräckelmann wrote: On Wed, 2008-05-14 at 16:25 +1200, Kathryn Kleinschafer wrote: which seems to me that it is actually loading up the correct files - yet when

Re: How to output Debugged Lint to file

On Wed, 2008-05-14 at 16:25 +1200, Kathryn Kleinschafer wrote: > which seems to me that it is actually loading up the correct files - yet > when i do a test on a piece of mail which should hit heaps of rules > especially the sought_rules it is not hitting at all. > Are there any other tests I can

Re: How to output Debugged Lint to file

I am running it by going: sudo -u postfix spamassassin -p /etc/MailScanner/spam.assassin.prefs.conf -t < messagename.mai Matt Kettler wrote: Kathryn Kleinschafer wrote: Awesome thanks. the output showed [3887] dbg: config: using "/etc/mail/spamassassin" for site rules pre files [3887] d

Re: How to output Debugged Lint to file

Kathryn Kleinschafer wrote: Awesome thanks. the output showed [3887] dbg: config: using "/etc/mail/spamassassin" for site rules pre files [3887] dbg: config: read file /etc/mail/spamassassin/init.pre [3887] dbg: config: read file /etc/mail/spamassassin/v310.pre [3887] dbg: config: read file /e

Re: How to output Debugged Lint to file

Awesome thanks. the output showed [3887] dbg: config: using "/etc/mail/spamassassin" for site rules pre files [3887] dbg: config: read file /etc/mail/spamassassin/init.pre [3887] dbg: config: read file /etc/mail/spamassassin/v310.pre [3887] dbg: config: read file /etc/mail/spamassassin/v312.pre [

Re: How to output Debugged Lint to file

Kathryn Kleinschafer wrote: Hi all, My installation of spamassassin seems to have stopped using all the rules I have added when checking email. They now reside in /var/lib/spamassassin/3.002002 I'm trying to run spamassassin -D --lint and output it to say test.txt so that I can see it all l