On 2014-06-03 14:08, Adam Camp wrote:
So we can't run pilerimport against that folder, logged in as (for instance) the mail administrator account (not used in production for e-mails) - then import all e-mails from the folder into piler based on that admin e-mail address as well as the address it was originally sent to, then allowing all users to search e-mails archived under that user account?
a similar approach may work out. I'll hack the pilerimport utility to add a new option, eg. -R <shared-folder@company>, then piler adds this as an extra address to the email. Then one more task to do: have all users to be in a group allowed to access this artificial email. Perhaps it could be more easily done by creating a distribution list in Active Directory, and make sure everyone is member of it.
By checking headers, are you thinking that maybe headers are added when the e-mail is moved to the public folder?
yes, that's my idea, but I'm not sure if it really works that way. Janos
