| Testing new rulesets with --lint [message #668] |
Tue, 22 June 2004 10:55 |
Greyhound
Messages: 6
Registered: June 2004
|
Junior Member |
|
|
I have written some new company specific rules for spamassissan (No Spam Today!). Before putting them into an productive environment I wanted to test them. To do so I used the –lint option.
C:\XXX\sa>C:\XXX\sa\spamassassin -d --configpath=C:\XXX\sa --prefspath
C:\XXX\sa\ruleset\local.cf --siteconfigpath=C:\XXX\sa\ruleset\ --lint
That worked fine and I could find some syntax errors, except the fact that I get two error messages that I can not explain nor correct:
Use of uninitialized value in concatenation (.) or string at /PerlApp/File/Spec
Win32.pm line 240.
Use of uninitialized value in open at /PerlApp/Mail/SpamAssassin/TextCat.pm lin
63.
cannot open languages: No such file or directory
As it is an NT Installation there is no path like “/PerlApp/Mail/SpamAssassin”
Some body a clou where the error comes from and a hint what to do ?
|
|
|
|
| Re: Testing new rulesets with --lint [message #669 is a reply to message #668] |
Tue, 22 June 2004 11:59  |
support
Messages: 925
Registered: April 2004
|
Senior Member |
|
|
Does 'XXX' contain blanks? If so, use paths relative to c:\XXX in your commands only, like this:
C:\XXX>sa\spamassassin -d -c sa\ruleset --lint
Customer Support
Byteplant GmbH
|
|
|
|
| Re: Testing new rulesets with --lint [message #670 is a reply to message #669] |
Tue, 22 June 2004 16:08 |
Greyhound
Messages: 6
Registered: June 2004
|
Junior Member |
|
|
Thanks for your quick answer.
There are no blanks in the XXX...
Well in a certain way that helped  . Using your your command “C:\testsa>sa\spamassassin -d -c sa\ruleset –lint” I found an other mistake in my rules. But still I have the same problem.
C:\testsa>sa\spamassassin -d --configpath=\sa --prefspath=sa\ruleset\local.cf --
siteconfigpath=sa\ruleset\ --lint
Use of uninitialized value in open at /PerlApp/Mail/SpamAssassin/TextCat.pm line
63.
cannot open languages: No such file or directory
Or using your command:
C:\testsa>sa\spamassassin -d -c sa\ruleset --lint
Cannot open /usr/share/spamassassin/user_prefs.template: No such file or directo
ry
Failed to create default user preference file C:\Dokumente und Einstellungen\abc
/.spamassassin/user_prefs
|
|
|
|
|
|
| Re: Testing new rulesets with --lint [message #672 is a reply to message #670] |
Wed, 23 June 2004 10:53 |
support
Messages: 925
Registered: April 2004
|
Senior Member |
|
|
> C:\testsa>sa\spamassassin -d --configpath=\sa
> --prefspath=sa\ruleset\local.cf --
> siteconfigpath=sa\ruleset\ --lint
> Use of uninitialized value in open at
> /PerlApp/Mail/SpamAssassin/TextCat.pm line
> 63.
> cannot open languages: No such file or directory
Are you sure about the config path? My guess is there are no rule files in this directory, and the SpamAssassin error message is a consequence of this.
> Or using your command:
>
> C:\testsa>sa\spamassassin -d -c sa\ruleset --lint
> Cannot open /usr/share/spamassassin/user_prefs.template: No
> such file or directo
> ry
> Failed to create default user preference file C:\Dokumente
> und Einstellungen\abc
> /.spamassassin/user_prefs
Not to worry, this is just a warning. Spamassassin always tries to create a user_prefs file if it is not present, but you do not need it anyway. Adding a -x or -p option should suppress this. See the SpamAssassin site for a documentation of command line switches:
http://www.spamassassin.org/doc/spamassassin.html
Customer Support
Byteplant GmbH
|
|
|
|
|
|
|
|
Members
Search
Help
Register
Login
Home
