Activity for Thomas Eckardt
-
Thomas Eckardt committed [r432] on SVN
version 2.8.2 build (25303)
-
version 5.53
-
this is not a HOWTO forum - this is a bug tracker - use the forum instead answer: this is not possible! changelog 2017-11-13 fixed in assp 2.5.6 Fortress build 17317: changed: If the filename for an attachment contains no extension, but the given Content-Type MIME header provides the filetype, the related extension is added to the file name to prevent unexpected blocked attachments. related to this change, the ASSP_AFC.pm Plugin is updated to version 4.71 ..... set AttachmentLog to diagnostic and...
-
External Attachments Blocking not work as expected
-
If the ASSP_AFC plugin is not used, processing a message is imited to maxBytes. Thomas
-
exit code on restart
-
version 2.8.2 build (25270)
-
version 2.8.2 build (25268)
-
ASSP perl module installer 2.16
-
ASSP perl module installer 2.16 (complete)
-
ASSP perl module installer 2.15
-
ASSP perl module installer 2.15 (complete)
-
version 2.8.2 build (25223)
-
version 2.8.2 build (25213)
-
version 2.8.2 build (25212)
-
version 2.8.2 build (25211)
-
version 2.8.2 build (25192)
-
If assp is running under systemd control - start and stop assp using systemd! If assp is under systemd control, exit code 1 is returned - because assp is unable to detect from where INT/TERM/KILL/... was sent. It is assumed that systemd will not restart assp, if it has requested a service stop - in every other case it is assumed, that systemd will know what to do! You can't use DB: for griplist - RTM! assp uses the default BerkeleyDB file permission, which is -rw-rw-rw- (0666) on linux/nix the file...
-
exit code on restart
-
version 2.8.2 build (25098)
-
version 2.8.2 build (25075)
-
version 2.8.2 build (25042)
-
Malformed UTF-8 character (fatal) at sub main::fixsub line 5
-
Malformed UTF-8 character (fatal) at sub main::fixsub line 5
-
version 2.8.2 build (25014)
-
version 2.8.2 build (24340)
-
version 2.8.2 build (24334)
-
DoNoSpoofing4From not work
-
DoNoSpoofing4From not work
-
I can't reproduce this issue. The feature works like expected. check that the following exceptional conditions are not set for such a mail noprocessing acceptall addressedToSpamBucket relayok whitelisted check that BounceSenders does not match also check the feature exceptions onlySpoofingCheckIP noSpoofingCheckIP onlySpoofingCheckDomain noSpoofingCheckDomain Thomas
-
version 2.8.2 build (24291)
-
version 2.8.2 build (24289)
-
version 2.8.2 build (24288)
-
version 2.8.2 build (24282)
-
version 2.8.2 build (24261)
-
version 2.8.2 build (24245)
-
version 2.8.2 build (24226)
-
version 2.8.2 build (24226)
-
ASSP version 2.8.1 build 24222 is released
-
version 2.8.2 build (24222)
-
version 2.8.2 build (24194)
-
version 2.8.2 build (24193)
-
version 2.8.2 build (24169)
-
version 2.8.2 build (24124)
-
version 5.52
-
version 2.8.2 build (24107)
-
version 2.8.2 build (24107)
-
https://www.abuseipdb.com/check/194.169.175.10
-
Error: failed IO::Socket::SSL: SSL wants a read first
-
use the SVN version of assp.pl set SSLRetryOnError back to default or higher seems the related ip needs some more handshare cycles Thomas
-
Why using a 8 years old perl with outdated SSL libs? - If the latest is available? strawberry-perl-5.38.2.1-64bit-relocateable_4-assp.7z ! Thomas
-
client failed IO::Socket - SSL wants a read first
-
Using the provided information, we may talk about the weather!!!!!!!!!!!!!!!!!!!!!!!!! Closed!
-
SSL Context init failed
-
version 2.8.2 build (24081)
-
version 2.8.2 build (24071)
-
manual for ASSP v2.8.1 and 2.8.2
-
version 5.51
-
version 2.8.2 build (24031)
-
version 2.8.2 build (24025)
-
version 2.8.2 build (24009)
-
NetSNMP 5.9.4 - perl source for Strawberry-Perl X64
-
NetSNMP binaries - compiled for c:\usr
-
NetSNMP WinX64 libraries and includes GCC13 - Strawberry-Perl
-
MIB create tool
-
version 5.49
-
read https://www.openssl.org/docs/manmaster/man3/SSL_CTX_set_security_level.html the ssl_sec_lvl used by assp can be set in assp.pl or lib/CorrectASSPcfg.pm our $openssl_security_level; # ( /1/2/3/4/5) used openssl security level - empty uses the libssl buildin value (default = 1) Thomas
-
openssl error description: error:140A90F1:SSL routines:SSL_CTX_new:unable to load ssl2 md5 routines The error indicates that the SSL v2 code could not load the MD5 routines. your openssl installation and perl Net::SSLeay are NOT compatible at least one component is compiled without the MD5 option! note: Net::SSLeay uses XS code compiled dynamic against the installed openssl runtime libraries or compiled statc using the openssl header files and library Thomas
-
SSL Context init failed
-
possibly openssl was changed by the distro try to reinstall the perl module Net::SSLeay Thomas
-
version 2.8.2 build (23331)
-
ASSP perl module installer 2.12
-
ASSP perl module installer 2.12 (complete)
-
version 2.8.2 build (23251)
-
version 5.48
-
MXA-check on not needed subdomain
-
the domain 'out.onfact.be' was used in the 'From:' header line, like user@out.onfact.be every address used in From|ReturnReceipt|Return-Receipt-To|Disposition-Notification-To|Return-Path|Reply-To|Sender|Errors-To|List-.... is checked for a valid MX and the MX for an A record RTM - Validate MX and A Record (DoDomainCheck) Thomas
-
version 2.8.2 build (23225)
-
version 2.8.2 build (23214)
-
DQS Service spamhaus.net
-
there are still some small mistakes in the (new) enhanced functions of (2.8.2 build 23213) I'll release corrections today at SVN (2.8.2 build 23214) If you get any problem related to this ticket, please join the forum or the assp-test mailing list and report there. Thank you Thomas
-
hope I got it the access key for DQS has to be placed between the query data and the host name - for this reason the key becomes part of the hostname in assp and is published in the log as well as in replies (RBLLISTED). I think I've solved it in the attached version 2.8.2 build 23213 In case the key has to be placed in the middle of a query, it has to be surounded by curly brakets like: $DATA$.{your-spamhaus-key-here}.dbl.dq.spamhaus.org=>127.0.1.24=>1 From the configuration point of view, the only...
-
just saw that the querys are simple (nothing changed), you only need to prepend your key <key>.sbl.dq.spamhaus.net in the assp config</key> https://docs.spamhaus.com/datasets/docs/source/70-access-methods/data-query-service/040-dqs-queries.html Thomas
-
DQS Service spamhaus.net
-
simply configure assp to use this provider as long as I know DQS is not free, so you need to provide your key in the provider config - RTM for 'RBLServiceProvider' - your-key.$DATA$.rbl-provider.org! Or is there something not working? In this case a more detailed description would be nice. Thomas
-
help delist domain
-
The domain correosmasivos.com.co is not on any assp globaly managed blocking list. All IP's resolved from the SPF-record of the domain correosmasivos.com.co are not blocked or penalized by any central managed assp IP-list. BUT......: Each assp admin is free to configure (use or not) blocking lists from other providers (like: uribl.com, surbl.org, swinog.ch, spamhaus.org,spameatingmonkey.net,virustotal, dob.sibl.support-intelligence.net and much more). Each assp admin is also free to used self managed...
-
help delist domain
-
version 2.8.2 build (23198)
-
version 2.8.2 build (23195)
-
Malformed UTF-8 character (fatal) at lib/rebuildspamdb.pm line 2689.
-
the charset ISO-8859-8-I is used in the mail the issue is caused by the perl module 'Encode', which seems not uptodate on your system $Revision: 3.19 $ $Date: 2022/08/04 04:43:23 $ ! lib/Encode/Alias.pm /t/Aliases.t Add ISO-8859-8-I as an alias of ISO-8859-8 8ac3918e-5d77-4815-f1e6-6577397068c6@iki.fi https://en.wikipedia.org/wiki/ISO-8859-8-I upgrading Encode to version 3.19 or higher will fix the issue Thomas
-
Malformed UTF-8 character (fatal) at lib/rebuildspamdb.pm line 2689.
-
the charset ISO-8859-8-I is used in the mail the issue is caused by the perl module 'Encode', which seems not uptodate on your system $Revision: 3.19 $ $Date: 2022/08/04 04:43:23 $ ! lib/Encode/Alias.pm /t/Aliases.t Add ISO-8859-8-I as an alias of ISO-8859-8 8ac3918e-5d77-4815-f1e6-6577397068c6@iki.fi https://en.wikipedia.org/wiki/ISO-8859-8-I upgrading Encode to version 3.19 or higher will fix the issue Thomas
-
Wrong rights on SPFRecCache.sav after restart
-
version 2.8.2 build (23187)
-
version 2.8.2 build (23184)
1 >