On Fri, 26 Jul 2002 14:31:54 -0400 in message <[EMAIL PROTECTED]>, Chris Hilts <[EMAIL PROTECTED]> wrote: > eric wrote: > > > I have spamd, the spamassassin daemon running on port 3000. Spamd > > will always be using the dbmail username & prefs, but I'm not sure > > that that is really a problem. I may look to changing that so that > > you can use the sql storage for prefs for spamassassin. > > I've been looking at how to do this. I found instructions for making > spamc retrieve user preferences from a database, but it needs to have > the username passed to it on the command line.
That is a bit of a trick. Spamc's sql backend expects an 8 character username. For people running this as a full vurtual system (like me) that tends to be a bit of a pain. If you're just using it as a local mailer, then it's a lot easier to just pass in the local part on the command line. I can see a couple of ways to do this. 1) after alias resolution, use the user_idnr field as the username, but make it a varchar instead of a bigint. Then have the injector program call out if a flag is set on the account. 2) post processing by daemon/trigger. Using some extra fields in the message table, After delivery, have a daemon or trigger march over the newly delivered email and process it. (a trigger could just work on insert, a daemon could run on unprocessed messages every minute) I'm sorely tempted to do this for header parsing, since I have some apps where I'd like a richer set of headers for threading and other knowlege management types of stuff. > vacollections.com simply has dbmail as the transport in postfix. > birdbrained.org delivers to a unix mailbox as you'd normally expect with > postfix, but procmail then inserts it into dbmail. I'm going the > procmail route on birdbrained.org because I'm the only user on that > domain, and I am using procmail to filter into different IMAP folders > for me. If you're running simple domain setups, you could use procmail as your local delivery agent, and have it writer to dbmail as the delivery step. The systemwide default could just deliver directly, users of course could mess up their own delivery as they wish. > What I'd ultimately like to have is a mail system where I can have the > two domains running together, getting all incoming mail run through > spamassassin with database-stored/edited preferences, and delivered to > dbmail with mail sorting via database stored SIEVE rules. I'm looking for an arbitrary set of domains, [optionally] run through spamassassin, and dumped into dbmail with several apps hanging off of the back of the database for richer datamining than imap provides. And I want to get mailman running with this. On debian. On a system that is using the vserver kernel capabilities system. by tuesday. ;> Well, not really by tuesday, and most of the other stuff kind of works already. Except for mailman, which is having permission issues. eric
