{"id":420,"date":"2019-07-25T11:23:30","date_gmt":"2019-07-25T08:23:30","guid":{"rendered":"https:\/\/www.byteplant.com\/blog\/?p=420"},"modified":"2019-11-20T15:41:22","modified_gmt":"2019-11-20T12:41:22","slug":"what-is-greylisting-and-how-it-stops-spam-email","status":"publish","type":"post","link":"https:\/\/www.byteplant.com\/blog\/what-is-greylisting-and-how-it-stops-spam-email\/","title":{"rendered":"What Is Email Greylisting And How It Stops Spam Email"},"content":{"rendered":"

Ever since first spam appeared in 1978, email providers have been looking for ways to protect its clients from such messaging.<\/span> Blacklisting and whitelisting<\/span><\/a> have been doing a more or less reasonable job to keep the recipients safe. IP blocking, domain blacklisting, and many other tools have been created in the past decades.<\/span><\/p>\n

One of the most successful approaches is email greylisting (or graylisting). It\u2019s an easy way to check if the sender is a spam producer and keep your mailbox safe from the unwanted messages.<\/span><\/p>\n

A big problem the majority of users face is that legitimate emails end up in the spam folder due to filters not being perfect enough. Greylisting seems to be a good way to fight such a problem, bringing high-quality emails straight to your mailbox and getting rid of spam. So what is greylisting?<\/span><\/p>\n

What Is Email Greylisting?<\/span><\/h2>\n

Greylisting is a fairly simple way to figure out whether the sender is respectable or not. Recipient mail servers don\u2019t accept any of the incoming emails, telling the sending server to try re-sending their messages again within a certain time frame.<\/span><\/p>\n

A legitimate email server will analyze such a message and try again as requested. Once it tries again, you receive the message to your inbox. However, a server sending spammy emails won\u2019t try again, thus leaving the email out of your inbox.<\/span><\/p>\n

How Does Email Greylisting Work?<\/span><\/h2>\n

When an email server gets a message from an unknown sender, it\u2019s blocked by greylisting while the server\u2019s IP address and sender and recipient addresses are cached. The sending server gets a block, which looks like a temporary 451 error. The sending mail server views this message as a temporary delay and tries to resend the message within the time frame specified in the RFCs.<\/span><\/p>\n

When the message is resent, its IP and address information is discovered in the greylisting cache, and the message gets the green light to appear in the mailbox. The information stays in the cache for 24 hours. So senders who don\u2019t send you emails frequently would have to go through the greylisting process again.<\/span><\/p>\n

Each mail server sets a different time for the duration of which it requires the message to be resent. Usually, it\u2019s between one and thirty minutes. The default value for most servers is 15 minutes. Even though greylisting delays the delivery speed of the email, it filters out the majority of spam messages, making your email experience much better.<\/span><\/p>\n

If you are wondering how to stop spam email, greylisting is an excellent option.<\/span><\/p>\n

What is Anti-Greylisting?<\/span><\/h2>\n

In order to adjust to greylisting, some mail servers adopt anti-greylisting technology. After the email is rejected for the first time, they try to resend it after a long period of time (about 30 minutes) in order to minimize the number of rejections.<\/span><\/p>\n

Anti-greylisting may delay emails slightly because the server which exercises greylisting may be ready to receive the email earlier than in 30 minutes. However, it reduces the overall number of tries you have to make to get your email delivered. Overall, this method is highly efficient.\u00a0<\/span><\/p>\n

Email Greylist vs Blacklist<\/span><\/h2>\n

The differences between greylist and blacklist are simple. The email senders on your blacklist will never be allowed through regardless of the number of attempts. The emails that are greylisted are held for moderation. Meaning they are blocked only if the sending server doesn\u2019t try to redeliver the message.<\/span><\/p>\n

In case you\u2019ve accepted emails from a certain sender address before, it won\u2019t get greylisted and end up in your mailbox immediately.<\/span><\/p>\n

Email Greylisting vs SPF<\/span><\/h2>\n

Greylisting and SPF are both spam-fighting techniques. There is no need to choose between both options – they can be used together.<\/span><\/p>\n

For example, some domains use several mail servers to send mail. Each mail server can be used for each next delivery attempt. In such a case, the greylisting process can be too time-consuming because each attempt from a new server will be greylisted separately.<\/span><\/p>\n

This problem can be solved by using the<\/span> Sender Policy Framework<\/span><\/a> for such domains that make their SPF data available.<\/span><\/p>\n

Greylisting is an efficient way to fight spam even though it comes with certain nuisances. By utilizing this tool together with other approaches, it\u2019s possible to fight the majority of today\u2019s spam.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

Ever since first spam appeared in 1978, email providers have been looking for ways to protect its clients from such messaging. Blacklisting and whitelisting have been doing a more or less reasonable job to keep the recipients safe. IP blocking, domain blacklisting, and many other tools have been created in the past decades. One of […]<\/p>\n","protected":false},"author":3,"featured_media":421,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[10],"tags":[],"_links":{"self":[{"href":"https:\/\/www.byteplant.com\/blog\/wp-json\/wp\/v2\/posts\/420"}],"collection":[{"href":"https:\/\/www.byteplant.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.byteplant.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.byteplant.com\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.byteplant.com\/blog\/wp-json\/wp\/v2\/comments?post=420"}],"version-history":[{"count":2,"href":"https:\/\/www.byteplant.com\/blog\/wp-json\/wp\/v2\/posts\/420\/revisions"}],"predecessor-version":[{"id":670,"href":"https:\/\/www.byteplant.com\/blog\/wp-json\/wp\/v2\/posts\/420\/revisions\/670"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.byteplant.com\/blog\/wp-json\/wp\/v2\/media\/421"}],"wp:attachment":[{"href":"https:\/\/www.byteplant.com\/blog\/wp-json\/wp\/v2\/media?parent=420"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.byteplant.com\/blog\/wp-json\/wp\/v2\/categories?post=420"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.byteplant.com\/blog\/wp-json\/wp\/v2\/tags?post=420"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}