We employs certain anti-spam measures not only to protect our customers from inbound spam, but also to protect the rest of the Internet from spam coming from customer connections (often caused by malware that has infected the customer's computer)
Because anti-spam strategies are an ever-changing arms race, messages from our customers that have multiple strong concurrent indicators of junk content may sometimes be inadvertently blocked. We regrets this and tries to keep such 'false positives' to a minimum, but sometimes they cannot be avoided. The most common reasons why legitimate e-mail is marked as being likely spam are the following:
- The date and time set incorrectly on the customer's machine.
Check the date and time to make sure that they are accurate.
- Strong use of 'ALL CAPS' in the subject line or the body of the message.
Consider revising the message to use less all-caps text.
- Malformed message content (HTML, HTML without alternate plain-text version, or malformed SMTP headers).
If an e-mail message has been generated by common e-mail clients (such as Outlook or Thunderbird), the message is usually "well-formed" (containing no syntax errors) and has normal, expected SMTP headers. Common spam-generating software, on the other hand, often generates poorly-formed HTML, fails to include certain SMTP headers, or forges the 'Message-Id' header to look like a legitimate e-mail client. If you are using any custom software or scripts that automatically generate e-mails, please ensure that the HTML is well-formed, that it includes a valid Message-Id header as specified in RFC 2822. If you send HTML e-mail, please configure your e-mail client to also attach a text-only version of the message.
Please note that all of the above will ensure that the maximum number of e-mail clients can receive and read your e-mail, and other e-mail systems that use the same anti-spam solutions that we use (those incorporating SpamAssassin or components thereof, including IronPort and Barracuda) will also be less likely to tag your message as spam if you address these issues.
Please note also that many of these rules are not merely cumulative, but compound when combined. This is because, as the number of rules triggered increases, the message is much more likely to be spam. The good news here is that by identifying and addressing one of the issues above, your score can be significantly reduced.
The exact reasons why a particular message is being rejected can be ascertained by sending that message to firstname.lastname@example.org
for further analysis. This account is configured to receive all e-mail, regardless of spam score, and can see all of the tests that were triggered by any message.