
1.9.9 (12358)


-enableCFGShare (Enable Configuration Sharing) 
Read all positions in this section carefully (multiple times is recommended!!!)! A wrong configuration sequence or wrong configuration values can lead in to a destroyed ASSP configuration!
  If set, the configuration value and option files synchronization will be enabled. This synchronization belong to the configuration values, to the file that is possibly defined in a value and to the include files that are possibly defined in the configured file.
  If the configuration of all values in this section is valid, the synchronization status will be shown in the GUI for each config value that is, or could be shared. There are several configuration values, that could not be shared. The list of all shareable values could be found in the distributed file assp_sync.cfg
  For an initial synchronization setup set the following config values in this order: setup syncServer, syncConfigFile, syncTestMode and as last syncCFGPass (leave isShareSlave and isShareMaster off). Use the default (distributed syncConfigFile assp_sync.cfg) file and configure all values to your needs - do this on all peers by removing lines or setting the general sync flag to 0 or 1 (see the description of syncConfigFile ).
  If you have finished this initial setup, enable isShareMaster or isShareSlave - now assp will setup all entrys in the configuration file for all sync peers to the configured default values (to 1 if isShareMaster or to 3 if isShareSlave is selected). Do this on all peers. Now you can configure the synchronization behavior for each single configuration value for each peer, if it should differ from the default setup.
  For the initial synchronization, configure only one ASSP installation as master (all others as slave). If the initial synchronization has finished, which will take up to one hour, you can configure all or some assp as master and slave. On the initial master simply switch on isShareSlave. On the inital slaves, switch on isShareMaster and change all values in the sync config file that should be bedirectional shared from 3 to 1. As last action enable enableCFGShare on the SyncSlaves first and then on the SyncMaster.
  After such an initial setup, any changes of the peers (syncServer) will have no effect to the configuration file (syncConfigFile)! To add or remove a sync peer after an initial setup, you have to configure syncServer and you have to edit the sync config file manualy.
  This option can only be enabled, if isShareMaster and/or isShareSlave and syncServer and syncConfigFile and syncCFGPass are configured!
  Because the synchronization is done using a special SMTP protocol (without "mail from" and "rcpt to"), this option requires an installed Net::SMTP module in PERL. This special SMTP protocol is not usable to for any MTA for security reasons, so the "sync mails" could not be forwarded via any MTA.
  For this reason all sync peers must have a direct or routed TCP connection to each other peer.
    

-isShareMaster (This is a Share Master) 
If selected, ASSP will send configured configuration changes to sync peers.  

-isShareSlave (This is a Share Slave) 
If selected, ASSP will receive configured configuration changes from sync peers. To accept a sync request, every sending peer has to be defined in syncServer - even if there are manualy made entrys in the sync config file for a peer.  

-syncServer (Default Sync Peers) 
Define all configuration sync peers here (to send changes to or to receive changes from). Sepatate multiple values by "|". Any value must be a pair of hostname or ip-address and :port, like 10.10.10.10:25 or mypeerhost:125 or mypeerhost.mydomain.com:225. The :port must be defined!
  The target port can be the listenPort , listenPort2 or relayPort of the peer.  

-syncTestMode (Test Mode for Config Sync) 
If selected, a master (isShareMaster) will process all steps to send configuration changes, but will not really send the request to the peers. A slave (isShareSlave) will receive all sync requests, but it will not change the configuration values and possibly sent configuration files will be stored at the original location and will get an extension of ".synctest".  

-syncConfigFile (Configuration File for Config Sync*) 
Define the synchronization configuration file here (default is file:assp_sync.cfg).
 This file holds the configuration and the current status of all synchronized assp configuration values.
 The format of an initial value is:  "varname:=syncflag" - where syncflag could be 0 -not shared and 1 -is shared - for example: HeaderMaxLength:=1 . The syncflag is a general sign, which meens, a value of 0 disables the synchronization of the config value for all peers. A value of 1, enables the peer configuration that possibly follows.
 The format after an initial setup is: "varname:=syncflag,syncServer1=status,syncServer2=status,......". The "status" could be one of the following:
 0 - no sync - changes of this value will not be sent to this syncServer - I will ignore all change requests for this value from there
 1 - I am a SyncMaster, the value is still out of sync to this peer and should be synchronized as soon as possible
 2 - I am a SyncMaster, the value is still in sync to this peer
 3 - I am not a SyncMaster but a SyncSlave - only this SyncMaster (peer) knows the current sync status to me
 4 - I am a SyncMaster and a SyncSlave (bidirectional sync) - a change of this value was still received from this syncServer (peer) and should not be sent back to this syncServer - this flag will be automaticaly set back to 2 at the next synchronization check
  
Default: file:assp_sync.cfg 

-syncCFGPass (Config Sync Password) 
The password that is used and required (additionaly to the sending IP address) to identify a valid sync request. This password has to be set equal in all ASSP installations, from where and/or to where the configuration should be synchronized.
  The password must be at least six characters long.
  If you want or need to change this password, first disable enableCFGShare here an on all peers, change the password on all peers, enable enableCFGShare on SyncSlaves then enable enableCFGShare on SyncMasters.  

-syncShowGUIDetails (Show Detail Sync Information in GUI) 
If selected, the detail synchronization status is shown at the top of each configuration parameter like:
  nothing shown - there is no entry defined for this parameter in the syncConfigFile or it is an unsharable parameter
  "(shareable)" - the parameter is shareable but the general sync sign in the syncConfigFile is zero
  "(shared: ...)" - the detail sync status for each sync peer
  If not selected, only different colored bulls are shown at the top of each configuration parameter like:
  nothing shown - no entry in the syncConfigFile or it is an unsharable parameter
  "black bull &bull;" - the parameter is shareable but the general sync sign in the syncConfigFile is zero
  "green bull &bull;" - the parameter is shared and in sync to each peer
  "red bull &bull;" - the parameter is shared but it is currently out of sync to at least one peer
  If you move the mouse over the bull, a hint box will show the detail synchronization status.
  Notes Config Sync
    

-ConnectionLog (Connections Logging) 
  

-listenPort (SMTP Listen Port) 
The port number on which ASSP will listen for incoming SMTP connections (normally 25). You can specify both an IP address and port number to limit connections to a specific interface. Multiple ports  (interface:port) are possible separated by a pipe (|). Hint: If you set this port to 25, you must not set "listenPort2" to 25Examples:25 123.123.123.1:25|123.123.123.5:25 
Default: 25 

-smtpDestination (SMTP Destination) 
The IP number! and port number of your primary SMTP mail transfer agent (MTA). If multiple servers are listed and the first listed MTA does not respond, each additional MTA will be tried. If only a port number is entered, or the dynamic keyword INBOUND is used with a port number, then the connection will be established to the local IP address on which the connection was received. This is useful when you have several IP addresses with different domains or profiles in your MTA. If INBOUND:PORT is used, ReportingReplies (Analyze,Help,etc and CopyMail will go to 127.0.0.1:PORT. If your needs are different, use smtpReportServer (SMTP Reporting Destination) and sendAllDestination (Copy Spam SMTP Destination). Separate multiple entries by "|".Examples:127.0.0.1:1025, 127.0.0.1:1025|127.0.0.5:1025, INBOUND:1025 
Default: 127.0.0.1:1025 

-EmailReportDestination (ASSP Internal Mail Destination) 
Port to connect to when  ASSP sends replies to email-interface mails, notifications and block reports. Must be set when smtpDestination contains INBOUND. For example "10.0.1.3:1025", etc.  

-listenPort2 (Second SMTP Listen Port) 
A secondary port number on which ASSP can accept SMTP connections. This is useful as a dedicated port for TLS or VPN clients or for those who cannot directly send mail to a mail server outside of their ISP's network because the ISP is blocking port 25. Multiple ports  (interface:port) are possible separated by a pipe (|). Hint: If you set this port to 587, you must not set another portlike "listenPort" to 587Examples: 587192.168.0.100:587192.168.0.100:587|192.168.0.101:587 
Default: 587 

-smtpAuthServer (Second SMTP Destination) 
The IP address/hostname and port number to connect to when mail is received on the second SMTP listen port. If the field is blank, smtpDestination will be used. The purpose of this setting is to allow remote users to make authenticated connections and transmit their email without encountering SPF failures.Examples:127.0.0.1:687  

-EnforceAuth (Force SMTP AUTH on Second SMTP Listen Port) 
Do not allow clients to connect to listenPort2 without Authentication.   

-DisableAUTH (Disable SMTP AUTH for External Clients) 
If you do not want  external clients to use SMTP AUTH - check this option.  

-enableINET6 (Enable IPv6 support) 
For IPv6 network support to be enabled, check this box. Default is disabled. IO::Socket::INET6 is able to handle both IPv4 and IPv6. NOTE: This option requires an installed IO::Socket::INET6 module in PERL and your system should support IPv6 sockets.
  Before you enable or disable IPv6, please check every IP listener and destination definition in assp and correct the settings. Changing this requires a restart of ASSP! IPv4 addresses are defined for example 192.168.0.1 or 192.168.0.1:25 - IPv6 addresses are defined like [FE80:1:0:0:0:0:0:1]:25 or [FE80:1::1]:25 ! If an IPv4 address is defined for a listener, assp will listen only on the IPv4 socket. If an IPv6 address is defined for a listener, assp will listen only on the IPv6 socket. If only a port is defined for a listener, assp will listen on both IPv4 and IPv6 sockets.
    

-smtpDestinationRT (SMTP Destination Routing Table*) 
If INBOUND is used in the SMTP Destination field, the rules specified here are used to route the inbound IP address to a different outbound IP address. You must specify a port number with the outbound IP address. This feature works by assigning as many IP addresses to ASSP as you have different receiving Mailservers. 
  Example:141.120.110.1=>141.120.110.129:25|141.120.110.2=>141.120.110.130:125|141.120.110.3=>141.120.110.130:125 requires ASSP restart
Notes On Network Setup
  

-SessionLog (Session Limit Logging) 
 
Default: standard 

-MaxErrors (Maximum Errors Per Session) 
The maximum number of SMTP session errors encountered before the
connection is dropped. Scoring is done  with meValencePB. 
Default: 3 

-MaxAUTHErrors (Max Number of AUTHentication Errors) 
If an IP (/24 network is used) exceeds this number of authentication errors (535) the transmission of the current message will be canceled and any new connection from that IP will be blocked for 5-10 minutes.
  Every 5 Minutes the 'AUTHError' -counter of the IP will be decreased by one. autValencePB is used for the penalty box.
  No limit is imposed by ASSP if the field is left blank or set to 0. This option allows admins to prevent external bruteforce or dictionary attacks via AUTH command. Whitelisted, noBlockingIPs and NoProcessing IP's are ignored like any relayed connection.  

-noMaxAUTHErrorIPs (Do not check MaxAUTHErrors for these IPs*) 
List of IP's which should not be checked for MaxAUTHErrors .  For example: 145.145.145.145|145.146.  

-maxSMTPSessions (Maximum Sessions) 
The maximum number of simultaneous SMTP sessions. This can prevent server overloading and DoS attacks. 64 simultaneous sessions are typically enough. No entry or zero means no limit. 
Default: 64 

-noMaxSMTPSessions (No Maximum Sessions IP addresses*) 
Mail from any of these IP addresses and Hostnames will pass through without checking maximum number of simultaneous SMTP sessions. For example: localhost|145.145.145.145  

-maxSMTPipSessions (Maximum Sessions Per IP address) 
The maximum number of SMTP sessions allowed per IP address. Use this setting to prevent server overloading and DoS attacks. 5 sessions are typically enough. If left blank or set to 0 there is no limit imposed by ASSP. ispip (ISP/Secondary MX Servers) and acceptAllMail (Accept All Mail) matches are excluded from SMTP session limiting. Scoring is done  with iplValencePB. 
Default: 5 

-maxSMTPipSessionsISPIP (Include IPs in ispip in Maximum Sessions Per IP Check) 
IP addresses in ispip (ISP/Secondary MX Servers) are normally not checked, this option will include them into SMTP session limiting  

-HeaderMaxLength (Maximum Header Size) 
The maximum allowed header length, in bytes. At each mail hop header information is added by the mail server. A large mail header can indicate a mail loop. If the value is blank or 0 the header size will not be checked. 
Default: 100000 

-MaxEqualXHeader (Maximum Equal X-Header Lines*) 
The maximum allowed equal X-header lines - eg. "X-SubscriberID". If the value is set to empty the header will not be checked for equal X-header lines. This check will be skipped for noprocessing, whitelisted and outgoing mails.
  The default is "*=&gt;20", which means any X-header can occure 20 time maximum. You can define different values for different X-headers - wildcards like "*" and "?" are allowed to be used.
  For example:
  *=&gt;20|X-Notes-Item=&gt;100|X-Subscriber*=&gt;10|X-AnyTag=&gt;0
  An value of zero disables the check for the defined X-header. The check is also skipped if no default like "*=&gt;20" is defined and the X-header defintion is not found. 
Default: *=&gt;20 

-detectMailLoop (Detect Possible Mailloop) 
If set to a value higher than 0, ASSP count its own Received-header in the header of the mail. If this count exceeds the defined value, the transmission of the message will be canceled. 
Default: 10 

-maxSize (Max Size of Outgoing Message) 
If the value of ([message size]) exceeds maxSize in bytes the transmission of the local message will be canceled. No limit is imposed by ASSP if the field is left blank or set to 0. This option allows admins to limit useless bandwidth wasting based on the transmit size.  

-MaxSizeAdr (Max Size of Local Message Adresses*) 
Use this parameter to set individual maxSize values for email addresses, domains, user names and IP addresses. A file must be specified if used.
Accepts specific addresses (user@domain.com), user parts (user), entire domains (@domain.com) and IP addresses (CIDR notation like 123.1.101/32 is here not supported!) - group definitions could be used. Use one entry per line. Wildcards are supported (fribo*@domain.co?). A second parameter separated by "=>" specifies the size limit. 
For example:
fribo*@thisdomain.co?=>1000000
jhanna=>0
@sillyguys.org=>500000
101.1.2.*=>0

If multiple matches (values) are found in a mail for any IP address in the transport mail chain, any envelope recipient and the envelope sender, the highest value or 0 (no limit) will be used! If no match (value) is found in a mail, the definition in maxSize will take place. 
Default: file:files/MaxSize.txt 

-maxSizeExternal (Max Size of Incoming Message) 
If the value of ([message size]) exceeds maxSizeExternal in bytes the transmission of the message will be canceled. No limit is imposed by ASSP if the field is left blank or set to 0. This option allows admins to limit useless bandwidth wasting based on the transmit size.  

-MaxSizeExternalAdr (Max Size of External Message Adresses*) 
Use this parameter to set individual maxSizeExternal values for email addresses, domains, user names and IP addresses. A file must be specified if used.
Accepts specific addresses (user@domain.com), user parts (user), entire domains (@domain.com) and IP addresses (CIDR notation like 123.1.101/32 is here not supported!) - group definitions could be used. Use one entry per line. Wildcards are supported (fribo*@domain.co?). A second parameter separated by "=>" specifies the size limit. 
For example:
fribo*@thisdomain.co?=>1000000
jhanna=>0
@sillyguys.org=>500000
101.1.2.*=>0

If multiple matches (values) are found in a mail for any IP address in the transport mail chain, any envelope recipient and the envelope sender, the highest value or 0 (no limit) will be used! If no match (value) is found in a mail, the definition in maxSizeExternal will take place. 
Default: file:files/MaxSizeExt.txt 

-noMaxSize (Dont Check Messages from these Addresses/Domains*) 
Don't check the value of  maxSizeExternal and maxRealSizeExternal in messages from these addresses/domain. Accepts specific addresses (user@example.com), user parts (user) or entire domains (@example.com).  

-maxRealSize (Max Real Size of Outgoing Message) 
If the value of (number of [rcpt to] * [message size]) exceeds maxRealSize in bytes the transmission of the message will be canceled. No limit is imposed by ASSP if the field is left blank or set to 0. This option allows admins to limit useless bandwidth wasting based on the total transmit size.  

-MaxRealSizeAdr (Max Real Size of Local Message Adresses*) 
Use this parameter to set individual maxRealSize values for email addresses, domains, user names and IP addresses. A file must be specified if used.
Accepts specific addresses (user@domain.com), user parts (user), entire domains (@domain.com) and IP addresses (CIDR notation like 123.1.101/32 is here not supported!) - group definitions could be used. Use one entry per line. Wildcards are supported (fribo*@domain.co?). A second parameter separated by "=>" specifies the size limit. 
For example:
fribo*@thisdomain.co?=>1000000
jhanna=>0
@sillyguys.org=>500000
101.1.2.*=>0

If multiple matches (values) are found in a mail for any IP address in the transport mail chain, any envelope recipient and the envelope sender, the highest value or 0 (no limit) will be used! If no match (value) is found in a mail, the definition in maxRealSize will take place. 
Default: file:files/MaxRealSize.txt 

-maxRealSizeExternal (Max Real Size of Incoming Message) 
If the value of (number of [rcpt to] * [message size]) exceeds maxRealSizeExternal in bytes the transmission of the external message will be canceled. No limit is imposed by ASSP if the field is left blank or set to 0. This option allows admins to limit useless bandwidth wasting based on the total transmit size.  

-MaxRealSizeExternalAdr (Max Real Size of External Message Adresses*) 
Use this parameter to set individual maxRealSizeExternal values for email addresses, domains, user names and IP addresses. A file must be specified if used.
Accepts specific addresses (user@domain.com), user parts (user), entire domains (@domain.com) and IP addresses (CIDR notation like 123.1.101/32 is here not supported!) - group definitions could be used. Use one entry per line. Wildcards are supported (fribo*@domain.co?). A second parameter separated by "=>" specifies the size limit. 
For example:
fribo*@thisdomain.co?=>1000000
jhanna=>0
@sillyguys.org=>500000
101.1.2.*=>0

If multiple matches (values) are found in a mail for any IP address in the transport mail chain, any envelope recipient and the envelope sender, the highest  value or 0 (no limit) will be used! If no match (value) is found in a mail, the definition in maxRealSizeExternal will take place. 
Default: file:files/MaxRealSizeExt.txt 

-maxRealSizeError (Max Real Size Error Message) 
SMTP error message to reject maxRealSize exceeding mails. For example:552 message exceeds MAXREALSIZE byte (size * rcpt)! MAXREALSIZE will be replaced by the value of maxRealSize. 
Default: 552 message exceeds MAXREALSIZE byte (size * rcpt) 

-smtpIdleTimeout (SMTP Idle Timeout) 
The number of seconds a session is allowed to be idle before being forcibly disconnected. No limit is imposed by ASSP if the field is left blank or set to 0. If you have not defined an IdleTimeout on your MTA, this value should not be set to 0, because then a connection will never be timed out!  
Default: 600 

-smtpNOOPIdleTimeout (SMTP Idle Timeout after NOOP) 
The number of seconds a session is allowed to be idle after a "NOOP" command is received, before being forcibly disconnected. No limit is imposed by ASSP if the field is left blank or set to 0.
  This should prevent hackers to hold and block connections by sending "NOOP" commands short before the "smtpIdleTimeout" is reached.  

-smtpNOOPIdleTimeoutCount (SMTP Idle Timeout after NOOP Count) 
The number of counts a session is allowed send "NOOP" commands following on each other, before being forcibly disconnected. No limit is imposed by ASSP if the field is left blank or set to 0.
  This in cooperation with "smtpNOOPIdleTimeout" should prevent hackers to hold and block connections by sending repeatedly "NOOP" commands short before the "smtpNOOPIdleTimeout" is reached. If "smtpNOOPIdleTimeout" is not defined or 0, this value will be ignored!Notes On SMTP Session Limits  

-spamSubject (Prepend Subject of Spam Mails) 
For example: [SPAM]  

-allTestMode (Set all Filters to TestMode) 
Setting TestMode will tell ASSP not to reject the mail but rather build up the whitelist and spam and notspam collections. This can go on for some time without disturbing normal operation. Be sure spamSubject is blank, no user should see anything strange.  

-spamTag (Prepend Spam Tag) 
ASSP uses many methods. The method which caught the spam  will be prepended to the subject of the email. For example: [DNSBL]  

-NotSpamTag (Ham Password) 
If an incoming email matches this text string it will be considered not-spam. This can be used in SpamError to ask for resending the mail with this text in the subject. 
Default: 424242 

-NotSpamTagRandom (Generate NotSpamTag Randomly) 
ASSP will use MSGIDSec to make a NotSpamTag. This will change daily. The last 10 days will be saved.  

-NotSpamTagToWhite (Whitelist Messages with NotSpamTag) 
  

-SpamError (Spam Error) 
SMTP error message to reject spam. The literal LOCALDOMAIN will be replaced by the recipient domain or defaultLocalHost. SESSIONID will be replaced by the unique ASSP identifier set by uniqeIDLogging. REASON will be replaced by the actual reason. NOTSPAMTAG will be replaced by NotSpamTag. MYNAME will be replaced by myName. 
Default: 554 5.7.1 Mail (SESSIONID) appears to be unsolicited - REASON - resend with NOTSPAMTAG appended to subject and contact postmaster@LOCALDOMAIN for resolution 

-send250OK (Send 250 OK ) 
Set this checkbox if you want ASSP to reply with '250 OK' instead of SMTP error code '554 5.7.1'.  

-AddSpamHeader (Add Spam Header) 
Adds a line to the email header "X-Assp-Spam: YES" if the message is spam. 
Default: On 

-AddCustomHeader (Add Custom Header) 
Adds a line to the email header if the message is spam. For example: X-Spam-Status:yes  

-AddLevelHeader (Add Graphical Level Header) 
Adds a line to the email header "X-Assp-Spam-Level:**** " showing the totalscore represented by stars (1 - 20), every star representing five scoring points.  

-AddIPHeader (Add IP Match Header) 
Add X-Assp- header for all IP matches. 
Default: On 

-AddRegexHeader (Add  RegEx Match Header) 
 
Default: On 

-AddIntendedForHeader (Add Intended-For Header for Recipients) 
Notes On RWL 
Default: multiple recipients 

-AddSpamReasonHeader (Add Spam Reason Header) 
Adds a line to the email header "X-Assp-Spam-Reason: " explaining why the message is spam.Notes On Spam Control 
Default: On 

-noGriplistUpload (Dont Upload Griplist Stats) 
Check this to disable the Griplist upload when rebuildspamdb runs. The Griplist contains IP addresses and their values between 0 and 1, lower is less spammy, higher is more spammy. This value is called the grip value.   

-noGriplistDownload (Dont auto-download the Griplist file) 
Set this checkbox, if you don't use the Griplist.    

-GriplistDownloadNow (Run GriplistDownload Now) 
If selected, ASSP will download the Griplist right away. &nbsp;  

-noGRIP (Dont do Griplist for these IP addresses and Hostnames* ) 
Enter IP addresses and Hostnames that you don't want to get gripvalues from. For example:server.example.com|145.145.145.145|145.146.  

-DoFullGripDownload (Full Griplist Download Period) 
The Global Griplist is downloaded once in full, then only deltas are downloaded each day subsequently.  This option forces a new full download after this many days.  Leave it blank to not force new full downloads. Recommended: 30 days.Notes On Griplist 
Default: 30 

-spamSubjectSL (Suppress SpamSubject to SpamLover-Messages) 
If set spamSubject does NOT get prepended to the subject of any SpamLover-Message.  

-spamLoverSubjectSelected (Suppress SpamSubject For Selected Recipients*) 
spamSubject does NOT get prepended to the subject for these recipients. To enable the selection you need to uncheck spamSubjectSL. 
Default: ALL 

-spamTagSL (Suppress spamTags to SpamLover-Messages) 
If set, spamTags does NOT get prepended to the subject of the SpamLover-Message. 
Default: On 

-SpamLoversRe (Regular Expression to Identify  SpamLovers*) 
If a message matches this regular expression it will not been blocked, but tagged.  

-slMaxScore (Block Spamlover Messages Above This Score) 
Messages to e.g. baysSpamLovers  whose score exceeds this threshold will be blocked. For example: 75  

-spamLovers (All Spam-Lover*) 
Messages to Spam-Lovers are processed and filtered by ASSP, but get tagged with spamSubject and are not blocked. When a
 Spam-Lover is not the sole recipient of a message, the message is processed
 normally, and if it is found to be spam, it will not be delivered to the
 Spam-Lover. Accepts specific addresses (user@domain.com), user parts (user) or entire domains (@domain.com). Wildcards are supported (fribo*@domain.com). Default: postmaster|abuse.For example: fribo*@thisdomain.com|jhanna|@sillyguys.org
 
 This option and all SpamLover-Options below accepting a second score parameter like "user@your-domain.com=>70"
 If such a parameter is defined in any option for an entry and the recipient address matches this entry and the message score exceeds the parameter value, the message will be blocked.
 If there are multiple possible matches for a recipient address found, the generic longest match (and value) will be used.
 ASSP will use the highest found value for all recipients of an email.  

-baysSpamLovers (Bayesian Spam-Lover*) 
  

-baysSpamLoversRe (Regular Expression to Identify Bayesian SpamLover*) 
If a message matches this regular expression it will be considered a Bayesian SpamLover message.  

-blSpamLovers (Blacklisted Domains Spam-Lover*) 
  

-blackSpamLovers (SpamLover Black Regex Check*) 
  

-bombSpamLovers (Bomb Spam-Lover*) 
  

-hlSpamLovers (HELO Blacklisted Spam-Lover*) 
  

-hiSpamLovers (Valid/Invalid Helo*) 
  

-atSpamLovers (Bad Attachment Spam-Lover*) 
  

-spfSpamLovers (SPF Failures Spam-Lover*) 
  

-rblSpamLovers (DNSBL Failures Spam-Lover*) 
  

-uriblSpamLovers (URIBL Failures Spam-Lover*) 
  

-delaySpamLovers (SpamLover Greylisting/Delaying *) 
  

-isSpamLovers (Invalid Sender Spam-Lover*) 
  

-mxaSpamLovers (Missing MX Spam-Lover*) 
  

-ptrSpamLovers (Invalid/Missing PTR Spam-Lover*) 
  

-msSpamLovers (MessageScore Blocking Spam-Lover *) 
  

-sbSpamLovers (Country Blocking Spam-Lover *) 
  

-spamHaters (All SpamHaters*) 
SpamHaters are used to override SpamLovers / Testmodes / Tagmodes.
 If a recipient is set as as SpamHater, all spam-messages are blocked, scoring , testmode and spamlover are overwritten..
 Example: If you have set your entire domain as a SpamLover(s), but there are some addresses you still wish to block spam for. The message will only be blocked if all recipients are SpamHaters. Accepts specific addresses (user@example.com), user parts (user) or entire domains (@example.com).  Wildcards are supported (fribo*@example.com).For example: *fribo@example.com|jhanna|@example.org   

-baysSpamHaters (Bayesian SpamHater*) 
SpamHaters are used to override baysSpamLovers / allTestMode. It may also be used to increase scoring for DoBayesian with Addhater. Notes On Spam-Lover  

-npSize (Incoming Messages NoProcessing Size) 
This limit ensures that only incoming messages smaller than this limit are processed by ASSP. Most spam
isn't bigger than a few k. ASSP will treat incoming messages larger than this SIZE (in bytes) as 'NoProcessing' mail. Empty or 0 disables the feature. 
Default: 500000 

-npSizeOut (Message Size Limit Outgoing) 
ASSP will treat outgoing messages larger than this SIZE (in bytes) as 'No Processing' mail. Empty or 0 disables the feature.  
Default: 500000 

-noProcessingIPs (NoProcessing IPs*) 
Mail from any of these IP addresses and Hostnames will pass through without processing. newest example file is here
 
Default: file:files/ipnp.txt 

-noProcessing (NoProcessing Addresses*) 
Contains addresses of sender and recpients. All recipients must be marked as noprocessing. Accepts specific addresses (user@example.com), user parts (user) or entire domains (@example.com).  Wildcards are supported (fribo*@example.com). Better to use noProcessingFrom and noProcessingTo instead.  

-noProcessingFrom (NoProcessing Sender*) 
Mail from any of these addresses are proxied without processing. Accepts specific addresses (user@example.com), user parts (user) or entire domains (@example.com).  Wildcards are supported (fribo*@example.com). 
Default: file:files/noprocessingfrom.txt 

-noProcessingTo (NoProcessing Recipient*) 
Mail solely to any of these addresses are proxied without processing. All recipients must be marked as noprocessing. Accepts specific addresses (user@example.com), user parts (user) or entire domains (@example.com).  Wildcards are supported (fribo*@example.com). 
Default: file:files/noprocessingto.txt 

-noProcessingDomains (NoProcessing Domains*) 
Domains from which you want to receive all mail and  proxy without processing. Your ISP, domain registration, mail list servers, stock broker, or other key business partners might be good candidates. Note this matches the end of the address, so if you don't want to match subdomains then include the @. Note that buy.com would also match spambuy.com but .buy.com won't match buy.com. For example: sourceforge.net|@google.com|.buy.com 
Default: file:files/noprocessingdomains.txt 

-noNoProcessing (Do not mark these Addresses as Noprocessing*) 
Enter senders email addresses that you want to be processed, even if they are in noprocessing lists. You can list specific addresses (user@anydomain.com), addresses at any domain (user), or entire domains (@anydomain.com).  Wildcards are supported (fribo*@domain.com).For example: fribo@anydomain.com|jhanna|@sillyguys.org or place them in a plain ASCII file one address per line: 'file:files/nodelayuser.txt'.  

-npRe (Regular Expression to Identify NoProcessing Incoming Mails*) 
If a message matches this Perl regular expression ASSP will treat the message as a 'NoProcessing' mail. For example: X-Assp-VersionNotes On NoProcessing  

-redRe (Regular Expression to Identify Redlisted Mail*) 
If an email matches this Perl regular expression it will be 
considered redlisted.
The Redlist serves several purposes:
1) the Redlist is a list of addresses that cannot contribute to the 
whitelist and which are not considered local even if their mail is 
from a local computer. For example, if someone goes on a vacation and 
turns on their autoresponder, put them on the redlist until 
they return. Then as they reply to every spam they receive they won't 
corrupt your non-spam collection or whitelist: \[autoreply\]
2) Redlisted addresses will not be added to the Whitelist.
3) Redlisted messages will not be stored in the 
SPAM/NOTSPAM-collection. 
As all fields marked by * this field accepts 
a list separated by | or a plain ASCII file one address per line: 'file:files/redre.txt'.  
Default: file:files/redre.txt 

