![]() |
||
Lucatec® MASK Outlook® Add-in
|
If you also have questions or suggestions that you feel should be included here, please contact us at mask@lucatec.de .
Many issues are not really specific to Lucatec® Mask but instead are often caused by confusion about how to configure the delegatable objects on the Exchange Server.
In order to avoid the suffix you have to grant the respective user the "Send As" permission on the relevant object. This is different from assigning "Send on behalf" rights which is what happens when you declare a user to be the delegate of an account via the Outlook UI (you can also do this via the Delivery Options button on the Exchange General tab of the corresponding AD object's Properties window).
The steps necessary for assigning "Send As" permissions differ slightly depending on whether you want to send on behalf of a shared mailbox account or a mail-enabled Public Folder:
Note that in both cases you will often have to restart the Exchange Information Store service for the changes to become effective.
There is no harm in assigning both "Send on behalf" and "Send As" permissions on an object but the "Send As" will take precedence, i.e. when both are set no suffix will be shown.
This section describes issues or questions that occur before or during the installation of Lucatec® Mask.
In order to easily install Lucatec® Mask on multiple machines with identical settings you could perform the following steps:
Install Lucatec® Mask manually on the first machine, using a commandline like:
LucatecMask-2.1.2-setup.exe /saveinf="myconfig.ini"where you should replace myconfig.ini with a fully qualified file name of your own liking (even on a network path). All settings and customizations you enter or select during this installation will be saved into the specified config file.
Make sure to enter your registration details when you perform this installation. For example, if you received licensing information in the following form:
MyCompany, Ltd. 123456-ABCDEF-789012-GHIJKL-345678-MNOPQR-901234-STUVWXthen MyCompany, Ltd. should go into the field labelled "Organization" and the key should be entered into the "Serial" field.
On the other machines launch the installation using the following commandline:
LucatecMask-2.1.2-setup.exe /silent /loadinf="myconfig.ini"where myconfig.ini is again the fully-qualified path to the configuration file that was produced by the first installation in step 1.
This will install Lucatec® Mask
with exactly the same settings and licensing information as on the
first machine without any user-interaction. The only thing you will
see is the progress bar. If you want to avoid that as well, use the
/verysilent argument instead of /silent
Note that on all machines the installation has to be performed from an administrative account and that Outlook needs to be restarted before the addin becomes available!
This section describes known limitations and issues of Lucatec® Mask as well as possible remedies or workarounds if available.
Sometimes after a crash or critical error Outlook will disable third-party addins that it thinks might have played a part in causing the error. To reenable them, follow these steps:


In all versions of Outlook to date, when applications create E-Mail messages via the so called MAPI interface, Outlook will not notify third-party addins about this, thus not allowing them to "hook" into the process before the message gets sent. As a result Lucatec® Mask will neither apply any context-dependent message options (i.e. sender, signature, save target) nor will its Message Options button appear on the toolbar allowing you to set these options yourself. A slight improvement in Outlook 2007 does at least allow the addin's button to be available on the "Ribbon" control but it's still not possible to automatically apply any message options right on message creation.
Here's a random and far from complete list of commonly used applications that exhibit this problem:
Note that as of version 2.2.0 Lucatec® Mask includes an additional addin for Microsoft Word and Excel which will allow you to use the File|Send to|Mail recipient (as Attachment) menu items in those applications without the limitations listed above. For all other applications there currently exists no workaround.
This is most likely due to a bug in Outlook that was only fixed in Office XP Service Pack 3. Lucatec® Mask will not work with Outlook 2002 prior to Service Pack 3. It is strongly recommended that you always install the latest available Office service packs.
You can get the Office XP Service Pack 3 either via automatic update from Microsoft Office Update or directly from Microsoft Downloads.
The following issues are only listed for reference. They have been resolved in recent product releases.
Lucatec® Mask versions until 2.1.2 had several limitations when using Microsoft Word to edit eMails:
All of the above have been resolved in Lucatec® Mask 2.2.0 for all versions of Outlook except Outlook 2000. If you are still using that version of Outlook the only known remedy currently is to disable WordMail (i.e. uncheck Use Microsoft Word to edit e-mail messages on the Mail Format tab of the main Options dialog).
Windows Vista was not officially supported by Lucatec® Mask prior to version 2.2.0. This particular issue has been resolved in that version. It was caused by an incompatibility with Vista-specific changes to the so called "DEP Hardware Protection". Disabling that feature of the operating system has reportedly worked as a workaround for a number of customers. Here's how to do that if you do not want to upgrade Lucatec® Mask yet (steps courtesy of tech-recipes.com):
bcdedit.exe /set {current} nx AlwaysOff
I'm using Microsoft Outlook 2002 (aka Outlook XP) and whenever I create a
new message or reply I get a security warning. What can I do?
(Resolved in 2.2.0)This was a known issue in the addin's signature insertion engine that was fixed in the 2.2.0 release. The only known workarounds were either to disable signature insertion or to update to a different version of Microsoft Outlook (both 2000 and 2003 did work).
Alle auf dieser Seite genannten Marken oder Warenzeichen unterliegen den Bestimmungen der jeweiligen Eigentümer.