Hi all,

a quick fixup version of assp V2 is published at sourceforge.

https://sourceforge.net/projects/assp/files/ASSP%20V2%20multithreading/2.6.1%20latest%20fixup/

latest production version       : assp 2.6.1 build 17355
current fixup                   : assp 2.6.1 build 18022

 
fixes:

- workaround for a Regexp::Optimizer bug, where some times \r plus 
quantifier in a regular expression is optimized as \r\? - in case assp 
skips the optimization 

- MaxAllowedDups may caused stucking workers in case of a havy workload 

- a not installed perl module Thread::State caused exceptions and 
restarted high workers - the rebuildspamdb task was not running 

- 'noCollectRe' was ignored, if a suspicious virus was found in the stored 
.eml file 

- on some systems the maillog.txt OS buffer was not flushed and so the 
file tail was not readable just in time

- the perl garbage collection for the rebuild spamdb task was not working, 
if 'useDB4Rebuild' was not enabled

- if the very important perl module 'LWP::Protocol::https' is not 
installed, assp will try the installation at startup
 
******************************************************************************************************
  ************  IF THIS IS NOT POSSIBLE - install the module 
LWP::Protocol::https manually! ************
 
******************************************************************************************************
  nix:
  >cpan LWP::Protocol::https

  windows:
   active perl:
  >ppm install LWP-Protocol-https
 
   strawberry perl: (should normaly already include this module)
  >cpan LWP::Protocol::https 
 

- possibly unwanted X-ASSP passing reason hearders were added to outgoing 
mails - this is no longer the case

- the 'valid_Message-ID_signature' check has overwritten other 
whitelisting and noprocessing reasons, this caused reply mails stored 
outside the corpus
 
- SMIME signing was completely skipped for a defined sender address, if a 
recipient exception (eg. rcpt=-recipi...@domain.com) was defined for this 
sender address
  this issue is fixed in ASSP_AFC 4.77
 

- Changing the certificates, KEY-password and RSA-privat-keys caused 
unexpected errors written to the maillog.txt for each defined SSL-listener
  until all required parameters were changed by assp in a sequence.
  The renew of the SSL-listeners and SSL-context is now delayed until all 
required SSL-parameters are changed. 
 

added:

'MSGIDsigProc','Process valid Message-ID Signed 
Mails','0:normal|1:whitelisted|2:noprocessing|3:whitelisted and 
noprocessing',
 'How are received mails processed, if they contain a valid local 
MessageID-Signature/Tag (eg. because it is an answer/reply to a tagged 
mail).
 The default value is \'whitelisted\'. Notice that noprocessing and/or 
whitelisted may prevent those mails from being collected in the corpus 
folders - check 
 noProcessingLog and NonSpamLog.'
 


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

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Assp-user mailing list
Assp-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-user

Reply via email to