In most roles, a large amount of time goes into writing and sending ordinary emails. This article explains a programmatic approach you can take, to test your emails for a spam score, with an API.

What’s that? Check your email content spam score before sending. To solve the problem, there’s a practical solution. If that email spam score is too high, the message delivery stops right there and then. That is because the messages within the emails are rated by email checking code, and a score is returned. There are 333 billion emails coming from mail servers every day, but 1 in 6 don’t even reach a mailbox. Getting legitimate email delivered is a major challenge. So how do you get through the filters, if your message is worthwhile? By taking a look at your spam scores. Many would now say that the biggest challenge is getting your messages to cut-through the white noise (and get around the spam filters) that are everywhere. With the advent of technology, spam has proliferated, and in turn, spam filters have ratcheted up their efforts to block unwanted messages. Yes, the OG form of advertising continues… but instead of being on the streets, it’s in our inboxes. Now imagine how relieved they’d be if their daily work (shouting about their goods to passersby) was automated.

Imagine for a moment, a street hawker in the 19th century. In a multi-server Zimbra infrastructure this file and in general all the settings must be copied on all the MTA server where you need filtering.Email Marketing API Configuration Use Cases In general you can use this file to increase and decrease scores or define you own. You can whitelist you server using the internal_networks parameter. You can turn Bayes filtering off by setting “ use_bayes” to zero. Bayes works great for some but not for others. SpamAssassin also comes with a Bayes filtering engine. This way the spammer can receive replies to an email account that was not the source of the spam. The mail forgery tests return a higher score than the default SpamAssassin score, because spammers send junk mail from a “real” mail server, but fake the response so that it points to a gmail, hotmail, etc. To get around this, we can set its score to a very low value. The next test, for Reverse DNS, has a high score by default, with among other things a high false positive rate. On the other hand, the PBL test is used by other tests, so we will set it to a small value. They should then be adjusted down to zero, otherwise, emails sent from Outlook using the Connector for Outlook will often be flagged as spam. The first lines that contain SpamAssassin’s “_MX” and “_PBL” tests have default scores that are very high, and they go off when a user with Zimbra Connector for Outlook sends email. Let’s go over, now, many SpamAssasin default scores could be too high or too low for your environment or maybe you need to specify custom scores, to achieve this create a new file nano ~/data/spamassassin/localrules/zzsauser.cfĪnd let’s go edit it, adding the lines that we report below: score DOS_OUTLOOK_TO_MX 0 One last customization to improve SpamAssassin

Spamassassin score test