This document includes a list of the parameters available to configure SMSDOM from the notes.ini file and the expected behavior. Symantec strongly suggest to add or modify these parameters only when instructed by a Symantec Technical Support Engineer.
SMSDOM Debugging
SMSDOM debug options can be enabled from notes.ini. For information on how to enable Debug logging in SMS for Domino, please refer to the following KB: http://www.symantec.com/docs/TECH80022
SMSDOM Configuration
The following are applicable to both SMSDOM-MPE and SMSDOM Windows:
SAVMailThreads
A number that decides the number of threads to scan email.
Example: SAVMailThreads=8
SAVWriteThreads
A number that decides the number of threads to scan document writes.
Example: SAVWriteThreads=16
SAVScanSentMail
Sent mail is not scanned by default. Set this to scan sent email and copies of mail that is filed when using ‘Send and File’.
Example: SAVScanSentMail=1
SAVMimeFuzzyMainHeader
Setting this to non-zero makes decomposer ignore invalid MIME header lines in the email.
Example: SAVMimeFuzzyMainHeader=1
SAVEnhancedTextID
This settings has many possible values:
These flags are not exclusive and can be combined by summing individual values.
Example: SAVEnhancedTextID=3
SAVMimeIdStrength
Setting this value between 0 and 4 changes the way MIME engine identifies MIME files.
Example: SAVMimeIdStrength=2.
SMSDOMMassMailer
Specifies the pattern of Mass Mailer virus names. By default it is @m
Example: SMSDOMMassMailer=@sms
SAVExtractOLE10NativeOnly
Setting this to nonzero makes OLE structured storage engine to extract only Ole10Native data streams.
Example: SAVExtractOLE10NativeOnly=1
SAVMalformityDetection
If set, SMSDOM detects malformed MIME messages.
Example: SAVMalformityDetection=1
SAVExtendedMalformityDetection
If set, decomposer engine detects malformed MIME messages.
Example: SAVExtendedMalformityDetection=1
SAVPartialMessageDetection
If set, SMSDOM detects if MIME message is not complete, i.e. partial.
Example: SAVPartialMessageDetection=1
SAVRapidReleasePkg
By default, name of the package RapidRelease downloads from Liveupdate website is symrapidreleasedefsi32.exe. If this changes in future, we don’t need to release a CRT with different name, that’s why this has been kept.
Example: SAVRapidReleasePkg=symrapidreleasedefsi64.exe
SAVRapidReleaseAuth
If this is set, the downloaded RapidRelease package is verified with its signature.
Example: SAVRapidReleaseAuth=1.
SAVRapidReleaseForceDelete
If this is set, the downloaded RapidRelease package will be deleted otherwise it will automatically get overwritten with the next download.
Example: SAVRapidReleaseForceDelete=1
The following are applicable only to SMSDOM-MPE:
SAVLog
Specifies the name of SAV Log database name.
Example: SAVLog=sav/savmpelog.nsf
SAVOptions
Specifies the name of SAV Settings database name.
Example: SAVOptions=sav/savmpe.nsf
SAVMassMailerPattern
As described in SMSDOMMassMailer
SAVEnableOnDemandCFScan
Enable CF in On Demand Scan. This will override the Settings Database.
Example: SAVEnableOnDemandCFScan=1
SAVEnableScheduledCFScan
Enable CF in Scheduled Scan. This will override the Settings Database.
Example: SAVEnableScheduledCFScan =1
SAVIgnoreMalformedContainer
If set, SMSDOM ignores malformed containers.
Example: SAVIgnoreMalformedContainer=1
The following are applicable only to SMSDOM v7.5:
SAVACFDIR
Specifies the directory where verity engine files are available.
Example: SAVACFDIR=c:\progra~1\symantec\smsdom\verity\bin\
SAVACFBYTEBUFFERSIZE
Specifies the maximum size of buffer used to store the extracted text from Verity engine.
Example: SAVACFBYTEBUFFERSIZE=65536
SAVACFFILTERPROCESS
If set to nonzero, specifies whether Verity Engine runs out of process.
Example: SAVACFFILTERPROCESS=1
SAVACFCHARSETVAL
An integer that specifies the charset Verity Engine should use if it finds a file with an unidentifiable character set.
Example: SAVACFCHARSETVAL=1 specifies Japanese. The default is 7 – Windows Latin 1
The list is