Simple net tests command

[Gary V <mr...@hotmail.com>]

I understand since 3.1.6, 'spamassassin --lint -D' turns off net tests and 
AWL. I would like to request a feature that provides the functionality of 
what was lost here. It's a pain to have to perform the additional task of 
locating a test message so debug has something legitimate to work with. 
Maybe something like 'spamassassin --test -D' could bring back the old 
behavior. Some of us also counted on this to create initial user_prefs and 
AWL files for us.

Gary V

_________________________________________________________________
MSN Shopping has everything on your holiday list. Get expert picks by style, 
age, and price. Try it! 
http://shopping.msn.com/content/shp/?ctId=8000,ptnrid=176,ptnrdata=200601&tcode=wlmtagline

Re: Simple net tests command

[Gary V <mr...@hotmail.com>]

>Gary V wrote:

> > I understand since 3.1.6, 'spamassassin --lint -D' turns off net tests
> > and AWL. I would like to request a feature that provides the
> > functionality of what was lost here. It's a pain to have to perform
> > the additional task of locating a test message so debug has something
> > legitimate to work with.

Matt wrote:

>There's two included in the SA tarball.. It really shouldn't be *that* 
>hard.

No, it's not, but if you are setting up a new system and installing from a 
package and wish to test Pyzor/Razor/DCC as you add and configure them it 
can be disruptive to have to download source code simply to obtain a test 
message.

>But I would agree with your suggestion below:
> > Maybe something like 'spamassassin --test -D' could bring back the old
> > behavior.
>Fair enough, although really this would have to be revamped
>considerably. The old --lint did NOT contain any Received: headers, so
>there wasn't any real testing of the DNS based network checks. I think a
>good "second reason" why network tests were turned off in --lint is
>because people actually thought it was a useful test for them. Other
>than Razor/Pyzor/DCC, it's a pretty useless test case for network tests.
>
>If SA adds a "--test", the message used should be reasonably complete,
>and not a trivial dummy.

Yes, that would be ideal.

Gary V

_________________________________________________________________
Share your latest news with your friends with the Windows Live Spaces 
friends module. 
http://clk.atdmt.com/MSN/go/msnnkwsp0070000001msn/direct/01/?href=http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx&mk

Re: Simple net tests command

[Matt Kettler <mk...@verizon.net>]

Gary V wrote:
> I understand since 3.1.6, 'spamassassin --lint -D' turns off net tests
> and AWL. I would like to request a feature that provides the
> functionality of what was lost here. It's a pain to have to perform
> the additional task of locating a test message so debug has something
> legitimate to work with.
There's two included in the SA tarball.. It really shouldn't be *that* hard.

But I would agree with your suggestion below:
> Maybe something like 'spamassassin --test -D' could bring back the old
> behavior. 
Fair enough, although really this would have to be revamped
considerably. The old --lint did NOT contain any Received: headers, so
there wasn't any real testing of the DNS based network checks. I think a
good "second reason" why network tests were turned off in --lint is
because people actually thought it was a useful test for them. Other
than Razor/Pyzor/DCC, it's a pretty useless test case for network tests.

If SA adds a "--test", the message used should be reasonably complete,
and not a trivial dummy.
> Some of us also counted on this to create initial user_prefs and AWL
> files for us.
Ouch. Well, that's what you get for counting on side effects.

It might be another good idea to add a "--init" which creates the
user_prefs, awl and bayes DB files, as appropriate for the current
config. This would also have the benefit of not populating the AWL with
a dummy record.

Even SA 2.60 never advertised --lint as being useful for anything but
checking the rulefile syntax:

--lint
    Syntax check (lint) the rule set and configuration files, reporting
typos and rules that do not compile correctly. Exits immediately with 0
if there are no errors, or greater than 0 if any errors are found.