Jonathan Ellis's submitted patch has raised an interesting question. Do we really need the second column/field in any of the address databases; text, CDB and DBM?
Quite frankly, I think it's confusing to see this in my filter file: from-file ~/.tmda/lists/whitelist accept and then keep some addresses in that file where I bounce or drop or confirm. A better solution, from the documentation standpoint at the very least, would be to move those addresses to a separate file and use a second from-file rule in the filter to drop/bounce/confirm all of them. Essentially, we don't lose any functionality that can't be accomplished by an additional file or two, the code gets a little simpler because we never have to worry about the second field and filters become a little more self-documenting. On the other hand, users may have lots of these overrides and we may create significant work for them just because they upgraded TMDA (maybe we should add a SURPRISE file, in addition to UPGRADE...). Personally, I'd like to see this feature go away, but perhaps it could be staged. We could support it, but if we find an override, we could log it to the debug log as deprecated and not supported in versions after .70, or something like that. That would give people time to fix their files without simply forcing it on them NOW. In any case, any discussion on this would be appreciated. Tim _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
