Just created an own public folder structure. To avoid that every user is seeing the entire expanded public folder structure every time he starts Peg I have created only one main folder under the public tree head but with a lot of subfolders under the first main folder. This subfolder structure could be collapsed and keeps collapsed also after a restart. This avoids annoying of users which are not involved in working with those public folders.

But the main problem was the automatic new mail delivery of Mercury into one defined subfolder.

When creating the public folder/subfolder structure, Peg creates single file folders at your server file system (or where you've defined the location for saving) in the form folder.mai where the folder naming is always cryptic like S14DQYXS.MAI.

Now I have used one of that cryptic *.mai folder for the definition of the PUBLIC: alias in Mercury. And it works. Also with a deep path (I'm using e.g.: PUBLIC:E:\MERCURY\MAIL\public\public.MAI\S14DQYXS.MAI). Mercury is retrieving emails from our special public internet mail address as usual. But there is no local user defined where Mercury should drop the new mails. Instead of this Mercury has an alias for that address and drops the mails into the defined *.MAI folder.

Of course, you never will get a "new mail" notification. But public mail folders based on another concept other than ordinary mail account.

Hi,

Just playing arround with public folders for our Pmail users. Therefore I have create a new internet e-mail account which will be retrieved by Mercury regularly. Further, as described in manual, I have created a special Mercury alias in form  public@domain.com = PUBLIC:path_to_folder

A test has shown that Mercury is delivering emails adressed to public@domain.com into this folder. So far so good.

Now I have added a public folder structure to a Pmail account. When creating the public folder structure a path has to be set to the corresponding folder at the server where Mercury is delivering the mails to. But adding the public folder is creating the "public tree head" only. But where do the e-mails appear? Creating additional subfolders in the public tree structure do not have connections to a server path.

Has anybody an idea?