Hi all,

fixed in assp 2.3.4 build 13300:

- authentication to the relayhost using relayAuthUser and relayAuthPass 
was not working if the
  connection used STARTTLS and the first EHLO reply of the relayHost has 
not contained an AUTH offer
 
- authentication to the relayhost was not working for the methodes LOGIN , 
CRAM-MD5 and DIGEST-MD5
  depending on the values set for relayAuthUser and relayAuthPass
 
- authentication to the relayhost was not working for resent mail and 
report requests

- if a listener (port definition) was done using only a port (like ':25') 
and the system used both IPv4 and IPV6
  IP-addresses , on some systems there was only one listener created
 
- it was possible that foreign domain names were added to the 
'ldaplistdb'. This caused unexpected behavior for
  several checks
 
 
 
changed:

 - the hidden config parameter 'DoHeaderAddrCheck' is moved in to GUI 
config
 
 'DoHeaderAddrCheck','Check TO,CC and BCC headers' checkbox,
 'If enabled TO: , CC: and BCC: header lines are checked the following 
way:
 
 1. a possible recipient replacement is done
 2. local email address validation is done -  if OK, the next address or 
headerline is processed
 3. spamtrapaddresses will be detected - scored with stValencePB - mail is 
blocked (noPenaltyMakeTraps is honored)
 4. a local but not valid BCC: address will be removed - scored with 
irValencePB
 5. a RelayAttempt will be detected if a BCC address is not local - scored 
with rlValencePB - mail is blocked
 The check 3 and 4 honors whitelisting , noprocessing and noBlockingIPs
 Enable this check only, if assp is configured to validate local domains 
and email addresses!
 NOTICE: that removeForeignBCC take place before this check is done - step 
5 will be never reached if removeForeignBCC 
 is enabled!'
 
- it is no longer allowed to separate entries with ':' in 
'UserAttach','User based Good and Bad Attachments*'

- the hidden config parameter 'DBCacheMaxAge' is moved in to GUI config

'DBCacheMaxAge','Database Maximum Cache Age'
'Setting this value above zero, enables an internal database cache for 
every defined table to reduce the concurrent 
 database queries and to prevent possible record access collisions, which 
could cause stucking workers on some systems
 The value defines the maximum age in seconds a record will exists 
untouched in the table cache.
 Be carefull, setting this value too high in a database replication 
envirionment could cause unexpected query results, 
 because this cache is NOT shared between multiple assp instances.
 If set, a value of 10 seems to be popular in any case. An too less value, 
will produce overhead without any advantage.
 An too high setting could cause the described database consistency 
problems.'


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


------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test

Reply via email to