Can you create a 'dummy' mailbox without creating a 'dummy' mailbox?

[irbk]

Long story short my company is starting to work on a project that could be very litigious. This is just one of many projects that people are working on and many people are working on this one project. The project manager would like a dummy account set up in exchange that everyone in the project could CC when they send an e-mail, that way if litigation ever comes up about what was sent, there was a single location the project manager could go to get all the e-mail that was sent (assuming that everyone on the project always cc'ed this dummy account with every e-mail they sent for the project). It's a reasonable enough request.
However, my worry is creating a "dummy" account that's not actually used by a user. It's taking up space on the server, taking up licences, and I'm sure that IT won't be informed when the project is over so we will have this "dummy" account sitting on the server forever. Not to mention that if we do this for one project manager, other people are going to want individual "dummy" accounts set up for all their projects because it's easier to trust that all the project e-mail is getting into the dummy account then actually managing your inbox.
So, what I would really like is a way to satisfy both worlds. A way to have a "dummy" mailbox that could be CC'ed for all the project related e-mails but not creating an actual user on my network.
Any suggestions on what to do in this situation? We have Exchange 2010.
Thanks in advance.

 

[baddos]

I would probably just create the dummy mailbox and then archive it to a .PST file after the project is complete. Exchange license shouldn't be affect because there wouldn't be an additional client accessing it, but possible any exchange addons you have might have their licensing affected.

If you feel this is a usefull feature and are afraid other project manager will run with it, maybe you should look at some kind of ediscovery archive solutions.

 

[irbk]

Thanks for the reply.
It's not a bad idea except for the fact that this isn't a short term project. It will run for several years. By the time it's actually complete no one will tell us that the project is complete so we will have a "dead" mailbox (meaning that no one is accessing it) consisting of several gig of data (if not more, my users LOVE to e-mail HUGE documents). Again, I don't want mailboxes on my server that are not actual mailboxes. The fact that my Backup Exec user now needs a mailbox since this latest version of Backup Exec ticks me off to no end.
As for the ediscovery archive suggestion.... well that would require my company spending money. Not even worth asking about. My company is so tight if you so much as roll a piece of coal through the accounting department, it's a diamond when it comes out the other side.