Hmm, perhaps I spoke to soon. It's entirely possible Debian has modified the source and configuration to look in those directories.

If you're using Debian's version, try SpamAssassin -tD and see what paths the copy you have REALLY uses.

Even though I disagree with the license of djgbdns, I can understand why the author doesn't like "vendorization" of the install paths.

At 02:47 PM 11/15/2002 -0500, Tom Allison wrote:

COOL!

This is either a problem with:
Old Version
or
Debian

Debian sometimes has some weird policies...


--
[It is] best to confuse only one issue at a time.
-- K&R



-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk


-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to