Community Discussions and Support
cleaning up Hierarch.pm

Thanks; I'll give that a try.

 

<p>Thanks; I'll give that a try.</p><p> </p>

I've used Pegasus for about a decade, and due to the very large volume of email and folder is contains, I've always installed new versions in place, instead of clean installs.

All this is fine, except my Hierarch.pm currently has 1432 lines in it, with ~400 ending in Name_Unavailable.

One consequence of this is, I suspect the long delay in event pmail crashes and has to restore the folder list/hierarchy at the next startup.

So: is there an established guide to thinning out the junk in hierarch.pm? I realize of course it needs a plain text editor, but what can I safely delete?

I suspect this is not a new question, so feel free to point me to an existing thread.

 

tnx!

 

<p>I've used Pegasus for about a decade, and due to the very large volume of email and folder is contains, I've always installed new versions in place, instead of clean installs.</p><p>All this is fine, except my Hierarch.pm currently has 1432 lines in it, with ~400 ending in Name_Unavailable.</p><p>One consequence of this is, I suspect the long delay in event pmail crashes and has to restore the folder list/hierarchy at the next startup.</p><p>So: is there an established guide to thinning out the junk in hierarch.pm? I realize of course it needs a plain text editor, but what can I safely delete?</p><p>I suspect this is not a new question, so feel free to point me to an existing thread. </p><p> </p><p>tnx!</p><p> </p>

One way is to "delete" the hierarch.pm file and manually rebuild the tray\folder structure.

If you have "Filing trays" it is is more complex.
If the "Message folders" do not have unique names it is even more complex.
The "Filing trays" are only defined in hierarch.pm file.
If you rename hierarch.pm to hierarch.bak and start Pegasus, a clean  hierarch.pm file will be created.

This:
+ filingTray01
| + messageFolder01
| \ messageFolder02
\ filingTray02
  + messageFolder01
  \ messageFolder02

Becomes:
messageFolder01
messageFolder01
messageFolder02
messageFolder02

However the "Filing trays" will need be manually recreated, then the "Message folders" may be appropriately relocated.

 

<P>One way is to "delete" the hierarch.pm file and manually rebuild the tray\folder structure.</P> <P>If you have "Filing trays" it is is more complex. If the "Message folders" do not have unique names it is even more complex. The "Filing trays" are only defined in hierarch.pm file. If you rename hierarch.pm to hierarch.bak and start Pegasus, a clean  hierarch.pm file will be created.</P> <P>This: + filingTray01 | + messageFolder01 | \ messageFolder02 \ filingTray02   + messageFolder01   \ messageFolder02</P> <P>Becomes: messageFolder01 messageFolder01 messageFolder02 messageFolder02</P> <P>However the "Filing trays" will need be manually recreated, then the "Message folders" may be appropriately relocated.</P> <P mce_keep="true"> </P>

Thanks, but I've got

several hundred folders and a few dozen trays (this is a decade's worth

of email), so if there's a way to clean up rather than re-build that

would be easier.

Cleanup doesn't have to get rid of every last unneeded entry in the file; a general housekeeping would be good enough.

 

 

<p>Thanks, but I've got several hundred folders and a few dozen trays (this is a decade's worth of email), so if there's a way to clean up rather than re-build that would be easier.</p><p>Cleanup doesn't have to get rid of every last unneeded entry in the file; a general housekeeping would be good enough.</p><p> </p><p> </p>

You can delete all 'name_unavailable' entries.  Be aware that 'name_unavailable' entries maintain the structures created in added mailboxes which have been disconnected.  They get reused when that mailbox gets added again.  Deleted entries will be recreated the next time the mailbox is added but any previously created structure will be lost.

Work with the hierarch.pm file only while Pegasus Mail is closed or work on a copy.  Be sure to backup/maintain your original so you can restore it just in case.


<p>You can delete all 'name_unavailable' entries.  Be aware that 'name_unavailable' entries maintain the structures created in added mailboxes which have been disconnected.  They get reused when that mailbox gets added again.  Deleted entries will be recreated the next time the mailbox is added but any previously created structure will be lost. </p><p>Work with the hierarch.pm file only while Pegasus Mail is closed or work on a copy.  Be sure to backup/maintain your original so you can restore it just in case. </p><p> </p>
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