This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Message Header "X-SEA-Spam" Report explanation

Hello,

the X-SEA-SPAM Report informations in a message header can look like this:

X-SEA-Spam: Gauge=XXXXXXXIIIII, Probability=75%, Report='
 SXL_URI_SBC 7, HTML_70_90 0.1, HTML_NO_HTTP 0.1, SUPERLONG_LINE 0.05, BODYTEXTH_SIZE_10000_LESS 0, BODYTEXTH_SIZE_3000_MORE 0, BODYTEXTP_SIZE_3000_LESS 0, HREF_LABEL_TEXT_NO_URI 0, HREF_LABEL_TEXT_ONLY 0, IN_REP_TO 0, KNOWN_MSGID 0, KNOWN_MTA_TFX 0, LEGITIMATE_SIGNS 0, MSG_THREAD 0, NO_CTA_URI_FOUND 0, NO_REAL_NAME 0, NO_URI_HTTPS 0, REFERENCES 0, SENDER_NO_AUTH 0, SPF_PASS 0, SXL_IP_TFX_WM 0, WEBMAIL_SOURCE 0, WEBMAIL_XOIP 0, WEBMAIL_X_IP_HDR 0, __ANY_URI 0, __BODY_TEXT_X4 0, __BOUNCE_CHALLENGE_SUBJ 0, __BUSINESS_SIGNATURE 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __CTYPE_MULTIPART_ALT 0, __DQ_NEG_HEUR 0, __DQ_NEG_IP 0, __FRAUD_REFNUM 0, __FROM_DOMAIN_NOT_IN_BODY 0, __FROM_NAME_NOT_IN_ADDR 0, __FROM_NAME_NOT_IN_BODY 0, __HAS_FROM 0, __HAS_HTML 0, __HAS_MSGID 0, __HAS_REFERENCES 0, __HAS_XOIP 0, __HREF_LABEL_TEXT 0, __HTML_AHREF_TAG 0, __HTML_FONT_BLUE 0,
 __HTML_TAG_DIV 0, __IMS_MSGID 0, __IN_REP_TO 0, __LINES_OF_YELLING 0, __MAIL_CHAIN 0, __MIME_HTML 0, __MIME_TEXT_H 0, __MIME_TEXT_H1 0, __MIME_TEXT_H2 0, __MIME_TEXT_P 0, __MIME_TEXT_P1 0, __MIME_TEXT_P2 0, __MIME_VERSION 0, __MULTIPLE_RCPTS_TO_X2 0, __REFERENCES 0, __SANE_MSGID 0, __STYLE_RATWARE_NEG 0, __STYLE_TAG 0, __SUBJ_ALPHA_END 0, __SUBJ_REPLY 0, __TAG_EXISTS_HTML 0, __TO_MALFORMED_2 0, __TO_NO_NAME 0, __URI_MAILTO 0, __URI_NO_WWW 0, __URI_NS

Is there an explanation or overview of these shortnames?
Or does anyone know what "SXL_URI_SBC" means?

Thanks,
Andy



This thread was automatically locked due to age.
  • Hi  

    I don't think if anyone outside Sophos will have an overview of shortnames from X-SEA-Spam header. However, I do know that SXL_URI_SBC filed indicates if the email contains a known Spam based on the query to SXL lookup.

    I'd suggest raising a low priority case to know what would be the exact description of the field and its value.

    Regards

    Jaydeep