Community Discussions and Support
Moving Home Mailbox to a Different Drive... Redux

[quote user="David Harris"]

I am working on a tool that will simplify the process of moving mailboxes around by doing all the necessary patching and file adjustment for you, but it won't be ready in time for v4.72. I wanted you to know that I'm aware of the issue though, and that there is a fix on the horizon.

[/quote]

Such a tool would be extremely useful indeed.

May I ask whether you plan to release it as a standalone utility or bundled in some future release of Pegasus mail?

Thanks in advance and all the best,

  Corrado

 

<p>[quote user="David Harris"] </p><p>I am working on a tool that will simplify the process of moving mailboxes around by doing all the necessary patching and file adjustment for you, but it won't be ready in time for v4.72. I wanted you to know that I'm aware of the issue though, and that there is a fix on the horizon. </p><p>[/quote]</p><p>Such a tool would be extremely useful indeed.</p><p>May I ask whether you plan to release it as a standalone utility or bundled in some future release of Pegasus mail?</p><p>Thanks in advance and all the best,</p><p>  Corrado</p><p> </p>

This topic/problem has a plethora of related posts attempting to explain/solve the difficult encountered in changing Home Mailbox Drive location.

In attempting this move I have discovered a couple of clues...

Win 7

Pegasus V4.71

Orig Folder Structure: C:\PMAIL\MAIL\ADMIN, etc.

  PMAIL.USR =  A;Admin;Mail Administrator

Manually moved all from C:\PMAIL\MAIL to K:\MY DOCS\DATA FILES\PMAIL\MAIL

Manually changed all Home Mailbox Locations in C:\PMAIL\MAIL\ADMIN\PMAIL.ini to the above K:\ path

Ran Pconfig32.exe making K:...\MAIL the Root Mailbox Directory

Running Pegasus results in being asked for & not accepting Username

Ho-hum - we know this place

Ran PConfig32 making C:\PMAIL\MAIL Root Mailbox Directory & place PMAIL.USR there

Running Pegasus now, "No Home Mailbox... Create?"  - Ans No

  then receive ERROR - Invalid Mailbox WARNING - Click OK

 HERE IT GETS INTERESTING

SPAMHALTER throws up a window: Failed to open database at

    C:\MY DOCS\DATA FILES\PMAIL\MAIL\words4.db3

     IT looks like Spamhalter has changed the drive K:\ to C:\ (there is no My Docs on C:)

 AND THEN

    When Pegasus opens, Help --> Info reveals:

     Home Mailbox Location ALSO shows C:\MY DOCS\DATA FILES\PMAIL\MAIL

     AND, in the Registry, HKEY_CURRENT_USER\Software\Pegasus Mail\Mailbox ALSO is C:\MY DOCS....

Is something in this spurious drive Letter substitution at the bottom of the perennial Drive Change Problem????  

Realizing that I've not gone about this in orthodox fashion... but, with every other setting seeming to have been correctly set resulting in Pegasus evidently looking in the wrong place for the USR file...    

 

Any thoughts / help appreciated.

Sorry for the double spaced lines????

==

Joshua


<p>This topic/problem has a plethora of related posts attempting to explain/solve the difficult encountered in changing Home Mailbox Drive location. </p><p>In attempting this move I have discovered a couple of clues...</p><p>Win 7</p><p>Pegasus V4.71</p><p>Orig Folder Structure: C:\PMAIL\MAIL\ADMIN, etc.</p><p>  PMAIL.USR =  A;Admin;Mail Administrator </p><p>Manually moved all from C:\PMAIL\MAIL to K:\MY DOCS\DATA FILES\PMAIL\MAIL</p><p>Manually changed all Home Mailbox Locations in C:\PMAIL\MAIL\ADMIN\PMAIL.ini to the above K:\ path</p><p>Ran Pconfig32.exe making K:...\MAIL the Root Mailbox Directory </p><p>Running Pegasus results in being asked for & not accepting Username</p><p>Ho-hum - we know this place </p><p>Ran PConfig32 making C:\PMAIL\MAIL Root Mailbox Directory & place PMAIL.USR there </p><p>Running Pegasus now, "No Home Mailbox... Create?"  - Ans No</p><p>  then receive ERROR - Invalid Mailbox WARNING - Click OK </p><blockquote><p> <i>HERE IT GETS INTERESTING</i></p><p>SPAMHALTER throws up a window: Failed to open database at</p><p>    C:\MY DOCS\DATA FILES\PMAIL\MAIL\words4.db3</p><p>     IT looks like Spamhalter has changed the drive K:\ to C:\ (there is no My Docs on C:)</p><p> <i>AND THEN</i></p><p>    When Pegasus opens, Help --> Info reveals:</p><p>     Home Mailbox Location ALSO shows C:\MY DOCS\DATA FILES\PMAIL\MAIL</p><p>     AND, in the Registry, HKEY_CURRENT_USER\Software\Pegasus Mail\Mailbox ALSO is C:\MY DOCS.... </p></blockquote><p><b>Is something in this spurious drive Letter substitution at the bottom of the perennial Drive Change Problem????  </b></p><p>Realizing that I've not gone about this in orthodox fashion... but, with every other setting<b> </b>seeming to have been correctly set resulting in Pegasus evidently looking in the wrong place for the USR file...<b>    </b></p><p> </p><p>Any thoughts / help appreciated.</p><p>Sorry for the double spaced lines???? </p><p>==</p><p>Joshua </p>

