On Sat, 2002-10-12 at 05:19, Eric Renfro wrote: > 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. ;) > >
The forwards table isn't necessary, the aliases table can take non-local addresses as arguments to the deliver_to field. > 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. > -dfp are the options I use for dbmail-maintenance > 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: > Those #'s are really really old, like around RC-1 timeframe, so most of them are probably gonna be in 1.0 > AUTH methods, such as CRAM-MD5 and DIGEST-MD5, will they be supported? > (preferably without SASL getting in the way? <G>) Well, the latest draft of the IMAP rfc has wording REQUIRING some form of encrypted auth mechanism, or plaintext auth over SSL, which was an IETF requirement. So I'd say that will be on the TODO list, but dunno how soon.
