Anti Spam Best Practice
This article contains the most effective practices for outgoing email from your server to the web. These practices have to be followed in order that your emails don’t get filtered, blocked, or marked as spam by ExpertPK or other different anti-spam organisations.
Why does we apply protective measures to outgoing emails?
For every IP out there with ExpertPK product and services, as an online service provider, ExpertPK can register and reserve it with organisations like RIPE or ARIN. This means that we tend to seem as the ip abuse contact for legal proceeding within the WHOIS database.
If an ip from our network is reported to organisations like Spamhaus and SpamCop?, which work to combat spam, malicious websites and phishing, then the name of the complete ExpertPK network is at stake.
It is so vital that we take care of the reputation, quality and security of the network, which additionally forms a very important part of your service.
How does the protection system work?
ExpertPK has been implemented “Vade Retro anti-spam technology” based system to protect our network and to identify spams.
What to do after receiving an email alert?
Important steps to take on receiving a block alert BEFORE creating ticket to unblock the affected IP.
- stop sending email (e.g. stop all mail software such as qmail, Postfix, Sendmail or any script etc.)
- check the email queue (e.g. qmHandle for qmail, postqueue -p for Postfix)
- analyse your logs using the Message-ID found in the block alert.
If you’ve got checked and located that Message-ID are from your legitimate email, you must then make sure that your email messages befits the RFC and also the Best Practices indicated below. If they are doing abide by, you’ll be able to inform us by sending a sample of your email (including header). Our technical support team can then assist you with consequent steps. merely call our support line or contact us via the e-mail support interface in your manager.
RFC and Best Practices
RFCs (Request For Comments) are documents intended to describe technical aspects of the internet. They are produced and published by the IETF (Internet Engineering Task Force), a group which basically produces and defines standards.
For more information, see: RFC, IETF and Internet Draft
Best practices are recommended methods which are often based on these documents and are intended to advise you on the best way to proceed. In this instance, currently here this means the basic things to follow so that your emails are not marked as spam.
High Volume of Sending Emails
If your outgoing email volume is extremely high, you’re suggested to:
- Reserve associate IP block dedicated exclusively to email usage
- Provide an ‘abuse’ address on this block in order to receive complaints
- Configure reverses on all IPs properly.
This operation will enable you to simultaneously isolate the IP and domain reputation if you send emails for numerous domains, to receive the complaints, and therefore do what’s necessary to induce unblocked by numerous organisations. It additionally permits you to find a problem more quickly on a kind that uses domain X or Y, because the emails aren’t sent out from identical IP and do not have identical reverse.
Avoid using spammer keywords in your emails like “buy” and “last chance”, and avoid capital letters, impersonal subjects, exclamation marks, and of course discounts.
Don’t forgot to supply an unsubscribe link for people who haven’t requested to receive your email or who believe it to be illegitimate.
Be significantly careful to confirm that your emails contain the sender’s address (or an alias), a subject, and an accurate quantitative relation of text, pictures and links within the body of the message.
FBL - Feedback Loop
This system will enable you to follow up on feedback provided by some internet service providers directly,informing you that their users have marked your message as illicit, and that it has thus been classified as spam. This will enable you to interact with these ISPs directly concerning your reputation. Some FBLs:
Some authentication services help you to protect your reputation.
An email authentication technology developed by Microsoft which validates the authenticity of your domain name by verifying the IP address of the sender. This technology is based on the IETF standard: RFC4406
Sender Policy Framework is a standard for verififying the domain of the sender. It is based on RFC4408 and consists of adding an SPF or TXT field to the domain DNS, which contains the list of IPs authorised to send emails from this domain.
- Reverse DNS
Reverse enables your IP to be “translated” into your domain. That allows the domain associated with the IP address to be found.
DKIM This standard is described in RFC4871
- AOL, Google (Gmail) work on this basis. Official website: DKIM