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 2006/10/19 03:00:44 UTC

[Bug 5135] New: Expose LOCAL_STATE_DIR for 3rd party clients

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5135

           Summary: Expose LOCAL_STATE_DIR for 3rd party clients
           Product: Spamassassin
           Version: unspecified
          Platform: All
               URL: http://lists.roaringpenguin.com/pipermail/mimedefang/200
                    6-October/thread.html
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P5
         Component: sa-update
        AssignedTo: dev@spamassassin.apache.org
        ReportedBy: shiva@sewingwitch.com


MIMEDefang needs to know the value of the spamassassin Makefile macro
LOCAL_STATE_DIR to access new rules acquired from sa-update.

See the thread titled "SA Scores" in this month's MIMEDefang mailing list for
the discussion.

http://lists.roaringpenguin.com/pipermail/mimedefang/2006-October/thread.html



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 5135] Expose LOCAL_STATE_DIR for 3rd party clients

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





------- Additional Comments From jm@jmason.org  2006-10-20 06:57 -------
I think that LOCAL_STATE_DIR on the Mail::SA object should be accessible to
MIMEDefang, too.   if it's not readable as a simple var, use the sed_path() API.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 5135] Expose LOCAL_STATE_DIR for 3rd party clients

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





------- Additional Comments From felicity@apache.org  2006-10-18 18:55 -------
(In reply to comment #0)
> MIMEDefang needs to know the value of the spamassassin Makefile macro
> LOCAL_STATE_DIR to access new rules acquired from sa-update.

What exactly is the issue?  I looked through some of the thread, and it appears
people are using updatedir, which they really shouldn't be doing, but that's a
different matter.

As of 3.1.5, SpamAssassin sets a default LOCAL_STATE_DIR anyway, so as long as
mimedefang isn't overriding things, everything should work.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 5135] Expose LOCAL_STATE_DIR for 3rd party clients

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


shiva@sewingwitch.com changed:

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




------- Additional Comments From shiva@sewingwitch.com  2006-10-20 06:30 -------
Fixed in 3.1.5. Marking as dup of bug 4952. MIMEDefang 2.58-BETA-1 contains code
to check the SA version and only stuff a LOCAL_STATE_DIR for earlier versions.

*** This bug has been marked as a duplicate of 4952 ***



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.