[Update (2009-08-26): A hotfix package for the issue discussed in this article is now available from Microsoft. Please see this blog entry for details.]
Earlier today we have identified an issue with Lucatec® Mask that is apparently caused directly by changes in the latest Service Pack for Microsoft Office System 2007. The symptoms of this issue are that replies and forwards are no longer moved to the intended target folder after sending, i.e. they remain in the primary user’s Sent Items folder. Furthermore when looking at those items in that folder the sender will be shown as “[Current User] on behalf of [Intended Sender]” or even just “[Current User]” even if the “Send as” permissions have been correctly set up on the Exchange Server. According to our tests however it seems the sender information is only changed after the message has already been sent, so recipients will not notice any change.
We strongly recommend users of Lucatec® Mask to postpone installation of Service Pack 2 until a fix has been devised. See below for a partial workaround.
Resolving this issue is currently our top priority. We will update this article as new information becomes available.
This issue affects all versions of Lucatec® Mask since at least version 2.0.1 (released January 2007).
Update (2009-05-19): We have now implemented a workaround for the issue of items not being moved. Note that this does not fix the issue of inaccurate sender names in stored sent items. We are still researching how best to address this.
You can download a pre-release build of the upcoming next Service Release containing the fix (amongst others) from this link:
Lucatec® Mask 2.3.1 Code name “Cadillac” (Build 435)
(please see the release notes document included with the download for further details on changes in this release)
Update: (2009-05-26): We have now opened a support case with Microsoft about the changing sender information as we have also been able to reproduce this in environments that do not have Lucatec® Mask installed at all. We will post updates on the case to this blog as they become available.
Furthermore, this issue can occur in seemingly erratic patterns, i.e. some users might never notice this at all while for others it can happen for almost every single message they send on behalf of another account.
(Last updated 2009-08-27 10:50 CEST)
Kind regards,
Oliver Giesen
Chief Software Developer