I added the IP of some "clustered mailservers" to the "noDelay" list thinking that it would ONLY act on the delay behaviour, but it turns out that it's probably doing more than just that, at least judging from a *spam* message which got through and contained the following headers
X-OriginalArrivalTime: 22 Oct 2009 19:24:35.0970 (UTC) FILETIME=[4A6C9E20:01CA534D] X-Assp-Delay: not delayed (85.37.16.7 in whitebox ); 22 Oct 2009 21:24:46 +0200 X-Assp-Message-Score: -15 (In Penalty White Box) X-Assp-Received-SPF: neutral ip=85.37.16.7 [email protected] helo=smtpout09.attiva.biz X-Assp-Message/IP-Score: 5 (SPF neutral) X-Assp-Envelope-From: [email protected] now... why it's telling me that the IP is in "whitebox" while it should just be a "nodelay" ? Or is the "nodelay" list ALSO working as some kind of whitebox ? That sounds crazy to me, I thought the nodelay was just a mean to avoid delaying messages from known email servers not to tell ASSP that those servers are somewhat "whitelisted" ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
