[Assp-test] Fixes in 2.0.1_RC0.3.16

[Thomas Eckardt/e. <Tho...@th...>]

Hi all,

the following is fixed in 2.0.1_RC0.3.16

- adminusersdb is now a security value and could only be change by root
- if the MainThread has taken more than 60 seconds to initialize an error 
message was shown
- SMTPsessionLimt was not working like expected - this was possibly a 
reason for unexpected restarts of ASSP (overload on DoS)
- local registered AdminUser was able to logon with wrong password
- local registered AdminUser was unable to change his local password
- ASSP was crashing on signals abrt,break,quit,kill,term in any worker


the following should be fixed - tests are necessary

- wrong file name was used for collected files (wrong subject) - James!



new (improved) in this release:

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

-'maxSMTPSessions' does no more restrict connections on relayPort - the 
connections will be counted but not blocked because of too many SMTP 
connections

-'tlsValencePB','OK, Is a SSL/TLS connection, default=-10 Message Scoring 
& IP scoring Bonus for SSL/TLS connections

-'adminusersdbNoBIN','Admin Users Database uses no Binary Data (ASCII 
only)','Select this, if adminusersdb is set to "DB:" and your database 
engine does not accept or has problems with binary data. If you change 
this value, you have to stop all assp and to cleanup both tables 
(adminusers and adminusersright)'

-'NoTLSlistenPorts','Disable SSL support on listenPorts'  'This disables 
TLS/SSL on the defined listenPorts, if DoTLS is set to "do TLS". All other 
SMTP listeners will support TLS/SSL, if DoTLS is set to "do TLS". This 
option works for listenPort , listenPort2 and relayPort . The listener 
definition here has to be the same like in the port definitions. Separate 
multiple entries by "|". 25, 127.0.0.1:25, 127.0.0.1:25|127.0.0.2:25'


Thank you for reporting!

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!
*******************************************************