Since it is sporadic, I suspect that it is related to connectivity and/or congestion issues at (a/the) razor2 server(s). This suspicion is strengthened in my mind by the comment in the code about providing a better diagnostic than "Bad file descriptor" when the server is unavailable.
Well, that would make logical sence. Cool. That sets my mind at ease. At least I know that the razor2 checks are done via a server. That would explain why their bombing out periodically. :)
------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
