Just to throw my two cents worth in here...
I found the
copying of the root \mail folder or individual mailbox folders to be a
tried and true method of moving configurations and mail between machines
or just locations on a hard drive. At least until the release of
v4.61. I don't blame v4.61 as I suspect an in place upgrade would have
worked fine but problems came up on two occasions when doing a clean
install of v4.61 then trying to use existing mailboxes. The one thing
both problem installs had in common is that the existing Pegasus Mail
installation had been around for many years so had gone through many
upgrades, ISP changes, numerous identities, etc. I assume that the long
history resulted in residual stuff left behind that v4.61 didn't like.
In both instances I ended up deleting the existing pmail.ini and state.pmj files from
each mailbox folder then reconfiguring Pegasus Mail for each pmail
users. I saved a copy of the files for backup purposes
and used the old pmail.ini file for reference during the reconfiguration.
Let me make two things clear. First, I am not advocating
not upgrading to v4.61. It has been great since I worked out the kinks
(although keeping up with the HTML renderer updates has been a bit of a
challenge). Second, I recommend the method of copying the
\mail folder from old to new. It's not fail safe however so be aware of that, especially if you have a long history with Pegasus Mail
and the old to new includes upgrading to v4.61. It's also easy enough to
undo which makes it worth a try.
One other note: If you use a CD to transfer the \mail folder make sure the files are not flagged read only after copying them off of the CD.
<p>Just to throw my two cents worth in here...</p><p>&nbsp;I found the
copying of the root \mail folder or individual mailbox folders to be a
tried and true method of moving configurations and mail between machines
or just locations on a hard drive.&nbsp; At least until the release of
v4.61.&nbsp; I don't blame v4.61 as I suspect an in place upgrade would have
worked fine but problems came up on two occasions when doing a clean
install of v4.61 then trying to use existing mailboxes.&nbsp; The one thing
both problem installs had in common is that the existing Pegasus Mail
installation had been around for many years so had gone through many
upgrades, ISP changes, numerous identities, etc.&nbsp; I assume that the long
history resulted in residual stuff left behind that v4.61 didn't like.&nbsp;
In both instances I ended up deleting the existing pmail.ini and state.pmj files from
each mailbox folder then reconfiguring Pegasus Mail for each pmail
users.&nbsp; I saved a copy of the files for backup purposes
and used the old pmail.ini file for reference during the reconfiguration.
</p><p>&nbsp;Let me make two things clear.&nbsp; First, I am not advocating
not upgrading to v4.61.&nbsp; It has been great since I worked out the kinks
(although keeping up with the HTML renderer updates has been a bit of a
challenge).&nbsp; Second, I recommend the method of copying the
\mail folder from old to new.&nbsp; It's not fail safe however so be aware of that, especially if you have a long history with Pegasus Mail
and the old to new includes upgrading to v4.61.&nbsp; It's also easy enough to
undo which makes it worth a try.</p><p>One other note:&nbsp; If you use a CD to transfer the \mail folder make sure the files are not flagged read only after copying them off of the CD.
</p><p>
</p>