[Assp-test] fixes in assp 2.8.2 *SPAM-Eliminator* build 23184

[Thomas E. <Tho...@th...>]

Hi all,

fixed in assp 2.8.2 *SPAM-Eliminator* build 23184:

- if a backend-server (e.g. bad configured exim) offered the 
SMTP-extension PIPECONNECT and a client/server used the pipelining option, 
the connection failed after the DATA command

changed:

- the at least recommended version of the module Net::SSLeay is changed 
from 1.72 to 1.85

- the export extrem IP-List is now correctly sorted by IP

- it is now possible to find a match for an empty envelope recipient in 
'bombSenderRe'


added:

- it is now possible to set the OpenSSL security-level (default is 1) - 
using any of the following methodes
  - in lib/CorrectASSPcfg.pm:   $main::openssl_security_level = 1; # ( 
/1/2/3/4/5) used openssl security level - empty uses the libssl buildin 
value (default = 1)
  - SSLAdvancedServerConfigFile : SSL_CTX_set_security_level = 3;
  - SSLWEBConfigure: $parms->{'SSL_CTX_set_security_level'} = 3;
  - SSLSTATConfigure: $parms->{'SSL_CTX_set_security_level'} = 3;
  - SSLSMTPConfigure: $parms->{'SSL_CTX_set_security_level'} = 3;

- it is now possible to change the MIME-encoding of a mail before a 
DKIM-signature is added to it, if a specific MIME-header is found or the 
mail meets specific conditions
  to apply this behavior, define a sub DKIMconvCTE in 
lib/CorrectASSPcfg.pm
  if this sub is found by assp, it will be called by assp, providing the 
connection handle ($fh) and an array reference which can be modified 
inplace
  example:
 
sub DKIMconvCTE {
    my ($fh, $convCTE) = @_;
    my $this = $main::Con{$fh};
 
    if (! $this->{mailfrom}) {

        #                      ct(1)     ,   Regex for ct (2)    , target 
encoding (3)
        push @{$convCTE}, 
['Content-Type','(?:text\/(?:ht|x)ml)','base64'];
#       push @{$convCTE}, ['.....' ,      '.....',               '....'];
#       push ...
#       push ..
#       ...
    }
} 

   in this example, if there is no envelope sender, assp will check the 
'Content-Type' (1) of the mail against the given regular expression (2) - 
and if
   a match is found, the MIME-encoding will be changed to 'base64' (3) 
before the DKIM-signature is added
   the reason for this implementation is: some NDR's, delivery 
notifications, report mails, OoO-mails (e.g. mails with clear text 
attached rfc822 mails or mail headers) may cause
   the DKIM-signature to become invalid after passing the final MTA (if 
the MTA reformated the mail for any reason)
   (there is currently only one known case)

Thomas