What about the other options on the list:
Empty messages:
When this setting is enabled, any message in which the body and subject line are both empty, and which also has no attachment, will be marked as spam.
JavaScript or VBScript in HTML:
When this setting is enabled, any message that uses JavaScript or Visual Basic Script Edition in HTML will be marked as spam.
Frame or IFrame tags in HTML:
When this setting is enabled, any message that contains the "Frame" or "IFrame" HTML tag will be marked as spam. These tags are used on websites or in HTML messages to format the page for displaying text or graphics.
Object tags in HTML:
When this setting is enabled, any message that contains the "Object" HTML tag will be marked as spam. This HTML tag allows plug-ins or applications to run in an HTML window.
Embed tags in HTML:
When this setting is enabled, any message that contains the "Embed" HTML tag will be marked as spam. This HTML tag allows varying data types to be embedded into an HTML document. Examples include sounds, movies, or pictures.
Form tags in HTML:
When this setting is enabled, any message that contains the "Form" HTML tag will be marked as spam. This HTML tag is used to create website forms. Email advertisements often include this tag to solicit information from the recipient.
Web bugs in HTML:
When you enable this setting, any message that contains a web bug is marked as spam. A web bug is an object that’s embedded in a web page or email message. It’s designed to determine whether a user has viewed the page or message.
Apply sensitive word list:
When this setting is enabled, any message that contains a word that's included in the sensitive word list will be marked as spam.
SPF record: hard fail:
When this setting is enabled, messages that hard fail an SPF check will be marked as spam (SPF filtering is always performed). Turning this setting on is recommended for organizations who are concerned about receiving phishing messages. (In order to avoid false positives for messages sent from your company, make sure that the SPF record is correctly configured for your domains.)
Conditional Sender ID filtering: hard fail:
When this setting is enabled, any message that hard fails a conditional Sender ID check is marked as spam. Turning this setting on is recommended for organizations who are concerned about phishing, especially if their own users are being spoofed. This option combines an SPF check with a Sender ID check to help protect against message headers that contain forged senders.
NDR backscatter: