Hi Janos, Thanks for your response. To clarify, I think what the customer is looking for, is to be able to search the archive for e-mails that have been placed in the public store. The e-mail may have been placed in the public store by a different user, therefore the searching user should be able to see other users' e-mails that have been "made public" - but not other users' private e-mails.
I appreciate that this is a tricky one, they are used to the Folder View in Outlook, so that is how they are currently envisaging an archive working. Would it be possible, for instance, to target a specific folder with the pilerimport utility, and then "tag" all the e-mails imported in this way, as belonging to a certain e-mail address (in this case, a distribution list maybe) in order that everyone can view them? I know ultimately the e-mails will be archived, and therefore safe, as all inbound e-mails will be archived - however the trick here is going to be allowing access to the messages. Thanks Adam -----Original Message----- From: Janos SUTO [mailto:[email protected]] Sent: 03 June 2014 12:17 To: [email protected] Subject: Re: piler and public folders Hello Adam, On 2014-06-03 12:54, Adam Camp wrote: > --snip-- > > Therefore, I'm asking, how would we go about archiving the messages in > the public store? It's possible that some of the sub-folders have > restrictions, but I believe these are just write restrictions, not > read restrictions (which obviously won't affect archiving). I'm > guessing that perhaps this would take the form of an IMAP import > targeting the public store, run as a cron job? And let the original > copies of the e-mails stay in the users archives as deduplication will > step in here? > well, piler knows nothing about folders, it knows only email addresses. So no matter what permissions a user has on the shared folder with his mail application (let's assume Outlook for now) piler gives him access to only those emails he sent or received based on the email address in the email headers, eg. From, To and Cc. If your customer had Exchange for instance, then the piler gui could assemble a list of emails that the given user is associated with including distribution lists, then apply this as a filter to restrict him to his own emails only. With Exchange I think you may not need to handle the shared folder in regard of email archiving, since Exchange can pass a copy of each received email to piler no matter how it will process it later. Janos