Make sure the paths in pconfig end with either "\~8" or "\~N".  These are substitutes for the Pegasus Mail username (mailbox directory name).  The ~8 works fine for usernames of up to 8 characters with the ~N  being for long usernames.


<p>Make sure the paths in pconfig end with either "\~8" or "\~N".  These are substitutes for the Pegasus Mail username (mailbox directory name).  The ~8 works fine for usernames of up to 8 characters with the ~N  being for long usernames.</p><p> </p>

Thanks, Brian, but always have appended with ~N.

But, this appears to miss the point which is that the DRIVE LETTER is being changed in the Registry (as shown earlier) & perhaps elsewhere, during the process.

 BTW, there is a problem with the new PCONFIG32.exe... the path et.al. can get mixed-up if a shorter path replaces the existing instruction.

 

==

Joshua

<p>Thanks, Brian, but always have appended with ~N.</p><p>But, this appears to miss the point which is that the DRIVE LETTER is being changed in the Registry (as shown earlier) & perhaps elsewhere, during the process.</p><p> BTW, there is a problem with the new PCONFIG32.exe... the path et.al. can get mixed-up if a shorter path replaces the existing instruction. </p><p> </p><p>==</p><p>Joshua </p>

[quote user="Joshua Ramsepm"]But, this appears to miss the point which is that the DRIVE LETTER is being changed in the Registry (as shown earlier) & perhaps elsewhere, during the process.[/quote]

What is happening is the HKEY_CURRENT_USER\Software\Pegasus Mail... registry keys get updated with the information from the most recently run instance of Pegasus Mail.  If you were to run an instance installed on C: and then run an instance installed on a USB stick you would see those keys change accordingly.

What I would try at this point is to rename PMAIL.CFG then run PCONFIG to create a new one.  I would then rename PMAIL.INI to force creation of a new one.  Do minimal configuration just to test.  If it works, finish configuring it and assume the old PMAIL.INI file is munged.  I know that this can be tedious if you have a number of identities but it may be less tedious than continuing to troubleshoot the current problem.  Tip: using the old PMAIL.INI file for reference during reconfiguration can be helpful.  Can you tell I've been here, done this? <G>

[quote user="Joshua Ramsepm"]BTW, there is a problem with the new PCONFIG32.exe... the path et.al. can get mixed-up if a shorter path replaces the existing instruction. [/quote]

I hope one of the beta testers picks up on this and pursues it.


