Symantec Mail Security for Domino (SMSDOM) and Symantec Mail Security for Domino Multi-Platform Edition (SMSDOM MPE) parameters for notes.ini

Article:TECH90963  |  Created: 2008-01-19  |  Updated: 2014-07-09  |  Article URL http://www.symantec.com/docs/TECH90963
Article Type
Technical Solution


Issue



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.


Solution



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:

      1. 0x01 = This tells decomposer to pass the input from all text engines
      2. 0x02 = This tells decomposer Text Engine to process all files regardless of whether they have been identified as binary
      3. 0x04 = This tells decomposer MIME Engine to continue parsing area of main header portion of MIME message until a blank line is encountered.
      4. 0x08 = This tells decomposer Text Engine to abort processing when it encounters a byte with value less than 8.

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

          KVCS_SJIS, /* 1: Japanese (uses multibyte encoding), cp932 */
          KVCS_GB, /* 2: Simplified Chinese (China, Singapore, Malasia), cp936 */
          KVCS_BIG5, /* 3: Traditional Chinese (Taiwan, HongKong, Macaw), cp950 */
          KVCS_KSC, /* 4: Korean, cp949 */
          KVCS_1250, /* 5: Windows Latin 2 (Central Europe) */
          KVCS_1251, /* 6: Windows Cyrillic (Slavic) */
          KVCS_1252, /* 7: Windows Latin 1 (ANSI) */
          KVCS_1253, /* 8: Windows Greek */
          KVCS_1254, /* 9: Windows Latin 5 (Turkish) */

          KVCS_1255, /* 10: Windows Hebrew */
          KVCS_1256, /* 11: Windows Arabic */
          KVCS_1257, /* 12: Windows Baltic Rim */
          KVCS_1258, /* 13: Windows Vietnamese */
          KVCS_8859_1, /* 14: ISO 8859-1, Latin 1 (Western Europe, Latin America)*/
          KVCS_8859_2, /* 15: ISO 8859-2, Latin 2 (Central Eastern Europe) */
          KVCS_8859_3, /* 16: ISO 8859-3, Latin 3 (S.E. Europe) */
          KVCS_8859_4, /* 17: ISO 8859-4, Latin 4 (Scandinavia/Baltic) */
          KVCS_8859_5, /* 18: ISO 8859-5, Latin/Cyrillic */
          KVCS_8859_6, /* 19: ISO 8859-6, Latin/Arabic */

          KVCS_8859_7, /* 20: ISO 8859-7, Latin/Greek */
          KVCS_8859_8, /* 21: ISO 8859-8, Latin/Hebrew */
          KVCS_8859_9, /* 22: ISO 8859-9, Latin/Turkish */
          KVCS_8859_14, /* 23: ISO 8859-14 */
          KVCS_8859_15, /* 24: ISO 8859-15 */
          KVCS_437, /* 25: Dos Latin US */
          KVCS_737, /* 26: Dos Greek */
          KVCS_775, /* 27: Dos Baltic Rim */
          KVCS_850, /* 28: Dos Latin 1 */
          KVCS_851, /* 29: Dos Greek */

          KVCS_852, /* 30: Dos Latin 2 */
          KVCS_855, /* 31: Dos Cyrillic */
          KVCS_857, /* 32: Dos Turkish */
          KVCS_860, /* 33: Dos Portuguese */
          KVCS_861, /* 34: Dos Icelandic */
          KVCS_862, /* 35: Dos Hebrew */
          KVCS_863, /* 36: Dos Canadain French */
          KVCS_864, /* 37: Dos Arabic */
          KVCS_865, /* 38: Dos Nordic */
          KVCS_866, /* 39: Dos Cyrillic Russian */

          KVCS_869, /* 40: Dos Greek 2 */
          KVCS_874, /* 41: Thai */
          KVCS_PDFMACDOC, /* 42: PDF MAC DOC */
          KVCS_PDFWINDOC, /* 43: PDF WIN DOC */
          KVCS_STDENC, /* 44: Adobe Standard Encoding */
          KVCS_PDFDOC, /* 45: Adobe standard PDF character set */
          KVCS_037, /* 46: EBCDIC code page 037 */
          KVCS_1026, /* 47: EBCDIC code page 1026 */
          KVCS_500, /* 48: EBCDIC code page 500 */
          KVCS_875, /* 49: EBCDIC code page 875 */

          KVCS_LMBCS, /* 50: Lotus LMBCS Group 1 and Group 2 char set mapping */
          KVCS_UNICODE, /* 51: UNICODE, UCS-2 */
          KVCS_UTF16, /* 52: Unicode format that 'escapes' 32-bit characters */
          KVCS_UTF8, /* 53: Unicode transformation 8 bit */
          KVCS_UTF7, /* 54: Unicode transformation 7 bit */
          KVCS_2022_JP, /* 55: ISO 2022-JP, Japanese mail and news safe encoding */
          KVCS_2022_CN, /* 56: ISO 2022-CN, Chinese mail and news safe encoding */
          KVCS_2022_KR, /* 57: ISO 2022-KR, Korean mail and news safe encoding */
          KVCS_WP6X, /* 58: Word Perfect 6.x and higher character mapping */
          KVCS_10000, /* 59: MS Macintosh Roman */

          KVCS_KSC5601, /* 60: Unified Hangeul */
          KVCS_GB2312, /* 61: */
          KVCS_GB12345, /* 62: */
          KVCS_CNS11643, /* 63: */
          KVCS_JIS0201, /* 64: */
          KVCS_JIS0212, /* 65: */
          KVCS_EUC_JP, /* 66: EUC/JP */
          KVCS_EUC_GB, /* 67: Simplified Chinese EUC */
          KVCS_EUC_BIG5, /* 68: Traditional Chinese EUC */
          KVCS_EUC_KSC, /* 69: Korean EUC */

          KVCS_424, /* 70: EBCDIC Hebrew */
          KVCS_856, /* 71: PC Hebrew (old) */
          KVCS_1006, /* 72: */
          KVCS_KOI8R, /* 73: Russian Internet */
          KVCS_PDF_JAPAN1, /* 74: Adobe-Japan1-2 character collection */
          KVCS_PDF_KOREA1, /* 75: Adobe-Korea1-0 character collection */
          KVCS_PDF_GB1, /* 76: Adobe-GB1-3 character collection */
          KVCS_PDF_CNS1, /* 77: Adobe-CNS1-2 character collection */
          KVCS_2022_JP_8, /* 78: */
          KVCS_720, /* 79: Arabic DOS-720 */

          KVCS_VISCII, /* 80: Vietnamese VISCII */
          KVCS_8859_10, /* 81: ISO 8859-10 */
          KVCS_8859_13, /* 82: ISO 8859-13 */
          KVCS_57002, /* 83: ISCII Devanagari x-iscii-de */
          KVCS_57003, /* 84: ISCII Bengali x-iscii-be */
          KVCS_57004, /* 85: ISCII Tamil x-iscii-ta */
          KVCS_57005, /* 86: ISCII Telugu x-iscii-te */
          KVCS_57006, /* 87: ISCII Assamese x-iscii-as */
          KVCS_57007, /* 88: ISCII Oriya x-iscii-or */
          KVCS_57008, /* 89: ISCII Kannada x-iscii-ka */

          KVCS_57009, /* 90: ISCII Malayalam x-iscii-ma */
          KVCS_57010, /* 91: ISCII Gujarathi x-iscii-gu */
          KVCS_57011, /* 92: ISCII Panjabi x-iscii-pa */
          KVCS_GB18030b2, /* 93: Reserved for internal use */
          KVCS_GB18030, /* 94: New Chinese 4 byte charset GB18030 */
          KVCS_8859_11, /* 95: ISO 8859-11 */
          KVCS_8859_16, /* 96: ISO 8859-16 */
          KVCS_ARABICMAC, /* 97: Arabic Mac */
          KVCS_KOI8U, /* 98: Ukrainian Character Set KOI8-U */



Article URL http://www.symantec.com/docs/TECH90963


Terms of use for this information are found in Legal Notices