At 04:22 PM 8/31/2004, [EMAIL PROTECTED] wrote:
Folks,
We discovered a bug in razor-agents' interpretation of the updated server side ``se'' mask (supported engines) wherein razor-agents were incorrectly inferring that engine 4 was unavailable through the backend. The backend ``se'' was changed on August 18th and was reverted yesterday so things should be back to normal. If you still see engine 4 missing, please force a rediscovery (razor-admin -discover). If that still doesn't fix it, please notify me!
Thanks Vipul,
The fix works great here, e4 sigs are once again being generated and used by razor (using 2.61):
$razor-check -d <sample-spam.txt
<snip>
Aug 31 17:31:26.165222 check[913]: [ 8] mail 1.0 e4 sig: maD-J2LHO2hbHzZrbOXcsZ6ndsoA
Aug 31 17:31:26.165896 check[913]: [ 5] mail 1.0 e8 got no sig
<snip>
Aug 31 17:31:26.426416 check[913]: [ 3] mail 1 is known spam.
------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________ Razor-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/razor-users
