A great deal of communication with your X-Cart store users will happen via email. It includes automatic email notifications, email marketing messages like abandoned cart reminders, and - sometimes - newsletters. If you take communication with your customers seriously, you will invest some time and effort into the design and content of your emails. However, after all that work, there's still a chance your emails will find a way to the spam folder of your customer email boxes. This article discusses why this may happen and what you can do to improve the situation from your end.
According to recent research, up to 80-90% of all email on the Internet is spam. Be it unsolicited promotional business materials, virus spam, illegal money transfer scam, or phishing scam to obtain sensitive information - spam is terrible. It causes financial harm, interferes with day-to-day work, and makes it more difficult for people to find legitimate emails that they may have received.
To stop the bombardment by spam emails, people and businesses are using all kinds of spam prevention tools and techniques to receive only relevant content.
Advanced anti-spam systems of today use three major types of email analysis (or their variations) to determine if an email message is spam:
Analysis of the email sending server IP address.
Analysis of the SPF/DMARC records of the sender's domain and the DKIM signature.
Analysis of the email content (headers, subject, body, links, etc.).
For example, IP addresses are essential when it comes to determining the credibility of an inbound email. Every time a receiving host gets connected by a sending host for email transfer, it takes steps to resolve the domain name presented to it as the sender's domain name to an IP address. Then it contacts the DNS server of the identified domain to confirm via SPF records that the mail server specified by the IP address in question is on the list of servers and IP addresses authorized to send an email for that specific domain. The SPF(Sender Policy Framework) email authentication helps the receiving host confirm that inbound mail has not been forged. To put it simply, one cannot send email from a domain that they do not own. It includes free mail services like Gmail and Yahoo Mail. If you try to send an email from your website specifying a @gmail.com address as the sender, the first thing your addressee's mail server will do is check if you are authorized to use a Gmail email address on mail sent from your website. Since Gmail's servers do not have SPF records for your domain, your mail will be deemed unauthorized. As a result, it will be blocked or end up in the spam folder.
Another popular method used by many servers to combat forged emails is DKIM (DomainKeys Identified Mail). DKIM authentication provides a way to sign and verify email messages using public and private keys at the message transfer agent level. When DKIM is used, an email is signed with a key generated for its origin domain. Then, when the email is received, the receiving email server grabs the key from the DNS records of the sender domain and uses this key to perform a cryptographic authentication to make sure the email was not modified during the sending process.
Then, of course, there are sender IP blacklists and various filters that identify spam based on the characteristics of email content (like wrong keywords or phrases typical of spam, suspicious HTML, broken links, etc.)
The diversity of anti-spam tools and methods used today makes us think about many factors that must be taken into account to ensure the deliverability of your emails. Unfortunately, it is not enough to compose a nice-looking message, and hope X-Cart will deliver it to the planned recipient. To get your emails delivered as intended, you will need to ensure your mail server and DNS records are appropriately configured for email authentication.
The easiest way to identify problems with your email transfer configuration is to use a tool called Mail Tester (mail-tester.com). This tool is handy for determining your "Spam Score" or the likelihood of your emails ending up in the spam inbox. Mail Tester allows you to run up to three tests a day for free and supports multiple languages.
To test your email transfer configuration:
Visit https://www.mail-tester.com/ and copy the email address provided on that page to the clipboard.
Go to the Admin area of your X-Cart store and do one of the following:
Create a new store user with the email address you have copied from Mail Tester. It will trigger the sending of an email notification to that email address.
Go to Store Setup > Email Notifications and select the Test Email Configuration tab:
Paste the email address you have copied into the "TO:" field. Then, use the form to send a test email.
Go back to https://www.mail-tester.com/ and press the button "Then check your score." Allow a few seconds for Mail Tester to check the inbox and calculate your score.
You should then see your Spam Score test results. Here is an example page:
The highest score would be 10/10. The lower your score, the more likely your emails will be flagged as spam.
If your score is above 7 or 8, you will probably be fine. To make sure, ask a bunch of your store users if they get your emails.
By clicking on the [+] buttons, you can get detailed information about each parameter of your test results. For example, if your results say "You're properly authenticated," and you see a checkmark on the green background for that item, it is a good thing. However, if that is not the case, serious work to adjust the configuration of your mail sending system is required.
Common issues resulting in bad scores include the following:
You are blacklisted.
SPF record is not set up.
DKIM is not set up.
The form or content of your email makes it look like spam for SpamAssassin (Note any wrong keywords, broken links, etc.)
If you get a bad Mail Tester score, share your testing results with your hosting provider staff or network administrator. They should know what to do.
If Mail Tester does not receive your email, it will remain stuck on the page below:
If you see this page, it means your current sending method is not working. Again, in this case, you should request help from your hosting provider or network administrator.