> > That pretty much equals your local.cf, no?
>
> No, the currently effective config is not equal to my local.cf (even for
> postconf -n equivalency) because, as you say, users can change their
> user_prefs.
>
> So we're lead to "Isn't that your local.cf plus your user_prefs?" Well, not
> just local.cf, IIUC, but potentially any of the 47 files in my hosting
> provider's /usr/share/spamassassin and /etc/mail/spamassassin dirs (or any
Aah... no. :) The stuff in /usr/share/spamassassin (granted, plus
the .pre files) is exactly the *base*. Stock SA. No user-servicable
parts inside. This dir won't even be used, after an sa-update.
Frankly, there are some important differences between SA and postfix
"configuration". Just to start the list, not exhaustive:
'postconf' without the handy -n switch dumps about 500 lines. The
equivalent dump for SA including the rules is about 6000 lines. And
that's a plain dump, *without* following and unfolding meta rules or
anything.
Also, frankly, I don't think SA rules are really the same as settings.
There are exactly two (sensible) possible places for custom configu-
ration. /etc/mail/spamassassin and the user_prefs, if any.
> others if they happen to have configured such), plus my user_prefs file
> (_except_ any items which are prohibited from being overridden (except the
> privileged settings which are actually allowed by allow_user_rules (except
> those
> privileged settings which are actually "administrator" privileged settings
> which
> cannot be allowed via allow_user_rules))), but minus misspellings and possibly
> minus rules following misspellings in any of the config files.
Hell, no! Assuming there are mis-spellings is inherently broken. Do
lint check your configuration after *any* change. No complaints, no
mis-spellings.
> [...] Meaning, if I want to
> know for sure exactly what results in the effective config, do I consult the
> POD? Or maybe the POD and the man pages, and perhaps a particular wiki
> article
> and that's it, period.
POD == man pages.
Anyway, you're contradicting yourself. POD plus a single wiki page -- to
grok the FULL configuration? That's what you requested to be dumped by a
postconf-alike. Right, 6000 lines full of meta-rules and ghastly REs.
Understood after the tiny bit of lecture you mentioned? No way.
> I imagine just about every SA admin here has played out the scenario
> repeatedly
> and knows the locations of the bodies. "Come on, there are only four." Heck,
> even though I didn't install the SA here and I'm coming at this as a total
> noob
> I may already have all the critical details I need. But how am I to know
> that?
> This is what I mean by open-ended.
As a "noob", you aren't interested in the full postconf dump, are you?
You want your custom settings, -n...
I guess you're approaching this from the wrong end. It's almost like you
don't trust the default config. The first thing for a new user after
installing any application (and ensuring it works) is to customize it.
Not to dissect and anatomize its deepest innards.
Maybe you should try to ask specific questions, and explain what you
want to accomplish.
--
char *t="\10pse\0r\0dtu...@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; }}}
