ASSP development mailing list <assp-test@lists.sourceforge.net> schreibt: >My own explanation was derived from the observation >that all current reported issues with this *new* ASSP >behaviour will show the mail host is blacklisted!
No. It did not show that. Would you please be so kind to read the logs which are in the first posting of this thread and to read the introduction of enhancedOrigin feature from Thomas: The log entry in the starting mail was: > >Aug-03-11 08:32:04 [Worker_1] [TLS-in] [DenyStrict] 216.32.180.12 ><tho...@universal.bm> to: ksm...@bldc.com blocked by >denySMTPConnections or droplist strict: 14.0.0.0/8 So the mail was blocked by an entry in "denySMTPConnections or droplist strict", not by an DNSBL. The explanation of the new feature stated: - Detect IP's on the Mail Route (enhancedOriginIPDetect) ASSP parses the received header lines and some other common OIP lines for IP-addresses. The detected IP addresses are checked against the IP-Blocking features and DNSBL in the same way like an OIP address would be checked for an ISP-email. This will help to detect bots that are using different gateways or open SMTP-relay servers. This feature will also detect hosts that are abusing ISP-servers like AOL,gmal,hotmail ..... Simply add the source IP or any other 'IP on the way to you' to the IP-Blocking features. ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
