Hello, A few more comments/responses to your questions:
There are numerous options for copying, which you should find in the documentation you've been searching. Imap->imap is a common way, though you do have to know (or temporarily change) the account passwords. You could do imap->dbmail-smtp (eg. I think fetchmail can do that, and probably other tools). If you have a large amount of mail to move, it would probably be faster to do so directly from the filesystem level of the remote mail server, if that's accessible (using something like mailbox2dbmail you mentioned). The poorly named dbmail-smtp (more recenctly renamed dbmail-inject) does not talk smtp, it takes a single message as stdin and stores it in the database. Check the manpage for the format, I think it's just mbox (if not, you just remove the "From " line 1 from mbox format to send it a raw message). If you wanted something you can talk smtp to, use dbmail-lmtp (it of course talks lmtp, but does what you need for delivery). Performance is better than spawning lots of processes/connections with dbmail-smtp, but I don't think you can specify a mailbox to store to, everything goes to INBOX (though I may be mistaken there). You could probably have a custom migration script fiddle with sieve scripts on the backend to work around that, if it's worth the effort (imap->imap would be less work). -- Jesse Norell Kentec Communications, Inc. [email protected] _______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
