Hi all,

fixed in 2.0.2_1.2.00:

- some Blockreports contains a double MIME header
- if the resulting score of a level 2 Plugin exceeds the penalty limit, 
the mail was not blocked


added:

'noMaxSMTPSessions','No Maximum Sessions IP numbers*','Mail from any of 
these IP numbers will pass through without checking maximum number of 
simultaneous SMTP sessions. For example: 145.145.145.145',

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

New heading : 'Configuration Synchronization and Sharing'

'enableCFGShare','Enable Configuration Sharing','<b>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!</b>
  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 <b>could be shared</b>. 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.<br />
  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!
  <b>Because the synchronization is done using a special SMTP protocol 
(without "mail from" and "rcpt to"), this option requires an installed <a 
href="http://search.cpan.org/search?query=Net::SMTP"; 
rel="external">Net::SMTP</a> 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.</b>

'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 realy 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

'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.

Thomas



DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally 
privileged and protected in law and are intended solely for the use of the 

individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no 
known virus in this email!
*******************************************************


------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test

Reply via email to