On Tue, Jan 30, 2007 at 02:36:18PM -0500, Daryl C. W. O'Shea wrote: > [copying Theo... I'm not sure if --channel and --channelfile not being > compatible is intended]
I believe the idea there was that if you use the commandline options, you don't want the default channel. I don't think there's a reason to not allow both options though, just that if you're going to have a channel file, why bother also stating things on the commandline? > ...it looks like you'll have to add the updates.spamassassin.org to your > channel file, like I suggested before, rather than adding it as a > --channel parameter on the command line. +1 > The POD doesn't make it clear that --channel and --channelfile aren't > compatible. I'm not sure if Theo intended this -- other than that it's > a messy way to have your config, I don't see a problem with both being > used. Theo? Feel free to open a bug about it. I think the general idea is "if either channel or channelfile is specified, remove the default channel listing, then continue", which isn't a hard change to make. I figure we're going to want to do a 3.1.8 release at some point here in the future (only 1 of the bugs so far really makes it worthwhile), so we could update and then backport 3.2's sa-update which is mostly the same but has some different internals. -- Randomly Selected Tagline: "Well, last time I checked, I wasn't a trout ..." - rei.com radio ad
pgpKsJYPPaH4F.pgp
Description: PGP signature
