On Tue, Sep 25, 2007 at 10:18:24PM +0100, James (njan) Eaton-Lee wrote:
> Dan Shearer wrote:
>
> >However, there is something interesting here.
> >A set of Outlook-related utilities that worked with OpenChange utilities
> >would be useful to many.
> >
> >For example, a utility that can read mapidump data and generate MSG or
> >PST. In the realm of all-the-pieces-are-functional-today consider
> >libpst (http://alioth.debian.org/docman/view.php/30390/47/readpst.1.html
> >) which could be used to read a pst file and then upload it to a mailbox
> >on an Exchange server.
>
> Mighty useful. See exmerge, which is a commonly used tool for such
> things in exchangeland: http://support.microsoft.com/kb/174197
I don't yet understand why exmerge would come up in the context of PST
files:
* to achieve the stated goal of exmerge, OC offers
openchangemapidump and openchangemapirestore. They take mailboxes
from server X and put them on server Y. The only thing lacking is a
merge feature, but I can see that is important and should be
included. And while exmerge uses PST as an intermediate form,
mapidump uses a format you can manipulate with LDAP and SQL
commands.
* the reason (I suppose) PST file merging with Exchange inboxes is
for migrating on and off an Exchange server. However exmerge
doesn't seem to be able to do this. From the description it seems
only to be able to do server <-> server, although presumably you can
trick a two-stage merge by replacing the PST file at the right
moment.
So, if we can make sure that openchangemapidump/restore together are a
functional superset of exmerge, which they certainly should be, do you
see any extra value in exmerge with respect to PST files?
What I was proposing someone other than OpenChange wrote was an
Outlook-specific tool that will either pull down to PST or upload to
Exchange.
Have I missed something here?
--
Dan Shearer
[EMAIL PROTECTED]
_______________________________________________
devel mailing list
[email protected]
http://mailman.openchange.org/listinfo/devel
