SA Bugzilla – Bug 5135
Expose LOCAL_STATE_DIR for 3rd party clients
Last modified: 2006-10-20 06:57:03 UTC
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
(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.
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 ***
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.