> -----Original Message----- > From: glpi-dev-boun...@gna.org > [mailto:glpi-dev-boun...@gna.org] On Behalf Of Erich Iseli > Sent: Tuesday, December 15, 2009 2:49 PM > To: glpi-dev@gna.org > Subject: [Glpi-dev] Mail import from one mailbox into several entities > > Hello again, > > Our company is part of a big corporation and we are making > the support for several of its entities, which are in > different locations. There's only one helpdesk e-mail address > for all entities and the users all have e-mail addresses of > type "firstname.lastn...@company.com". Therefore: we have no > way to know, from the e-mail address alone, to which entity > the mail belongs. > > This is a big problem when importing e-mails into tickets: We > have to let them import into the root entity and have to move > them manually to the correct one. The only thing that might > make sense is make several rules in the root entity and tell > it to move tickets of users located in location X to be moved > to the entity X, tickets of users located in location Y to be > moved to the entity Y and so on. Unfortunately, there's no such thing: > "move to another entity" in the rules. > > On IRC, I was suggested to create a subfolder for every > entity on the mailserver and create a server-based mail-rule > to move them to the correct folder and download each folder > separately in the correct entity in GLPI. > Unfortunately that is not practicable, since the only thing > we have is the e-mail address of the user, and so we would > need to constantly create new rules for every single user as > the join the company or leave it. > > Before starting coding around, I wanted to hear from you guys > if there's another approach to this problem? Thanks for your feedback. > > A bientot, > > Erich aka ricky_ds > > _______________________________________________ > Glpi-dev mailing list > Glpi-dev@gna.org > https://mail.gna.org/listinfo/glpi-dev >
Not positive this would work, but what if you create "Entities" to match all the locations/entities that you need to support. From that you would need to associate a user with a particular entity. Then you may be able to place rules around the users and their assigned entity. I have not tried this since we keep everyone in one entity for support purposes since our IT is a shared service to many subs. Andrew _______________________________________________ Glpi-dev mailing list Glpi-dev@gna.org https://mail.gna.org/listinfo/glpi-dev
