[quote user="PaulW"]
I've never had a problem with this over many versions. Are you remembering to disconnect the mailbox after use?[/quote]
Yes I did disconnect. However, even if not it should not end up in a fatal problem.
[quote user="PaulW"] The drive letters change all the time with my setup and I don't have any problem adding the mailbox again from any computer.
Perhaps if you give exact details of how to reproduce your error it may be clearer what is happening.
[/quote]
Well I did so many things with slight differences but here's one typical instance:
1) Add mailbox to list and set a directory eg. E:\test
2) Create a folder in the new mailbox and copy a bunch of messages from one folder into it.
3) Disconnect from the mailbox
4) Reconnect - ok. Disconnect again
One of my tests was to then move the folder from one place to another: So from E:\test I might make a folder on d:\test2 and copy the files into it.
5) Try to connect to d:\test2 - mailbox is empty.
6) go back and try to connect to e:\test - still ok.
7) Use PMRestArch.exe to copy from e:\test to d:\test2
8) connect to d:\test2 - still empty
9) connect to e:\test - now that's empty.
I've found without using PMRestArch.exe at all that I can't move the files anywhere else but where they were saved. The moment I do they no longer appear to contain anything. On some instances using PMRestArch.exe actually worked but this seems intermittent and eventually doing a few more moves resulted in the same scenario.
It's unclear what triggerss the original file/location to fail but it seems to happen in the process of playing with PMRestArch.exe but I can't be absolutely sure. Most of my tests were similar to the above. But it soon became clear to me that I can't trust this method because for me I can recreate this problem every single time.
The same archive can be connected to as long as I put into a folder called pmail. This can be anywhere and I have to connect to it as a different user. In the above case the user would be test or test2. It's inconvenient but at least it shows there's nothing wrong with the archive itself, just the "add mailbox" archiving method.
The only thing I have not tried is to test this on a separate computer just in case I've got some kind of problem with any external dependant files if Pegasus uses them - which I have no idea.
[quote user="PaulW"]
<P>I've never had a problem with this over many versions.&nbsp; Are you remembering to disconnect the mailbox after use?[/quote]</P>
<P>Yes I did disconnect. However, even if not it should not end up in a fatal problem.</P>
<P>[quote user="PaulW"] The drive letters change all the time with my setup and I don't&nbsp;have any problem&nbsp;adding the mailbox again from any computer.</P>
<P mce_keep="true">Perhaps if you give exact details of how to reproduce your error it may be clearer what is happening.</P>
<P>[/quote]</P>
<P>Well I did so many things with slight differences but here's one typical instance:</P>
<P>1) Add mailbox to list and set a directory eg. E:\test</P>
<P>2) Create a folder in the new mailbox and copy a bunch of messages from one folder into it.</P>
<P>3) Disconnect from the mailbox</P>
<P>4) Reconnect&nbsp;- &nbsp;ok. Disconnect again</P>
<P>One of my tests was to then move the folder from one place to another: So from E:\test I might make a folder on d:\test2 and copy the files into it.</P>
<P>5) Try to connect to d:\test2 - mailbox is empty.</P>
<P>6) go back and try to connect to e:\test - still ok.</P>
<P>7) Use&nbsp; PMRestArch.exe&nbsp; to copy from e:\test to d:\test2</P>
<P>8) connect to d:\test2 - still empty</P>
<P>9) connect to e:\test - now that's empty.</P>
<P>I've found without using&nbsp; PMRestArch.exe&nbsp; at all that I can't move the files anywhere else but where they were saved. The moment I do they no longer appear to contain anything. On some instances using&nbsp; PMRestArch.exe actually worked but this seems intermittent and eventually doing a few more moves resulted in the same scenario.</P>
<P>It's unclear what triggerss the original file/location&nbsp;to fail but it seems to happen in the process of playing with&nbsp; PMRestArch.exe&nbsp; but I can't be absolutely sure. Most of my tests were similar to the above. But it soon became clear to me that I can't trust this method because for me I can recreate this problem every single time.</P>
<P>The same archive can be connected to as long as I put into a folder called pmail. This can be anywhere and I have to connect to it as a different user. In the above case the user would be test or test2. It's inconvenient but at least it shows there's nothing wrong with the archive itself, just the "add mailbox" archiving method.</P>
<P>The only thing I have not tried is to test this on a separate computer just in case I've got some kind of problem with any external dependant files if Pegasus uses them - which I have no idea.</P>