Thank you for the advice. I will attempt to follow it. For today, it's been a long one and my stamina is not yet up to par. So more tomorrow perhaps.
joe a. >>> On 9/6/2013 at 9:42 AM, Axb <axb.li...@gmail.com> wrote: if you need help, the best way is to: - stay *concise* at all times - verbose blah can drive ppl away - post config and then explain issue, *concisely* - don't revive old threads. - help ppl help you - their time is precious and few have unlimited patience. - keep it down to facts - if you have a problem, "I thought", I assumed", "I hoped" are of little value. On 09/06/2013 03:20 PM, Joe Acquisto-j4 wrote: > I'd like to revisit this, now that I have sufficient energy to devote to some > hard sleuthing. Despite the > fact that I was less than sharp (ahem) when first looking at this, I do feel > I have covered all the obvious > suspects. > > Some gentle nudges (or not) might get me rolling again. I suppose I should > repost this with details of what I > have done so far, as even those of kind and gentle nature may not be inclined > to search it out. > > But I won't clutter further, if there is no interest. > > joe a. > >>>> "Joe Acquisto-j4" <j...@j4computers.com> 08/21/13 9:45 AM >>> > >> >> Bear in mind, that will tell you whether those configuration files are >> syntactically correct; that does not tell you anything about whether or >> not those are the files the spamd daemon is using. >> >> Take a look at the script that starts spamd. It may have a hardcoded path >> to the configuration directory. >> >> -- >> John Hardin KA7OHZ >> http://www.impsec.org/~jhardin/ > > The /etc/init.d/spamd file has a hardcoded reference to that specific file. > I'm pretty sure it is the one being read. > > However, I am not so certain others are not being read later. > > I find a lot of references, for example, to BAYES_99 in > /usr/share/spamassassin/blah.cf. I certainly don't know if these would > override the setting in /etc/mail/spamassassin/local.cf. > > joe a. > > > >
