Quanah, I see you already found a solution. However, for completeness and to clarify potential misunderstanding:
On Fri, 2013-10-18 at 16:07 -0700, Quanah Gibson-Mount wrote: > --On Friday, October 18, 2013 7:04 PM -0400 "Kevin A. McGrail" > <[email protected]> wrote: > > > I don't believe that is correct. It appears you are missing the > > /etc/mail/spamassassin/ pre files which includes v320.pre which includes > > this include: > > We of course don't install into /etc/mail That's just a default, actually depending on your $PREFIX. The resulting "site-specific configuration" directory is shared by all SA commands, including sa-update. The SA installation is responsible for that dir and its content to exist. Your failing sa-update command suggests you ran it from within your build tree, prior to installation. > And while building, we build out into a temporary location, related to the > OS of the system being built upon. > > It seems like a significant design flaw that there is no way to bootstrap > SA. There is. Install SA, run sa-update. See the INSTALL file. On this topic it is worth pointing out, that the Mail-SpamAssassin tarball contains everything necessary but the actual rules files. That includes the most basic .pre files. The rules snapshot tarball is equivalent to the "default configuration". -- char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4"; main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1: (c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
