> >> Please read the originating mail again and you will find this: " > >> blocked by denySMTPConnections or droplist strict: 14.0.0.0/8"
> >>> 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 >> This makes no sense; sounds like ASSP went crazy, see, the sending >> IP is 216.32.180.12 and ASSP is saying it blocked the email since it >> matched 14.0.0.0/8 (that is the range 14.0.0.0 to 14.255.255.255) >> now... don't you think that such match is totally wrong :) ? It's >> just a matter of playing with a little bit of subnetting math :) > <cough> heh ! > Does this have anything to do with the discussion on Monday re assp > picking out a software version number in the received headers as an ip > address? In that case it was "(ecelerity 2.2.3.46 r())" and Thomas suggested: > >> putting '2.2.3.46' in to 'noDelay' is the better way (not >> 'noBlockingIPs' and 'noRBL')! No idea here, but maybe it's related; if this is the case, then the code which deals with CIDR matching may have some bug causing such issues; I think we'll need to wait for a response from Fritz (or Thomas - not sure if the same issue affects ASSPv2) ------------------------------------------------------------------------------ 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
