-Allow Admin Connections From These Hostnames* (allowAdminConnectionsFromName) An optional additional list of Hostnames from which you will accept web admin connections. Blank means accept connections from any IP address in allowAdminConnectionsFrom or any connection if nothing is set there. Note: if you make a mistake here, you may disable your web administration interface and be forced to manually edit your configuration file to fix it.
-Blackish & Whitish Addresses** (blackAddresses) Accepts specific addresses ([email protected]), user parts (user) or entire domains (@example.com). Wildcards are supported. A positive weight will make the address 'blackish'. A negative weight will turn the address into 'whitish'. For example: [email protected]|@*.gov=>-0.5|@*.biz=>0.5 . -Send EHLO (sendEHLO) If selected, ASSP sends an EHLO even if the client has sent only a HELO. This is useful to force the usage of TLS to the server, because EHLO is needed before STARTTLS can be used. -Cache Unknown Addresses (DoPenaltyMakeTraps) If enabled, unknown addresses are cached. If set to 'use for spamtrapaddresses' very activ addresses will be used like spamtrapaddresses. If set to 'use for spamaddresses' they will work like spamaddresses. If set to 'use for validation' all entries regardless of their frequency will be used to validate incoming addresses. Note: LocalAddresses_Flat or doLDAP or doVRFY must be enabled. -Unknown Address Frequency Limit (PenaltyMakeTraps) An unknown address will be used for spamaddresses or spamtrapaddresses if the frequency per hour reaches this value. For example 5. -Exceptionlist for Unknown Address Cache* (noPenaltyMakeTraps) Addresses which should not be cached. Accepts specific addresses ([email protected]), user parts (user) or entire domains (@example.com). Wildcards are supported ([email protected]). -Unknown Address Cache Expiration (PBTrapCacheExp) Addresses will be removed after being inactive this many hours. For example 24. -Automatic Restart ASSP on new or changed Script (AutoRestartAfterCodeChange) If selected, ASSP will restart it self, if it detects a new or changed running script. An automatic restart will not be done, if ASSP is not running as daemon on linux/MAC ( AsADaemon ) or as a service on windows and AutoRestartCmd is not configured. Leave this field empty to disable the feature. Possible values are 'immed and 1...23' . If set to 'immed', assp will restart within some seconds after a detected code change. If set to '1...23' the restart will be scheduled to that hour. A restart at 00:00 is not supported. -Auto Update the Running Script (assp.pl) (AutoUpdateASSP) No action will be done if 'no auto update' is selected. If 'download only' is selected and a new assp version is available, this new version will be downloaded to the directory /Applications/assp/download (assp.pl). If 'download and install' is selected, the running script will be saved to download directory and replaced by the new version. Configure ( AutoRestartAfterCodeChange ), if you want the new version to become the active running script. The perl module Compress::Zlib is required to use this feature. -Auto Update Developer Version (AutoUpdateASSPDev) -Local Frequency Interval (LocalFrequencyInt) The time interval in seconds in which the number of envelope recipients per sending address has not to exceed a specific number ( LocalFrequencyNumRcpt ). Use this in combination with LocalFrequencyNumRcpt to limit the number of recipients in a given interval, to prevent local abuse - for example from highjacked local accounts. A value of 0 (default) will disable this feature and clean the cache within five minutes. It is recommended to enable DoLocalSenderAddress and/or DoLocalSenderDomain, if you want to use this feature. To give users the chance to inform an admin about such blocked mails, local mails to EmailAdmins are never blocked because of that feature. -Local Frequency Recipient Number (LocalFrequencyNumRcpt) The number of envelope recipients per sending address that has not to exceed in a specific time interval ( LocalFrequencyInt ). Use this in combination with LocalFrequencyInt to limit the number of recipients in a given interval, to prevent local abuse - for example from highjacked local accounts. A value of 0 (default) will disable this feature and clean the cache within five minutes. It is recommended to enable DoLocalSenderAddress and/or DoLocalSenderDomain, if you want to use this feature. To give users the chance to inform an admin about such blocked mails, local mails to EmailAdmins are never blocked because of that feature. -Check local Frequency for this Users only* (LocalFrequencyOnly) A list of local addresses, for which the 'local frequency check' should be done. Leave this field blank (default), to do the check for every address. Accepts specific addresses ([email protected]), user parts (user) or entire domains (@domain.com). Wildcards are supported ([email protected]). For example: [email protected]|jhanna|@sillyguys.org -Check local Frequency NOT for this Users* (NoLocalFrequency) A list of local addresses, for which the 'local frequency check' should not be done. Noprocessing messages will skip this check. Accepts specific addresses ([email protected]), user parts (user) or entire domains (@domain.com). Wildcards are supported ([email protected]). For example: [email protected]|jhanna|@sillyguys.org -Black & Green Addresses** (blackAddresses) Accepts specific addresses ([email protected]), user parts (user) or entire domains (@example.com). Wildcards and Weights are supported. A negative weight will turn the address into 'green'. For example: [email protected]|@*.gov=>-0.5|@*.biz=>0.5 . -Spoofing check uses SPF record. -ConnectionScoring Limit (ConnectionScoringLimit) MessageScoring will block connectionss whose score exceeds this threshold. A value of 0 here will disable this option. For example: 150 -ConnectionScoring Limit Exceeded (conValencePB) Message scoring in ConnectionScoringLimit. -Add MailFrom to Whitelist (RWLtoWhitelist) If ValidateRWL is set to 'whiting' and the RWL shows medium/high trustworthiness, the MailFrom address will be added to the whitelistdb. Trustworthiness : (127.0.x.T): 0 = none 1 = low 2 = medium 3 = high -Detect Same Subject (detectSameSubject) If set to a value higher than 0, ASSP count identical subjects within one hour. If this count exceeds the defined value, subValencePB will be added to the message- and ip-score. -RBL Service Providers* (RBLServiceProvider) Names of DNSBLs to use separated by "|" or name of list 'file:files/dnsbls.txt'. Defaults are: zen.spamhaus.org=>1|bl.spamcop.net=>1|bb.barracudacentral.org=>1|combined.njabl.org=>1|safe.dnsbl.sorbs.net=>1|psbl.surriel.com=>2|ix.dnsbl.manitu.net=>2|dnsbl-1.uceprotect.net=>2|dnsbl-2.uceprotect.net=>4. DNSBL providers can be classified like bl.spamcop.net=>1. '1' is the most trustworthy class. '6' is the least trustworthy class. Numbers above 6 will be used as score directly. The value of the class acts as a divisor of rblValencePB. So if rblValencePB = 50 bl.spamcop.net=>1 would be the same as bl.spamcop.net=>50, bl.spamcop.net=>2 would be the same as bl.spamcop.net=>25. If the sum of scores surpasses rblValencePB, the DNSBL check fails. If not the DNSBL hit is only scored even with RBLmaxhits reached. -Whitelisted Attachment Blocking (BlockWLExes) Set the level of Attachment Blocking to 0-4 for whitelisted senders. Choose 0 for no attachment blocking. -Local Attachment Blocking (BlockLCExes) Set the level of Attachment Blocking to 0-4 for local senders. Choose 0 for no attachment blocking. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
