The mail logs provide detail information on message processing. They do not however provide specifics on what anti-spam rules were matched. When a message is marked as "dropped by case" it means that the components that make up the message scored high enough to be classed as spam. To get specific details on why a message was marked as spam, or even why a message was not marked as spam you would need to submit the message to us. We typically ask customers to submit messages so that rule changes can be made if needed, which should not be often, but it does occur. Once submitted you will not receive any feed back however you can contact customer support if specific details about the messages are needed.
For customers using clients other than Microsoft Outlook, go to your email program and follow the instructions to attach the email as an RFC-822 MIME encoded attachment. See article 472.
(NOTE: All submitted messages must be in the RFC 822 format and ONLY that format. Any other formats (such as S/MIME) are currently not compatible with the submission tool.)
Note: Unless submitted through a plug-in (MS Outlook, not MS Outlook Express), messages forwarded must be RFC-822 compliant attachments. Forwards of previously forwarded messages cannot be processed at this time.
Each message is reviewed by a team of human analysts and used to enhance the accuracy and effectiveness of the product.
Once we receive submissions from a customer or from other sources, these messages are passed through automated classification systems that makes use of our latest rule set. If these messages are tagged by the new rule-set as spam, they are classified as such. Due to a delay in receiving samples and generating rules, many of the missed-spam messages usually have rules published between the time they are received by our customers and reported to us.
There are some messages that are part of new spam trends or new variants that are sufficiently different or new spam strains that are not classified by automated systems. Basically, any messages that are held for classification due to some mitigating factors are held for human review. We attempt to get to these messages within 2-3 hours of them being injested into the corpus.
Note: Although every report sent as an RFC-822 attachment to this address will be reviewed, most submissions will not receive an actual physical reply from IronPort.
Below are details on submitting messages in RFC-822 Format.
Customers using IronPort Anti-Spam or Symantec Brightmail Anti-Spam will want to submit both 'missed spam ' (False Negatives) and messages which are incorrectly classified as SPAM (False Positives). In either case, the submission must be attached to an email as an RFC-822 MIME encoded attachment. This ensures that the submission can be processed quickly and efficiently. The actual steps to follow are different for each mail program (Mail User Agent).
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...