You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2010/03/24 13:44:06 UTC

[Bug 6387] New: win32: no rules found when updatedir not specified for sa-update

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6387

           Summary: win32: no rules found when updatedir not specified for
                    sa-update
           Product: Spamassassin
           Version: 3.3.1
          Platform: Other
        OS/Version: Windows XP
            Status: NEW
          Severity: minor
          Priority: P5
         Component: sa-update
        AssignedTo: dev@spamassassin.apache.org
        ReportedBy: lemke@jam-software.com


After using sa-update, spamassassin doesn't find any rules under Windows. If
updatedir flag is set to default rules dir it works, however this isn't the
right way to use sa-update, is it?

sa-update uses the system-wide rules dir to download new rules, but
spamassassin doesn't. Instead it checks the default rules dir for rules.

At least there should be some mechanic to copy rules from the system wide dir
to default dir, if default dir is empty.

This is what the rules dir configuration looks like:

system-wide rules    C:\Perl\site\var\spamassassin\3.003001
default rules        C:\Perl\site/share/spamassassin
site rules        C:\Perl\site/etc/mail/spamassassin
local rules        C:\Perl\site/etc/mail/spamassassin

I've attached debug log for sa-update and spamassassin (this was immediately
after install).

-- 
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

[Bug 6387] win32: no rules found when updatedir not specified for sa-update

Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6387

Daniel <le...@jam-software.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |lemke@jam-software.com

--- Comment #4 from Daniel <le...@jam-software.com> 2010-03-24 13:42:17 UTC ---
No I didn't specify any path. This is what I've done:

C:\SA\Mail-SpamAssassin-3.3.1>sa-update --nogpg -v
Update available for channel updates.spamassassin.org
Update was available, and was downloaded and installed successfully

C:\SA\Mail-SpamAssassin-3.3.1>spamassassin < README
Mrz 24 14:31:30.088 [312] warn: config: created user preferences file:
C:\Dokume
nte und Einstellungen\Administrator/.spamassassin/user_prefs
config: no rules were found!  Do you need to run 'sa-update'? at spamassassin
line 400.


There were no changes made to the original SA source, path configuration of
C:\Perl\site\bin\spamassassin.bat looks like this:

my $PREFIX          = 'C:\Perl\site';             # substituted at 'make' time
my $DEF_RULES_DIR   = 'C:\Perl\site/share/spamassassin';      # substituted at
'make' time
my $LOCAL_RULES_DIR = 'C:\Perl\site/etc/mail/spamassassin';    # substituted at
'make' time
my $LOCAL_STATE_DIR = 'C:\Perl\site/var/spamassassin';    # substituted at
'make' time

-- 
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

[Bug 6387] win32: no rules found when updatedir not specified for sa-update

Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6387

Daniel <le...@jam-software.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID

--- Comment #6 from Daniel <le...@jam-software.com> 2010-03-25 10:42:33 UTC ---
Ok, forget what I said...


I called spamassassin from within the SA source directory. So the corresponding
batch file used the spamassin perl script from the source. I don't know WHY it
fails to find the rules but it does run fine when executed anywhere else than
the SA source directory.


Invalid.

-- 
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

[Bug 6387] win32: no rules found when updatedir not specified for sa-update

Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6387

--- Comment #3 from Karsten Bräckelmann <gu...@rudersport.de> 2010-03-24 13:12:10 UTC ---
Snippet from attachment 4719, spamassassin debug output.

> dbg: config: using "./rules" for sys rules pre files

This doesn't look right. It should use C:\Perl\site\var\spamassassin\3.003001
similar to a few lines earlier, where it correctly used the site rules dir.

> dbg: config: read file ./rules/init.pre
> dbg: config: read file ./rules/v310.pre
> dbg: config: read file ./rules/v312.pre
> dbg: config: read file ./rules/v320.pre
> dbg: config: read file ./rules/v330.pre

And there shouldn't be any pre files in the sa-update provided sys rules dir.

> dbg: config: using "./rules" for default rules dir

And again. Did you manually specify these *relative* paths when calling
spamassassin?

-- 
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

[Bug 6387] win32: no rules found when updatedir not specified for sa-update

Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6387

--- Comment #2 from Daniel <le...@jam-software.com> 2010-03-24 12:45:19 UTC ---
Created an attachment (id=4719)
 --> (https://issues.apache.org/SpamAssassin/attachment.cgi?id=4719)
spamassassin windows logfile

-- 
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

[Bug 6387] win32: no rules found when updatedir not specified for sa-update

Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6387

--- Comment #1 from Daniel <le...@jam-software.com> 2010-03-24 12:44:54 UTC ---
Created an attachment (id=4718)
 --> (https://issues.apache.org/SpamAssassin/attachment.cgi?id=4718)
sa-update windows logfile

-- 
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

[Bug 6387] win32: no rules found when updatedir not specified for sa-update

Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6387

--- Comment #5 from Daniel <le...@jam-software.com> 2010-03-25 09:03:42 UTC ---
Hmm definitely a problem of this part in spamassassin:

BEGIN {
  # Locate locally installed SA libraries *without* using FindBin, which
  # generates warnings and causes more trouble than its worth.  We don't
  # need to be too smart about this BTW.
.......
.......


If FindBin is used the rules are recognized but there should be another way to
do this, I'll have a look on it later.

-- 
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.