-whiteListedIPs (Whitelisted IPs*) 
They  contribute to the Whitelist and to Notspam. For example: 145.145.145.145|146.145.  All fields marked by '*' accept  a filepath/filename : 'file:files/ipwl.txt'.  

-whiteRe (Regular Expression to Identify Non-Spam* ) 
If an incoming email matches this Perl regular expression it will be considered non-spam.For example: Secret Ham Password|307\D{0,3}730\D{0,3}4[12]\d\d  

-whiteListedDomains (Whitelisted Domains and Addresses*) 
Domains and addresses from which you want to receive all mail. Your ISP, domain registration, mail list servers, stock broker, or other key business partners might be good candidates. Do not to put widely used domains here like hotmail.com. Put popular domains into whiteSenderBase. Note this matches the end of the address, so if you don't want to match subdomains then include the @. Note that 'example.com' would also match 'spamexample.com' but '.example.com' won't. Wildcards are supported. For example: sourceforge.net|group*@google.com|.example.com. *You may place them in a plain ASCII file one address per line:'file:files/whitedomains.txt' 
Default: sourceforge.net 

-WhitelistOnly (Reject All But Whitelisted Mail) 
Check this if you want to reject all mail from anyone NOT on the Whitelist ( whitelistdb ) and not marked noprocessing.   

-WhitelistOnlyAddresses (Reject All But Whitelisted Mail for these Addresses/Domains*) 
Put here addresses/domains which should only accept whitelisted/noprocessing mail. Accepts specific addresses (user@domain.com), user parts (user) or entire domains (@domain.com). Wildcards are supported (*@domain.com, abuse@*, *@*).    

-NoAutoWhite (Only Email-Interface Addition to Whitelist.) 
Check this box to  allow additions to the whitelist by EmailWhitelistAdd only.  

-NotGreedyWhitelist (Only the envelope-sender is compared to the whitelist) 
If this option is not set, all addresses in the FROM, SENDER, REPLY-TO, ERRORS-TO, or LIST-* header fields are processed. If this option is set only the envelope 'MAIL FROM\ will be used. 
Default: On 

-GreedyWhitelistAdditions (How to add Adresses to Whitelist) 
Defines what addresses are added to the whitelist if a message is considered to be from a whitelisted sender. 'all addresses' means all sender addresses in 'from|sender|reply-to|errors-to|list-' and all recipient addresses in 'to|cc|bcc' 
Default: envelope only 

-WhitelistLocalOnly (Only local or authenticated users contribute to the whitelist.) 
Normal operation allows all local, authenticated, or whitelisted users to contribute to the whitelist.Check this box to not allow whitelisted (but not local) users to add to the whitelist.  

-WhitelistLocalFromOnly (Only local users with a local domain in envelope contribute to the whitelist.) 
Check this box to prevent a local sender with non-local domain from contributing to the whitelist. (for example: redirected messages). 
Default: On 

-WhitelistAuth (Whitelist authenticated users.) 
Mails from 
authenticated users will be processed as whitelisted  

-UpdateWhitelist (Save Whitelist) 
Save a copy of the white list every this many seconds. Empty or Zero will prevent any saving.Notes On Whitelist 
Default: 3600 

-MaxWhitelistDays (Max Whitelist Days) 
This is the number of days an address will be kept on the whitelist without any email to/from this address. 
Default: 999 

-ValidateRWL (Enable Realtime Whitelist Validation) 
RWL: Real-time white list. These are lists of IP addresses that have
 somehow been verified to be from a known good host. Senders that pass RWL validation will pass IP-based filters. This requires an installed Net::DNS module in PERL.   

-RWLServiceProvider (RWL Service Providers*) 
Hostnames of RWLs to use separated by "|".Examples are: list.dnswl.org 
Default: list.dnswl.org 

-RWLmaxreplies (Maximum Replies) 
A reply is affirmative or negative reply from a RWL. The RWL module will wait for this number of replies (negative or positive) from the RWLs listed under Service Provider for up to the Maximum Time below. This number should be equal to or less than the number of RWL Service Providers listed to allow for randomly unavailable RWLs.  
Default: 1 

-RWLminhits (Minimum Hits) 
A hit is an affirmative response from a RWL. The RWL module will check all of the RWLs listed under Service Provider, and flag the email with a RWL 'pass' flag if equal to or more than this number of RWLs return a postive whitelisted response. If the number is less but not zero the email is marked 'neutral' 
Default: 1 

-RWLmaxtime (Maximum Time) 
This sets the maximum time to spend on each message performing RWL checks 
Default: 5 

-noRWL (Dont Validate RWL for these IPs*) 
Enter IP addresses that you don't want to be RWL validated, separated by pipes (|). For example: 145.145.145.145|146.145.  

-AddRWLHeader (Add X-Assp-Received-RWL Header) 
Add X-Assp-Received-RWL header to header of all emails processed by RWL. 
Default: On 

-RWLCacheInterval (RWL Cache Expiration Time) 
IPs in cache will be removed after this interval in days. 0 will disable the cache.    

-RWLLog (Enable RWL logging) 
Notes On RWL 
Default: standard 

-RelayLog (Enable Relay logging) 
Notes On Relaying 
Default: standard 

-acceptAllMail (Accept All Mail*) 
Relaying is allowed for these IP addresses and Hostnames. They  contribute also to the whitelist. This can take either a directly entered list of IP addresses and Hostnames separated by pipes or a plain ASCII file one address per line: 'file:files/acceptall.txt'. An IP range is defined e.g. '182.82.10.'. CIDR notation is accepted (182.82.10.0/24). Hyphenated ranges can be used (182.82.10.0-182.82.10.255)  

-relayHostFile (Relay Host File ) 
Similar to  acceptAllMail, but this is a file with an ABSOLUTE path, not relative to base. No IP-blocks supported. For example: /usr/local/assp/relayhosts  

-localDomains (Local Domains*) 
Put here are the domain names that your mail system considers local. Separate entries with |  or place them in a plain ASCII file one address per line: 'file:files/localdomains.txt'. Wildcards are supported. For example: example.org|*example.com
If ASSP finds no other hint that the domain is local, it  will reject messages to domains not listed here with 'RelayAttempt'. A successfull DoLDAP, DoVRFY or hit in LocalAddresses_Flat  will put the domain part of the queried address into ldaplistdb and will mark the domain as local.
You can set nolocalDomains to disable this check during setup and testing.
  
Default: file:files/localdomains.txt 

-localDomainsFile (Local Domains File) 
Similar to localDomains, but with absolute path to the file. Wildcards are not supported. For access to MTA generated files.   

-DoLocalIMailDomains (Local IMail domains) 
Consider domains in the IMail registry to be local  

-nolocalDomains (Skip Local Domain Check) 
Do not check relaying for invalid domains - let the MTA do it. This can be set to prevent 'RelayAttempt' errors. Attention: this will make ASSP an open relay, if the MTA behind it does not reject messages to unknown domains.  

-MaxRelayingErrors (Maximum Relaying Errors Per Session) 
The maximum number of Relaying Errors encountered before the
connection is dropped. Scoring is done  with meValencePB. 0 will not count Relaying Errors.  
Default: 3 

-relayHost (Relay Host) 
Your mail relayhost (smarthost). For example: mail.relayhost.com:25if you run Exchange/Notes and you want assp to update the nonspam database and the whitelist, then enter your smtp relay host here. Blank means no relayhost.   

-relayAuthUser (Username for  Authentication to Relay Host) 
The username used for SMTP AUTH authentication to the relayHost  -  if your ISP need authentication on the SMTP port. Supported authentication methodes are PLAIN, LOGIN, CRAM-MD5 and DIGEST-MD5 . If the relayhost offers multiple methodes, the one with highest security option will be used. The Perl module Authen::SASL must be installed to use this feature! The usage of this feature will be skipped, if the sending MTA uses the AUTH command. Leave this blank, if you do not want use this feature.  

-relayAuthPass (Password for  Authentication to Relay Host) 
The password used for SMTP AUTH authentication to the relayHost. Leave this blank, if you do not want use this feature.  

-relayPort (Relay Port) 
Tell your mail server to connect to this port as its smarthost/relayhost. For example: 225 Note that you'll want to keep the relayPort protected from external access by your firewall.You can supply an interface:port to limit connections.  

-allowRelayCon (Allow Relay Connection from these IPs*) 
Enter any addresses that are allowed to use the relayPort , separated by pipes (|). If empty, any ip address is allowed to connect to the relayPort. If this option is defined, keep in mind : Addresses defined in acceptAllMail are NOT automaticly included and have to be also defined here, if they should be allowed to use the relayPort. For example: 127.0.0.1|172.16..  

-ldLDAP (Do LDAP lookup for local domains) 
Check local domains against an LDAP database.Note: Checking this requires filling in LDAP DomainFilter ( ldLDAPFilter ).and NET::LDAP module in Perl.  

-ispip (ISP/Secondary MX Servers*) 
Enter any addresses or hostnames that are your ISP or backup MX servers, separated by pipes (|). These addresses will (necessarily) bypass Griplist, IP Limiting, Delaying, PenaltyBox, SPF, DNSBL and SRS checks unless the IP can be determined by ispHostnames (ISP Connecting IP). For example: 145.145.145.145|145.145.145.146.  

-contentOnlyRe (Regular Expression to Identify Forwarded Messages*) 
Put anything here to identify messages which should bypass all IP based filter like PB, Sender Validation, Griplist, IP Limiting, Delaying, SPF, DNSBL and SRS. For example:  email addresses of people who are forwarding from other accounts to their mailbox on your server.  

-ispHostnames (Regular Expression to Identify ISP/Secondary Hostnames*) 
Hostnames (regular expression) to lookup the IP that connected to the ISP/Secondary server.If found, this address is used to perform IP-based checks on forwarded messages. For example: mx1\.yourisp\.com or mx1\.yourisp\.net|mx2\.yoursecondary\.com . This hostnames are found in the 'Received:' header, like  'Received: from ...123.123.123.123... by mx1.yourisp.com'. The frontend IP must be listed in ispip. Leave this blank to disable the feature.   

-send250OKISP (Send 250 OK To ISP/Secondary MX Servers) 
Set this checkbox if you want ASSP to reply to IP addresses in ispip with '250 OK' instead of SMTP error code '554 5.7.1'.  
Default: On 

-PopB4SMTPFile (Pop Before SMTP DB File) 
Enter the DB database filename of your POP before SMTP implementation with records stored for dotted-quad IP addresses.For example: /etc/mail/popip.db  

-PopB4SMTPMerak (Pop Before SMTP Merak Style) 
If set Merak 7.5.2 is supported.  

-removeForeignBCC (Remove Unexpected BCC Recipients) 
Remove foreign bcc: header lines from the mail header 
Default: On 

-defaultLocalHost (Default Local Domain) 
If you want to be able to send mail to local users without a domain name then put the default local domain here.  Blank disables this feature. For example: assp.localNotes On Relaying 
Default: assp.local 

-NoExternalSpamProb (No Outgoing X-ASSP Header) 
Check this box if you don't want X-Assp- headers on outgoing mail. 
Default: On 

-npLocalRe (Regular Expression to Identify NoProcessing Local Mails*) 
If an outging message matches this Perl regular expression ASSP will treat the message as a 'NoProcessing' mail. For example: autoreply  

-blockLocalRe (Regular Expression to Identify Blocked Local Mails*) 
If an outging message matches this Perl regular expression ASSP will block the message.  

-LocalFrequencyInt (Local Frequency Interval) 
The time interval in seconds in which the number of envelope recipients per sending address should not 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. To give users the chance to inform an admin about such blocked mails, local mails to EmailAdmins are never blocked because of that feature.
    

-LocalFrequencyNumRcpt (Local Frequency Recipient Number) 
The number of envelope recipients per sending address that should not be exceeded 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. To give users the chance to inform an admin about such blocked mails, local mails to EmailAdmins are never blocked because of that feature. 
    

-LocalFrequencyOnly (Check local Frequency for this Users only*) 
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 (user@domain.com), user parts (user) or entire domains (@domain.com).  Wildcards are supported (fribo*@domain.com).
  For example: fribo*@thisdomain.com|jhanna|@sillyguys.org   

-NoLocalFrequency (Check local Frequency NOT for this Users*) 
A list of local addresses, for which the 'local frequency check' should not be done. Noprocessing messages will skip this check.
  Accepts specific addresses (user@domain.com), user parts (user) or entire domains (@domain.com).  Wildcards are supported (fribo*@domain.com).
  For example: fribo*@thisdomain.com|jhanna|@sillyguys.org   

-DoLocalSenderDomain (Do Local Domain Check for Local Sender) 
If activated, each local sender address must have a valid Local Domain - needs localDomains or localDomainsFile or ldLDAP or DoLocalIMailDomains.  

-DoLocalSenderAddress (Do Local Address Check for Local Sender) 
If activated, each local sender must have a valid Local Address - needs DoVRFY or DoLDAP or LocalAddresses_Flat.  

-LocalSender2NULL (Move Local Connection with wrong Sender Address to NULL) 
If set, ASSP will move all Local connections where the sender failed DoLocalSenderDomain or DoLocalSenderAddress to a NULL-connection. The sender will receive "250 OK".Notes On Control Outgoing  

-ValidateUserLog (Enable User Validation logging) 
 
Default: standard 

-LocalAddresses_Flat (Lookup Local Addresses from Here*) 
This is an optional list of local addresses for all MTAs behind ASSP. If the address is not found here ASSP will look for other methods of verification (DoLDAP, DoVRFY). If no ASSP-verification is used, the MTA behind ASSP will do it. You can list specific addresses (user@example.com), addresses at any local domain (user), or entire domains (@example.com).  Wildcards are supported (fribo*@example.com). Separate entries with a pipe (|).For example: fribo@example.com|jhanna|@example.org . You may use a plain ASCII file 'file:files/localuser.txt'.  

-LocalAddresses_Flat_Domains (Use Entries without leading @ as Domains) 
If set entries in LocalAddresses_Flat without leading '@' are handled as domains,for example 'example.com' means an entire domain.  

-LocalAddressesNP (Do Not Validate Local Addresses if in NoProcessing List) 
If a recipient is found in NoProcessing, the user validation is skipped.   

