On 08 March 2002, Craig Hughes said:
> I think for this setup, where most of the addresses are not mapped in
> /etc/passwd (and so have no ~ directory), you should look at storing the
> configurations in a database and use the SQL stuff.
Blech. I don't want to have to run a big hairy database just so I can
put SA config stuff somewhere. The filesystem is a perfectly good
database for many applications, and I so no reason why I should load
this machine down with yet more semi-relevant software. It's supposed
to be a mail server -- that's it.
(Yes, I realize lots of mail servers do need industrial strength
databases. Good for them. If I were an ISP with X thousand users, I'd
probably look into this. But I'm not.)
> If nothing else, it'll
> make your exim/python/whatever code easier to write, since you can just
> invoke spamc with the address, and not have to do the
> address->configlocation lookup in your own code.
I very much doubt that that lookup would be anything more complicated
than
spamc -C /etc/spamassassin/config-$domain/$local_part
(assuming a hypothetical -C option to specify an alternate
user_prefs-like file), which is a heck of a lot easier than selecting,
installing, maintaining, and updating a relational database.
> Another option would be to
> just create those ~100 users in /etc/passwd and give them home directories,
> and set their login shells to /bin/false, uid/gid to be the same as user
> nobody or something, and then just use the standard user_prefs location.
That sounds like almost as much fun as selecting, installing,
maintaining, and updating a relational database. No thanks.
Greg
--
Greg Ward - software developer [EMAIL PROTECTED]
MEMS Exchange http://www.mems-exchange.org
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
