[quote user="edg"]

Thanks Thomas. I understood your explanation of how it currently works and how to avoid it for now.

I just noticed  there is a "suggestions  and wishlists" section in this forum. Should I add an improvement request entry there... or is that even used by David and his team?

[/quote]

Not sure if it's used at all, it's the one forum I never look at though.  You certainly can add this if you wish but I do not know if David even looks at the forum either. 

I have just noticed an odd behavior of the interactive copies to self feature on my setup. I am using Pegasus 4.41

I have lots of folders and sub-folders (over 300 I believe) to help me organize my mail. I have pegasus configured to use interactive copies to self and prompt me regarding which folder to save the messages to whenever I send a mail message.

The strange thing is that it  is getting mixed up about which folder they end up in.

A specific example is:

I send a mail message and (interactively) save a copy to a folder named "misc" which is contained in a filing tray named "Tray1" (for example).
When I look for that saved message, I find it in a completely different folder named "Misc" which is contained in a different filing tray named "Tray 2".

Yikes!

When I look at the folders information, they both have unique names. I can move messages into each of these folders (drag and drop) and they properly stay there. But the copies to self doesn't seem to work right.

I have only noticed it with similarly named folders (ignoring case).

 Any ideas?

 

Copy self goes by folder name only, the trays are not a part of the name.  You reallt need to use unique folder names.  I would recommend that you add the name of the tray to the folder something like tray_misc.

Ouch...

hmmm... I explicitly and interactively selected a folder from within a tray and asked my copy to go there, and it did not.
Somone, please tell me this is considered a bug.

[quote user="edg"]

Ouch...

hmmm... I explicitly and interactively selected a folder from within a tray and asked my copy to go there, and it did not.
Somone, please tell me this is considered a bug.

[/quote]

Nope, by design the copy self uses the folder name since this folder will be created if it does not exist.  Since it uses the name, it will put the mail into the first folder it finds. You should not be using the same folder name in different trays since the tray only exists in the hierarch.pm and it it ever gets trashed for any reason at all you'll have a mess on you hands trying to rebuild it.

This may change in the future if the program is changed to require the user to manually create all folders.

 
Ok, let me rephrase. I believe you if you say it was done this way on purpose.

 
I disagree with you if you think this behavior is somehow "ok."  It is also unrelated to whether the program creates the folder for you when it does not exist. In my case, it existed and the UI showed me a tree of all possible folders to copy my mail to, but when I selected it, it did not copy it there it went somewhere else. You must be thinking of another use case. 

Providing functions which don't do what the user asks them to do (amd what the user interface gives every indication of doing) and possibly setting them up for future failure is not good.

It seems to me that it should either:

(a) prevent users from creating folders with the same name if they are not allowed especially if doing so will cause problems later

or

(b) allow this and fully support this behavior. 

 
Don't get me wrong. I am not complaining about Pegasus overall -- I have been using it for 10 years now. I just want to provide feedback on a behavior that seems wrong, in hopes that the developer will look at this and address it in future
 

Did not say it was "ok" or not.  You were given the explanation about why it happens and how to keep it from sending the mail to the wrong folder. You simply cannot have folders of the same name and expect the copyself to put the mail into the correct folder.

I do not know if this is going to be changed but if it is it will require a basic change in the program operation and the last I heard it was not to be changed.  It certainly has not been changed in the closed beta I'm using and so I do not expect that the next version will treat this any differently.

Thanks Thomas. I understood your explanation of how it currently works and how to avoid it for now.

I just noticed  there is a "suggestions  and wishlists" section in this forum. Should I add an improvement request entry there... or is that even used by David and his team?