Before you can send or schedule an email, Campaign runs a health check. Any errors that prevent the email from being sent are indicated in red. For example, your email doesn't contain an opt-out option or a click-through link doesn't contain a valid URL. These items must be corrected before you can send the email.
Additional issues may be indicated in yellow. These are items that you should fix, but they will not prevent the email from being sent. For example, your subject line uses the first name field for personalization, but that field doesn't have a default value. This could result in the personalization appearing blank.
Finally, Campaign includes a spam check, using a rule set from Apache SpamAssassin, to provide guidance. Areas which might cause issues are displayed along with a score. Generally, you want to avoid a total score of 5.0 or higher, but the spam score doesn't prevent you from sending the email.
The following table lists and gives examples of some of the areas that might be flagged during the spam check. For details on SpamAssassin, see https://spamassassin.apache.org/.
| Area/Category | Examples |
| Abnormal header | Header contains an unclosed bracket |
| Abnormal recipient |
Similar addresses in recipient list Recipient list sorted by address |
| Advertisement |
Admission that the email is an ad Use of "ad" or "advertisment" |
| Blacklisted |
Host name or domain is listed in the user's URI blacklist. |
| Bulk email |
Bulk email fingerprint found, such as eGroups and mPOP |
|
Foreign language SpamAssassin supports English only |
MIME character set indicates foreign language A foreign language charset used in headers |
|
Forged email |
Email determined to be pretending to be XXX |
|
HTML format |
HTML and text parts are different See section below for more detail. |
|
Image format |
Multiple images hosted at different large sites or redirected |
|
Incorrect date |
Date is different from Received date |
|
Incorrect rDNS |
Sender's public rDNS is "localhost" Delivered to internal network by a host with no rDNS |
|
Money or fraud |
Uses text "money back guarantee" Body mentions unclaimed money Uses text "eliminate debt" |
|
Message ID format |
Message-Id is not valid, according to RFC 2822 |
|
Obfuscation |
An obfuscated URL is a website address that is concealed or misleading. |
|
Spam content |
Subject line and HTML title tag don't match Text content and HTML content |
|
Spam words |
Refers to drugs, prescriptions, or urgent matters For more words or phrases that might increase your spam score, see Words and phrases that can trigger spam filters. |
|
Suspicious sender |
Malformed From address From field is empty |
|
Uppercase |
Significant portion of text in uppercase |
|
URI shortener/format |
Short subject with URL shortener |
HTML and text content are different
In messages where the HTML version consists entirely or almost entirely of images, you might receive a negative spam score for having different HTML and text content. The images in the HTML version might contain the same copy that is used in the text version. But spam filters determine that your HTML and text version are too different, which could indicate that you're sending spam.
There is a workaround: Add the body copy that is used in the text version to the bottom of your HTML, right before the ending </body> tag. Style this text with a size of 1 pixel and a font color that almost matches the background color of the message. If you use the exact color as the background color, spam filters apply a negative score. Instead, use a color that is close enough to not be perceptible on your screen. You might have to experiment to find the right color. When done correctly, you receive a lower spam score and your message goes straight to the inbox instead of being blocked in certain email clients.