The SpamTag Outlook plugin is failing to process selected emails. When a user clicks on the SpamTag buttons to mark as Spam or Not Spam, the plugin displays the following notification error:
Cannot process selected email
The recommended fix to address this problem is to uninstall the SpamTag plugin and thereafter re-install by following these steps on the client machine:
- Launch the Registry Editor by typing
regediton the Windows Run command box
- Manually remove the following registry keys:
Backup the above registry keys before deleting them.
- Uninstall any pre-existing versions of the SpamTag plugin from the uninstall feature in the Windows Control Panel. If you cannot uninstall the SpamTag plugin from the Windows Control Panel, you can also use this Microsoft tool to do so
- Install SpamTag plugin on the client machine by following the steps outlined in Installing the SpamTag Extension.
After successful re-installation, the SpamTag toolbar should be visible in the Microsoft Outlook Home ribbon and the Spam/Not Spam buttons should not be greyed out confirming that the plugin has successfully connected to the MailEssentials server.
Clicking on the Settings button will launch the SpamTag client configuration window which can be referenced to confirm the MailEssentials server URL and user credentials currently active for synchronization between the MailEssentials server and the client.
Clicking on the OK button should not prompt or display any authentication errors.
If the issue still persists, please generate the troubleshooting logs as follows:
- Make sure that you have tracing enabled.
- Wait for at least 30 minutes to gather enough information and for the issue to be reproduced.
- Run the troubleshooter:
- Start > Programs > GFI MailEssentials > Troubleshooter
- Follow the Log Generation Wizard for collecting the required and pertinent information.
- Select New Case when completing the log generation to attach the logs to a new case that will be automatically created, or open a support ticket manually and attach the logs to that ticket, so that the Support team can investigate the problem.