-RejectTheseLocalAddresses (Reject These Local Addresses*) 
If ANY recipient is on reject list, the message will not be delivered. Used for disabled legitimate accounts, where a user may have left the company. This stops wildcard mailboxes from getting these messages. You can list specific addresses (user@example.com), addresses at any local domain (user), or entire domains (@example.com).  Wildcards are supported (fribo*@example.com). The field accepts a list separated by '|' (for example: fribo*@example.com|@example.com|user) or a file designated as follows (path relative to the ASSP directory): 'file:files/filename.txt'. Putting in the file: will prompt ASSP to put up a button to edit that file. files is the subdirectory for files. The file does not need to exist, you can create it from the editor by saving it. The file must have one entry per line; anything on a line following a numbersign or a semicolon ( #  is ignored (a comment)  

-BlockLocalAddressesRe (Block Local Recipients Regular Expression*) 
Block all recipient addresses which match this RegEx. Note: if you want to block the pipe char '|' it must be masked with the mask character '\' . You may also use metacharacter brackets ([]) for this purpose. 
Default: [%|] 

-AllowLocalAddressesRe (Allow Local Recipient Addresses Regular Expression*) 
Allow only recipient addresses which match this RegEx.  

-TrapLog (Enable Trap logging) 
  

-spamtrapaddresses (Trap Addresses* ) 
Mail to any of these addresses will be blocked and the scoring value is added. These addresses are not checked for validity.  Accepts specific addresses (user@domain.com), user parts (user) or entire domains (@domain.com).  

-UseTrapToCollect (Use Penalty Trap Addresses To Collect) 
If set ASSP will use spamtrapaddresses to collect spams.  

-SpamTrap2NULL (Move Connection with Trap Addresses to NULL) 
If set, ASSP will move connections with spamtrapaddresses to a NULL-connection. The sender will receive "250 OK". 
Default: On 

-TrapReply (Trap Reply) 
SMTP reply for trapaddresses. Default: '550 5.1.1 User unknown: EMAILADDRESS'  The literal EMAILADDRESS (case sensitive) is replaced by the fully qualified SMTP recipient (e.g., thisuser@example.com). Make this empty if you do not want to be polite. 
Default: 550 5.1.1 User unknown: EMAILADDRESS 

-DoPenaltyMakeTraps (Cache Unknown Addresses) 
If enabled, unknown addresses are cached. If set to 'use for spamtrapaddresses' addresses which reach the limit in PenaltyMakeTraps 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. 
Default: use for spamaddresses 

-PenaltyMakeTraps (Unknown Address Frequency  Limit) 
Minimum number of times an address must appear during PBTrapCacheInterval before it will be used as spamaddress/spamtrapaddress in DoPenaltyMakeTraps. 
Default: 5 

-PBTrapCacheInterval (Address Cache Expiration) 
Addresses will be removed after this interval in days if the frequency in PenaltyMakeTraps is not reached.  
Default: 1 

-noPenaltyMakeTraps (Exceptionlist for Address Cache*) 
Addresses which should not be cached. Accepts specific addresses (user@example.com), user parts (user) or entire domains (@example.com).  Wildcards are supported (fribo*@example.com).  

-DoVRFY (Verify Recipients with SMTP-VRFY) 
If activated and the format 'Domain=>MTA' is encountered in
 vrfyDomains recipient addresses will be verified with SMTP-VRFY (if  VRFY is not supported 'MAIL FROM:' and 'RCPT TO:' will be used).
 If you know that VRFY is not supported with a MTA, you may put the MTA into VRFYforceRCPTTO.   

-vrfyDomains (VRFY Domains*) 
Put here the domain names that should be verified with SMTP-VRFY. Separate entries with |  or place them in a plain ASCII file one address per line: 'file:files/vrfydomains.txt'. 
Use the syntax: *mydomain.com=>smtp.mydomain.com|other.com=>mx.other.com:port to verify the recipient addresses with the SMTP-VRFY (if VRFY is not supported 'MAIL FROM:' and 'RCPT TO:' will be used) command on other SMTP servers. The entry behind => must be the hostname:port or ip-address:port of the MTA which is used to verify 'RCPT TO' addresses with a VRFY command! If :port is not defined, port :25 will be used. You can use an entry like ALL=>vrfyhost:port to define a VRFY host for all entries without the MTA part.  You have to enable the SMTP 'VRFY' command on your MTA - the 'EXPN' command should be enabled! This requires an installed Net::SMTP module in PERL. 
 If you have configured LDAP and enabled DoLDAP and ASSP finds a VRFY entry for a domain, LDAP search will be done first and if this fails, the VRFY will be used. So VRFY could be used for LDAP backup/fallback/failover!
 It is recommended to configure 'ldaplistdb' in the 'File Paths and Database' section when using this verify extension - so ASSP will store all verified recipients addresses there to minimize the querys on MTA's. There is no need to configure LDAP, but both VRFY and LDAP are using ldaplistdb. Please go to the 'LDAP setup' section to configure MaxLDAPlistDays and LDAPcrossCheckInterval or start a crosscheck now with forceLDAPcrossCheck. This three parameters belong also to VRFY. 
Default: file:files/vrfydomains.txt 

-VRFYQueryTimeOut (SMTP VRFY-Query Timeout) 
The number of seconds ASSP will wait for an answer of the MTA that is queryed with the VRFY command to verify a recipient address. 
Default: 5 

-VRFYforceRCPTTO (Force the usage of RCPT TO*) 
Define local MTAs here for which you want ASSP to force the usage of 'MAIL FROM:' and 'RCPT TO:' instead of the VRFY command. The definition of the MTA(s) has to be exactly the same as already defined in vrfyDomains (after the '=>') for example: smtp.mydomain.com|mx.other.com:port|10.1.1.1|10.1.1.2:125 .  

-DisableVRFY (Disable VRFY for External Clients) 
If you have enabled VRFY on your MTA to allow ASSP to verify addresses and you do not want external clients to use VRFY/EXPN - select this option.  

-MaxVRFYErrors (Maximum recipient verification Errors) 
The maximum number of failed 'RCPT TO' or 'VRFY' commands encountered before the connection is dropped. ASSP will drop the connection, if the count of '550 unknown user' errors, received from your 'smtpDestination'(MTA), reached this value! 
Default: 5 

-VRFYFail (VRFY failures return false) 
VRFY failures return false when an error occurs in VRFY lookups.  

-VRFYLog (Enable VRFY logging) 
 
Default: standard 

-DoMaxDupRcpt (Block Max Duplicate Recipients) 
Block remote servers that uses the same recipient address more times, than the number defined in MaxDupRcpt in the RCPT TO: command. Scoring is done with mdrValencePB . This check is skipped for outgoing, noprocessing, whitelisted and spamlovers mails. If a message has to be delayed, this check will score before the delay if set to block or score - and score and/or block on the next server request. 
Default: score 

-MaxDupRcpt (Maximum Allowed Duplicate Recipient Addresses) 
The maximum number of duplicate recipient addresses that are allowed in the sequence of the RCPT TO: commands!
  The number per mail is calculated by 'number of RCPT TO: commands  -  number of unique recipient addresses'.
  For example: if one address is used three times or two addresses are used each two times, will result in the same count - 2. Or if both is the case in one mail, the count will be 4.  

-ReplaceRecpt (Enable recipient replacement*) 
recommended if used: file:files/rcptreplrules.txt - default empty ! This enables recipient replacement. The replacement will be done before any ASSP check. For a more detailed description of the rules and options, read the file:    Recipient Replacement Test  

-sendAllPostmaster (Catchall Address for Messages to Postmaster) 
ASSP will deliver messages addressed to all postmasters of your local domains to this address. For example: postmaster@example.com  

-sendAllPostmasterNP (Skip Spam Checks for Postmaster Catchall) 
  

-sendAllAbuse (Catchall Address for Messages to Abuse) 
ASSP will deliver messages to all abuse addresses of your local domains to this address. For example: abuse@example.com  

-sendAllAbuseNP (Skip Spam Checks for Abuse Catchall) 
  

-DoRFC822 (Validate Recipient Address to Conform with RFC5322 ) 
If activated, each local address is checked to conform with the email format defined in RFC5322 .This requires an installed Email::Valid module in PERL. 
Default: On 

-CatchAll (Catchall per Domain*) 
ASSP will send to these addresses if no valid user is found in LocalAddresses_Flat or LDAP. For example: catchall@domain1.com|catchall@domain2.com  

-CatchallallISP2NULL (Move ISP Connection with wrong Recipient Address to NULL) 
If set, ASSP will move all ISP connections with wrong recipient addresses to a NULL-connection. The ISP will receive "250 OK" until the mail has passed, but the mail will not be sent to your MTA. This is done after CatchAll but before CatchAllAll is checked.  

-CatchAllAll (Catchall for All Domains) 
ASSP will send to this address if no valid user is found  in LocalAddresses_Flat or LDAP and no match is found in Catchall per Domain. For example: catchall@example.com  

-NullAddresses (NULL Connection Addresses*) 
ASSP will discard a message silently when encountering such an address in "MAIL FROM:" or "RCPT TO:". Accepts specific addresses (null@example.com), user parts (nobody) or entire domains (@example.com).  

-InternalAddresses (Accept Mail from Local Domains only*) 
These local addresses do not accept mail externally. Accepts specific addresses (user@example.com), user parts (user) or entire domains (@example.com). Wildcards are supported (fribo*@example.com).  

-SepChar (Separation Character for Subaddressing) 
RFC 3598 describes subaddressing with a Separation Character. A star ('*') is not allowed as Separation Character. Everything between Separation Character and @ is ignored (including Separation Character). For Example = '+' will allow user+subaddress@example.com.  

-EnableBangPath (Support Bang Path) 
If set, ASSP will support addresses like domainx!user@domainy and will convert them to user@domainx .  

-NoValidRecipient (No-Valid-Local-User Reply) 
SMTP reply for invalid Users. Default: '550 5.1.1 User unknown: EMAILADDRESS'  The literal EMAILADDRESS (case sensitive) is replaced by the fully qualified SMTP recipient (e.g., thisuser@example.com).Notes On Local Addresses 
Default: 550 5.1.1 User unknown: EMAILADDRESS 

-useHeloBlacklist (Use the Helo Blacklist) 
Use the list of blacklisted-helo hosts built by rebuildspamdb. Scoring is done with hlValencePB. 
Default: score 

-ValidateHeloLog (Enable Validate Helo Logging) 
 
Default: standard 

-DoSuspiciousHelo (Score Suspicious HELOs) 
Score servers with SuspiciousHeloRe in Helo. Scoring is done  with shValencePB 
Default: score 

-SuspiciousHeloRe (Regular Expression to Score Suspicious HELO**) 
Score Suspicious HELOs will check incoming HELOs for this. For example: file:files/invalidhelo.txt 
Default: file:files/invalidhelo.txt 

-DoIPinHelo ( Score Suspicious IPs in Helo) 
Score servers with reversed IP address in Helo and check for mismatch with sending IP. 
Default: score 

-DoFakedLocalHelo (Block Forged Helos) 
Block remote servers that claim to come from our Local Domain/Local IPs/Local Host. Scoring with fhValencePB. 
Default: block 

-myServerRe (Local Domains,IPs and Hostnames*) 
Local Domains, IP addresses and Hostnames are often use to fake (forge) the Helo. Include all IP addresses and hostnames for your server  here, localhost is already included. Include Local Domains of your choice here, if you deactivated the automatic use of the localDomains list.  For example: 11.22.33.44|mx.example.com|example.org  

-noHelo (Dont Validate HELO for these IPs*) 
Enter IP addresses that you don't want to be HELO validated.
   For example: 145.145.145.145|146.145  

-heloBlacklistIgnore (Dont block these HELOs*) 
HELO / EHLO greetings on this list will be excluded from the HELO checks. For example: host123.isp.com|host456.*.com  

-DoInvalidFormatHelo (Validate Format of HELO) 
If activated, the HELO is checked against the expression below. If the Regular Expression matches, the HELO is not ok. Scoring is done  with ihValencePB. 
Default: block 

-invalidFormatHeloRe (Regular Expression to Validate Format of HELO**) 
Invalidate Format HELO will check incoming HELOs for this. Each regex can be assigned a weight. If the score which results from weight is less than ihValencePB, the message will not be blocked (even if 'block' is set) but scored. 
 For example: \.user=>0.5|^\d+\.\d+\.\d+\.\d+$|^[^\.]+\.?$  or place them in a plain ASCII file one address per line: file:files/invalidhelo.txt 
Default: file:files/invalidhelo.txt 

-validFormatHeloRe (Regular Expression to Validate Format of HELO*) 
Validate Format HELO will check incoming HELOs according to rfc1123. For example: ^(([a-z\d][a-z\d-]*)?[a-z\d]\.)+[a-z]{2,6}$ .
  Notes On Validate Helo
    
Default: ^(([a-z\\d][a-z\\d-]*)?[a-z\\d]\\.)+[a-z]{2,6}$ 

-ValidateSenderLog (Enable Validate Sender Logging) 
 
Default: standard 

-DoBlackDomain (Do Blacklisted Addresses and Domains) 
 DoBlackDomain uses blackListedDomains and weightedAddresses. Scoring is done  with blValencePB. 
Default: block 

-DoBlackDomainWL (Blacklisting Addresses/Domains will overwrite WhiteListing) 
Do blacklisting addresses & domains in messages which are marked whitelisted by whiteRe, whiteListedDomains, whiteListedIPs or whitelistdb. 
Default: On 

-DoBlackDomainNP (Blacklisting Addresses/Domains will overwrite NoProcessing) 
Do blacklisting addresses & domains in messages marked 'noprocessing' by npRe, npSize, noProcessingDomains, noProcessingIPs or noProcessing.  

-blackListedDomains (Blacklisted Domains*) 
Addresses  and Domains from which you always want to reject mail, they only send you spam. Note this matches the end of the address, so if you don't want to match subdomains then include the @. Note that example.com would also match spamexample.com but .example.com won't match example.com. abc@example.com will match abc@example.com but won't match bbc@example.com. Wildcards are supported. newest file is here 
Default: file:files/blackdomains.txt 

-NotGreedyBlackDomain (Only the envelope-sender is added/compared to the BlackDomainlist) 
If not enabled all addresses in the FROM, SENDER, REPLY-TO, ERRORS-TO, or LIST-* header fields are checked.  

-noBlackDomain (Dont do Blacklisted for these Addresses and Domains* ) 
 Accepts specific addresses (user@example.com), user parts (user) or entire domains (@example.com). Wildcards are supported (fribo*@example.com).  

-weightedAddresses (Blackish &amp; Whitish Addresses** ) 
 Accepts specific addresses (user@example.com), user parts (user) or entire domains (@example.com). Wildcards are supported.  A positive weight will make the address 'blackish'. A negative weight will make the address into 'whitish'. For example: fribo*@example.com|@*.gov=>-0.5|@*.biz=>0.5 . 
Default: file:files/blackAddresses.txt 

-DoMsgID (Check Message IDs) 
Score messages with missing/suspicious/invalid Message-ID. Scoring is done by midmValencePB / midsValencePB / midiValencePB . 
Default: score 

-noMsgID (Dont Validate Message-IDs for these IPs*) 
Enter IP addresses that you don't want to be Message-ID validated, separated by pipes (|). For example: 127.0.0.1|192.168. 
Default:  127.0.0.|192.168.|10. 

-validMsgIDRe (Regular Expression to Validate Format of Message-ID*) 
Check Message IDs will check incoming messages for valid Message-IDs. For example: ^.+@.+\..+$   
Default: ^.+@.+\\..+$ 

-invalidMsgIDRe (Regular Expression to Invalidate Format of Message-ID**) 
Check Message IDs will check incoming messages for invalid Message-IDs.  

-DoNoValidLocalSender (Check External Sender for Local Address  ) 
If activated, each external sender from a domain listed in localDomains is checked against LocalAddresses_Flat, LDAP or is verified using VRFY. An external sender is a sender from an IP not in acceptAllMail, not authenticated and not coming through the relayPort. Scoring is done  with flValencePB. 
Default: block 

-DoNoSpoofing (Block Local Addresses from External Sender Alltogether) 
If activated, each external sender address with a domain listed in localDomains is regarded a spoofed address. An external sender is a sender from an IP not in acceptAllMail, not authenticated and not coming through the relayPort. flValencePB is used for scoring 
Default: score 

-DoNoSpoofing4From (Check Spoofing for From: Addresses) 
check spoofing also for 'From:' addresses. 
Default: On 

-noSpoofingCheckIP (Dont do Spoofing Check for these IPs* ) 
Enter IP addresses and Hostnames that you don't want to be checked for spoofing. For example:145.145.145.145|145.146.  

-noSpoofingCheckDomain (Dont do Spoofing Check for these Addresses/Domains* ) 
 Accepts specific addresses (user@example.com), user parts (user) or entire domains (@example.com). Wildcards are supported (fribo*@example.com).  

-DoRFC522Sender (Validate Sender Address to conform with RFC5322) 
Sender must be a valid address to conform with RFC5322. 
Default: On 

-DoPTRCheck (Reversed Lookup) 
If activated, each sender IP is checked for a PTR record. This requires an installed Net::DNS module in PERL. Scoring is done  with ptmValencePB.  

-DoPTRCheckInvalid (Reversed Lookup FQDN Validation) 
If activated - and Reversed Lookup is activated -, the PTR-FQDN record is checked against invalidPTRRe & validPTRRe. Scoring is done  with ptiValencePB  
Default: On 

-invalidPTRRe (Regular Expression to Invalidate Format of PTR**) 
Validate Format PTR will check PTR records for this. 
  newest files is here 
Default: file:files/invalidptr.txt 

-validPTRRe (Regular Expression to Validate Format of PTR*) 
Validate Format PTR will check PTR records for this. If found, the PTR will be considered valid
  newest example file is here 
Default: file:files/validptr.txt 

-whitePTRRe (Regular Expression to whitelist a PTR/IP*) 
Whitelist PTR will check PTR records for this. If found, the IP will be whitelisted
  newest example file is here 
Default: file:files/whiteptr.txt 

-PTRCacheInterval (Reversed Lookup Cache Refresh Interval) 
IPs in cache will be removed after this interval in days. 0 will disable the cache.   
Default: 3 

-DoDomainCheck (Validate MX or A Record) 
If activated, the sender address and each address found in the following header lines (ReturnReceipt:, Return-Receipt-To:, Disposition-Notification-To:, Return-Path:, Reply-To:, Sender:, Errors-To:, List-...:) is checked for a valid MX or A record. Scoring is done for non existing MX record and non existing A record - a messages failes (block), if both records are not found.  

-MXACacheInterval (Validate Domain MX Cache Refresh Interval) 
IP's in cache will be removed after this interval in days. 0 will disable the cache. 
Default: 3 

-DoNoFrom (Check For Existing From: Line ) 
Scoring is done  with fromValencePB. 
Default: score 

-removeDispositionNotification (Remove Disposition Notification Headers) 
If set, all headers "ReturnReceipt: , Return-Receipt-To: and Disposition-Notification-To:" will be removed (except whitelisted and noprocessing mails). Select this to prevent unwanted whitelisting of spammers . 
  Notes On Validate Sender
   
Default: On 

-DelayIP (Simple IP Greylisting) 
Enable simple delaying for IP's in black penaltybox with totalscore above this value. An value of zero or empty disables this feature. 
Default: 50 

-DelayIPTime (Simple IP Greylisting Embargo Time) 
Enter the number of minutes for which delivery, related with IP address of the sending host, is refused with a temporary failure. Default is 5 minutes. 
Default: 5 

-noBlockingIPs (Do not check these IPs in IP-based filters*) 
Manually maintained list of IP addresses and Hostnames which should not be used in in IP-based filters like ValidateRBL.  An IP range is defined e.g. '182.82.10.'. CIDR notation is accepted (182.82.10.0/24). Hyphenated ranges can be used (182.82.10.0-182.82.10.255)  

-DoDropList (Do Deny Connections from these IPs) 
If activated, the IP is checked against the droplist . The droplist is downloaded if a new one is available and contains the Spamhaus DROP List. See "http://www.spamhaus.org/drop/drop.lasso". 
Default: block 

-DoDenySMTP (Do Deny Connections from these IPs) 
If activated, the IP is checked against denySMTPConnectionsFrom. 
Default: block 

-denySMTPConnectionsFrom (Deny Connections from these IPs*) 
Manually maintained list of IP addresses and Hostnames which should be blocked. IP addresses and Hostnames in noPB, acceptAllMail, ispip, whiteListedIPs, noProcessingIPs, noBlockingIPs will pass. For example: server.example.com|145.145.145.145|145.146.  

-DoDenySMTPstrict (Do Deny Connections from these IP addresses and Hostnames Early) 
If activated, the IP is checked against denySMTPConnectionsFromAlways.   
Default: block 

-denySMTPConnectionsFromAlways (Deny Connections from these IPs Strictly*) 
List of IP addresses and Hostnames which should strictly be blocked before body and header is downloaded.  IP addresses and Hostnames in noPB, acceptAllMail, ispip, whiteListedIPs, noProcessingIPs, noBlockingIPs will pass.  
Default: file:files/denyalways.txt 

-denySMTPLog (Enables Logging for Deny SMTP Connections From) 
 
Default: standard 

-DenyError (Deny Error) 
SMTP error message to reject connections. Will be used from  and denySMTPConnectionsFromAlways and DoPenaltyExtreme. For example: 554 5.7.2 Service denied, closing transmission channel.  
Default: 554 5.7.2 Service denied, closing transmission channel 

-DoSameSubject (Check Number of Same Subjects) 
Scoring is done  with isValencePB. 
Default: block 

-maxSameSubject (Limit Number of IP addresses  Per Subject) 
The number of equal subjects during  maxSameSubjectExpiration. If a subject appears more often than this it will be banned from future connections until the expiration is reached. 5 connections are typically enough. If left blank or 0, there is no limit imposed by ASSP. 
Default: 5 

-maxSameSubjectExpiration (Expiration of Limit Number) 
The number of seconds that must pass before a subject blocked by maxSameSubject is allowed to connect again. 
Default: 1800 

-DoFrequencyIP (Check Frequency - Maximum Connections Per IP) 
Scoring is done  with ifreqValencePB. 
Default: block 

-maxSMTPipConnects (Maximum Frequency of Connections Per IP ) 
The maximum number of SMTP connections an IP Address can make during the maxSMTPipDuration (IP Address Frequency Duration). If a server makes more than this many connections to ASSP within the maxSMTPipDuration (IP Address Frequency Duration) it will be banned from future connections until the maxSMTPipExpiration (IP Address Frequency Expiration) is reached. This can be used to prevent server overloading and DoS attacks. 10 connections are typically enough. If left blank or 0, there is no limit imposed by ASSP. IP addresses in noPB, noDelay, acceptAllMail, ispip, whiteListedIPs, noProcessingIPs, PB-whitebox are excluded from SMTP session limiting, whitelisted and noprocessing addresses are honored.  
Default: 10 

-maxSMTPipDuration (Maximum Frequency of Connections Per IP Duration) 
The window (in seconds) during which the maxSMTPipConnects (IP Frequency) (see above for more details) will be scrutinized for each IP. 
Default: 90 

-maxSMTPipExpiration (Expiration of Maximum Frequency) 
The number of seconds that must pass before an IP address blocked by the maxSMTPipConnects (IP Address Frequency) setting is allowed to connect again. 
Default: 3600 

-DoDomainIP (Check Number of IP addresses Per Domain) 
Scoring is done  with idValencePB.  

-maxSMTPdomainIP (Limit Number of IP addresses  Per Domain) 
The number of IP(subnet) switches a domain may have during the maxSMTPdomainIPExpiration (Limit Different IP addresses Per Domain Expiration). If a domain switches more often than this it will be banned from future connections until the Expiration is reached. 10 connections are typically enough. If left blank or 0, there is no limit imposed by ASSP.   
Default: 10 

-maxSMTPdomainIPExpiration (Expiration of Limit Number) 
The number of seconds that must pass before a domain blocked by maxSMTPdomainIP settingis allowed to connect again. 
Default: 1800 

-maxSMTPdomainIPLD (Do Not Limit Different IP addresses For Local Domains*) 
This prevents local domains from limiting. 
Default: On 

-maxSMTPdomainIPWL (Do Not Limit Different IP addresses For These Domains*) 
This prevents specific domains from limiting. For example: yahoo.com|hotmail.*.com|gmail.com
  Notes On IP Blocking
   
Default: gmx.de|t-online.de|yahoo.com|hotmail.com|gmail.com 

-SenderBaseLog (Enable SenderBase Logging) 
 
Default: standard 

-AddSenderBaseHeader (Add SenderBase Header) 
 
Default: On 

-DoOrgWhiting (Do Organization Scoring ) 
If activated, each sending IP address has its assigned organization / domain
looked up and scored with sworgValencePB. This requires an installed Net::SenderBase module in PERL.  
Default: score 

-whiteSenderBase (White Organizations and Domains in SenderBase**  ) 
If the organization or domain  in the SenderBase IP description matches this Perl regular expression the message will be considered non-spam, the total messagescore will be decreased by sworgValencePB. newest example file (whiteorg.txt) is here 
Default: file:files/whiteorg.txt 

-DoOrgBlocking (Do Organization Blocking) 
If activated, each sending IP address has its assigned organization
looked up . This requires an installed Net::SenderBase module in PERL. Scoring is done  with sborgValencePB 
Default: monitor 

-blackSenderBase (Blacklisted Organizations and Domains in SenderBase** ) 
If the organization or domain in the SenderBase IP description matches this Perl regular expression the message will be considered spam.  

-DoCountryBlocking (Do Country Blocking) 
If activated, each sending IP address has it's assigned country
looked up and compared to CountryCodeBlockedRe. This requires an installed Net::SenderBase module in PERL. Messages from these countries will increase the total MessageScore using bccValencePB. 
Default: monitor 

-CountryCodeBlockedRe (Blocked Countries**) 
Messages from IP addresses based in these countries will be blocked if DoCountryBlocking is set accordingly. For example: CN|KR|RU|JP|TR|TH|PL|LT|CL|RO. "all" will block all foreign countrycodes which are not in 'Suspicious Country Codes' or 'Ignore Country Codes'. See: English country names and code elements.   

-DoCountryBlockingWL (Do Country Blocking for Whitelisted ) 
Enable Country Blocking for whitelisted messages.  

-DoCountryBlockingNP (Do Country Blocking for NoProcessing) 
Enable Country Blocking for noprocessing messages.  

-DoSenderBase (Do Suspicious Country Scoring) 
If activated, each sending IP address has it's assigned country
looked up and compared to CountryCodeRe.  
Default: score 

-CountryCodeRe (Suspicious Countries**) 
Messages from IP addresses based in these countries will increase the MessageScore. For example: CN|NG|UA|GR|HU|SA=>0.5. A positive or negative weight is possible, Messages from these countries will increase the total MessageScore using sbsccValencePB.  
Default: CN|NG|UA|GR|HU|SA|IN|IE|PT|MD|PE|CZ|TW|BR|CL|ID|PH|CN|KR|RU|JP|TR|TH|PL|LT|CL|RO 

-NoCountryCodeRe (Ignore Country Codes from these Countries*) 
Messages from IP addresses based in these countries will will be ignored in CountryCode checks.  

-MyCountryCodeRe (Home Countries**) 
Put here your own country code(s) (for example: US). Messages from IP addresses based in these countries will decrease the total MessageScore using sbhccValencePB, messages from other countries will increase the total MessageScore using sbfccValencePB if ScoreForeignCountries is set.   

-ScoreForeignCountries (Score Foreign Countries) 
Messages from countries not in MyCountryCodeRe, NoCountryCodeRe and CountryCodeRe will increase the total messageScore using sbfccValencePB. 
Default: On 

-SBCacheInterval (Country Cache Refresh Interval) 
IPs in cache will be removed after this interval in days. 0 will disable the cache.  
  Country Codes
   
Default: 3 

-DoPenaltyMessage (MessageScoring) 
If this feature is selected, the total score for all checks during a message is used to determine if the email should be considered Spam. If the combined score is greater than MessageScoringLowerLimit (MessageLimit for WarningTag) and less than or equal MessageScoringUpperLimit (MessageLimit for Blocking) the message will not be blocked but get the MessageScoringWarningTag. If the combined score is greater than the MessageScoringUpperLimit and blocking is selected the message will be blocked. If testmode is selected the message will not be blocked but tagged with spamSubject. 
Default: block 

-AddScoringHeader (Add Message Scoring Header) 
Adds a line to the email header "X-Assp-Score: " 
Default: On 

-MessageLog (Enable Message Scoring logging) 
 
Default: standard 

-spamFriends (Spam Friends **) 
A list of local user addresses that when matched will reduce the messagescore with friendsValencePB. This will make the scoring filter more softly. if you use negative weights here, the messagescore will be increased and the scoring filter will be more sharply. Accepts specific addresses (user@domain.com), user parts (user) or entire domains (@domain.com). Wildcards are supported (fribo*@domain.com). A second parameter separated by "=>" specifies the weight (multiplier) of friendsValencePB (default = -10). For example: @example.com=>0.5 will add -5 to the score of mails from @example.com.   

-friendsValencePB (&lt;span class=&quot;positive&quot;&gt;Spam Friends Score&lt;/span&gt;) 
 Bonus MessageScoring if the recipient is in spamFriends. 
Default: -10 

-MessageScoringLowerLimit (MessageScoring Lower Limit ) 
MessageScoring will tag messages with totalscore higher than this limit and not higher than MessageScoringUpperLimit.   
Default: 47 

-MessageScoringWarningTag (Warning Tag) 
Used instead of spamSubject if totalscore is  higher than MessageScoringLowerLimit and not higher than MessageScoringUpperLimit.  
Default: [PossibleSpam] 

-MessageScoringUpperLimit (MessageScoring Upper Limit) 
If MessageScoring is done  to block, it will block messages whose totalscore is  equal or higher than this threshold.Notes On Message Scoring
   
Default: 50 

-DoPenalty (IP Scoring) 
The PenaltyBox scores IP addresses based on some events and stores them into a BlackBox. The totalscore is used by DoPenaltyMessage for assigning a reputation. The total is also used by DelayIP.
There is also an extreme level - PenaltyExtreme - which can be used to export IP addresses with very bad reputation.. The WhiteBox stores IP addresses  which should not be put into the BlackBox. The WhiteBox is always enabled. If an address is in the whitelist or whitedomain, the IP goes into the WhiteBox too. The WhiteBox is one of the sources  Delaying/Greylisting uses to determine when delaying should not be done. Entries in noPB (Don't do penalties for these IP addresses ) or ispip (ISP/Secondary MX Servers) will prevent from penalties. Select 'enabled' to fill WhiteBox and BlackBox. This will not block IP addresses directly but enables  DoPenaltyMessage, DoPenaltyExtreme and DelayIP. 
Default: enabled 

-PenaltyLog (Enable PenaltyBox logging) 
 
Default: standard 

-PenaltyDuration (Penalty Interval) 
IP addresses will be kept in the BlackBox if their score exceeds the Penalty Limit during this interval in minutes. 
Default: 60 

-PenaltyLimit (Penalty Limit) 
PB will block messages from IP addresses whose totalscore exceeds this threshold during PenaltyDuration. For example: 50 
Default: 50 

-PenaltyExpiration (Expiration Time) 
Penalties with a score lower than PenaltyExtreme will expire after this number of minutes. If set to Zero the Penalty BlackBox will be deleted and started from scratch. 
Default: 360 

-noPB (Dont add these IP addresses and Hostnames to BlackBox* ) 
Enter IP addresses that you don't want to be in BlackBox. For example:145.145.145.145|145.146.  

-noPBwhite (Dont add these IP addresses to WhiteBox*) 
Enter IP addresses and Hostnames that you don't want to be in WhiteBox.  
Default: file:files/nopbwhite.txt 

-WhiteExpiration (Expiration Time for WhiteBox Entries) 
The WhiteBox is always activated. IP addresses in WhiteBox will allow content-related checks like Bayesian, URIBL, Bomb but skip IP-related checks like RBL. WhiteBox entries will expire after this specified number of days. For example: 30 
Default: 30 

-PenaltyUseNetblocks (Use IP Netblocks) 
Perform the IP address checks of the sending host based on the /24 subnet rather than on the specific IP. Part of DoPenalty  
Default: On 

-CleanPBInterval (Clean Up PB Databases) 
Delete outdated entries from blackbox and whitebox databases every this many hours.
  Note: the current timeout must expire before the new setting is loaded, or you can restart.
  Defaults to 6 hours. 
Default: 6 

-PenaltyExtreme (Extreme Scoring Threshold) 
 For example: 150. 
Default: 150 

-ExtremeExpiration (Expiration Time for Extreme Penalties) 
Penalties with score higher than PenaltyExtreme will expire after this number of days. If set to Zero nothing will be deleted. For example: 7 
Default: 7 

-DoExtremeExport (Do Export Penalty BlackBox Extreme) 
  

-DoExtremeExportAppend (Append Export File) 
Do not overwrite the export file but append to it.  

-ExportUseNetblocks (Use IP Netblocks) 
Export the IP address  based on the /24 subnet  rather than on the specific IP.   

-exportInterval (Export BlackBox Extreme File Interval) 
 Exported Penalty Black Box Extreme File every this hours.
  Defaults to 6 hours. 
Default: 6 

-exportExtremeBlack (Exported BlackBox Extreme File ) 
IPs in Penalty BlackBox which surpassed the extreme level will be regularly stored into this file. 
Default: file:files/exportedextreme.txt 

-PenaltyExtremeLog (Enable PenaltyBox Extreme logging) 
Notes On PenaltyBox
   
Default: standard 

-globalClientName (client registration name) 
The Name of this global-client for registation on the global-server. This entry has to be the full qualified DNS-Name of the IP-address over which ASSP is doing HTTP-requests! If you are using a HTTP-Proxy, this should be the public IP-address of the last Proxy in chain! This DNS-Name has to be resolveable worldwide and the resolved IP-address has to match the ASSP-HTTP-connection-IP-address. It is not possible to use an IP-address in this field! Dynamic DNS-Names like "yourdomain.dyndns.org" are supported!
 To use the global penalty box, you will need a paid subscription. To get registered and/or to get more information, please send an email with your personal/company details and the globalClientName to "assp.globalpb@thockar.com".
 The name of this client has to be known by the global server before it could be registered from here. Please wait until you've got an information, that your client name is known by the global server.
 In addition to Compress::Zlib this requires an installed LWP::UserAgent module in PERL.  

-globalClientPass (client registration password) 
If the global client is registered on the global-server, you will see a number of "*" in this field. This field is readonly.  

-globalClientLicDate (client subscription expiration date) 
The date of license/subscription expiration for this global client. If this date is exceeded, no upload and download of global PB will be done! This field is readonly.  

-DoGlobalBlack (Enable the Global-Black-Penalty) 
Enables the upload and download of Black-Penalty-Box-Entries, if the client is registered on the global-PB-server.  

-globalValencePB (Value for Global-Black-PB Entries) 
This penalty-value will be given to downloaded Black-Penalty-Box-Entries. As long as entries have the "GLOBALPB" state, they will never become extreme-Black. It is recommended to set this value above PenaltyLimit! 
Default: 20 

-globalBlackExpiration (Expiration for Global-PB-Black Records) 
Global-Black-Penalties will expire after this number of hours. 
Default: 48 

-DoGlobalWhite (Enable the Global-White-Penalty) 
Enables the upload and download of White-Penalty-Box-Entries, if the client is registered on the global-PB-server.  

-globalWhiteExpiration (Expiration for Global-PB-White Records(days)) 
Global-White-Penalties will expire after this number of days. 
Default: 7 

-GPBDownloadLists (Download List and Regex Updates from GPB-Server) 
Select, if assp should download updates for lists and regular expressions from the global penaltybox server. Downloads will be done to the 'download' folder. If install is selected, the downloaded lines will merged in to the defined files (file:...). If you want to disable a specific line in any of your files, do not delete the line, instead commed it out - putting an '#' or ';' in front of the line. If any list is not configured using the 'file:...' option, only the download will be done, even if install is selected. 
Default: download 

-GPBautoLibUpdate (Download Plugin and Library Updates from GPB-Server) 
Select, if assp should download updates for Plugins or Library-Files (../lib) from the global penaltybox server. Downloads will be done to the 'download' folder. If install is selected, the downloaded Plugins and/or modules will be installed in to there original location, if an older version of the file still exists. If an older version is not found, only the download will be done. To activate updated Plugins or modules a restart of assp is required. This feature will not force an automatic restart of assp!.
Notes On Global Penalty Box 
Default: download and install 

-autValencePB (Bad SMTP Authentication, default=60 +) 
Message/IP scoring
 
Default: 60 

-baValencePB (Bad Attachment, default=20 +) 
Message/IP Scoring 
Default: 20 

-backsctrValencePB (Backscatter detection, default=10 +) 
MessageScoring 
Default: 10 

-baysValencePB (Bayesian) 
Message/IP Scoring 
Default: 49 

-bayslocalValencePB (Bayesian for Local Messages) 
Message/IP Scoring 
Default: 55 

-baysconfidenceValencePB (Bayesian Confidence) 
Message/IP Scoring 
Default: 10 

-blValencePB (Blacklisted Domain) 
Message/IP Scoring 
Default: 30 

-bombSuspiciousValencePB (Bomb Suspicious - scoring only +) 
MessageScoring 
Default: 25 

-bombValencePB (Bomb Expression +) 
Message/IP Scoring 
Default: 25 

-blackValencePB (Bomb Black Expression, default=20 +) 
Message/IP Scoring 
Default: 25 

-erValencePB (Empty Recipients, default=5 +) 
Message/IP Scoring 
Default: 5 

-dropValencePB (Match in Droplist) 
For Message & IP scoring in DoDroplist. 
Default: 40 

-fhValencePB (Forged HELO, default=150 +) 
Message/IP Scoring 
Default: 150 

-fiphValencePB (Suspicious HELO: IP in HELO, default=10 +) 
Message/IP Scoring 
Default: 5 

-flValencePB (Invalid Local Sender, default=20 +) 
Message/IP Scoring 
Default: 20 

-hlValencePB (Blacklisted HELO, default=20 +) 
Message/IP Scoring 
Default: 20 

-iaValencePB (Internal Only Address, default=25 +) 
Message/IP Scoring 
Default: 25 

-idValencePB (Domain Changing IP Frequency, default=150 +) 
Message/IP Scoring 
Default: 150 

-isValencePB (Subject Changing IP Frequency, default=150 +) 
Message/IP Scoring 
Default: 150 

-ifValencePB (IP Frequency, default=150 +) 
Message/IP Scoring 
Default: 150 

-idleValencePB (Timeout Score) 
For IP scoring with smtpIdleTimeout.  

-iplValencePB (IP Parallel Sessions, default=5 +) 
Message/IP Scoring 
Default: 5 

-ihValencePB (Invalid HELO, default=10 +) 
Message/IP Scoring 
Default: 10 

-shValencePB (Suspicious HELO Score) 
For Message & IP scoring with SuspiciousHeloRe. 
Default: 10 

-irValencePB (Invalid Recipient, default=5 +) 
Message/IP Scoring 
Default: 5 

-mdrValencePB (Duplicate Recipient, default=10 +) 
Message/IP Scoring 
Default: 10 

-midmValencePB (Missing Message-ID, default=10 +) 
Message/IP Scoring 
Default: 10 

-midsValencePB (Suspicious Message-ID, default=10 +) 
Message/IP Scoring 
Default: 10 

-midiValencePB (Invalid Message-ID, default=10 +) 
Message/IP Scoring 
Default: 10 

-meValencePB (Max Errors Exceeded, default=10 +) 
Message/IP Scoring 
Default: 10 

-msigValencePB (Invalid MSGID-signature) 
MessageScoring 
Default: 455 

-mxValencePB (Missing MX) 
Message/IP Scoring 
Default: 15 

-mxaValencePB (Missing MX &amp;amp; A Record) 
Message/IP Scoring 
Default: 25 

-nofromValencePB (No From Score, default=25 +) 
For Message/IP scoring in DoNoFrom. 
Default: 50 

-pbeValencePB (Extreme Bad IP History) 
MessageScoring 
Default: 45 

-gripValencePB (GRIP value, default=15) 
MessageScoring 
Default: 15 

-ptmValencePB (Missing PTR Record, default=10) 
Message/IP Scoring 
Default: 10 

-ptiValencePB (Invalid PTR Record, default=15 ) 
Message/IP Scoring 
Default: 15 

-rblnValencePB (DNSBL Neutral, default=35 +) 
Message/IP Scoring 
Default: 35 

-rblValencePB (DNSBL Failed, default=100 +) 
Message/IP Scoring 
Default: 100 

-rlValencePB (Failed Relay Attempt, default=10 +) 
Message/IP Scoring 
Default: 10 

-reValencePB (Recipients Empty Score +) 
Message/IP Scoring 
Default: 5 

-rwlValencePB (RWL found) 
 Bonus for Message/IP scoring in ValidateRWL 
Default: -25 

-sbnValencePB (No Organization and No CountryCode) 
For Message & IP scoring in DoOrgBlocking and DoCountryBlocking 
Default: 10 

-sworgValencePB (White Organizations Score) 
 Bonus for Message/IP scoring in DoOrgWhiting 
Default: -35 

-sbsccValencePB (Suspicious Country Code) 
Message/IP scoring in DoSenderBase 
Default: 10 

-bccValencePB (Blocked Country Code Score) 
Message/IP scoring in DoSenderBase 
Default: 25 

-sbfccValencePB (Foreign Country Code Score) 
Message/IP scoring in DoSenderBase 
Default: 10 

-sbhccValencePB (&lt;span class=&quot;positive&quot;&gt;Home Country Code Score, &lt;/span&gt; ) 
 Bonus for Message/IP Scoring  in DoSenderBase  

-sborgValencePB (Blocked Organizations Score) 
Message/IP scoring in DoSenderBase 
Default: 25 

-spfpValencePB (SPF Pass Score, ) 
 Bonus for Message/IP scoring with SPF  

-spfnValencePB (SPF Neutral) 
Message/IP scoring 
Default: 5 

-spfsValencePB (SPF Softfailed) 
Message/IP scoring 
Default: 20 

-spfnonValencePB (SPF None) 
Message/IP scoring  

-spfuValencePB (SPF Unknown) 
Message/IP scoring  

-spfeValencePB (SPF Error) 
Message/IP scoring 
Default: 5 

-spfValencePB (SPF Failed) 
Message/IP scoring 
Default: 30 

-srsValencePB (SRS Validate Bounce Failed Score, default=10 +) 
For Message/IP scoring in SRSValidateBounce 
Default: 10 

-stValencePB (Penalty Trap Address, default=50 +) 
For Message/IP scoring 
Default: 50 

-uriblnValencePB (URIBL Neutral+) 
Message/IP Scoring 
Default: 30 

-uriblValencePB (URIBL Failed+) 
Message/IP Scoring 
Default: 55 

-vsValencePB (Virus suspicious, default=25) 
MessageScoring 
Default: 25 

-vdValencePB (Virus detected, default=50 +) 
Message/IP Scoring 
Default: 50 

-whiteValencePB (&lt;span class=&quot;positive&quot;&gt;White Expression Matching+&lt;/span&gt;) 
For Message & IP scoring with whiteRe 
Default: -50 

-teValencePB (TestRe Valence, default=20 +) 
Valence for testing testRe
  Notes On Penalty Box
   
Default: 20 

-EnableDelaying (Enable Delaying/Greylisting) 
Enable Greylisting as described at Greylisting-whitepaper.
   ASSP will "temporarily reject" any email from a sender it does not recognize. If the mail is legitimate the originating server will, after a delay, try again and, if sufficient time has elapsed, the email will be accepted. If the mail is from a spam sender, sending to many thousands of email addresses, it will probably not be retried.
   Greylisting involves sending a temporary 451 SMTP error code to the sending server when a message is received, along with sending this error code ASSP creates a Triplet and stores this. On the second delivery attempt if the Embargo Time set by the ASSP admin for the Triplet has been surpassed the message will be accepted and a Tuplet will be created and not delayed again for an Expiry Time set by the ASSP admin. 
Default: On 

-DelayLog (Enable Greylisting/Delaying logging) 
 
Default: standard 

-DelayWL (Whitelisted Greylisting) 
Enable Greylisting for whitelisted senders.  

-DelayNP (NoProcessing Greylisting) 
Enable Greylisting for noprocessing senders.  

-DelaySL (spamLovers Greylisting) 
Enable Greylisting for addresses in spamLovers. 
Default: On 

-DelayAddHeader (Add X-Assp-Delay Header) 
Add X-Assp-Delay header to all emails. 
Default: On 

-DelayEmbargoTime (Embargo Time) 
Enter the number of minutes for which delivery, related with new 'triplet' (IP address of the sending host + mail from + rcpt to), is refused with a temporary failure. 
Default: 5 

-DelayWaitTime (Wait Time) 
Enter the number of hours to wait for delivery attempts related with recognised 'triplet'; delivery is accepted 
  immediately and the 'tuplet' (IP address of the sending host + sender's domain) is whitelisted. 
Default: 28 

-DelayExpiryTime (Expiry Time) 
Enter the number of days for which a whitelisted 'tuplet' is considered valid. 
Default: 36 

-DelayUseNetblocks (Use IP Netblocks) 
Perform the IP address checks of the sending host based on the /24 subnet it is at rather than the specific IP. 
  This feature may be useful for legitimate mail systems that shuffle messages among SMTP clients between retransmissions. 
Default: On 

-DelayNormalizeVERPs (Normalize VERP Addresses) 
Some mailing lists (such as Ezmlm) try to track bounces to individual mails, rather than just individual recipients, which creates a variation on the VERP method where each email has its own unique envelope sender. Since the automatic whitelisting  that is built into Greylisting depends on the envelope addresses for subsequent emails being the same, the greylisting filter will attempt to normalize the unique sender addresses, when this option is checked. 
Default: On 

-DelayMD5 (Use MD5 for DelayDB) 
Message-Digest algorithm 5 is a cryptographic hash function and adds some level of security to the delay database. Must be set to off if you want to list the database with DelayShowDB/DelayShowDBwhite. 
Default: On 

-DelayShowDB (Show Delay/Greylisting Database) 
The directory/file with the delay local file. Obsolete if you use 'mysql' in delaydb. 
Default: file:delaydb 

-DelayShowDBwhite (Show Delay/Greylisting Save Database) 
The directory/file with the white-delay local file. Obsolete if you use 'mysql' in delaydb. 
Default: file:delaydb.white 

-DelayExpireOnSpam (Expire Spamming Whitelisted Tuplets) 
If a whitelisted 'tuplet' is ever associated with spam, viri, failed rbl, spf etc, it is removed from whitelisted tuplets database. 
  This renews the temporary embargo for subsequent mail involving the tuplet. 
Default: On 

-CleanDelayDBInterval (Clean Up Delaying Database) 
Delete outdated entries from triplets and whitelisted tuplets databases every this many seconds.
  Note: the current timeout must expire before the new setting is loaded, or you can restart.
  Defaults to 3 hours. 
Default: 10800 

-noDelay (Dont Delay these IPs*) 
Enter IP addresses that you don't want to be delayed, separated by pipes (|). There are misbehaving MTAs that will not be able to get a legitimate email through a Greylisting server because they do not try again later.newest example file is here 
Default: file:files/nodelay.txt 

-noDelayAddresses (Do not Delay these Addresses*) 
Enter sender/recipient email addresses that you don't want to be delayed, separated by pipes (|). You can list specific addresses (user@anydomain.com), addresses at any domain (user), or entire domains (@anydomain.com).  Wildcards are supported (fribo*@domain.com).For example: fribo@anydomain.com|jhanna|@sillyguys.org or place them in a plain ASCII file one address per line: 'file:files/nodelayuser.txt'.  

-DelayError (Reply Code to Refuse Delayed Messages) 
SMTP reply code to refuse delayed messages. Default: 451 4.7.1 Please try again later
  
  Notes On Delaying
   
Default: 451 4.7.1 Please try again later 

-ValidateSPF (Enable SPF Validation) 
Enable Sender Policy Framework Validation as described at openspf.
  This requires an installed Mail::SPF module in PERL.  Scoring is done  with spfValencePB. 
Default: score 

-SPFLog (Enable SPF logging) 
 
Default: standard 

-SPFWL (Whitelisted SPF Validation) 
Enable Sender Policy Framework Validation for whitelisted users also.  

-SPFNP (noProcessing SPF Validation) 
Enable Sender Policy Framework Validation for nonprocessed messages also.  

-SPFLocal (Local and outgoing mail SPF Validation) 
Enable Sender Policy Framework Validation for local and outgoing messages also. Don't forget to configure your DNS-server for SPF if you enable this option.  

-failstrictLOCAL (Strict SPF Failing for Local Domains*) 
Softfail/Neutral/None messages with local domain in sending address will be Failed. 
Default: On 

-blockstrictLOCAL (Strict SPF Blocking for Local Domains*) 
Failed messages with local domain in sending address will be blocked . 
Default: On 

-AddSPFHeader (Add Received-SPF Header) 
Add Received-SPF header. 
Default: On 

-noSPFRe (Regular Expression to Skip SPF Processing*) 
Put anything here to identify these messages in header  

-SPFsoftfail (Fail SPF Softfail Validations) 
SPF 'softfail' status responses will be set to 'fail' if strictSPFRe is matched.
  The possible results of a query are:
pass:The client IP address is an authorized mailer for the sender. The mail should be accepted subject to local policy regarding the sender.
fail:The client IP address is not an authorized mailer, and the sender wants you to reject the transaction for fear of forgery.
softfail:The client IP address is not an authorized mailer, but the sender prefers that you accept the transaction because it isn't absolutely sure all its users are mailing through approved servers. The softfail status is often used during initial deployment of SPF records by a domain.
neutral:The sender makes no assertion about the status of the client IP.
none:There is no SPF record for this domain.
permerror &amp; temperror:The DNS lookup encountered an error during processing.
unknown:The domain has a configuration error in the published data or defines a mechanism that this library does not understand. 
Default: On 

-SPFneutral (Fail SPF Neutral Validations) 
Intentionally fail SPF neutral status responses  

-SPFqueryerror (Fail SPF Error Responses) 
Intentionally fail SPF 'error' status responses  

-SPFnone (Fail SPF None and Unknown Responses) 
Intentionally fail SPF 'none' and 'unknown' status responses  

-SPFunknown (Fail SPF Unknown  Responses) 
Intentionally fail SPF 'unknown'  status responses  

-strictSPFRe (Strict SPF Processing Regex*) 
SPF 'softfail' status responses will be set to 'fail' for these sending addresses. Put anything here to identify the addresses. For example: '@aol.com|@gmail.com|@msn.com|@live.com|@ebay.com|@ebay.nl|@bbt.com|@paypal.com|@einsundeins.de|@microsoft.com' 
Default: file:files/strictspf.txt 

-blockstrictSPFRe (Strict SPF Blocking Regex*) 
All failed messages will be blocked for these sending addresses. Put anything here to identify the addresses. For example: '@ebay.com|@paypal.com|@facebook.com' 
Default: @ebay.com|@paypal.com|@facebook.com|@ups.com 

-DoSPFinHeader (Do SPF check on header from:) 
Do an additional SPF check on the header from: address if it is in blockstrictSPFRe *** breakes RFC rules ***  

-SPFCacheInterval (SPF Cache Refresh Interval) 
SPF records in cache will be removed after this interval in days. 0 will disable the cache.   
Default: 3 

-DebugSPF (Enable SPF Debug output to ASSP Logfile) 
Enables verbose debugging of SPF queries within the Mail::SPF::Query module.
 
 Notes On SPF
    

-EnableSRS (Enable Sender Rewriting Scheme) 
Enable Sender Rewriting Scheme as described at www.openspf.org/SRS.
  This requires an installed Mail::SRS module in PERL.
  You should use SRS if your message handling system forwards email for domains with published spf records.
  Note that you have to setup the outgoing path (Relay Host and Port) to let ASSP see and rewrite your outgoing traffic.  

-SRSAliasDomain (Alias Domain) 
SPF requires the SMTP client IP to match the envelope sender (return-path). When a message is forwarded through
  an intermediate server, that intermediate server may need to rewrite the return-path to remain SPF compliant.
  For example: example.com 
Default: example.com 

-SRSSecretKey (Secret Key) 
A key for the cryptographic algorithms -- Must be at least 5 characters long.  

-SRSTimestampMaxAge (Maximum Timestamp Age) 
Enter the maximum number of days for which a timestamp is considered valid. 
Default: 21 

-SRSHashLength (Hash Length) 
The number of bytes of base64 encoded data to use for the cryptographic hash.
  More is better, but makes for longer addresses which might exceed the 64 character length suggested by RFC5321.
  This defaults to 4, which gives 4 x 6 = 24 bits of cryptographic information, which means that a spammer will have 
  to make 2^24 attempts to guarantee forging an SRS address. 
Default: 4 

-SRSValidateBounce (Enable Bounce Recipient Validation) 
Bounce messages that fail reverse SRS validation (but not a valid SMTP probe)
  will receive a 554 5.7.5 [Bounce address not SRS signed] SMTP error code. Scoring is done  with srsValencePB.  

-SRSno (Dont Rewrite These Addresses*) 
Don't rewrite addresses when messages come from/to these addresses. Accepts specific addresses (user@example.com), user parts (user) or entire domains (@example.com). For example: fribo@example.com|jhanna|@example.org  

-noSRS (Dont Validate Bounces From these IPs*) 
Enter IP addresses that you don't want to validate bounces from, separated by pipes (|).
  For example:  145.145.145.145|145.146.
  Notes On SRS
    

-ValidateRBL (Enable DNS Blacklist Validation) 
This requires an installed Net::DNS module in PERL. Scoring is done  with rblValencePB for 'fail' and rblnValencePB for 'neutral' results.  
Default: block 

-RBLLog (Enable DNSBL logging) 
 
Default: standard 

-noRBL (Dont do DNSBL for these IPs*) 
Enter IP addresses that you don't want to be DNSBL validated, separated by pipes (|). For example:  145.145.145.145|145.146.  

-RBLWL (Whitelisted DNSBL Validation) 
Enable DNSBL for whitelisted messages   

-RBLNP (NoProcessing DNSBL Validation) 
Enable DNSBL for noprocessing messages   

-AddRBLHeader (Add X-Assp-DNSBL Header) 
Add X-Assp-DNSBL header to messages with positive reply from DNSBL. 
Default: On 

-RBLServiceProvider (RBL Service Providers*) 
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  bl.spamcop.net=>1 would score 50, bl.spamcop.net=>2 would score 25 if rblValencePB is set to 50. 
If the sum of scores surpasses rblValencePB, the DNSBL check fails. If not, the DNSBL check will be considered 'neutral' and use the resulting score. 
newest example file is here 
Default: file:files/dnsbls.txt 

-RBLmaxreplies (Maximum Replies) 
A reply is affirmative or negative reply from a DNSBL.
  The DNSBL module will wait for this number of replies (negative or positive) from the DNSBLs listed under Service Provider for up to the Maximum Time(RBLmaxtime).
  This number should be equal to or less than the number of DNSBL Service Providers listed to allow for randomly unavailable DNSBLs.

 
Default: 13 

-Showmaxreplies (Show All Possible Hits ) 
Show all hits instead of stopping at RBLmaxhits.  

-RBLmaxhits (Maximum Hits) 
A hit is an affirmative response from a DNSBL.
  The DNSBL module will check all of the DNSBLs listed under Service Provider. If the number of hits is greater or equal Maximum Hits, the email is flagged failed. If the number of hits is greater 0 and less Maximum Hits, the email is flagged neutral.  
RBLmaxhits is ignored if the RBLServiceProvider are classified (weighted), the email is flagged failed if weights for all DNSBLs is greater or equal RBLvalencPB. 
Default: 2 

-RBLmaxtime (Maximum Time) 
This sets the maximum time in seconds to spend on each message performing DNSBL checks. 
Default: 10 

-RBLsocktime (Socket Timeout) 
This sets the DNSBL socket read timeout in seconds. 
Default: 1 

-RBLCacheInterval (DNSBL Expiration Time) 
IPs in cache will be removed after this interval in days. 0 will disable the cache. Notes On DNSBL
   
Default: 3 

-ValidateURIBL (Enable URI Validation) 
Enable URI Blocklist. Messages that fail URIBL validation will receive URIBLError SMTP error code. This requires an installed Net::DNS module and an installed Email::MIME::Modifier module in PERL. 
   Scoring is done  with uriblValencePB 
Default: block 

-URIBLLog (Enable URIBL logging) 
 
Default: standard 

-URIBLWL (Do URI Blocklist Validation for Whitelisted) 
URIBL check is done ignoring all spamlovers and testmodes!  

-URIBLNP (Do URI Blocklist Validation for NoProcessing) 
URIBL check is done ignoring all spamlovers and testmodes!  

-URIBLLocal (Do URI Blocklist Validation for Local Mails) 
  

-URIBLISP (Do URI Blocklist Validation for ISP/Secondary) 
 
Default: On 

-URIBLServiceProvider (URIBL Service Providers*) 
Domain Names of URIBLs to use separated by "|". You may set for every provider a weight like multi.surbl.org=>50|black.uribl.com=>25.
 The value of the weight can be set directly like=>45 or as a divisor of URIBLmaxweight . Low numbers 50  would be the same as multi.surbl.org=>1, multi.surbl.org=>2 would be the same as multi.surbl.org=>25.
 If the sum of weights of all found uris surpasses URIBLmaxweight, the URIBL check fails.  If not, the URIBL check is scored as "neutral" . URIBLmaxhits is ignored when weights are used. 
 Some URIBL Service Providers, like multi.surbl.org and black.uribl.com , provides different return codes in a single DNS-zone: like 127.a.b.c - where a,b,c are used to identify a weight or type (or what ever) of the returned entry. If you want to care about special return codes, or if you want to use different weights for different return codes, you should use the following enhanced entry syntax:
 URIBL-Service-Provider=>result-to-watch=>weight (like:)
 multi.surbl.org=>127.0.0.2=>2
 multi.surbl.org=>127.0.0.4=>3
 multi.surbl.org=>127.0.0.?=>4
 multi.surbl.org=>127.0.0.*=>5
 You can see, the wildcards * (multiple character) and ? (single character) are possible to use in the second parameter. Never mix the three possible syntax types for the same URIBL Service Provider. An search for a match inside such a definition is done in reverse ASCII order, so the wildcards are used as last. 
Default: multi.surbl.org=&gt;1|black.uribl.com=&gt;1 

-TLDS (Country Code TLDs*) 
List of one level country code TLDs  
Default: file:files/tlds-alpha-by-domain.txt 

-URIBLCCTLDS (URIBL Country Code TLDs*) 
List of two level country code TLDs and three level country code TLDs used to determine the base domain of the uri. Two level TLDs will be checked on third level, third level TLDs will be checked on fourth level. Any not listed domain will be checked in level two. 
Default: file:files/URIBLCCTLDS.txt 

-URIBLmaxuris (Maximum URIs) 
More than this number of URIs in the body will increase scoring with uribleValencePB. Enter 0 to disable feature.  

-URIBLmaxdomains (Maximum Unique Domain URIs) 
More than this number of unique domain URIs in the body will increase scoring with uribleValencePB. Enter 0 to disable feature.  

-URIBLNoObfuscated (Disallow Obfuscated URIs ) 
When enabled, messages with obfuscated URIs of types [integer/octal/hex IP, other things!] in the body will will increase scoring with uribleValencePB and if weights are used, the double weight will be used.  

-URIBLcheckDOTinURI (Check for DOT in URI) 
When enabled, assp will also check for the used word 'DOT' instead of a '.' in URI's like 'exampledotcom or example!d o-t_com' .
   Enable this feature only, if you don't expect any problems in your national language (using 'dot' + a toplevel domain in any words).  

-URIBLmaxreplies (Maximum Replies) 
A reply is affirmative or negative reply from a URIBL.
   The URIBL module will wait for this number of replies (negative or positive) from the URIBLs listed under Service Provider
   for up to URIBLmaxtime. This number should be equal to or less than the number of URIBL Service Providers
   listed to allow for randomly unavailable URIBLs. 
Default: 3 

-URIBLmaxhits (Maximum Hits) 
A hit is an affirmative response from a URIBL.
   The URIBL module will check all of the URIBLs listed under Service Provider,
   and flag the email with a URIBL failure flag if more than this number of URIBLs return a postive blacklisted response.
   This number should be less than or equal to URIBLmaxreplies and greater than 0.
   If the number of hits is greater or equal URIBLmaxhits, the email is flagged failed.
    If the number of hits is greater 0 and less URIBLmaxhits, the email is flagged neutral 
    URIBLmaxhits is ignored if the URIBLServiceProvider are classified (weighted), the email is flagged failed if weights for all URIs is greater or equal URIBLvalencPB.
    
Default: 1 

-URIBLmaxweight (URIBL Maximum Weight) 
A weight is a number representing the trust we put into a URIBL.
  The URIBL module will check all of the URIBLs listed under URIBLServiceProvider for every URI found in an email. If the total of weights for all URIs is greater or equal this Maximum Weight, the email is flagged Failed. If the total of weights is greater 0 and less Maximum Weight, the email is flagged Neutral . If not defined or set to zero only URIBLmaxhit will be used to detect a fail or neutral state.  

-URIBLmaxtime (Maximum Time) 
This sets the maximum time in seconds to spend on each message performing URIBL checks. 
Default: 10 

-URIBLsocktime (Socket Timeout) 
This sets the URIBL socket read timeout in seconds. 
Default: 1 

-URIBLwhitelist (Whitelisted URIBL Domains*) 
This prevents specific domains from being checked by URIBL module. For example:files/uriblwhite.txt. 
Default: file:files/uriblwhite.txt 

-noURIBL (Dont Check Messages from these Addresses*) 
Don't validate URIBL when messages come from these addresses. Accepts specific addresses (user@domain.com), user parts (user) or entire domains (@domain.com). For example: fribo@thisdomain.com|jhanna|@example.org  

-AddURIBLHeader (Add X-Assp-Received-URIBL Header) 
Add X-Assp-Received-URIBL header to messages with positive reply from URIBL. 
Default: On 

-URIBLCacheInterval (URIBL Cache Refresh Interval for Hits) 
Domains in cache will be removed after this interval in days. 0 will disable the cache. Notes On URIBL
 
Default: 3 

-DoBlockExes (Checking ) 
Note:Attachment checking will only be done if Email::MIME::Modifier is installed. Scoring is done  with baValencePB.  

-AttachmentLog (Enable Attachment logging) 
 
Default: standard 

-BlockExes (External Attachment Checking Level ) 
Set the level of Attachment Blocking to 1-3 for attachments that should be blocked, set level to 4  for attachments that should be allowed only. Choose 0 for no attachment blocking.  

-BlockWLExes (Whitelisted Attachment Checking) 
Set the level of Attachment Checking to 0-4 for whitelisted senders. Choose 0 for no attachment blocking.  

-BlockLCExes (Local Attachment Checking) 
Set the level of Attachment Blocking to 0-4 for local senders. Choose 0 for no attachment blocking.  

-BlockNPExes (NoProcessing Attachment Checking) 
Set the level of Attachment Checking to 0-4 for noprocessing messages. Choose 0 for no attachment checking.   

-BadAttachL1 (Level 1 rejected File Extensions) 
This regular expression is used to identify Level 1 attachments that should be blocked.
  Separate entries with a pipe |. The dot . is assumed to precede these, so don't include it. For example: ad[ep]|asx|ba[st]|chm|cmd|com|cpl|crt|dbx|exe|hlp|ht[ab]|in[fs]|isp|js|jse|lnk
  |md[abez]|mht|ms[cipt]|nch|pcd|pif|prf|reg|sc[frt]|sh[bs]|vb|vb[es]|wms|ws[cfh] 
Default: exe|scr|pif|vb[es]|js|jse|ws[fh]|sh[sb]|lnk|bat|cmd|com|ht[ab] 

-BadAttachL2 (Level 2 rejected File Extensions) 
This regular expression is used to identify Level 2 attachments that should be checked.
  Level 2 already includes all rejected extensions from Level 1.  For example: (ad[ep]|asx|ba[st]|chm|cmd|com|cpl|crt|dbx|exe|hlp|ht[ab]|in[fs]|isp|js|jse|
  lnk|md[abez]|mht|ms[cipt]|nch|pcd|pif|prf|reg|sc[frt]|sh[bs]|vb|vb[es]|wms|ws[cfh]).zip  

-BadAttachL3 (Level 3 rejected File Extensions) 
This regular expression is used to identify Level 3 attachments that should be checked.
  Level 3 includes Level 2 and Level 1. For example: zip|url  

-GoodAttach (Level 4 Allowed File Extensions) 
This regular expression is used to identify  attachments that should be allowed. All others are blocked. Separate entries with a pipe |. The dot . is assumed to precede these, so don't include it. For example: ai|asc|bhx|dat|doc|docx|eps|gif|htm|html|ics|jpg|jpeg|hqx|od[tsp]|pdf|ppt|rar|
  
  rpt|rtf|snp|txt|xls|zip  

-PassAttach (Passing File Names  ) 
This regular expression is used to identify  attachments that should mark the message as noprocessing. If you enter extensions do not precede it with a dot. This will take precedence over any bad attachment.  

-AttachmentError (Reply Code to Refuse Rejected Attachments) 
The literal FILENAME (case sensitive) will be replaced with the name of the blocked attachment!
 Notes On Attachment Blocking 
Default: 550 5.7.1 These attachments are not allowed -- Compress before mailing. 

-ScanLog (Enable Virus Check logging) 
 
Default: standard 

-noScan (Do Not Scan Messages from/to these Addresses*) 
Accepts 
specific addresses (user@example.com), user parts (user) or entire 
domains (@example.com).  

-noScanIP (Do Not Scan Messages from these IPs*) 
Enter IP addresses that you don't want to be scanned for virus , separated by pipes (|). For example: 145.145.145.145|145.146.  

-ScanWL (Scan Whitelisted Senders) 
 
Default: On 

-ScanNP (Scan NoProcessing Messages) 
  

-ScanLocal (Scan Local Senders) 
  

-ScanCC (Scan Copied Spam Mails) 
  

-AvError (Reply Code to Refuse Infected Messages) 
Reply
code to refuse infected messages. The string INFECTION is replaced with
the name of the detected virus.  For example: 554 5.7.1 Mail appears
infected with INFECTION -- disinfect and resend. 
Default: 554 5.7.1 Mail appears infected with INFECTION. 

-EmailVirusReportsTo (Send Virus Report To This Address) 
If set an email containing the Message ID, Remote IP, Message 
Subject, Sender email address, Recipient email address, and the virus 
detected will be sent to this address. For example: 
admin@example.com  

-EmailVirusReportsHeader (Add Full Header To Virus Report To Mail Address Above) 
If set the full message 
headers will also be added to Virus Reports.  

-EmailVirusReportsToRCPT (Send Virus Report To Recipient) 
If set the intended 
recipient of the message will be sent a copy of the Virus Report. 
  

-UseAvClamd (Use ClamAV) 
If activated, the message is checked by ClamAV, this requires an installed
  File::Scan::ClamAV Perl module and a running Clamd . The viruses will
  be stored in a special folder if the SpamVirusLog is set to 
'quarantine' and the
  filepath to the viruslog is set. Scoring is done  using vdValencePB.  

-modifyClamAV (Modify ClamAV Module) 
If set ClamAV modules ping and streamscan are modified. This may be disabled to use the original modules. NOTE: Changing this  requires ASSP restart 
Default: On 

-AvClamdPort (Port or file socket for ClamAV) 
 If the socket has been setup as a TCP/IP socket (see the TCPSocket option in the clamav.conf file - located for example in /etc/clamav/clamd.conf), then specify the TCPSocket (port). For example: 3310.
 If LocalSocket is specified in the clamav.conf file  then specify here the LocalSocket. For example /var/run/clamav/clamd.ctl. 
Default: /private/tmp/clamd 

-ClamAVBytes (Scan Bytes) 
The number of bytes per message that will be scanned for virus and 
attachment blocking. Normally ASSP looks only at MaxBytes of a message. Values of 100000 or larger are not recommended. 
Default: 50000 

-ClamAVtimeout (ClamAV Timeout) 
ClamAV will timeout after this many seconds. default: 10 
seconds. 
Default: 10 

-NoScanRe (Skip ClamAV Regular Expression*) 
Put anything here to identify messages which should not be checked 
for viruses.  

-SuspiciousVirus (No-Blocking Virus Scan Scoring Regex**) 
If a ClamAV or FileScan result matches this expression it will be scored with the suspicious virus score ( vsValencePB ) and the message will not be blocked.
 It is possible to weight such results. Every weighted regex that contains at least one '|' has to begin and end with a '~' - inside such regexes it is not allowed to use a '~', even it is escaped - for example:  ~abc\~|def~=>23 or ~abc~|def~=>23 - instead use the octal (\126) or hex (\x7E) notation (\126), for example ~abc\126|def~=>23 or ~abc\x7E|def~=>23 . Every weighted regex has to be followed by '=>' and the weight value. For example: Phishing\.=>1.45|~Heuristics|Email~=>50  or ~(Email|HTML|Sanesecurity)\.(Phishing|Spear|(Spam|Scam)[a-z0-9]?)\.~=>4.6|Spam=>1.1|~Spear|Scam~=>2.1 . The multiplication result of the weight and the penaltybox valence value will be used for scoring, if the absolute value of weight is less or equal 6. Otherwise the value of weight is used for scoring. 
Default: file:files/suspiciousvirus.txt 

-DoFileScan (Use File System Virus Scanner) 
If activated, the message is written to a file inside the 
'FileScanDir' with an extension of 'maillogExt'. After that ASSP 
will call 'FileScanCMD' to detect if the temporary file is infected 
or not. The temporary created file(s) will be removed.
  The viruses will be stored in a special folder if the SpamVirusLog 
is set to 'quarantine' and the filepath to the viruslog is set.  

-FileScanWL (Scan Whitelisted Senders) 
 
Default: On 

-FileScanNP (Scan NoProcessing Messages) 
 
Default: On 

-FileScanLocal (Scan Local Senders) 
  

-FileScanDir (File Scan Directory) 
Define the full path to the directory where the messages are 
temporary stored for the file system virus scanner. This could be any 
directory inside your file system. The running ASSP process must have 
full permission to this directory and the files inside! For defining any full filepathes, always use slashes ("/") not backslashes.  
Default: /Applications/assp/virusscan 

-FileScanCMD (File Scan Command) 
ASSP will call this system command and expects a returned string 
from this command. This returned string is checked against 
'FileScanBad' and/or 'FileScanGood' to detect if the message is 
OK or not! If the file does not exists after the command call, the 
message is consider infected. ASSP expects, that the file scan is 
finished when the command returns!
   The literal 'FILENAME' will be replaced by the full qualified 
file name of the temporary file.

   The literal 'FILESCANDIR' will be replaced with the value of 
FileScanDir.
   All outputs of this command to STDERR are automatic redirected to 
STDOUT.
   FileScan will not run, if FileScanCMD is not specified.
   If you have your online/autoprotect file scanner configured to 
delete infected files inside the 'FileScanDir', define 'NORUN' in 
this field! In this case FileScanGood and FileScanBad are ignored. If 
there is a need to wait some time for the autoprotect scanner, write 
'NORUN-dddd', where dddd are the milliseconds to wait!
   Depending on your operating system it may possible that you have to 
quote (' or ") the command, if it contains whitespaces. The replaced 
file name will be quoted by ASSP if needed. For example: 'd:\utility\touch.exe FILENAME' 
Default: NORUN 

-FileScanBad (RegEx to Detect BAD in Returned String*) 
Put anything here to identify bad messages by the string returned 
from the FileScanCMD. If this regular expression matches, the message 
is considered infected.  

-FileScanGood (RegEx to Detect GOOD in Returned String*) 
Put anything here to identify good messages by the string returned 
from the FileScanCMD. If this regular expression matches and 
'FileScanBad' does not, the message is considered not infected.  

-FileScanRespRe (FileScan Reponds Regex*) 
A regular expression that will be used over the text returned from 
the FileScanCMD. The result of this regex is used as virus name 
(INFECTION) in AvError. For example: infected by (.+)
  Notes On Virus Checks  

-BombLog (Enable Bomb logging) 
 
Default: standard 

-preHeaderRe (Regular Expression to early Identify Spam in Handshake and Header Part*) 
Until the complete mail header is received, assp is processing the handshake and header content line per line, but the first mail content check is done after the complete mail header is received.
 It is possible, that some content (malformed headers, forbidden characters or character combinations) could cause assp to die or to run into a unrecoverable exception (eg. segment fault).
 Use this regular expression to identify such incoming mails based on a line per line check, at the moment where a single line is received.
If a match is found, assp will immediately send a '421  closing transmission' reply to the client and will immediately terminate the connection.  
Default: file:files/preheaderre.txt 

-maxBombValence (Maximum Penalty on Regex Match per Mail per Check) 
This option is valid for all regex searches which allow weights (marked with **) and limits the maximum penalty per check. maxBombHits is overwritten. If not set the search will stop if MessageScoringUpperLimit or maxBombHits is reached. For example: 70  

-maxBombHits (Maximum Number Of Hits in Regex Search*) 
This option is valid for all regex searches which allow weights (marked with **). Use the syntax: regextype=>3|other.regextype=>3 to set the maximum number of hits a regexsearch should perform. Maximum for regex searches not set here is 1. The search will stop if MessageScoringUpperLimit or maxBombHits is reached. This can be overwritten by maxBombValence. 
Default: blackRe=&gt;2|bombSenderRe=&gt;1|bombHeaderRe=&gt;1|bombSubjectRe=&gt;3|bombCharSets=&gt;1|bombSuspiciousRe=&gt;3|bombRe=&gt;2|scriptRe=&gt;2 

-DoBlackRe (Use Black Regular Expression to Identify Spam) 
This works similar to DoBombRe but has different defaults in processing whitelisted  and noprocessing. Both will will be checked if the defaults are used. Envelope, Header and Data Part are checked  against the BlackRe. Scoring is done  with blackValencePB - the scoring value is the sum of all valences(weights) of all found blackRe(s). Blocking will only be done if 'block' is set  (default) and the messagescore is equal or exceeds blackValencePB.   
Default: block 

-blackRe (Black Regular Expressions to Identify Spam ** ) 
This is a stricter version of bombRe (blackReWL, blackReNP, blackReISPIP are enabled by default). If an incoming email matches this expression it will be considered spam. The expressions here will work as original Regular Expressions As all fields marked with two asterisk (**) do - this  regular expressions (regex) can accept a weight value. Every weighted regex has to be followed by '=>' and the weigth value. The search will continue until maxBombHits is reached or maxBombValence is exceeded (if set). 
Default: file:files/blackre.txt 

-blackReWL (Do Black Regular Expressions Checks for Whitelisted) 
 
Default: On 

-blackReNP (Do Black Regular Expressions Checks for NoProcessing) 
 
Default: On 

-blackReISPIP (Do Black Regular Expressions Checks for ISPIP) 
 
Default: On 

-blackReLocal (Do Black Regular Expressions Checks for Local Messages) 
  

-DoBombHeaderRe (Use Header Regular Expressions ) 
If activated, each message-header is checked  against bombHeaderRe. Scoring is done  with bombValencePB 
Default: score 

-bombSenderRe (DoBombHeaderRe: RegEx to find Spam in Envelope**) 
Expression to identify mailfrom,ip and helo. 
Default: file:files/bombsenderre.txt 

-bombHeaderRe (DoBombHeaderRe: RegEx to find Spam in Header Part **) 
Header will be checked against this Regex if DoBombHeaderRe is enabled.  
Default: file:files/bombheaderre.txt 

-bombSubjectRe (DoBombHeaderRe: RegEx to find Spam in Subject **) 
Subject will be checked against this Regex if DoBombHeaderRe is enabled. The expressions here will work as original Regular Expressions 
Default: file:files/bombsubjectre.txt 

-maxSubjectLength (Maximum allowed Subject Length) 
If set to a value greater than 0, assp will check the length of the Subject of the mail. If the Subject length exceeds this value, the message score will be increased by 'bombValencePB' and the string that is checked in 'bombSubjectRe' will be trunked to this length. It is possible to define a special weight using the syntax 'length=>value', in this case the defined absolute value will be used instead of 'bombValencePB' to increase the message score. If the subject is too long and this weight is equal or higher than 'bombValencePB' no further bomb checks will be done on the subject. 
Default: 150=&gt;40 

-bombCharSets (DoBombHeaderRe: RegEx to find Foreign Charsets ** ) 
Header will be checked against this Regex if DoBombHeaderRe is enabled. A weight can be assigned. For example: charset=.?BIG5|charset=.?CHINESEBIG|charset=.?GB2312|charset=.?KS_C_5601|charset=.?KOI8=>0.5|charset=.?EUC-KR|charset=.?ISO-2022|charset=.?CP1251.  
Default: file:files/charsets.txt 

-DoBombRe (Use Bomb Regular Expressions) 
If activated, each message is checked  against bombRe Regular Expressions. Scoring is done  with bombValencePB - the scoring value is the sum of all valences(weights) of all found bombRe(s)
   
Default: score 

-bombSuspiciousRe ( DoBombRe: Regular Expression to Score Blackish and/or Whitish Expressions **) 
Put here anything which might be suspicious (blackish) or trustworthy (whitish). bombSuspiciousValencePB will be multiplied by the weight and increases/decreases the total score.  Trustworthiness (whitishness) will be assigned by using a negative weight.  For example:news=>-0.4|no-?reply=>-0.5|passwor=>-0.7 
Default: file:files/suspiciousre.txt 

-bombRe ( DoBombRe: RegEx for Header and Data Part **) 
Header and Data will be checked against this Regular Expressions if DoBombRe is enabled.  The expressions here will work as original Regular Expressions 
Default: file:files/bombre.txt 

-bombCharSetsMIME (DoBombRe: RegEx to Identify Foreign Charsets in MIME** ) 
MIME parts will be checked against this Regex. A weight can be assigned. For example: charset=.?BIG5|charset=.?CHINESEBIG|charset=.?GB2312|charset=.?KS_C_5601|charset=.?KOI8=>0.5|charset=.?EUC-KR|charset=.?ISO-2022|charset=.?CP1251.  
Default: file:files/charsets.txt 

-bombDataRe (DoBombRe: RegEx for Data Part **) 
Data part will be checked against this Regular Expression if DoBombRe is enabled
The expressions here will work as original Regular Expressions.  
Default: file:files/bombdatare.txt 

-DoTestRe (DoBombRe: RegEx for Testing ) 
If activated, each message is checked  against the Test Regular
  Expression below. This provides a way to test regex strings on live mail.  

-testRe (Test Regular Expression **) 
The expressions here will work as original Regular Expressions  

-scriptRe (DoBombRe: RegEx to find Mobile Scripts **) 
Spam emails may contain mobile scripting code, eg activex and java. You can use this feature to block those messages.For example: \&lt;applet|\&lt;embed|\&lt;iframe|\&lt;object|\&lt;script|onmouseover|javascript:  

-bombReISPIP (Do Bomb/Script Regular Expressions Checks for ISPIP) 
 
Default: On 

-maxBombSearchTime (Maximum time spend on Regex Search) 
Maximum time in seconds that is spend on  regex check. This time check is done, after every found regex. So it is possible that the regex search takes longer as the defined value, if no match is found or a single search takes more time. 
Default: 5 

-noBombScript (Dont Check Messages from these Addresses*) 
Don't detect spam bombs or scripts in messages from these addresses. Accepts specific addresses (user@example.com), user parts (user) or entire domains (@example.com).Notes On Bomb Regex  

-BayesianLog (Enable Bayesian Logging) 
Enables verbose logging of  Bayesian checks in the maillog. 
Default: standard 

-DoBayesian (Bayesian Check) 
If activated, the message is checked  based on Bayesian factors in spamdb . This needs a fully functional spamdb built by rebuildspamdb. For starters it is best practice  to put this inactiv and built the spamdb collection with the help of DSNBL ,URIBL and spamaddresses. Scoring is done with baysValencePB for external mails, baysValencePB_local is used for outgoing and internal mails - both values are multiplied with the detected baysProbability . 
Default: score 

-BayesianStarterDB (Bayesian Starter Database ) 
A ready to use spamdb which can be used alone or together with your local spamdb. It will be automatically downloaded at startup and placed in folder "assp/starterdb".  No download if empty. Manually download from here: <img height=12 width=12 src="get?file=images/info.png" alt="sourceforge.net/projects/assp/files/ASSP%20Installation/Spam%20Collection/spamdb.gz" 
Default: starterdb/spamdb 

-downloadStarterDBNow (Run downloadStarterDB Now) 
If selected, ASSP will download the BayesianStarterDB right away. &nbsp;  

-BayesWL (Bayesian Check on Whitelisted Senders) 
  

-BayesNP (Bayesian Check on NoProcessing Messages) 
  

-BayesLocal (Bayesian Check on Local Senders) 
  

-BayesMaxProcessTime (Bayesian Check Timeout ) 
The Bayesian Checks are the most memory and CPU consuming tasks that ASSP is doing on a message. If such tasks running to long on one message, other messages could run in to SMTPIdleTimeout. Define here the maximum time in seconds that ASSP should spend on Bayesian Checks for one message. 
Default: 30 

-noBayesian (Skip Bayesian Check*) 
Mail from/to any of these addresses are ignored by Bayesian check, mails will not be stored in spam/notspam collection. Accepts specific addresses (user@example.com), user parts (user) or entire domains (@example.com). Wildcards are supported (user*@example.com)  

-noBayesian_local (Skip Bayesian for this local senders*) 
Mail from any of these local addresses are ignored by Bayesian check, mails will not be stored in spam/notspam collection. Accepts specific addresses (user@domain.com), user parts (user) or entire domains (@domain.com)  

-yesBayesian_local (Do Bayesian for this local senders only*) 
Mail from any of these local addresses will perform Bayesian check, noBayesian_local will be ignored. Accepts specific addresses (user@domain.com), user parts (user) or entire domains (@domain.com)  

-baysTestModeUserAddresses (Bayesian Testmode User Addresses*) 
These users are in testmode ( mark subject only ) for bayesian spam, even with testmode off  

-maxBayesValues (Maximum most significant results used per mail to calculate Bayesian-Probability) 
Maximum count of most significant values used to calculate the Bayesian/HMM-Spam-Probability and the confidence of that probability.
  
Default: 40 

-baysProbability (Bayesian Probability Threshold ) 
 Messages with spam-probability below or equal this threshold are considered Ham. Recommended '0.6'.
 An resulting Spam-Probability above this value is multiplied with baysValencePB_local or baysValencePB to get the penaltybox scoring value for the IP- and message score. In other words, the penaltybox scoring value is weighted by the Spam-Probability in case Spam is detected.
 An resulting Spam-Probability below this value but higher than ( 1 - baysProbability ) is stated as 'UNSURE' . In this case the half score will be added to the message score but not to the IP score and the message will not be blocked.
 The following default Bayesian math (prob = p1 / (p1 + p2)) is used to calculate the SpamProb value for 'n' found Bayesian-Word-Pairs, each with a spam-weight 'p' - where 0&lt;p&lt;1 :
 'SpamProb' = (p1 * p2 * ... * pn) / ( p1 * p2 * ... * pn  + (1 - p1) * (1 - p2 ) * ... * (1 - pn)) 
Default: 0.6 

-AddSpamProbHeader (Add Bayes Probability Header) 
Adds a line to the email header "X-Assp-Spam-Prob: 0.0123" Probability ranges from 0 to +1 where > baysProbability is spam.

  Notes On Bayesian
    

-ReportLog (Enable Report logging) 
 
Default: verbose 

-EmailBlockReport (Request Block Report) 
Any mail sent by local/authenticated users to this username will be interpreted as a request to get a report about blocked emails. Do not put the full address here, just the user part. For example: assp-blockreport
 Leading digits/numbers in the mail subject will be interpreted as "report request for the last number of days". If the number of days is not specified in the mail subject, a default of 5 days will be used to build the report. 
 All characters behind the "number of days" will be interpreted as a regular expression to overwrite the BlockReportFilter - leading and trailing white spaces will be ignored.
Only Users defined in EmailBlockTo, EmailAdmins and EmailAdminReportsTo are 'Admins' and can request a report for other users. They have to use a special syntax with '=>' in the body of the report request. The syntax is: 
 QueryAddress=>ReportRecipient=>ReportDaysThere may be one or many lines with this syntax . For example:
 user@domain and user@domain=>user@domain - will send a report for this user to this user
 *@domain (better use) *@domain=>* - will send a report for every blocked user in this domain to this user
 user@domain=>recipient@any-domain - will send a report for user@domain to recipient@any-domain
 *@domain=>recipient@any-domain - will send a report for every blocked user in this domain to recipient@any-domain
 A third parameter is possible to set, which defines the number of days for which the report should be created. The default (if empty or not defined) is one day. This value is used to calculate the 'next run date'. For example:
 *@domain=>recipient@any-domain=>2 - creates a report for two days.
 *@domain=>*=>14 - creates a report for 14 days.
 user@domain=>=>3 or user@domain=>*=>3 - creates a report for three days. The second parameter is here empty or *.
 To overwrite the defined BlockReportFilter, you can define a fourth parameter, which contains the regular expression to use.
 *@domain=>*=>14=>virus|newsletter - creates a report for 14 days and skips all lines that contains the words 'virus' or 'newsletter'.
 If an admin emails a block report request and specifies a filter in the subject of the email and a fourth parameter in the body, both regular expressions will be merged in to a single regex for each line.
 If you or a user want the default BlockReportFilter to become part of the overwrite regex, the literal '$BRF' should be inluded in the regex like:
 *@domain=>*=>14=>virus|$BRF|newsletter - or even in the subject of the email
 In this case the literal '$BRF' will be replaced by the BlockReportFilter.
 Only Admins are able to request blockreports for non local email addresses. For example:
 user@non_local_domain=>recipient@any-domain=>4
 *@non_local_domain=>recipient@any-domain=>4
 This will result in an extended blockreport for the non local address(es). Replace 'non_local_domain' with the domain name you want to query for.
 It is possible to change the complete design of the BlockReports to your needs,  using a html-css file. An default css-file 'blockreport.css' is in the image folder.
 There you can also find a default icon file 'blockreporticon.gif' and a default header-image-file 'blockreport.gif' - which is the same like 'logo.gif'.  There is no need to install that fles. If assp can not find this files in its
 image folder, it will use default hardcoded css and icon. If the file 'blockreport.gif' is not found 'logo.gif' will be used.
 
  
  
   
Default: assp-blockreport 

-EmailBlockReply (Reply to Block-Report Request) 
 
Default: REPLY TO SENDER 

-EmailBlockTo (Send Copy of Block-Reports TO) 
Email sent from ASSP acknowledging your submissions will be sent to this address if EmailBlockReply is set. For example: admin@domain.com  

-EmailBlockReportDomain (Request Blocked Email Domain) 
Set this to the domain to which the users can send a request to receive blocked messages. Notice the leading required '@'. For example: @assp.local. 
Default: @assp.local 

-QueueUserBlockReports (Queue User Block Report Requests) 
How to process block report requests for users (not EmailBlockTo, EmailAdmins, EmailAdminReportsTo).
  'run instantly' - the request will be processed instantly (not stored).
  'store and run once at midnight' - the request will be stored/queued, runs at QueueSchedule, and will be removed from queue after that

 'store and run scheduled' - the request will be stored/queued, runs permanently scheduled at BlockReportSchedule until it will be removed from queue - a '+' in the subject is not needed
  'run delayed' - the request will be stored and  processed during the next minutes
  To add a request to queue the user has to send an email to EmailBlockReport. Leading digits/numbers in the mail subject will be interpreted as "report request for the last number of days". If the number of days is not specified in the mail subject, a default of 5 days will be used to build the report.
  If 'run instantly','run delayed' or 'store and run once at midnight' is selected, but a user wants to schedule a permanent request, a leading '+' before the digits in subject is required.
  To remove a request from queue the user has to send an email to EmailBlockReport with a leading '-' in the subject.
    

-QueueSchedule (Runtime for Queued Requests) 
Runtime hour for reports in QueueUserBlockReports. Set a number between 0 and 23. 0 means midnight and is default  

-BlockRepForwHost (Forward The Blockreportrequest to other ASSP) 
If you are using more than one ASSP (backup MX), define the IP:relayPort of the other ASSP here (separate multiple entries by "|"). The Blockreportrequest will be forwarded to this ASSP and the user will get a blockreport from every ASSP. The perl module Net::SMTP is required to use this feature.  

-BlockReportFile (File for Blockreportrequest) 
A file with BlockReport requests. ASSP will generate a block report for every line in this file (file:files/blockreportlist.txt - file: is required if defined!) every day at BlockReportSchedule for the last day. The perl modules Net::SMTP and Email::MIME::Modifier  are required to use this feature. A report will be only created, if there is at least one blocked email found! The syntax is: 
 QueryAddress=>ReportRecipient=>ReportDays 
There may be one or many lines with this syntax. For example:
 user@domain and user@domain=>user@domain - will send a report for this user to this user
 *@domain (better use) *@domain=>* - will send a report for every blocked user in this domain to this user
 *@* - creates a report for all local users in all local domains
 user@domain=>recipient@any-domain - will send a report for user@domain to recipient@any-domain
 *@domain=>recipient@any-domain - will send a report for every blocked user in this domain to recipient@any-domain
A third parameter is possible to set, which defines the number of days for which the report should be created. The default (if empty or not defined) is one day. This value is used to calculate the 'next run date'. For example:
 *@domain=>recipient@any-domain=>2 - creates a report for two days.
 *@domain=>*=>14 - creates a report for 14 days.
 user@domain=>=>3 or user@domain=>*=>3 - creates a report for three days. The second parameter is here empty or *!
 To overwrite the defined BlockReportFilter, you can define a fourth parameter, which contains the regular expression to use.
 *@domain=>*=>14=>virus|newsletter - creates a report for 14 days and skips all lines that contain the words 'virus' or 'newsletter'.
 Only Admins are able to request blockreports for non local email addresses. For example:
 user@non_local_domain=>recipient@any-domain=>4
 *@non_local_domain=>recipient@any-domain=>4
 This will result in an extended blockreport for the non local address(es). Replace 'non_local_domain' with the domain name you want to query for.  

-BlockReportSchedule (Runtime BlockReportFile) 
Runtime hour for reports in BlockReportFile. Set a number between 0 and 23. 0 means midnight and is default.  

-BlockReportNow (Generate a BlockReport from BlockReportFile Now) 
If selected, ASSP will generate a block report from BlockReportFile now. &nbsp;  

-BlockMaxSearchTime (Max Search time per log File) 
The maximum time in seconds, the Blockreport feature spends on searching in one log file. If this value is reached, the next log file will be processed. A value of 0 disables this feature and all needed log files will be fully processed.  

-BlockReportFormat (The format of the Report Email) 
Block reports will be sent as multipart/alternative MIME messages. They normaly contains two parts, a plain text part and a html part. Select "text only" or "html only" if you want to skip any of this parts.
  To make it possible to detect a resent email, ASSP will add a header line "X-Assp-Resend-Blocked: myName" to each email! 
Default: text only 

-BlockReportHTTPName (My HTTP Name) 
The hostname for HTTP links in AdminUsers Blockreports and use of the webSecondaryPort. If not defined the local hostname will be used.  

-BlockReportFilter (Regular Expression to Skip Log Records*) 
Put anything here to identify messages which should not be reported. For example:  \[Virus\]|\[BlackDomain\]  

-inclResendLink (Include a Resend-Link for every resendable email) 
Block reports will be sent as multipart/alternative MIME messages. They contains two parts, a plain text part and a html part. If a blocked email is stored in any folder, it is possible to include a link for each email in to the report. Define here what you want ASSP to do. Note: File name logging (fileLogging) must be on! The perl module Email::Send is required to use this feature. 
Default: in both 

-BlockResendLink (Which Link Should be included) 
If HTML is enabled in inclResendLink, two links (one on the left and one on the right site) will be included in the report email by default. Depending on the used email clients it could be possible, that one of the two links will not work for you. Try out what link is working and disable the other one, if you want.  

-BlockResendLinkLeft (User which get the Left link only* ) 
List of users and domains that will get the left link only. The setting for BlockResendLink will be ignored for this entries!  

-BlockResendLinkRight (User which get the right link only* ) 
List of users and domains that will get the right link only. The setting for BlockResendLink will be ignored for this entries!  

-DelResendSpam (Delete Mails in Spam Folder) 
If selected, an user request to resend a blocked email will delete the file in the spamlog folder - an admin request will move the file to the correctednotspam folder. 
Default: On 

-autoAddResendToWhite (Automatic add Resend Senders to Whitelist) 
If a resend request is made by any of the selected users, the original sender of the resent mail will be added to whitelist.
  Notes On Blocking Reports
   
Default: Users and Admins 

-EmailInterfaceOk (Enable Email Interface ) 
Checked means that you want ASSP to intercept and parse mails to the below usernames at any domain which is listed in localDomains. You can use 'assp.local' or '@assp-notspam.org' because they are automatically included.  The interface accepts mails only from local senders coming from acceptAllMail or through relayPort or from authenticated SMTP connections or from addresses listed in EmailSenderOK. 
  Notes On Email Interface
   
Default: On 

-EmailAdminReportsTo (Admin Mail Address) 
Warnings/infos  will be sent to this address. For example: admin@domain.com  

-EmailFrom (From Address for Reports) 
Email sent from ASSP acknowledging your submissions will be sent from this address. For example:  
Default: &lt;postmaster@assp-notspam.org&gt; 

-EmailHelp (Help Address) 
Any mail sent by local/authenticated users to this username will be interpreted as a request for help. Do not put the full address here, just the user part. For example: assp-help. The user would then send to assp-help@anylocaldomain.com. 
Default: assp-help 

-EmailAdmins (Authorized Addresses* ) 
Mail from any of these addresses can add/remove to/from redlist, spamlovers, noprocessing. May request an EmailBlockReport for a list of users. Accepts specific addresses (user@example.com), user parts (user) or entire domains (@example.com)  

-EmailAdminDomains (Restrict Email Admins to Domains*) 
Use this parameter to restrict users registered in EmailAdmins, EmailAdminReportsTo and EmailBlockTo to a list of domains or users, for which they can request BlockReports.
  The file: option is required. Use the following syntax to define an entry (one per line):
  EmailAdminAddress=>*@domain1,*@domain2 user@domain3 ...
  [user@domain]=>*@domain1,*@domain2 user@domain3 ...
  Wildcards are allowed to be used in the domain definition - like *@*.domain.tld - separate multiple domains by comma or space.
  If a BlockReport is requested for a not allowed email address, the complete BlockReport request will be ignored.
  If an EmailAdmins address is not registered in this parameter, he/she is able to request BlockReports for all domains.  

-EmailSenderOK (Accept Emails (Reports) from these external addresses*) 
Allow these external domains/addresses to send to the email
interface. This overwrites the standard behaviour, which allows only reqests from local or authenticated users. Accepts specific addresses (user@domain.com), user parts (user) or entire domains (@domain.com)  

-EmailSenderNotOK (Not Authorized Addresses*) 
Mail from any of these addresses are not accepted from Email Interface. Accepts specific addresses (user@example.com), user parts (user) or entire domains (@example.com).  

-EmailSenderIgnore (Ignore Not Authorized Addresses*) 
Mail from any of these addresses are not accepted from Email Interface, except "Help Report", "Analyze Report" and "Block Report/Resend". Accepts specific addresses (user@example.com), user parts (user) or entire domains (@example.com). The user will get not informed about the denied request.  

-EmailSpam (Report Spam to this Address) 
Any mail sent or forwarded by local/authenticated users to this username will be interpreted as a report about a Spam that got through (counts 2x). Do not put the full address here, just the user part. For example: assp-spam. The user would then send to assp-spam@anylocaldomain.com.
  This works best if the mails are reported as attachments or copied into a new mail (header and body), because forwarding the mail will remove the original header.
  You can sent multiple emails as attachments. Each attached email-file must have the extension defined in "maillogExt". In this case only the attachments will be processed. Multiple attachments get truncated to MaxBytesReports. To use this multi-attachment-feature an installed Email::MIME::Modifier module in PERL is needed. 
Default: assp-spam 

-EmailHam (Report NotSpam to this Address) 
Any mail sent or forwarded by local/authenticated users to this username will be interpreted as a good mail that was mistakenly listed as spam (counts 4x). Do not put the full address here, just the user part. For example: assp-notspam. The user would then send to assp-notspam@anylocaldomain.com
This works best if the mails are reported as attachments or copied into a new mail (header and body) because forwarding the mail will remove the original header. You can sent multiple emails as attachments. Each attached email-file must have the extension defined in "maillogExt". In this case only the attachments will be processed. Multiple attachments get truncated to MaxBytesReports. To use this multi-attachment-feature an installed Email::MIME::Modifier module in PERL is needed. 
Default: assp-notspam 

-MaxBytesReports (Error Max Bytes) 
How many bytes of an error report (EmailHam, EmailSpam) will ASSP look at. For example: 20000. 
Default: 20000 

-EmailErrorsReply (Reply to Spam/NotSpam Reports) 
 
Default: REPLY TO SENDER 

-EmailErrorsTo (Send Copy of Spam/NotSpam Reports TO) 
Email sent from ASSP acknowledging your submissions will be sent to this address. For example: admin@domain.com  

-EmailErrorsModifyWhite (Spam/NotSpam Report will modify Whitelist ) 
If set to 'modify whitelist' NotSpam Reports will add email addresses to the Whitelist, Spam Reports will remove addresses from the Whitelist. If set to 'show whitelist' Spam Reports will show if addresses are whitelisted. This works best if the mails are reported as attachments or copied into a new mail (header and body) because forwarding the mail will remove the original header. 
Default: modify whitelist 

-EmailErrorsModifyNoP (Combined Spam Report and NoProcessing Deletion) 
If set to 'modify noProcessing' Spam Reports will remove email addresses from noProcessing list. If set to 'show noProcessing' Spam Reports will show if addresses are on noProcessing list. 
Default: modify noprocessing 

-EmailWhitelistAdd (Add to Whitelist Address) 
Any mail sent by local/authenticated users to this username will be interpreted as a request to add addresses to the whitelist.   Whole domains can be added by putting a wildcard in the userpart of the address: '*@example.com'. Do not put the full address here, just the user part. For example: assp-white. The user would then send to assp-white@anylocaldomain.com.
   
Default: assp-white 

-EmailWhitelistRemove (Remove from Whitelist Address) 
Any mail sent by local/authenticated users to this username will be interpreted as a request to remove addresses from the whitelist. Do not put the full address here, just the user part.For example: assp-notwhite. The user would then send to assp-notwhite@anylocaldomain.com.
   
Default: assp-notwhite 

-EmailWhiteRemovalAdminOnly (Allow  Whitelist Removals for Admins only ) 
Only the users defined in EmailWhitelistTo, EmailAdmins and EmailAdminReportsTo are able to remove addresses from the whitelist.  

-EmailWhitelistReply (Reply to Add to/Remove from Whitelist) 
 
Default: REPLY TO SENDER 

-EmailWhiteRemovalToRed (Add  Whitelist Removals To Redlist ) 
Addresses which are removed from Whitelist via EmailWhitelistRemove will automatically be added to the Redlist. The address can only be added again to the Whitelist after it is removed from the Redlist.  

-EmailWhitelistTo (Send Copy of Whitelist-Reports TO) 
Email sent from ASSP acknowledging your submissions will be sent to this address. For example: admin@domain.com  

-EmailRedlistAdd (Add to Redlist Address) 
Any mail sent by local/authenticated users to this username will be interpreted as a request to add the sender address to the redlist. Only the users defined in EmailRedlistTo, EmailAdmins and EmailAdminReportsTo are able to define a list of email addresses in the mail body.  Do not put the full address here, just the user part. For example: assp-red. The user would then send to assp-red@anylocaldomain.com.
   
Default: assp-red 

-EmailRedlistRemove (Remove from Redlist Addresses) 
Any mail sent by local/authenticated users to this username will be interpreted as a request to remove the sender address from the redlist. Only the users defined in EmailRedlistTo, EmailAdmins and EmailAdminReportsTo are able to define a list of email addresses in the mail body. 
  Do not put the full address here, just the user part. For example: assp-notred. The user would then send to assp-notred@anylocaldomain.com. 
Default: assp-notred 

-EmailRedlistReply (Reply to Add to/Remove from Redlist) 
 
Default: REPLY TO SENDER 

-EmailRedlistTo (Send Copy of Redlist-Reports TO) 
Email sent from ASSP acknowledging your submissions will be sent to this address. For example: admin@domain.com  

-EmailSpamLoverAdd (Add to SpamLover Addresses) 
Any mail sent by local/authenticated users to this username will be interpreted as a request to add the sender address to spamLovers. Only the users defined in EmailSpamLoverTo, EmailAdmins and EmailAdminReportsTo are able to define a list of email addresses in the mail body. Do not put the full address here, just the user part. For example: assp-spamlover. To use this option, you have to configure spamLovers in a plain ASCII file one address per line: file:files/bombre.txt". 
Default: assp-spamlover 

-EmailSpamLoverRemove (Remove from SpamLover Addresses) 
Any mail sent by local/authenticated users to this username will be interpreted as a request to remove the sender address from spamLovers. Only the users defined in EmailSpamLoverTo, EmailAdmins and EmailAdminReportsTo are able to define a list of email addresses in the mail body. 
  Do not put the full address here, just the user part. For example: assp-notspamlover 
Default: assp-notspamlover 

-EmailSpamLoverReply (Reply to Add to/Remove from SpamLovers) 
 
Default: REPLY TO SENDER 

-EmailSpamLoverTo (Send Copy of Spamlover-Change-Reports TO) 
Email sent from ASSP acknowledging your submissions will be sent to this address. For example: admin@domain.com  

-EmailNoProcessingAdd (Add to NoProcessing Addresses) 
Any mail sent by local/authenticated users to this username will be interpreted as a request to add the sender address to the noProcessing addresses. Only the users defined in EmailNoProcessingTo, EmailAdmins and EmailAdminReportsTo are able to define a list of email addresses in the mail body. Do not put the full address here, just the user part. For example: assp-nop. To use this option, you have to configure noProcessing in a plain ASCII file one address per line: "file:files/noprocessing.txt" 
Default: assp-nop 

-EmailNoProcessingRemove (Remove from noProcessing Addresses) 
Any mail sent by local/authenticated users to this username will be interpreted as a request to remove the sender address from noProcessing .
  Do not put the full address here, just the user part. Only the users defined in EmailNoProcessingTo, EmailAdmins and EmailAdminReportsTo are able to define a list of email addresses in the mail body. For example: assp-notnop. To use this option, you have to configure noProcessing in a plain ASCII file one address per line: "file:files/noprocessing.txt" 
Default: assp-notnop 

-EmailNoProcessingReply (Reply to Add to/Remove from noProcessing) 
 
Default: REPLY TO SENDER 

-EmailNoProcessingTo (Send Copy of NoProcessing-Change-Reports TO) 
Email sent from ASSP acknowledging your submissions will be sent to this address. For example: admin@domain.com  

-EmailBlackAdd (Add to BlackListed  Addresses) 
Any mail sent by local/authenticated users to this username will be interpreted as a request to add to blackListedDomains. Only the users defined in EmailAdmins and EmailAdminReportsTo are able to request an addition. Do not put the full address here, just the user part. For example: assp-black. To use this option, you have to configure blackListedDomains in a plain ASCII file one address per line: "file:files/blackdomains.txt"  
Default: assp-black 

-EmailBlackRemove (Remove from BlackListed Addresses) 
Any mail sent by local/authenticated users to this username will be interpreted as a request to remove from weightedAddresses .
  Do not put the full address here, just the user part. Only the users defined in EmailAdmins and EmailAdminReportsTo are able to request an addition. For example: assp-notblack. To use this option, you have to configure weightedAddresses in a plain ASCII file one address per line: "file:files/weightedAddresses.txt" 
Default: assp-notblack 

-EmailErrorsModifyPersBlack (Spam/NotSpam Report will modify Personal Blacklist *) 
Spam Reports will add email addresses to the Personal Blacklist, NotSpam Reports will remove addresses from the Personal Blacklist, if the report senders address matches. EmailAdmins will automatically add/remove to Personal Blacklist in a special way (from,*), which blocks an address for all recipients.
  Accepts specific addresses (user@domain.com), user parts (user) or entire domains (@domain.com). Wildcards are supported (fribo*@domain.com).
  Default is *@* , which matches all addresses. 
Default: *@* 

-EmailErrorsModifyNotPersBlack (Spam/NotSpam Report will not modify Personal Blacklist *) 
Spam Reports will not add email addresses to the Personal Blacklist, NotSpam Reports will not remove addresses from the Personal Blacklist, if the report senders address matches. 
  Accepts specific addresses (user@domain.com), user parts (user) or entire domains (@domain.com). Wildcards are supported (fribo*@domain.com).  

-EmailAdminsModifyGlobalBlack (EmailAdmins will block for all Recipients ) 
  EmailAdmins will automatically add/remove to Personal Blacklist using a wildcard (*) for the sender which blocks an address for all recipients. 
Default: On 

-EmailPersBlackAdd (Add to Personal BlackListed  Addresses) 
Any mail sent by local/authenticated users to this username will be interpreted as a request to add the listed address(es) to the personal blackListed addresses. Do not put the full address here, just the user part. 
  For example: assp-persblack.
  The add and remove is done via email-interface, by sending specific email addresses to 'EmailPersBlackAdd'  and 'EmailPersBlackRemove'.

  A local user can force a complete report about all his personal black list entries by defining an email address that begins with 'reportpersblack' in a remove or add request : eg: reportpersblack@anydomain.com or by sending an empty body.
  EmailAdmins will automatically add/remove in a special way (from,*), blocking for all recipients - if EmailAdminsModifyGlobalBlack is set.
  Only an admin can force a complete cleanup of all personal black entries for a specific email address for all local users - sending an email to 'EmailPersBlackRemove' with the address followed by ',*' in the body
  eg: address_to_remove@the_domain.foo,*
 
Default: assp-persblack 

-EmailPersBlackRemove (Remove from Personal BlackListed Addresses) 
Any mail sent by local/authenticated users to this username will be interpreted as a request to remove the listed address(es) from the personal blackListed addresses .
  Do not put the full address here, just the user part.
  For example: assp-notpersblack.
  The add and remove is done via email-interface, by sending specific email addresses to 'EmailPersBlackAdd'  and 'EmailPersBlackRemove'.
  A local user can force a complete report about all his personal black list entries by defining an email address that begins with 'reportpersblack' in a remove or add request : eg: reportpersblack@anydomain.com or by sending an empty body.
  Only an admin can force a complete cleanup of all personal black entries for a specific email address for all local users - sending an email to 'EmailPersBlackRemove' with the address followed by ',*' in the body
  eg: address_to_remove@the_domain.foo,*
   
Default: assp-notpersblack 

-EmailBlackReply (Reply to Add to/Remove from BlackListed) 
 
Default: REPLY TO SENDER 

-EmailBlackTo (Send Copy of Black-Change-Reports TO) 
Email sent from ASSP acknowledging your submissions will be sent to this address. For example: admin@domain.com  

-EmailAnalyze (Request Analyze Report) 
Any mail sent or forwarded by local/authenticated users to this username will be interpreted as a request for analyzing the mail. Do not put the full address here, just the user part. For example: assp-analyze 
Default: assp-analyze 

-EmailAnalyzeReply (Reply to Analyze Request) 
 
Default: SEND TO SENDER 

-EmailAnalyzeTo (Send Copy of Analyze-Reports) 
A copy of the Analyze-Report will be sent to this address. For example: admin@domain.com  

-DoAdditionalAnalyze (Spam and Ham Reports will trigger an additional Analyze Report ) 
Additional Analyze Report will be generated for Spam and Ham Reports. Setting the TO Address accordingly and choosing EmailAnalyzeTo will send the Analyze Report to the admin only.  

-EmailSenderNoReply (Do Not Reply To These Addresses*) 
Email sent from ASSP acknowledging your submissions will not be sent to these addresses. Accepts specific addresses (user@example.com), user parts (user) or entire domains (@example.com).
  Notes On Email Interface
    

-base (Directory Base) 
All paths are relative to this folder.
  Note: Display only. 
Default: . 

-spamlog (Spam Collection) 
The folder to save the collection of spam emails. This directory will be used in building the spamdb. For example: spam 
Default: spam 

-notspamlog (Not-spam Collection) 
The folder to save the collection of not-spam emails. This directory will be used in building the spamdb. For example: notspam 
Default: notspam 

-incomingOkMail (OK Mail) 
The folder to save non-spam (message ok). These are messages which are considered as HAM, but are not stored in the standard HAM folder because of our policy to use only confirmed HAM messages (whitelisted or local) for SpamDB. If you want to keep copies of ok mail then put in a directory name. This directory will not be used in building the spamdb. 
Default: okmail 

-discarded (Discarded Spam) 
The folder to save discarded spam-messages. These are Spam messages which are not stored for building the spamdb but for resending with an EmailBlockReport. If you want to keep copies of discarded Spam then put in a directory name. 
Default: discarded 

-viruslog (Attachment/Virus Collection) 
The folder to save rejected attachments and virii. Leave this blank to not save these files (default). If you want to keep copies of rejected content then put in a directory name. Note: you must create the directory. This directory will not be used in building the spamdb. For example: quarantine 
Default: quarantine 

-correctedspam (False-negative Collection) 
Spam that got through -- counts double. This directory will be used in building the spamdb. For example: errors/spam 
Default: errors/spam 

-correctednotspam (False-positive Collection) 
Good mail that was listed as spam, count 4x. This directory will be used in building the spamdb. For example: errors/notspam 
Default: errors/notspam 

-resendmail (try to resend this files) 
ASSP will try to resend the files in this directory to the original recipient. The files must have the "maillogExt" extension and must have the SMTP-format. ASSP will try to send every  file up to ten times (with 5 minutes delay). If the resend fails ten times, the file will be renamed to *.err, on success the file will be deleted!
For example: resendmail. This requires an installed Email::Send module in PERL. 
Default: resendmail 

-maillogExt (Extension for Mail Files) 
Enter the file extension (include the period) you want appended to the mail files in the mail collections. For Example: .eml 
Default: .eml 

-spamdb (Spam Bayesian Database File) 
The output file from rebuildspamdb.pl.
  Write "mysql" to use a MySQL table instead of a local file, in this case you need to edit the MySQL parameters starting with myhost. Last Run Rebuildspamdb 
Default: spamdb 

-whitelistdb (E&lt;!--get rid of google autofill--&gt;mail Whitelist Database File) 
The file with the whitelist.
  Write "mysql" to use a MySQL table instead of a local file, in this case you need to edit the MySQL parameters starting with myhost. 
Default: whitelist 

-redlistdb (E&lt;!--get rid of google autofill--&gt;mail Redlist Database File) 
The file with the redlist.

  Write "mysql" to use a MySQL table instead of a local file, in this case you need to edit MySQL parameters starting with myhost.The Redlist serves several purposes:
- the Redlist is a list of addresses that cannot contribute to the 
whitelist and which are not considered local even if their mail is 
from a local computer. For example, if someone goes on a vacation and 
turns on their autoresponder, put them on the redlist until 
they return. Then as they reply to every spam they receive they won't 
corrupt your non-spam collection or whitelist. There is also a redRe available where you can put some text from standard out of office messages, to automatically add a local user to the redlist when they send the out of office message, for example: \[autoreply\]
- Redlisted addresses will not be added to the Whitelist.
This is used by EmailWhiteRemovalToRed to prevent repeated adding to the whitelist.
So if somebody whitelisted ebay@ebay.com you will surely remove that from the whitelist, but you can also be sure, that somebody will add that address again. Putting ebay@ebay.com into the redlist will give that pause.
- Redlisted messages will not be stored in the 
SPAM/NOTSPAM-collection.  
Default: redlist 

-ldaplistdb (LDAP/VRFY Cache) 
The file with the LDAP/VRFY-cache.  . 
Default: ldaplist 

-ldapnotfounddb (LDAP/VRFY Not Found Cache) 
The file with the LDAP/VRFY-NotFound-Cache, see also LDAPShowNotFound.  
Default: ldapnotfound 

-droplist (Drop also Connections from these IPs*) 
Automatically downloaded (http://www.spamhaus.org/drop/drop.lasso) list of IP's which should be blocked right away.  
Default: file:files/droplist.txt 

-delaydb (Delaying Database) 
The file with the delay database.Write "mysql" to use a MySQL table instead of a local file, in this case you need to edit the MySQL parameters starting with myhost.  
Default: delaydb 

-pbdb (PenaltyBox Database) 
The directory/file with the penaltybox database files. For removal of entries from PenaltyBlackBox use noPB.
 For removal of entries from WhiteBox noPBwhite. For  whitelisting IP addresses use noProcessingIPs. For blacklisting IP addresses use denySMTPConnectionsFrom. 
 
  
Default: pb/pbdb 

-persblackdb (Personal Blacklist Database File) 
The file with the personal blacklist. The check of the personal black list is done shortly after the RCPT TO: command. This command will be rejected if an entry is found - any other setting except send250OK and send250OKISP will be ignored.
 
Default: persblack 

-griplist (GReyIPlist Database) 
The file with the current GRey-IP-List  database -- make this blank if you don't use it. 
Default: griplist 

-myhost (MySQL hostname or IP) 
You need Tie::RDBM to use MySQL instead of local files.
  This way you can share whitelistdb, delaydb and redlistdb between servers if "mysql" is written into their file-path.  

-mydb (MySQL database name) 
This database must exist before starting ASSP,
  necessary tables will be created automatically into this database  

-myuser (MySQL username) 
This user must have CREATE privilege on the configured database in order for tables to be created automatically  

-mypassword (MySQL password) 
  

-logfile (ASSP Logfile) 
Blank if you don't want a log file. Change it to maillog.log if you don't want auto rollover.
  NOTE: Changing this field requires restarting ASSP before changes take effect. 
Default: logs/maillog.txt 

-pidfile (PID File) 
Blank to skip writing a pid file. *nix users need pid files.
  Leave it blank in Windows. You have to restart the service before you get a pid file in the new location.Notes On File Path 
Default: pid 

-sendAllSpam (Copy Spam and Send to this Address) 
ASSP will deliver a copy of spam emails to this address if the collection mode in the collection section is set to do so (eg. baysSpamLog ). For example: spammonitor@example.com. The address can be different depending on the recipient. The literal USERNAME (case sensitive) is replaced by the user part of the recipient, the literal DOMAIN (case sensitive) is replaced by the domain part of the recipient. For example: USERNAME@Spam.DOMAIN, USERNAME+Spam@DOMAIN, spammonitor@DOMAIN  

-ccSpamInDomain (Copy Spam and Send to this Address per Domain*) 
ASSP will deliver an additional copy of spam emails of a domain to this address - if the domain of the recipient-address is matched. For example: monitorspam@example1.com|monitor@example2.com.  

-sendAllDestination (SMTP Destination for Spam Copies) 
Port to connect to when  Spam messages are copied. If blank they go to the main smtpDestination. eg "10.0.1.3:1025".  

-ccSpamFilter (Copy Spam to these Recipients Only*) 
Restricts Copy Spam to these recipients. Accepts specific addresses (user@example.com), user parts (user) or entire domains (@example.com). Wildcards are supported (fribo*@example.com).  

-ccSpamAlways (Copy Spam to these Recipients always*) 
Copy Spam to these recipients regardless of collection mode. Accepts specific addresses (user@example.com), user parts (user) or entire domains (@example.com).  Wildcards are supported (fribo*@example.com).  

-ccSpamNeverRe (Do Not Copy Spam Regular Expression*) 
Never Copy Spam regardless of collection mode. Put anything here to identify messages which should not be copied.  

-ccMaxScore (Do Not Copy Messages Above This MessageTotal score) 
Messages whose score exceeds this threshold will not be copied.  For example: 75  

-ccMaxBytes (Cut Copied Spam to MaxBytes Lenght) 
MaxBytes will be used to cut off copied mails, thereby reducing the load considerably. 
Default: On 

-spamSubjectCC (Prepend Spam Subject to Copied Spam) 
If set spamSubject gets prepended to the subject of the copied message.  

-spamTagCC (Prepend Spam Tag to Copied Spam) 
The check which caused the spam detection will be prepended to the subject of the message. For example: [DNSBL] 
Default: On 

-sendAllHamDestination (SMTP Destination for Ham Copies) 
Port to connect to when  Ham messages are copied. If blank they go to sendAllDestination. eg "10.0.1.3:1025"  

-sendHamInbound (Copy Incoming Ham and Send to this Address) 
If you put an address in this box  ASSP will forward a copy of notspam messages from outside to this address. The literal USERNAME is replaced by the user part of the recipient, the literal DOMAIN is replaced by the domain part of the recipient. For example: archiv@example.com, USERNAME@mybackup.domain, catchallforthis@DOMAIN  

-sendHamOutbound (Copy Outgoing Ham and Send to this Address) 
If you put an address in this box ASSP will forward a copy of outgoing notspam messages to this address. The literal USERNAME is replaced by the user part of the recipient, the literal DOMAIN is replaced by the domain part of the recipient. For example: archiv@example.com, USERNAME@mybackup.domain, catchallforthis@DOMAIN  

-ccHamFilter (Copy Ham Filter*) 
Copy Not-Spam to these addresses only. Accepts specific addresses (user@example.com), user parts (user) or entire domains (@example.com). Wildcards are supported (fribo*@example.com).  

-ccnHamFilter (Do Not Copy Ham Filter*) 
Do Not Copy Ham to these addresses. Accepts specific addresses (user@example.com), user parts (user) or entire domains (@example.com). Wildcards are supported (fribo*@example.com).  

-ccMailReplaceRecpt (ccMail Recipient Replacement) 
The recipient replacement (ReplaceRecpt) rules from the "Recipients/Local Domains" section, will be used to replace ccMail recipients. For example: sendHamInbound = USERNAME@yourspamdomain.lan - in this case you are able to detect the target domain "yourspamdomain.lan" in a rule and you can replace the recipient/domain depending on its values and/or on the senders address.
Notes On CC Messages  

-spamaddresses (SpamBucket Addresses* ) 
Mail to any of these addresses are always spam and will contribute to the spam-collection unless from someone on the whitelist. Accepts specific addresses (user@example.com), user parts (user) or entire domains (@example.com).   

-noCollecting (Do Not Collect Messages from/to these Addresses*) 
Accepts specific addresses (user@example.com), user parts (user) or entire domains (@example.com).  

-noCollectRe (Do Not Collect Messages - Content Based*) 
  

-UseSubjectsAsMaillogNames (Use Subject as Maillog Names) 
You can turn this on to help you manually identify mail in your spam and non-spam collections. 
Default: On 

-MaxAllowedDups (Max Number of Duplicate File Names) 
The maximum number of logged files with the same filename (subject) that are stored in the spam folder (spamlog), if UseSubjectsAsMaillogNames is selected. A low value reduces the number of possibly duplicate mails, assuming that mails with the same subject will have the same content. A value of 0 disables this feature. If this number of files with the same filename is reached, new files will be stored in the 'discarded' folder, which has to be defined ( in addition to spamlog ) for this feature to work. 
Default: 5 

-AllowedDupSubjectRe (Regular Expression to Allow Unlimited Duplicates *) 
Messages with subject matching this regular expression will be collected regardless of the setting in MaxAllowedDups .  

-MaxFileNameLength (Max Length of File Names) 
The maximum character count that is used from the mail subject to build the file name of the logged file, if UseSubjectsAsMaillogNames is selected. This could be usefull, if your mail clients having trouble to build the resend file name (right button - URL) correctly in block reports. Every non printable character will be replaced by a 4 byte string in this link. 
Default: 30 

-DoNotCollectRed (Do Not Collect Red Mails) 
Mails matching redRe will not be stored in the collection folders. 
Default: On 

-KeepWhitelistedSpam (Do Not Delete Whitelisted Spams) 
Mails matching  Whitelist will not be removed from the Spam folder.  

-DoNotCollectBounces (Do Not Collect Bounced Mails) 
Mails matching BounceSenders will not be collected. 
Default: On 

-NoMaillog (Dont Collect Mail) 
Check this if you're using Whitelist-Only and don't care to save mail to build the Bayesian database.  

-MaxFiles (Max Files) 
Maximum number of files to keep in each collection (spam and nonspam)
 
Default: 10000 

-MaxBytes (Max Bytes) 
How many bytes of the message will ASSP look at? Mails stored in the collecting folders will be truncated to this size if StoreCompleteMail is not set. 
Default: 10000 

-StoreCompleteMail (Store the Complete Mail) 
If set, ASSP will analyze only MaxBytes of the mail, but  will store the complete mail up to the selected limit. This could be usefull for example, if you want to resend blocked messages. Be carefull using this option, your disk could be filled up very fast! 
Default: up to 500 kByte 

-baysNonSpamLog (OK Mail) 
Where to store non spam (message ok) messages. These are messages which are considered as HAM, but should not stored in the standard HAM folder because of our policy to use only confirmed HAM messages (whitelisted or local) for SpamDB. Set incomingOkMail accordingly if you choose 'okmail folder'. 
Default: okmail folder 

-NonSpamLog (Non Spam) 
Where to store whitelisted/local non spam messages. 
Default: notspam folder 

-SpamLog (Store Spam) 
Set this to 'disabled' if you do not want to store any Spam regardless of settings in. Default: enabled (store in folder spamlog ). 
Default: enabled 

-noProcessingLog (NoProcessing Non Spam) 
Where to store noprocessing non spam messages.  

-whitelistedLog (Whitelisted Non Spam) 
Where to store whitelisted non spam messages. 
Default: notspam folder 

-localLog (Local Non Spam) 
Where to store local non spam messages. 
Default: notspam folder 

-AttachLog (Rejected Attachments) 
Where to store rejected mail+attachments.  

-SpamVirusLog (Virus Infected) 
Where to store virus infected messages.   

-spamBombLog (SpamBombs) 
Where to store spam bombs -> DoBombHeaderRe, DoBombRe, DoBlackRe. 
Default: discard folder and sendAllSpam 

-blDomainLog (Blacklisted Domains - DoBlackDomain) 
Where to store blacklisted domain messages. 
Default: spam folder and sendAllSpam 

-invalidHeloLog (Invalid Helos , Forged Helos, Blacklisted Helos) 
Where to store invalid helo messages. 
Default: discard folder and sendAllSpam 

-spamBucketLog (Spam Collect Addresses) 
Where to store emails addressed to Spam Collect Addresses. 
Default: spam folder 

-baysSpamLog (Bayesian Spams - DoBayesian) 
Where to store Bayesian spam messages. 
Default: discard folder and sendAllSpam 

-RBLFailLog (DNSBL Failures - ValidateRBL) 
Where to store DNSBL Failure spam messages. 
Default: spam folder and sendAllSpam 

-SPFFailLog (SPF/ SRS Failures) 
Where to store SPF / SRS Failure spam messages. 
Default: spam folder and sendAllSpam 

-URIBLFailLog (URIBL Failures - ValidateURIBL) 
Where to store URIBL Failure spam messages. 
Default: spam folder and sendAllSpam 

-spamISLog (Invalid Local Sender - DoNoValidLocalSender) 
Where to store messages from a local domain with an unknown userpart.  

-spamSBLog (Blocked Country - DoCountryBlocking, DoOrgBlocking) 
Where to store messages from a blocked country. 
Default: spam folder and sendAllSpam 

-spamMSLog (Message Limit Blocks - DoPenaltyMessage) 
Where to store Message Scoring Limit rejected messages.  
Default: spam folder and sendAllSpam 

-spamDenyLog (Denied IP addresses - DoDenySMTP) 
Where to store IP denied  messages.  
Default: discard folder and sendAllSpam 

-BackLog (Backscatter check failed) 
Where to store FBMTV rejected messages.  
Default: discard folder 

-FilterLogging (Logging for filters are located in their section) 
Attachment ( AttachmentLog )
Bayesian ( BayesianLog )
Bomb ( BombLog )
Connections ( ConnectionLog )
Deny SMTP Connections ( denySMTPLog )
DNSBL ( RBLLog )
Greylisting/Delaying ( DelayLog )
LDAP ( LDAPLog )
Maintenance ( MaintenanceLog )
Message Scoring ( MessageLog )
Message-ID signing ( MSGIDsigLog )
PenaltyBox Extreme ( PenaltyExtremeLog )
PenaltyBox ( PenaltyLog )
Relay ( RelayLog ) 
Report ( ReportLog )
RWL ( RWLLog )
SenderBase ( SenderBaseLog )
Session Limit (SessionLog )
SPF ( SPFLog )
SSL ( SSLLog )
Trap ( TrapLog )
URIBL ( URIBLLog )
User Validation ( ValidateUserLog )
Validate Helo ( ValidateHeloLog )
Validate Sender ( ValidateSenderLog )
Virus Check ( ScanLog )
VRFY ( VRFYLog )  
Default: On 

-Notify (Notification Email To) 
Email address(es) to which you want ASSP to send a notification email, if a matching log entry ( NotifyRe , NoNotifyRe ) is found. Separate multiple entries by "|". This requires an installed Email::Send module in PERL.  

-NotifyRe (Do Notify, if log entry matches*) 
Regular Expression to identify loglines for which a notification message should be send.
  usefull entries are:

  autoupdate: - to get informed about an autoupdate of the running script
  adminupdate: - for config changes
  admininfo: - for admin information
  option list file: - for option file reload
  error: - for any error
  restart - to detect a ASSP restart
  Admin connection - for GUI logon
  You may define a comma separated list (after '=>') of recipients in every line, this will override the default recipient defined in 'Notify'. For example: adminupdate=>user1@yourdomain.com,user2@yourdomain.com.
  As third parameter after a second ('=>') you can define the subject line for the notification message.
  for example: adminupdate:=>user1@yourdomain.com,user2@yourdomain.com=>configuration was changed
  or: adminupdate:=>=>configuration was changed.  

-NoNotifyRe (Do NOT Notify, if log entry matches*) 
Regular Expression to identify loglines for which no notification message should be send.  

-noLog (Dont Log these IPs*) 
Enter IP addresses that you don't want to be logged, separated by pipes (|).
  This can be IP address of the SMTP service monitoring agent. For example: 145.145.145.145|145.146.  

-noLogRe (Regular Expression to Identify NoLog-Mails*) 
Put anything here to identify mails that you don't want to be logged.  

-noLogLineRe (Regular Expression to Suppress Log-Messages*) 
Put anything here to identify log messages that you want to be suppressed. For example: max errors|collect 
Default: max errors|collect 

-allLogRe (Regular Expression to Identify Messages from/to Problematic Addresses *) 
Put anything here to identify mails from/to addresses you want to look at for problem solving. Mails identified will also be set to StoreCompleteMail.  

-subjectStart (Subject Start Delimiter) 
Start delimiter of subject in log  
Default: [ 

-subjectEnd (Subject End Delimiter) 
End delimiter of subject in log 
Default: ] 

-regexLogging (Regex Match logging) 
Show matching regex in log.   

-ipmatchLogging (IP Matches Logging) 
Enables logging of IP addresses matches in the maillog. Will show a comment instead of the range if there is text after the IP ranges (and before any numbersign)  eg. 182.82.10.0/24 AOL  

-slmatchLogging (Logging Address Matches) 
Enables logging of address matches in the maillog.  

-uniqueIDPrefix (Prepend Unique ID logging) 
Prepend ID. For example: m1- 
Default: m- 

-tagLogging (Spam Tag Logging) 
Add spam tag to log. 
Default: On 

-ExceptionLogging (Timeout Exception Logging) 
  

-replyLogging (SMTP Status Code Reply Logging) 
  

-AUTHLogUser (Username Logging) 
Write the username for AUTH (PLAIN/LOGIN) to maillog.txt.  

-AUTHLogPWD (Password Logging) 
Write the userpassword for AUTH (PLAIN/LOGIN) to maillog.txt.  

-expandedLogging (Logging Records include IP &amp; MailFrom) 
 
Default: On 

-sysLog (SYSLOG Centralized Logging) 
Enables logging to UNIX Syslog. Needs Sys::Syslog for local (UNIX/LINUX) logging or Net::Syslog for Windows or Network logging.  

-sysLogPort (Syslog Port (UDP)) 
Port for Syslog logging with Net::Syslog. 
Default: 514 

-SysLogFac (Syslog Facility) 
Syslog Facility. Valid are kern, user, mail, daemon, auth, syslog, lpr, news, uucp, cron, authpriv, ftp, local0, local1, local2, local3, local4, local5, local6 
Default: mail 

-sysLogIp (Syslog IP) 
IP Address of your Syslog Daemon for Syslog logging with Net::Syslog. 
Default: 127.0.0.1 

-asspLog (ASSP local logging) 
ASSP manages local logging. The logs are stored inside the directory where ASSP is installed. This is needed if you want to use any of the "Block Reporting" and "View Maillog Tail" features like searching, deleting, moving, resending of messages. 
Default: On 

-LogRollDays (Roll the Logfile How Often?) 
ASSP closes and renames the log file after this number of days. 
Default: 1 

-MaxLogAge (Max Age of Logfiles) 
The maximum file age in days of logfiles. If a logfile is older than this number in days, the file will be deleted. A value of 0 disables this feature and no logfile will be deleted because of its age. 
Default: 60 

-LogNameMMDD (No Year in LogName) 
The standard name for the logfile is YY-MM-DD.maillog.txt, use this option to set it to MM-DD.maillog.txt  

-LogDateFormat (Date/Time Format in LogDate) 
Use this option to set the logdate. The default value is 'MMM-DD-YY hh:mm:ss'. The following (case sensitive !) replacements will be done:
 YYYY - year four digits
 YY - year two digits
 MMM - month three characters - like Oct Nov Dec
 MM - month numeric two digits
 DDD - day three characters - like Mon Tue Fri
 DD - day numeric two digits
 hh - hour two digits
 mm - minute two digits
 ss - second two digits
 A value has to be defined for every part of the date/time. Allowed separators in date part are '_ -.' - in time part '-_.:' . 
Default: MMM-DD-YY hh:mm:ss 

-LogDateLang (Date/Time Language) 
Select the language for the day and month if LogDateFormat contains DDD and/or MMM.  

-enableWORS (Windows Output Record Separator) 
Checked means write CRLF to the end of the logfile instead of the standard LF. This can only be used if LogCharset is set to 'System Default'.  

-silent (Silent Mode) 
Checked means don't print log messages to the console.   

-debug (General Debug Mode) 
Checked sends debugging info to a .dbg file.
  Leave this unchecked unless there is a program error you are trying to track down.  

-DebugRollTime (Roll the Debugfile How Often?) 
ASSP closes and opens a new debug file after this number of seconds. 
Default: 1800 

-Win32Debug (Win32 OutputDebugString) 
Make Win32 OutputDebugString available. Needs Win32::API::OutputDebugString  

-IgnoreMIMEErrors (Ignore MIME Errors) 
Errors, based on wrong email MIME contents, will not be written to log! 
Default: On 

-ConTimeOutDebug (Connection Timeout Debug Mode) 
Select to debug SMTP connections that are running into timeout!  

-RegExLength (RegEx Length in Log) 
Defines how many bytes of a matching Regular Expression will be shown in the log
  Some matching Regular Expressions are too long for one line. Default: 32 
Default: 32 

-sendNoopInfo (Send NOOP Info) 
Checked means you want ASSP to send a "NOOP Connection from $ip" message to your SMTP server.
  
  Notes On Logging
    

-LDAPLog (Enable LDAP logging) 
 
Default: standard 

-DoLDAP (Do LDAP lookup for valid local addresses ) 
Check local addresses against an LDAP database before accepting the message.Note: Checking this requires filling in the other LDAP parameters like LDAPHost.This requires an installed NET::LDAP module in PERL.  

-LDAPHost (LDAP Host(s) ) 
Enter the DNS-name(s) or IP address(es) of the server(s) that run(s) the LDAP database. Second entry is backup. For example: localhost. Separate entries with pipes: LDAP-1.domain.com|LDAP-2.domain.com 
Default: localhost 

-DoLDAPSSL (Use SSL with LDAP (ldaps)) 
ASSP will use 'ldaps (SSL port 636)' instead of ldap (port 389) or 'ldaps (TLS over port 389)'. The Perl module IO::Socket::SSL must be installed to use SSL or TLS!  

-LDAPtimeout (LDAP Query Timeout) 
Timeout when connecting to the remote server. 
Default: 15 

-LDAPLogin (LDAP Login) 
Most LDAP servers require a login and password before they allow queries.Enter the DN specification for a user with sufficient permissions here.For example: cn=Administrator,cn=Users,DC=yourcompany,DC=com  

-LDAPPassword (LDAP Password) 
Enter the password for the specified LDAP login here.  

-LDAPVersion (LDAP Version) 
Enter the version for the specified LDAP here. 
Default: 3 

-ldLDAPRoot (LDAP Root container for Local Domains) 
The LDAP lookup will use this container and all sub-containers to match the local domain query.The literal DOMAIN is replaced by the domain part of SMTP recipient (eg. domain.com) during the search.For example: DC=yourcompany,DC=com.If you use DOMAIN here, you must check "LDAP failures return false" below or non local domains will be treated as local. If not defined, LDAPRoot will be used.  

-ldLDAPFilter (LDAP Filter for Local Domains) 
This filter is used to query the LDAP database. This strongly depends on the LDAP structure.The filter must return an entry if the domain must be relayed.The literal DOMAIN (case sensitive) will be replaced by the domain name during the search.  

-LDAPRoot (LDAP Root container for Local Addresses) 
The LDAP lookup will use this container and all sub-containers to match the local email address query.The literal DOMAIN is replaced by the domain part of SMTP recipient (eg. domain.com) during the search.For example: DC=yourcompany,DC=com.If you use DOMAIN here, you must check "LDAP failures return false" below or non local domains will be treated as local.  

-LDAPFilter (LDAP Filter for Local Addresses) 
This filter is used to query the LDAP database. This strongly depends on the LDAP structure.The filter must return an entry if the recipient address matches with that of any user.The literal EMAILADDRESS is replaced by the fully qualified SMTP recipient (eg. user@example.com) during the search.The literal USERNAME (case sensitive) is replaced by the user part of SMTP recipient (eg. user) during the search.The literal DOMAIN (case sensitive) is replaced by the domain part of SMTP recipient (eg. domain.com) during the search.For example: (proxyaddresses=smtp:EMAILADDRESS) or (|(mail=EMAILADDRESS)(mailaddress=EMAILADDRESS))  

-LDAPcrossCheckInterval (Clean Up local LDAP Database) 
Delete outdated entries from the LDAP cache. Crosscheck LDAP cache to LDAP server and delete not existing entries.
  Note: the current timeout must expire before the new setting is loaded, or you can restart.
  Defaults to 12 hours. Is only used, if ldaplistdb is defined in the filepath section. 
Default: 6 

-forceLDAPcrossCheck (force to run LDAP/VRFY-CrossCheck - now.) 
ASSP will force to run a LDAP/VRFY-CrossCheck now!&nbsp;  

-MaxLDAPlistDays (Max LDAP/VRFY cache Days) 
This is the number of days an address will be kept on the local LDAP cache without any email to this address. 0 disables the cache. 
Default: 7 

-LDAPFail (LDAP failures return false) 
LDAP failures return false when an error occurs in LDAP lookups.Notes On LDAP   

-BounceSenders (Bounce Senders*) 
Envelope sender addresses treated as bounce origins. Null sender (\) is always included.
 Accepts specific addresses (postmaster@example.com), usernames (mailer-daemon), or entire domains (@bounces.domain.com)Separate entries with pipes: |. For example: postmaster|mailer-daemon 
Default: mailer-daemon 

-DoMSGIDsig (Do Message-ID Signing) 
If activated, the message-ID of each outgoing message will be signed with an unique Tag and every incoming mail from BounceSenders will be checked against this. This tagging is called FBMTV for "FBs Message-ID Tag Validation" and is worldwide unique to ASSP. This tag will be removed from any incoming email, to recover the original references in the mail header. Scoring is done  with msigValencePB 
  This check requires an installed Digest::SHA1 module in Perl. 
Default: block 

-MSGIDsigLog (Enable Message-ID signing logging) 
 
Default: standard 

-MSGIDpreTag (Message-ID pre-Tag for MSGID-TAG-generation) 
To use Message-ID signing and to create the MSGID-Tags, a pre-Tag is needed. This Tag must be 2-5 characters [a-z,A-Z,0-9] long. 
Default: assp 

-MSGIDSec (Message-ID Secrets for MSGID-TAG-generation*) 
To use Message-ID signing and to generate the MSGID-Tags, at least one secret key is needed, up to ten are possible.
  The notation is : generationnumber[0-9]=secretKey. Multiple paires are separated by pipes (|). Do not define spaces, tabs and '=' as part of the keys(secrets)! 
Default: 0=asspv1 

-MSGIDsigAddresses (Do MSGID-Signing For These Addresses Only* ) 
Only messages from any of these addresses will be tagged and checked by FBMTV. Accepts specific addresses (user@domain.com), user parts (user) or entire domains (@domain.com). If empty FBMTV will be done for all addresses.  

-noMSGIDsigRe (Skip Message-ID signing, mail content dependend*) 
Use this to skip the Message-ID tagging depending on the content of the email. If the content of the email matches this regular expression (checking MaxBytes only), FBMTV will not be done. For example: 'I am out of office' . 
Default: out of officeI|on leave 

-noRedMSGIDsig (Skip Message-ID signing for Redlisted mails) 
If selected, FBMTV will not be done for redlisted emails! 
Default: On 

-DoBackSctr (Do DNS-Backscatter Detection) 
If activated, the IP-address of each message received for null sender,bounced or postmaster will be checked against BackSctrServiceProvider below.
   For more information about backscatter detection please read http://www.backscatterer.org/?target=usage.  

-BacksctrLog (Enable DNS-Backscatter detection logging) 
 
Default: standard 

-BackDNSInterval (Backscatter-DNS Cache Refresh Interval) 
IP's in cache will be removed after this interval in days. 0 will disable the cache.  
Default: 7 

-BackSctrServiceProvider (ServiceProvider for Backscatterer Detection*) 
ServiceProvider for DNS check on Backscatterer. Possible value is ips.backscatterer.org for DNS check.The following configurations are valid for all Backscatter Detection Options! 
Default: ips.backscatterer.org 

-Back250OKISP (Send 250 OK if Backscatter Detection fails) 
If Backscatter check fails for a bounced mail , ASSP will send "250 OK" , but will discard the mail, if the check is configured to block! 'To ISP' means sender in ispip.  
Default: To ISP 

-noBackSctrRe (Regular Expression to Skip all BackScatter Checks*) 
If the content of a mail matches these regular expressions, all BackScatter checks will be skipped.  

-noBackSctrAddresses (Do not Backscatter detection for these Addresses * ) 
Mail to and from any of these addresses will not be tagged and checked by the backscatter option. Accepts specific addresses (user@domain.com), user parts (user) or entire domains (@domain.com).  

-noBackSctrIP (Exclude these IP addresses and Hostnames from any Backscatter detection*) 
Enter IP addresses and Hostnames that you want to exclude from FBMTV, separated by pipes (|). 
  Notes On Backscatter Detection  

-UseLocalDNS (Use System Default DNS) 
Use system default DNS Name Servers. 
Default: On 

-DNSResponseLog (Show DNS Name Servers Response Time in Log) 
You can use this to arrange DNSServers for better performance. Put the fastest first.  

-DNSServers (Overwrite Domain Name Servers*) 
 Note: UseLocalDNS must be disabled.  

-DNStimeout (DNS Query Timeout) 
Global DNS Query Timeout for DNSBL, RWL, URIBL, PTR, SPF, MX and A record lookups. 
Default: 5 

-DNSretry (DNS Query Retry) 
Global DNS Query Retry. Set the number of times to try the query. 
Default: 1 

-DNSretrans (DNS Query Retrans) 
Global DNS Query Retransmission Interval. Set the retransmission interval. 
  Notes On DNS Setup 
Default: 3 

-enableSSL (Enable TLS support on  listenPorts) 
This enables STARTTLS on listenPort, listenPort2 and relayPort if the paths to your SSL Certificate ( SSLCertFile ) and SSL Key (SSLKeyFile) are set correctly. If you do not have valid certificates, you may generate both files online with www.mobilefish.com or you may use OpenSSL to generate Self-signed SSL certificates!. Changing this requires a restart of ASSP.  

-SSL_version (SSL version used for transmission) 
Sets the version of the SSL protocol used to transmit data. The default is SSLv2/3,
  which auto-negotiates between SSLv2 and SSLv3. You may specify 'SSLv2', 'SSLv3', or 'TLSv1' (case-insensitive) if you do not want this behavior. 
Default: SSLv2/3 

-SSL_cipher_list (SSL key cipher list) 
If this option is set the cipher list for the connection will be set to the given value, e.g. something like 'ALL:!LOW:!EXP:!ADH'. Look into the OpenSSL documentation (http://www.openssl.org/docs/apps/ciphers.html#CIPHER_STRINGS) for more details.
 If this option is not used (default) the openssl builtin default is used which is suitable for most cases.  

-SSLLog (Enable SSL logging) 
 
Default: standard 

-noTLSIP (Exclude these IP addresses and Hostnames from TLS*) 
Enter IP addresses and Hostnames that you want to exclude from starting TLS. For example, put all IP addresses here, which have trouble to switch to TLS every time. 
Default: file:files/notls.txt 

-NoTLSlistenPorts (Disable SSL support on listenPorts) 
This disables TLS/SSL on the listenPorts listenPort , listenPort2 and relayPort . The listener definition here has to be the same like in the port definitions. Separate multiple entries by "|".Examples: 25, 127.0.0.1:25, 127.0.0.1:25|127.0.0.2:25   

-sendEHLO (Send EHLO) 
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 or to satisfy XCLIENT/XFORWARD helo offers, because EHLO is needed before STARTTLS or XCLIENT/XFORWARD could be used.  

-SSLRetryOnError (Retry TLS on &quot;SSL want a read first&quot; error) 
If selected, ASSP retries 3 times to establish a TLS connection, if the peer was not ready after STARTTLS because of a "SSL want a read/write first" error. 
Default: On 

-SSLtimeout (SSL Timeout) 
SSL/TLS negotiation will timeout after this many seconds. 
Default: 5 

-SSLCacheInterval (TLS Error Cache Refresh Interval) 
If a connection fails with 'TSL negotiation with client failed' or 'Connection idle .. timeout' the connecting IP will be stored into this cache. ASSP will not offer STARTTLS to IP addresses in the error cache. The entry will be removed after this interval in days. 0 will disable the error cache.    

-SSLCertFile (SSL Certificate File (PEM format)) 
Full path to the file containing the server's SSL certificate, for example : '/etc/ssl/certs/yourdomain.com.crt' or 'c:/assp/certs/server-cert.pem'. A general cert.pem file is already provided in /Applications/assp/certs/server-cert.pem 
Default: /Applications/assp/certs/server-cert.pem 

-SSLKeyFile (SSL Key File (PEM format)) 
Full path to the file containing the server's SSL privat key, for example: '/etc/ssl/private/yourdomain.com.key' or '/usr/local/etc/ssl/certs/assp-key.pem' or 'c:/assp/certs/server-key.pem'. A general key.pem file is already provided in /Applications/assp/certs/server-key.pem  
Default: /Applications/assp/certs/server-key.pem 

-SSLPKPassword (SSL Privat Key Password) 
Optional parameter. If your privat key ' SSLKeyFile ' is password protected, assp will need this password to decrypt the server's SSL privat key file.  

-SSLCaFile (SSL Certificate Authority File) 
Optional parameter to enable chained certificate validation at the client side. Full path to the file containing the server's SSL certificate authority, for example : /usr/local/etc/ssl/certs/assp-ca.crt or c:/assp/certs/server-ca.crt. A general ca.crt file is already provided in '/Applications/assp/certs/server-ca.crt'. The default value is empty and leave it empty as long as you don't know, how this parameter works.  

-listenPortSSL (SMTPS Listen Port) 
The port number on which ASSP will listen for SMTPS connections. This is only for legacy clients like Eudora. Hint: If you set this port to 465, you must not set "listenPort" or "listenPort2" to 465.
Examples: 465  
Default: 465 

-EnforceAuthSSL (Force SMTP AUTH on SMTP Secure Listen Port) 
Do not allow clients to connect to listenPortSSL without Authentication.   

-smtpDestinationSSL (SSL Destination) 
The IP address! and port number to connect to when mail is received on the SSL listen port. If the field is blank, the primary SMTP destination will be used. Examples:127.0.0.1:565, 565  

-SSLDEBUG (Debug Level for SSL/TLS) 
Set the debug-level for SSL/TLS. Increasing the level will produce more information to STDOUTNotes On SSL Setup  

-EnableWatchdog (Enable Watchdog ) 
  

-WatchdogHeartBeat (Restart/Kill after this many Seconds ) 
 
Default: 600 

-WatchdogRestart (Kill &amp; Restart) 
Enabling this will ask the Watchdog to restart ASSP, disabling this will only kill ASSP. AutoRestartCmd must be configured. 
Default: On 

-NoMultipleASSPs (Prevent Multiple ASSP Processes) 
If set, ASSP will try to find out, if it is already running. 
Default: On 

-AutoUpdateASSP (Auto Update the Running Script (assp.pl)) 
No action will be done if 'no auto update' is selected. You'll get a hint in the GUI (top) and a log line will be written, if a new version is availabe at the download folder.
  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) and the syntax will be checked. The still running script will be saved version numbered to the download directory. A Changelog is also downloaded.
  If 'download and install' is selected, in addition the still running script  will be replaced by the new version. No settings or option files are changedd. Read the Changelog for recommended new option files. 
  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.   

-AutoUpdateASSPDev (AutoUpdate with Developer Version) 
  

-AutoUpdateNow (Run Auto Update Now) 
If selected, ASSP will run Auto Update. &nbsp;  

-ForceRestartAfterCodeChange (Enforce Termination on new or changed assp.pl Script) 
ASSP will terminate even if AutoRestartCmd is not configured. This is only useful if you run ASSP inside an external loop.  

-AutoRestartAfterCodeChange (Automatic Restart ASSP on new or changed assp.pl Script) 
If selected, ASSP will restart it self, if it detects a new or changed running script. An automatic restart will be done only, if ASSP runs as a Service on Windows or AutoRestartCmd is 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.  

-AutoRestart (Automatic Restart after Exception) 
If ASSP detects a main exception and a AutoRestartCmd, it will try to restart itself.  
Default: On 

-MainloopTimeout (Mainloop Timeout) 
Mainloop will timeout after this many seconds. 
Default: 600 

-AutoRestartAfterTimeOut (Automatic Restart after Timeout) 
If ASSP detects a mainloop timeout and a AutoRestartCmd is configured, it will try to restart itself.   

-AutoRestartCmd (OS-shell command for AutoRestart) 
The OS level shell-command that is used to autorestart ASSP, if it runs not as a service. A possible value for your system is:sleep 30;"perl" "/Applications/assp/assp.pl" "/Applications/assp" & Put a dummy command here 'cd .', if ASSP runs inside an external loop. If you use runAsUser make sure to start ASSP with root privileges (sudo). 
Default: sleep 30;&quot;perl&quot; &quot;/Applications/assp/assp.pl&quot; &quot;/Applications/assp&quot; &amp; 

-AutoRestartInterval (Restart Interval) 
ASSP will automatically terminate and restart after this many hours. Use this setting to periodically reload configuration data, combat potential memory leaks, or perform shutdown/startup processes. This will only work properly if ASSP runs as a Windows service or AutoRestartCmd is configured.Notes On  Automatic Update / Restart
    

-webAdminPort (Web Admin Port) 
The port on which ASSP will listen for http connections to the web administration interface. You may also supply an IP address or hostname to limit connections to a specific interface.Separate multiple entries by pipe "|"!Examples: 55555, 192.168.0.5:12345, myhost:12345, 192.168.0.5:22345|myhost:12345 
Default: 55555 

-enableWebAdminSSL (Use https instead of http) 
If selected the web admin interface will be only accessable via https.  After you click Apply of a change here you must change the URL(to https) on your browser to reconnect.
  This requires an installed IO::Socket::SSL module in PERL.
  A server-certificate-file ( SSLCertFile ) and a server-key-file (SSLKeyFile) must exist and must be valid!
  If you do not have valid certificates, you may generate both files online with www.mobilefish.com or you may use OpenSSL to generate Self-signed SSL certificates!  

-webAdminPassword (Web Admin Password) 
The password for the web administration interface (minimum of 5 characters, max 8 characters will be used). 
Default: nospam4me 

-allowAdminConnectionsFrom (Only Allow Admin Connections From*) 
An optional list of IP addresses and/or hostnames from which you will accept web admin connections. Blank means accept connections from any IP address. 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.Examples:
  127.0.0.1|172.16.  

-allowLocalHostConnectionsAlways (Enable LocalHost Web Admin Connections) 
LocalHost web admin connections will be allowed regardless of allowAdminConnectionsFrom 
Default: On 

-webStatPort (Raw Statistics Port) 
The port on which ASSP will listen for http connections to the statistics interface. You may also supply an IP address to limit connections to a specific interface.Examples: 55553, 192.168.0.5:12345 
Default: 55553 

-allowStatConnectionsFrom (Only Allow Raw Statistics Connections From*) 
An optional list of IP addresses from which you will accept raw statistical connections. Blank means accept connections from any IP address. Examples:
127.0.0.1|172.16. 
Default: 127.0.0.1 

-enableWebStatSSL (Use https instead of http) 
The web stat interface will be only accessable via https.
  This requires an installed IO::Socket::SSL module in PERL.
  A server-certificate-file "certs/server-cert.pem" and a server-key-file "certs/server-key.pem" must exits and must be valid!  

-SaveStatsEvery (Statistics Save Interval) 
This period (in minutes) determines how frequently ASSP statistics are written to a local file.  

-EnableHTTPCompression (Enable HTTP Compression in GUI) 
Enable HTTP Compression for faster web administration interface loading. The perl module Compress::Zlib is required to use this feature.  

-hideAlphaIndex (Hide the Alpha Index Menu Panel in GUI) 
Removes the alphanumeric index panel on the left side in the GUI, but the index is accessable by clicking on "Index".  

-IndexSlideSpeed (Sliding Speed of the Alpha Index Menu Panel in GUI) 
Adjust the sliding speed of the Alpha Index Menu Panel in GUI to your needs. 
Default: normal 

-EnableFloatingMenu (Enable Floating Menu Panel in GUI) 
Allow the menu panel on the web administration interface to float (floating Div code taken from www.javascript-fx.com).  

-EnableInternalNamesInDesc (Show Internal Names in the GUI) 
Show the internal names in the web interface. The internal names are used in the configuration file (assp.cfg), in the application code, and in the menu bar on the left side of the GUI. 
Default: On 

-MaillogTailJump (Jump to the End of the Maillog) 
Causes the browser window to jump to the bottom of the maillog instead of sitting at the top of the display.  

-MaillogTailBytes (Maillog Tail Bytes) 
The number of bytes that will be shown when the end of the maillog is viewed. The default value is 10000. 
Default: 10000 

-MaillogTailWrap (Maillog Tail Wrap) 
Force maillog lines to wrap if there are too many characters in a line to fit into the window-width.  
Default: On 

-MaillogTailOrder (Maillog Tail Order) 
Reverse the time order of line   

-MaillogTailColorLine (Maillog Tail Color Line) 
Color alternate lines . 
  Notes On Administration Interface 
Default: On 

-MaintenanceLog (Enable Maintenance logging) 
 
Default: standard 

-ConsoleCharset (Charset for STDOUT and STDERR) 
Set the characterset for the console output to your local needs. Best on non Windows systems is "utf8" if available or "System Default" - no conversion.   

-LogCharset (Charset for Maillog) 
Set the characterset/codepage for the maillog output to your local needs. Best on non Windows systems is "utf8" if available or "System Default" - no conversion. On Windows systems set it to your local codepage or UTF-8 (chcp 65001). To display nonASCII characters in the subject line and maillog files names setup decodeMIME2UTF8 . 
Default: utf-8-strict 

-decodeMIME2UTF8 (Decode MIME Words To UTF-8) 
If selected, ASSP decodes MIME encoded words to UTF8. This enables support for national languages to be used in Bombs , Scripts , Spamdb , Logging. If not selected, only US-ASCII characters will be used for this functions. This requires an installed Email::MIME::Modifier module in PERL. 
Default: On 

-AsAService (Run ASSP as a Windows Service) 
In Windows NT/2000/XP/2003 ASSP can be installed as a service. This setting tells ASSP that this has been done -- it does not install the Windows service for you. Installing ASSP as a service requires several steps which are detailed in the Quick Start for Win32 doku page. Information about the Win32::Daemon module which which is necessary can be found here: The Official Win32::Daemon Home Page requires ASSP restart  

-AsADaemon (Run ASSP as a Daemon) 
In Linux/BSD/Unix/OSX fork and exit. Similar to the command "perl assp.pl &amp;", but better.
   Changing this requires a restart of ASSP.  

-runAsUser (Run as UID) 
The *nix user name to assume after startup (*nix only).Examples: assp, nobody
   Changing this requires a restart of ASSP.  

-runAsGroup (Run as GID) 
The *nix group to assume after startup (*nix only).Examples: assp, nobody
   Changing this requires a restart of ASSP.  

-ChangeRoot (Change Root) 
The new root directory to which ASSP should chroot (*nix only). If blank, no chroot jail will be used. Note: if you use this feature, be sure to copy or link the etc/protocols file in your chroot jail.
   Changing this requires a restart of ASSP.  

-setFilePermOnStart (Set ASSP File Permission on Startup) 
If set, ASSP sets the permission of all ASSP- files and directories at startup to full (0777) - without any function on windows systems!  

-checkFilePermOnStart (Check ASSP File Permission on Startup) 
If set, ASSP checks the permission of all ASSP- files and directories at startup - all files must be writable for the running job - the minimum permission is 0600 - without any function on windows systems!  

-myName (My Name) 
ASSP will identify itself by this name in the email "Received:" header and in the helo when sending report-replies. Usually the fully qualified domain name of the host.Examples: assp.example.com 
Default: ASSP.nospam 

-HideIPandHelo (Hide IP and Helo) 
replace with these information in our received header for outgoing mails   

-myHelo (My Helo) 
How ASSP will identify itself when connecting to the target MTA. 
transparent - the Helo of the sender will be used
use myName - myName will be used
use Hostname - name of host assp is running on, should be a fully qualified FQDN
use IP - IP will be used 
Default: use myName 

-asspCfg (assp.cfg) 
For internal use only : assp.cfg file. 
Default: file:assp.cfg 

-AutoReloadCfg (Automatic Reload ConfigFile) 
If selected and the assp.cfg file is changed externaly, ASSP will reload the configuration from the file.  

-asspCfgVersion (assp.cfg version) 
This is the current assp.cfg version.  

-proxyserver (Proxy Server) 
The Proxy Server to use when uploading global statistics and downloading the greylist.Examples: 192.168.0.1:8080, 192.168.0.1  

-proxyuser (Proxy User) 
The Proxy-UserName that is used to authenticate to the proxy.  

-proxypass (Proxy Password) 
The password for Proxy-UserName that is used to authenticate to the proxy.  

-OutgoingBufSizeNew (Size of TCP/IP Buffer) 
If ASSP talks to the internet over a modem change this to 4096. 
Default: 10240000 

-HouseKeepingSchedule (Starting time for HouseKeeping) 
ASSP uses the scheduled hour to run cache-housekeeping. For example '3' will run cache-housekeeping at 3.00. Use 24 to run it at midnight. 
Default: 3 

-totalizeSpamStats (Upload Consolidated Spam Statistics) 
ASSP will upload its statistics to be consolidated with the global ASSP totals. This is a great marketing tool for the ASSP project &mdash; please do not disable it unless you have a good reason to do so. No private information is being disclosed by this upload. 
Default: On 

-ReloadOptionFiles (Reload Option Files Interval) 
If set not to zero, ASSP reloads configuration option files (file:.....) every this many seconds if they have changed externally. 
Default: 60 

-OrderedTieHashTableSize (Ordered-Tie Hash Table Size) 
The number of entries allowed in the hash tables used by ASSP and rebuildspamdb.pl. Larger numbers require more more RAM but result in fewer disk hits. The default value is 10000. Adjust down to use less RAM. 
Default: 5000 

-ALARMtimeout (Module Call Timeout) 
Global Timeout for calling other modules. 
Default: 10 

-UseLocalTime (Use Local Time) 
Use local time and timezone offset rather than UTC time in the mail headers.
  Notes On Server Setup 
Default: On 

-AutoUpdateREBUILD (Auto Update rebuildspamdb.pl) 
No action will be done if 'no auto update' is selected or AutoUpdateASSP is disabled.
  If 'download only' is selected and a new assp version is available, the newest rebuildspamdb.pl will be downloaded to the directory /Applications/assp/download .
  If 'download and install' is selected, the old rebuildspamdb.pl will be saved to download directory (rebuildspamdb.pl_old) and replaced by the new version.

  The perl module Compress::Zlib is required to use this feature. 
Default: download and install 

-RebuildSchedule (Schedule time for RebuildSpamdb) 
If not set to 0 ASSP uses scheduled hours to run RebuildSpamdb.pl. For example '6|18' will run rebuildspamdb.pl at 6.00 and 18.00. Use 24 to run it at midnight. '*' will schedule it every hour.   
Default: 3|6|9|12|15|18|21|24 

-RebuildCmd (OS-shell command for starting rebuildspamdb.pl) 
The OS level shell-command that is used to start rebuildspamdb.pl, if it runs not as a cronjob. A possible value for your system is:"perl" "/Applications/assp/rebuildspamdb.pl" "/Applications/assp" silent &You may overwrite it with your own script. Note that the parm 'silent' must be used. For example to run as user root: su -m assp -c "/usr/bin/perl /usr/local/share/assp/rebuildspamdb.pl
/var/db/assp silent &"  

-RebuildNow (Run RebuildSpamdb Now) 
If selected, ASSP will run RebuildSpamdb.pl now. &nbsp;  

-RebuildNotify (Notification Email To) 
Email address(es) to which you want ASSP to send a notification email after the rebuild task is finished. Separate multiple entries by "|". If empty no notify will take place. This requires an installed Email::Send module in PERL.  

-MaxNoBayesFileAge (Max Age of non Bayes Files) 
The maximum file age in days of every file in every non bayesian collection folder ( incomingOkMail , discarded , viruslog ). If defined and a file is older than this number in days, the file will be deleted.  
Default: 31 

-MaxKeepDeleted (Max Days of Keep Deleted) 
The maximum number in days deleted files in the bayesian collection folders ( spamlog , notspamlog ) will be kept. This is necessary when EmailBlockReport is used to handle the file and the file is meanwhile deleted. The list of files that are maked for deletion is stored in trashlist.db . 
Default: 7 

-autoCorrectCorpus (Automatic Corpus Correction) 
Setting this to standard will correct the spamdb to a norm of 1, soft will correct to 0.7 which let more mails pass the bayesian check. 
Default: standard 

-MaxCorrectedDays (Max Corrected File Age) 
This is the number of days a error report will be kept in the correctednotspam and correctedspam folders.
  Notes On Rebuild  
Default: 1000 

-POP3ConfigFile (POP3 Configuration File*) 
The file with a valid POP3 configuration. Only the file: option is allowed to use. 
  If the file exists and contains at least one valid POP3 configuration line and POP3Interval is configured, assp will collect the messages from the configured POP3-servers. 
  Each line in the config file contains one configuration for one user.
  All spaces will be removed from each line.
  Anything behind a # or ; is consider a comment.
  If the same POP3-user-name is used mutiple times, put two angles with a unique number behind the user name. The angles and the number will be removed while processing the configuration.
  e.g: pop3user&lt;1&gt; will result in pop3user  -  or  - myName@pop3.domain&lt;12&gt; will result in myName@pop3.domain
  It is possible to define commonly used parameters in a separate line, which begins with the case sensitive POP3-username "COMMON:=" - followed by the parameters that should be used for every configured user.
  A commonly set parameter could be overwritten in every user definition.
  Each configuration line begins with the POP3-username followed by ":=" : e.g myPOP3userName:=
  This statement has to followed by pairs of parameter names and values which are separated by commas - the pairs inside are separated by "=". 
  e.g.: POP3username:=POP3password=pop3_pass,POP3server=mail.gmail.com,SMTPsendto=demo@demo_smtp.local,......
  The following case sensitive keywords are supported in the config file:
  POP3password=pop3_password
  POP3server=POP3-server or IP[:Port]
  SMTPsender=email_address
  SMTPsendto=email_address or &lt;TO:&gt; or &lt;TO:email_address&gt;
  SMTPserver=SMTP-server[:Port]
  SMTPHelo=myhelo
  SMTPAUTHuser=smtpuser
  SMTPAUTHpassword=smtppass
  POP3SSL=0/1
  POP3SSL, SMTPHelo, SMTPsender, SMTPAUTHuser and SMTPAUTHpassword are optional.
  If POP3SSL is set to 1 - POP3S will be done! The Perl module IO::Socket::SSL is required for POP3S!
  If SMTPsender is not defined, the FROM: address from the header line will be used - if this is not found the POP3username will be used.
  If the &lt;TO:&gt; syntax is used for SMTPsendto, the mail will be sent to any recipient that is found in the "to: cc: bcc:" header lines if it is a local one.
  If the &lt;TO:email_address&gt; syntax is used for SMTPsendto, the literals NAME and/or DOMAIN will be replaced by the name part and/or domain part of the addresses found in the "to: cc: bcc:" header lines. This makes it possible to collect POP3 mails from a POP3 account, which holds mails for multiple recipients.
  For example: &lt;TO:NAME@mydomain.com&gt;  or  &lt;TO:NAME@subdomain.DOMAIN&gt;  or  &lt;TO:central-account@DOMAIN&gt;
  If the &lt;TO:&gt; or &lt;TO:email_address&gt; syntax is used for SMTPsendto, "localDomains" and/or "localAdresses_Flat" must be configured to prevent too much error for wrong recipients defined in the "to: cc: bcc:" header lines. The POP3collector will not do any LDAP or VRFY query!
  If you want assp to detect SPAM, use the listenPort or listenPort2 as SMTP-server.
  To use this feature, you have to install the perl script "assp_pop3.pl" in the assp-base directory. 
Default: file:files/pop3cfg.txt 

-POP3Interval (POP3 Collecting Interval) 
The interval in minutes, assp should collect messages from the configured POP3-servers. A value of zero disables this feature.  

-POP3KeepRejected (POP3 Keep Rejected Mails on POP3 Server) 
If selected, any collected POP3 mail that fails to be sent via SMTP will be kept on the POP3 server.  

-POP3debug (POP3 debug) 
If selected, the POP3 collection will write debug output to the log file. Do not use it, unless you have problems with the POP3 collection!
  Notes On POP3 collecting
    

-PrimaryMXping (Ping PrimaryMX Host) 
Will be used if two ASSPs are running before two MXses. Disables connections on port 25 on THIS instance of ASSP if  the PrimaryMX is up and running. This can be used to run this second MX (ONLY) if the PrimaryMX is down. Reduces hassles with double collections etc.  

-PrimaryMX (Primary MX Host) 
The IP or hostname of the Primary MX.   

-AutostartSecondary (Enable AutoStart Secondary ) 
This is also used to start/stop the 'Secondary'. Switching this to OFF will terminate the Secondary after some seconds. Switching this to ON will start the 'Secondary'. Sometimes It may be necessary to cleanup AutostartSecondary. Disabling it and enabling it will remove the pid_Secondary and restart the 'Secondary' clean.   

-SecondaryCmd (OS-shell command for AutoStart Secondary AI) 
The OS level shell-command that is used to overwrite the default command for starting ASSP as a secondary administration interface if AutostartSecondary is enabled. The default value for your system is:sleep 30;"perl" "/Applications/assp/assp.pl" "/Applications/assp"  --AsASecondary:=1  

-webSecondaryPort (Web Admin Port for Second Instance of ASSP ) 
The port on which a second instance of ASSP will listen for http connections to the web administration interface (instead of 55555). BlockReportHTTPName must be set. The second instance 'Secondary' will run without SMTP connections and can be used for heavy search use of the 'Maillog Tail' tool. 
Default: 22222 
