On 6/30/05 5:39 PM, "Elliot F" <[EMAIL PROTECTED]> wrote: > Another method (and a very scalable one) would be to store user data in DNS. > If you've got your user data in some sort of store (DB/LDAP/whatever), it > would be fairly easily to export it to a zone (bind/tinydns) file. You could > then create a subdomain for the domain (users.example.com) with valid users as > further subdomains (jdoe.users.example.com, with a TXT record storing their > mail server?) You could use hesiod for that matter. It could take advantage > of the caching architecture that DNS has, and you would simply need to > restrict access by IP. It'd probably be the fastest/most scalable way to do > it, I think.
This is, loosely speaking, what I do. I don't get to do the per-user type of config as it would be lost with the admins maintaining aliases and such, so I do a per domain config with records in tucked in there to clue me for how their SA/etc. filters are to be handled or tuned. I run full-boat 9.3.1 as a caching nameserver on the systems. In both my config database as well as the plethora of lookups that happen as a product of SA, dnsbl, uribl and such I can't say that I've ever had an issue with it as a database. The potential problem I'm going to have to face at some point is how to turn off a domain through my domain-agnostic filters. If the records are in DNS, I'll take, filter and requeue the mail. At some point there will need to be a key or something in there. Anyway, I find this thread interesting because with each release I'm left to scan all the plugins for the various changes so I can stitch in my dynamic configuration data. Just between 0.28 and 0.29 and now on to current I see that some of my "custom" fields are becoming somewhat standard. Thanks all,
