Well, after hammering, and hammering away with dbmail, after 1.0rc4's release, I plucked it right into my exim configuration, and so far, all but a few lacking custom "extensions" of my own, namely a domains table storing domain types for local and relays linked to the client_idnr, and another custom table, forwards, allowing users to setup forwards to other non-local email addresses, I have a pretty solid-apearing dbmail setup.
Getting it to work, in it's basics, was actually fairly easy too, after doing some hunting around and re-remembering how to do a few tricks of mine. ;) Now, I have a more sophisticated feeling email server, using the following: exim, exiscan, spamassassin, sophos, postgresql, and openldap (now, only until I change the SMTP AUTH mechanisms to use dbmail's user table.) I've been trying to setup a very decently well ballenced mail server, with spam blocking, and only today, have I finally managed to accomplish this much. (Though, yet, I have only stress tested it, but haven't seen any spam come in to see if it holds up yet, <G>) Anyway. I wanted to start off with a thanks to the authors of dbmail, for taking the time to build something like this. It makes a lot of sense to use a database server for mail storage. I'd been using Maildir for quite some time, and it's extremely annoying to manage, especially with virtual domains with virtual users. Second. I wanted to know how would be a good routine for nightly maintenance with dbmail-maintenance. What command-line options should I use, to perform a nightly dbmail routine? I'm using my own program, pgmaint, to schedule nightly vacuum jobs, since my PostgreSQL server is strictly auth based. And then some future goals/questions? With the numbers on dbmail.org on the status of the project being 99% in just about everything, I doubt some of these will be included in the final 1.0 release, but I wanted to ask about them: AUTH methods, such as CRAM-MD5 and DIGEST-MD5, will they be supported? (preferably without SASL getting in the way? <G>) Regarding the domains table I mentioned earlier, creation of the domains in a rowset similar to: domain_idnr, domain, client_idnr, (and optional: type, being for possible "local" or "relay") For letting the MTA do it's portion of the job. Bouncing, or denying during delivery attempt, instead of plain bouncing. And lastly. Everytime I kill dbmail-imapd, (not sure if dbmail-pop3d does the same, yet. I'm scared to try, so far), it literally starts to consume all the RAM of my system, until it just crashes it to almost a dead halt. I'm using "killall dbmail-imapd" to stop it, until I make a gentoo-style init script for it, but I can't see that dbmail-imapd is dropping a pid file down anywhere. Eric Renfro
