Geek asks and answers

Should I process rejection messages?

We have a web application that is not unusual in terms of email notifications. It would be nice to find out if the end user entered the email address is incorrect and the bomb is delivered to him.

In the modern world of email spam, is it worth trying to catch the bounces? In the configuration of the mail server today, it is generally considered best practice not to send rejected emails to unknown recipients due to backscatter, etc.

So, trying to catch any delivery failures beyond the simplest cases (for example, the bad domain that your local outbound mail server should tell you) is really worth the effort?

+3
source share
2 answers

Bounce Management is of the utmost importance, let's say you are a company that sends 50,000 letters a month for newsletters or receipts. If any mail server allows you to say "mx.maildomain.com", the email bounces off, hard or soft. And if the server "mx.maildomain.com" installed advanced spam filtering methods. And you send the same user over and over again because you send weekly newsletters. Then "mx.maildomain.com" may decide that you are a spammer, and then most of your letters will go to the junk mail folder (including your receipts to other clients on this mail server), or you may be blacklisted.

, , . , "" . , . , . , , , - , . . , , .

+5

, , , .

. , , , . , , , , .

- , , 3 , 3 / , .

+1

More articles:


All Articles