One of the key factors which impacts deliverability is poor or inadequate bounce handling for non-existent users. By this we mean, when yahoo, gmail, rediff, hotmail and many other corporate mail server generate errors like “this user no longer exists”, “user not found”, “no such user”, or some variation of that message. Are you equipped to act upon these errors?
Many of the larger ISPs give your incoming email a rating which is based on, among other things, how many non-existent or no-longer existing email addresses you send to, and how often you keep trying to send to the same address once your system has been told that it doesn’t exist. If you send to the same non-existent address more than a couple of times, that’s considered poor practice.
Bounced Mails can be handled if the mails are few but when the mail volume is high manual becomes impossible. BML was designed to handle preciously the same thing With SEBi and IT Act 2000 making it clear that if a mail is NOT delivered it should be PRINTED and delivered physically, BML gained compliance importance.
It tackles the issue of non-delivery of mails by maintaining a detailed log of the resulting bounced mails, as per SEBI mandate.
The email server was unable to deliver your message. (ie. 550 Mailbox not found)
The email server temporarily cannot deliver your message. (ie. Mailbox size exceeds quota, Host not found)
The email server temporarily cannot deliver your message, but it is still trying. (ie. Warning: message still undelivered after 4 hours. Will keep trying until message is 2 days old)
Notification that the recipient's email server is blocking email from your email server. (ie. 554 Client host rejected)
Someone is requesting to be added to your opt-in email list.
Recipient is requesting to be removed from future email from you. Auto-Reply: An automatic response from recipient. (ie. Out Of Office, Vacation Message)
Challenge-Response email systems were created as a reaction to the increasing circulation of spam.