&lt;p&gt;[quote user=&quot;Joshua Ramsepm&quot;]But, this appears to miss the point which is that the DRIVE LETTER is being changed in the Registry (as shown earlier) &amp;amp; perhaps elsewhere, during the process.[/quote]&lt;/p&gt;&lt;p&gt;What is happening is the HKEY_CURRENT_USER\Software\Pegasus Mail... registry keys get updated with the information from the most recently run instance of Pegasus Mail.&amp;nbsp; If you were to run an instance installed on C: and then run an instance installed on a USB stick you would see those keys change accordingly. &lt;/p&gt;&lt;p&gt;What I would try at this point is to rename PMAIL.CFG then run PCONFIG to create a new one.&amp;nbsp; I would then rename PMAIL.INI to force creation of a new one.&amp;nbsp; Do minimal configuration just to test.&amp;nbsp; If it works, finish configuring it and assume the old PMAIL.INI file is munged.&amp;nbsp; I know that this can be tedious if you have a number of identities but it may be less tedious than continuing to troubleshoot the current problem.&amp;nbsp; Tip: using the old PMAIL.INI file for reference during reconfiguration can be helpful.&amp;nbsp; Can you tell I&#039;ve been here, done this? &amp;lt;G&amp;gt; &lt;/p&gt;&lt;p&gt;[quote user=&quot;Joshua Ramsepm&quot;]BTW, there is a problem with the new PCONFIG32.exe... the path et.al. can get mixed-up if a shorter path replaces the existing instruction. [/quote]&lt;/p&gt;&lt;p&gt;I hope one of the beta testers picks up on this and pursues it. &lt;/p&gt;

[quote user="Joshua Ramsepm"]
BTW, there is a problem with the new PCONFIG32.exe... the path et.al. can get mixed-up if a shorter path replaces the existing instruction.
[/quote]

Just to let you know that this has been reported to me and I'm looking into it. There will be a v4.72 release in the next week or so, and there should be no reason why a fix for this couldn't be included there.

Cheers!

-- David --

[quote user=&quot;Joshua Ramsepm&quot;] BTW, there is a problem with the new PCONFIG32.exe... the path et.al. can get mixed-up if a shorter path replaces the existing instruction. [/quote] Just to let you know that this has been reported to me and I&#039;m looking into it. There will be a v4.72 release in the next week or so, and there should be no reason why a fix for this couldn&#039;t be included there. Cheers! -- David --

[quote user="David Harris"][quote user="Joshua Ramsepm"]
BTW, there is a problem with the new PCONFIG32.exe... the path et.al. can get mixed-up if a shorter path replaces the existing instruction.
[/quote]

Just to let you know that this has been reported to me and I'm looking into it. There will be a v4.72 release in the next week or so, and there should be no reason why a fix for this couldn't be included there.
[/quote]

I can't duplicate this problem here, which suggests that I'm not understanding exactly what you're reporting. Could you please mail me directly using my David.Harris@pmail.gen.nz address with a set of steps to duplicate what you're seeing?

-- David --

[quote user=&quot;David Harris&quot;][quote user=&quot;Joshua Ramsepm&quot;] BTW, there is a problem with the new PCONFIG32.exe... the path et.al. can get mixed-up if a shorter path replaces the existing instruction. [/quote] Just to let you know that this has been reported to me and I&#039;m looking into it. There will be a v4.72 release in the next week or so, and there should be no reason why a fix for this couldn&#039;t be included there. [/quote] I can&#039;t duplicate this problem here, which suggests that I&#039;m not understanding exactly what you&#039;re reporting. Could you please mail me directly using my David.Harris@pmail.gen.nz address with a set of steps to duplicate what you&#039;re seeing? -- David --

[quote user="Joshua Ramsepm"]

This topic/problem has a plethora of related posts attempting to explain/solve the difficult encountered in changing Home Mailbox Drive location.

[/quote]

Just to comment on the original posting topic... Moving the mailbox location in Pegasus Mail is not trivial, mostly for historical and legacy reasons (the program has been around for so long that there are a lot of these).

I am working on a tool that will simplify the process of moving mailboxes around by doing all the necessary patching and file adjustment for you, but it won't be ready in time for v4.72. I wanted you to know that I'm aware of the issue though, and that there is a fix on the horizon.

Cheers!

-- David --

[quote user=&quot;Joshua Ramsepm&quot;]&lt;p&gt;This topic/problem has a plethora of related posts attempting to explain/solve the difficult encountered in changing Home Mailbox Drive location. &lt;/p&gt;[/quote] Just to comment on the original posting topic... Moving the mailbox location in Pegasus Mail is not trivial, mostly for historical and legacy reasons (the program has been around for so long that there are a lot of these). I am working on a tool that will simplify the process of moving mailboxes around by doing all the necessary patching and file adjustment for you, but it won&#039;t be ready in time for v4.72. I wanted you to know that I&#039;m aware of the issue though, and that there is a fix on the horizon. Cheers! -- David --
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft