Hello guys,
Wel, i've read about 12 million posts and websites about the infamous "shared mailbox, sent items" issue. To clarify, the issue is as follows:
You have 2 mailboxes (Let's say: your own my.name@mycompany.com as your primary mail, and your department mailbox mydepartment@mycompany.com as a shared mailbox between you and your department colleagues. Items you sent out with the mail address mydepartment@mycompany.com, do not (as you would expect) get delivered into the Sent Items folder of the My Department mailbox, but in the Sent Items folder of my own mailbox. Ok. So i'm running into this same issue. The reason i've decided to throw up a post here, is because this is rather important in our municipality to achieve (if it were only for a traceback of the mailflow when someone is on a holiday, and you do not have any recount whether or not there was response on a certain mail by someone else).
So, after reading up and searching the web for about a week now, i have to conclude there is only one 'real' response so far: KB 970944, a (not supported) hotfix, followed by a registry entry. So, i went this route, installed the hotfix on some systems (Windows 7, Outlook 2007, fully patched through WSUS), and started testing. Strangely enough, the fix does quite simply: nothing for us. It doesn't work. I checked the patch, i doublechecked, i checked the registry entry, etc... but i cannot get it to work somehow.
I'm stumbling upon this problem quite a bit, and i'm always seeing the same responses:
- 'create a rule', which is not the most elegant solution, and it seems a 'condition' to check on outgoing mail account quite simply isn't available
- use a third-party program...
- KB970944 and a registry change (Windows 7 x32, Outlook 2007 SP2) ... not supported by MS, and indeed: in my case it doesn't work for whatever reason
So this made me wonder: Isn't it logical to 'assume' a sent item from another mailbox is getting delivered into the corresponding mailbox's sent items? The same for deleted items btw. Is this "by design" for some reason, or are other quite important bits n' pieces playing some role here? Why is this issue getting fixed on the client side (Outlook) (with KB970944), and not on the server-side? Is someone else aware of some other 'elegant' solution for this matter. Thanks in advance,
Sven