Hi all,
fixed in assp 2.8.2 *SPAM-Eliminator* build 26133 - ticket#162 - fixed+closed "After enabling DoT10Stat, the Top Ten Statistics page (/top10stats) remains empty in the GUI, even though spam is being blocked correctly and the corresponding entries appear in maillog.txt." - ticket#161 - fixed+closed "We are currently running ASSP 2.8.2 (build 26034) and have experienced email delivery failures with a "451 Connection timeout" error. After investigation, we traced the problem to messages containing extremely long lines. In particular, these emails include a base64-encoded image of approximately 34k characters contained within a single line." The maximum allowed line length of the SMTP protocol is 1000 byte (incl. [CR][LF]) defined in RFC5321#section-2.3.8 and RFC5322#section-2.1.1 Most mail server will reject such mails - how ever, assp does NOT and let the backend server decide what to do. ASSP is waiting for a line terminator [LF] before it sends junks to the backend server - this behavior is changed: in case the length of data waiting to be send exceeds 1000 byte (without a line terminator), this junk is now send to the backend server. - if a DKIM or ARC signature was added to an email that contained wrong terminated lines (only single [LF] instead of [CR][LF]) the resulting calculated signature was invalid. For most of the processed emails assp will correct such wrong line terminations. how ever, this is not done by assp, if the email was signed before, to prevent breaking existing signatures. NOW, if ASSP finds wrong terminated lines in an email and is unable to correct these lines, a warning about the wrong line termination is written to the maillog.txt, and no signature will be added to the email and an error is logged, that the DKIM/ARC signature was not added. - if 'baysConf' was set to a value of 0.01 and a Bayes/HMM confidence chart was requested in the GUI, the assp main thread was crashing with a division by zero error. this was caused by an operation y = x / (log(baysConf * 100)) -> 0.01 * 100 = 1 and log(1) == 0 - the analyzer has shown unexpected PTR-check results, if 'localhost' was to be resolved - if a user was not allowed to change config value of 'pbdb' in the configuration, he/she was unexpected able to change the pbdb content in pbWhite pbBlack PTRCache URIBLCache SBCache RBLCache MXACache BackDNSCache RWLCache - the log line "Info: TTL for '$sl' is only $ttl seconds in configuration of '$name' - minimum config reload interval ( host2IPminTTL ) is $host2IPminTTL seconds" was too often logged, if hostnames had to be resolved by the configuration ckeck this log line is now only shown if 'MaintenanceLog' is set to at least 'verbose'
_______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
