#0. Keep reporting. The server prioritizes certain traffic over others # (authentication, for instance), so you may be timing out but (after # authentication) your reports still get through.
I don't believe this to be the case lately. It fails like below, sometimes on the very first message, or in this case, after about 45 minutes, it failed only about 30% of the way through my spam folder (currently 1600 messages). Dec 09 14:44:12.643830 report[21164]: [ 4] folly.cloudmark.com << 2256 Dec 09 14:44:12.643936 report[21164]: [ 6] [length=2256] -a=r&message=* Dec 09 14:44:13.646651 report[21164]: [ 4] folly.cloudmark.com >> 7 Dec 09 14:44:13.646760 report[21164]: [ 6] response to sent.565 res=1 Dec 09 14:44:13.646867 report[21164]: [ 4] folly.cloudmark.com << 3426 Dec 09 14:44:13.646974 report[21164]: [ 6] [length=3426] -a=r&message=* Dec 09 14:44:28.643458 report[21164]: [11] Error: Timed out (15 sec) while reading from folly.cloudmark.com Dec 09 14:44:28.689399 report[21164]: [ 1] razor-report error: report5: Timed out (15 sec) while reading from folly.cloudmark.com report5: Timed out (15 sec) while reading from folly.cloudmark.com Very random as to when it will fail, sometimes it fails as it is parse/checks the messages, and doesn't even get to the reporting stage. By parse/check I mean the process where it generates this stuff: a=r&e=4&ep4=7542-10&s=ZzREYKcsuv6NfMyEjz4ML1atooAA a=r&e=1&s=lOcNP-bit7nahgWwZJ2GJoxfuN4A a=r&e=4&ep4=7542-10&s=htERqvYJsveJvxVXqheXcm12UZAA I do understand what you are saying though. Hopefully this can get resolved quickly, as while I do hate to not report my large volumes of spam, I really don't have the time it now takes to do so. I don't mind spending an hour total, out of my day, reporting periodically thoughout the day. But, when it literally takes me 4+ actual hours of sorting, re-reporting, scanning for false positives again, then re-reporting, and so on and so on, only to continually fail, it just is no longer feasible for me to continue. Keep in mind, this is just in the attempt to report just one batch of spam (meanwhile, more spam is piling up as well, and doesn't get reported because the first batch never gets through). I usually just give up and delete the trapped spam, as there are literally 3-4K+ each day in total (as I'm sure you are aware if you've checked on my reporting activity). I'd imagine my trust level must be about as high as it can get, simply do to my being extremely careful in going through all those thousands of spams, removing anything that could possibly be wanted by anyone using Razor. I just delete those outright, my customer doesn't get them (making them happy), and razor doesn't get them reported, which should keep the few that might want some of the "grey area" type spam that is kinda sorta subscription based, but not opt-out'able. Just for curiosity sake, is there any way to find out what our trust level is? Would be nice to know, so that I'll have feedback on just how good my reporting is, and how many "false" reports I've sent, causing a revoke. That info would allow me to refine my procedure, if needed. I'm sure this info would be very helpful for anyone else reporting large volumes of spam. Thanks, - Steve Porter - NAISP ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ Razor-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/razor-users
