Manually remove SpamSentinel for Domino

Created by Daniel Calkin, Modified on Fri, 31 Jan at 10:57 PM by Daniel Calkin

Before you Begin


This procedure should not be used unless SpamSentinel cannot be removed using the SpamSentinel Installer program as detailed in this KB article: How to uninstall SpamSentinel for Domino


This procedure is intended for use by experienced Domino administrators who will understand all the references used here and do not need detailed instructions for each step.



Procedure


This procedure covers manual removal of SpamSentinel for Domino from both Standard and Checking Machine installation types.



1. End the capture of mail by SpamSentinel.

Standard: 

a.  Notes.ini must be updated.  You can use the domino console commands 'show config' and 'set config' to update Notes.ini parameters while Domino is running.  Otherwise, shut down Domino and then edit the notes.ini file directly.

  • Remove from EXTMGR_ADDINS the entries for 'SSIntercept..', 'InboxGenius..', 'MBE...' if present
  • Remove from SERVERTASKS the entries for 'SSMon', 'MBEAdmin' if present

b.  Restart Domino


Checking Machine:

a.  Disable the Mail Rule "When all documents change routing state - mark as held"

b.  Issue this command to the Domino server: set rules


2.  Before continuing, allow SpamSentinel a few minutes to complete processing any messages which are in the scan.box databases or on hold.


3.  For Checking Machines: open the Windows Services manager and stop the service named SpamSentinel Monitor


4.  Uninstall the Windows services for SpamSentinel

The SpamSentinel services can each be un-installed using an elevated command prompt and running the executable using a parameter of :  -u   i.e.  SScanner.1.exe -u


Remove the following services using their executables at the command line from the directory where the service files are located.


Standard: 

a.  SpamSentinel Scanner 1

SScanner.1.exe -u

b.  SpamSentinel Duo 1

SSDuoE1.exe -u

c.  SpamSentinel Duo 2

SSDuoE2.exe -u

d.  SpamSentinel Reporter 1

SSReporter.1.exe -u

e.  SpamSentinel Anti-Virus Updater

SSAvUpdate.1.exe -u


Checking Machine:

a.  SpamSentinel Scanner 1

SScanner.1.exe -u

b.  SpamSentinel Duo 1

SSDuoE1.exe -u

c.  SpamSentinel Duo 2

SSDuoE2.exe -u

d.  SpamSentinel Reporter 1

SSReporter.1.exe -u

e.  SpamSentinel Anti-Virus Updater

SSAvUpdate.1.exe -u 

f.  SpamSentinel Monitor 1

SSMonitor.1.exe -u

g.  SpamSentinel Manager 1

SSManager.1.exe -u


5.  Delete all files and the folder where the SpamSentinel services in the previous step were found.


6.  Delete all files and the folder c:\Program Files\SpamSentinel\Complib if it exists.  Also check for and delete the folder c:\Program Files (x86)\Complib which may exist if the Domino server or Notes client is a 32-bit version.


7.  For Standard: remove the following files from the Domino Program directory.  Filenames may vary based on specific version numbers.  Not all files may be present.

  • MBEAdmin.exe
  • MBEAdmin.exe.config
  • MBEServer4037.dll
  • NotesSSBkup_<date>_<time>.ini  (there may be multiple files with this name format)
  • SSInstall2019.dll
  • SSIntercept.ini
  • SSIntercept_x64_3004.dll
  • SSMgr.exe
  • SSMgr.exe.config
  • SSMon.exe
  • SSMon.exe.config
  • SSRouter.exe
  • SSRouter.exe.config


8.  Remove the Windows registry contents found in HKEY_LOCAL_MACHINE\SOFTWARE\Mayflower


9.  For Standard: remove the scan.box databases in the Domino Data folder \SpamSentinel\Scan.  These are most easily found and removed using the Domino Administration client with the option 'Show Me: All Database Types' enabled.


10.  OPTIONAL

Delete Notes database and template files from the following folders (and sub-folders) within the Domino Data directory if they exist:

  • \MBE
  • \SpamSentinel
  • \Verisend





Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article