I removed the custom rule for OPTO_HEADER, and just got this one through.. also seems suspicious...
X-Spam-Status: No, hits=4.1 required=5.5 tests=AWL,BAYES_50,HTML_FONT_BIG, HTML_FONT_FACE_BAD,HTML_IMAGE_ONLY_16,HTML_IMAGE_RATIO_02, HTML_MESSAGE,HTML_WEB_BUGS,MIME_QP_LONG_LINE,MPART_ALT_DIFF, NORMAL_HTTP_TO_IP,RCVD_IN_SBL,URIBL_SBL,URIBL_WS_SURBL,unsub15 version=3.0.0
If you had a bad rule OPTO_HEADER that was being abused, you'll want to reset your AWL database or disable it. The AWL will spread the effects of configuration problems out over time, just because of it's nature.
(The AWL works great on a well configured machine, and will even soften the blow of new misconfiguration problems, but it will make old misconfiguration problems linger like a hangover after they are fixed.)
