On Wed, Feb 09, 2005 at 09:35:57AM -0800, Justin Mason wrote: > Hold on -- something's just occurred to me from the SPF development; > this won't be possible, because BIND doesn't support bar.*.foo wildcards > (ie. wildcards in a non-lowest-level record.)
Yeah, we'd never want to do that anyway. You'd never do "2.*.3" to match all 3.y.2 versions. > We may have to have a way to explicitly mark wildcards. in other > words, do lookups like > > 1.0.3.updates.spamassassin.org > star.0.3.updates.spamassassin.org > star.3.updates.spamassassin.org > star.updates.spamassassin.org (possibly N/A) You don't lookup wildcards. It's up to the DNS server to resolve the specific query (1.0.3.updates.sa.org) from the data it has (use the specific RR if it exists, otherwise fall back to any appropriate wildcards). > What about just letting the rule file names be defined there? The issue is more of: using /etc/mail/spamassassin to create the channel.cf file (so SA automatically uses it), versus putting includes in local.cf where the admin could specify the loading order. The automatic method requires the files being named specifically so SA loads them in the right order, which requires knowledge of channel coupling, which ... It quickly snowballs into a large pain. -- Randomly Generated Tagline: Leela: Hold Still, I don't have good depth perception!
pgp1tEEMCqigO.pgp
Description: PGP signature
