Mailscanner + spamassassin +Razor + Pyzor + DCC

[Glenn Steen]

On 15/03/07, Matt Kettler <mkettler at evi-inc.com> wrote:
> Glenn Steen wrote:
> > On 15/03/07, Matt Kettler <mkettler at evi-inc.com> wrote:
> >> Scott Silva wrote:
> >> > Matt Kettler spake the following on 3/14/2007 11:05 AM:
> >> >> Nicolas Canepa wrote:
> >> >>> Hi, I am using Mailscanner with spamassassin. For what i've read
> >> you can
> >> >>> define in Mailscanner.conf to use pyzor, razor and dcc, or tell
> >> >>> spamassassin to use razor, pyzor and dcc in the local.cf file.
> >> >> Em, no. you can define it in MailScanner.cf,
> >> spam.assassin.prefs.conf, or local.cf.
> >> >>
> >> >> You cannot define it in MailScanner.conf, which is a MailScanner
> >> config file.
> >> >> Mailscanner.cf on the other hand is a spamassassin config file, and
> >> lives in the
> >> >> spamassassin site rules directory.
> >> > Actually, mailscanner.cf is supposed to be a softlink to
> >> > spamassassin.prefs.conf. If you have something else, you are
> >> breaking the
> >> > reason that this was done.
> >>
> >> First, *I* am the reason that was done. So please don't tell me I'm
> >> breaking the
> >> reason it was done.
> >>
> >> Second, I do acknowledge this is how it is by default later on in my
> >> message.
> >>
> >> IMHO, softlinking spamassassin.prefs.conf to MailScanner.cf is
> >> counterproductive.
> >>
> >> When I told Julian to move privileged settings to a .cf file, I meant
> >> for him to
> >> *MOVE* them.
> >>
> >> That said, the softlinking is probably the only usable solution that
> >> can be
> >> automatically applied to existing installs. But the intent is not to
> >> softlink
> >> the two, that's a compromise to avoid breaking peoples systems.
> >>
> >> Now you're all double-parsing the settings for no good reason. Which
> >> isn't
> >> terribly harmful, but it is pointless. You've also defeated all the
> >> benefit of
> >> having a spam.assassin.prefs.conf in the first place.
> >
> > Uh, correct me if I'm wrong, but AFAICR Jules removed the user-prefs
> > setting entirely. So unless you have the link in place you will not
> > get those settings spam.assassin.prefs.conf/mailscanner.cf at all (and
> > this would imply no "double-parsing" happening). One might say that
> > the name spam.assassin.prefs.conf is a real mis-nomer now:-).
>
> Actually, you appear to be right.
Don't sound so surprised, it actually happens from time to time:-D.

> I guess he just linked it to support folks who are used to editing
> spam.assassin.prefs.conf.

IIRC from the Changelog (that I'm way too lazy to go look at:), that
is exactly it.

Cheers
-- 
-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se