> I have an existing mail server running pop3, smtp, and imap. I have  
> around 40
> domains to transfer. The most users per domain would be around 70. I can
> get a dump of accounts and groups and build an sql import script  
> without trouble,
> but I could use so help migrating the mailbox's to dbmail. The mail  
> box format is
> not one you are probably familiar with (EIMS) so I would appreciate  
> any tips, like
> using some command line mail client to "clone" the mailbox's to the  
> dbmail by
> looping through a list of users subscribing to all mailbox's, and  
> then storing them
> all locally in some format that could be imported into dbmail, or  
> passed to postfix
> for delivery. I haven't done this before so I'm sure there are better  
> approaches.

  Do you have an imap daemon on your current system?  Try something like
imapsync if so.

> Once this is done I want to migrate away from squirrelmail to  
> something along the
> lines of what Erik is doing with SwiftMail. This functionality is why  
> I found dbmail
> in the first place. I would also build the webmail interface with php  
> but would like
> to do so in such a way that creating other front-ends would be  
> trivial. I'm open to
> working with someone on this if there are already some projects going  
> that have
> a roadmap compatible with my needs. This is off topic I'm sure but  
> this community
> seems small and I don't know where else to probe.

  There are plans to "officially" support python, I believe, but haven't
heard of anything for php.  A long time ago when we used to work on
weDBmail I started work on a generic api-like setup you could include
in other php programs, but A) it's not finished (not even close), B) it
was working towards adding postgres to the support, but no other rdbms
were even considered yet, C) I hadn't at all begun any dbmail version
stuff to support 1.x, 2.0, 2.2, etc., and D) I'm sure the whole thing
could benefit greatly from a ground-up redesign by someone who knows how
php is supposed to work.


> Also, could I drop the table that holds the user pass info and make  
> that a view?
> I haven't seen or heard any reason this wouldn't work but I haven't  
> been on the
> list all that long nor looked into dbmail in that kind of detail.

  Can you update a view?  That table (dbmail_users) has a few columns
that update regularly (last_login time, and quota usage).  If so, and
you handle all user creation yourself, I'd guess probably so.


-- 
Jesse Norell - [EMAIL PROTECTED]
Kentec Communications, Inc.

Reply via email to