The HIERARCH.PM file maintains the folder structure. It is written to
each time you a change in the folder structure and each time you close Pegasus
regardless of whether you made any folder changes.
When you first
add a mailbox to your folder list any existing folder files are read
into HIERARCH.PM. The structure of any nested folders (folders within
trays) can not be discerned during this process so any folder structure gets flattened. This sounds like what is happening
to you. The HIERARCH.PM file relies on unique folder ID's which are
assigned when a folder is created. The "add mailbox" function is
designed to provide access to a different users mailbox or an archived mail directory so I
wonder if the unique folder ID function does not behave properly when
trying to create a mailbox using the "add mailbox" function. I say that because a tired folder structure is maintained in my test with another users mailbox added to my folder list.
As
for how the folder structure of added mailboxes is recorded in
HIERARCH.PM, the structure is recorded differently depending on whether
the added mailbox is connected or disconnected at the time Pegasus Mail
is closed. If connected, the folder structure should be recorded in
HIERARCH.PM based on the unique folder ID and restored when Pegasus Mail
is opened. If disconnected, the folder ID reference entries are left
in HIERARCH.PM however without an associated folder name. Pegasus
attempts to use these entries to restore the folder structure the next
time that mailbox is added, again, based on the folder id's. You might test these actions to see if either one maintains the
structure. One thing I don't know is how the folder structure is retained if you connect,
modify, disconnect then reconnect an added mailbox during the same
session of Pegasus Mail.
Like Guy, I am also curious why you are opting to add a mailbox rather utilize trays and folders within "My Mailbox".
<p>The HIERARCH.PM file maintains the folder structure.&nbsp; It is written to
each time you a change in the folder structure and each time you close Pegasus
regardless of whether you made any folder changes.</p><p>When you first
add a mailbox to your folder list any existing folder files are read
into HIERARCH.PM.&nbsp; The structure of any nested folders (folders within
trays) can not be discerned during this process so any folder structure gets flattened.&nbsp; This sounds like what is happening
to you.&nbsp; The HIERARCH.PM file relies on unique folder ID's which are
assigned when a folder is created.&nbsp;&nbsp; The "add mailbox" function is
designed to provide access to a different users mailbox or an archived mail directory so I
wonder if the unique folder ID function does not behave properly when
trying to create a mailbox using the "add mailbox" function.&nbsp; I say that because a tired folder structure is maintained in my test with another users mailbox added to my folder list.
</p><p>As
for how the folder structure of added mailboxes is recorded in
HIERARCH.PM, the structure is recorded differently depending on whether
the added mailbox is connected or disconnected at the time Pegasus Mail
is closed.&nbsp; If connected, the folder structure should be recorded in
HIERARCH.PM based on the unique folder ID and restored when Pegasus Mail
is opened.&nbsp; If disconnected, the folder ID reference entries are left
in HIERARCH.PM however without an associated folder name.&nbsp; Pegasus
attempts to use these entries to restore the folder structure the next
time that mailbox is added, again, based on the folder id's.&nbsp; You might test these actions to see if either one maintains the
structure.&nbsp; One thing I don't know is how the folder structure is retained if you connect,
modify, disconnect then reconnect an added mailbox during the same
session of Pegasus Mail.</p>Like Guy, I am also curious why you are opting to add a mailbox rather utilize trays and folders within "My Mailbox".&nbsp;
