Making Sure Your EMails Won”t Bounce
When sending e-mails it happens that they are not delivered in the correct inbox . Many marketers make a distinction between hard and soft bounces. However, this is a too simple distinction. When sending e-mails can be so much wrong, it is ridiculous to errors in only two categories to classify. The marketing software makes this distinction clear to the user fortunately, without using too vague notions of ””soft”” and ””hard bounce.
How does sending an e-mailing anyway? In fact, sending an e-mailing in three steps: first, the e-mailing compiled, then the e-mailing – a message – by sending a (client) to a receiving mail server (server) sent. However, if the mailing was accepted, that does not always mean that even when the receiver is delivered, there may still a ””bounce”” and an error will occur via e-mail is returned. In this article we go through these three steps.
For techies, there is also a detailed description about the difference between hard and soft bounce bounce .
Step 1: compile a mailing
Putting together an e-mailing itself consists of several steps. For example:
– Generating the HTML code
– Personalize the e-mailing
– Loading XML Feeds
– Embed Images
– Etc.
In short, even when composing e-mailing a lot may go wrong even before the messages are actually sent. How would this error in the e-mail statistics to be called? A hard bounce? A soft bounce? We make this distinction. If e-mailing when compiling against an error increases, the software simply reported that an error has occurred while composing the e-mail. Be so clear.
Step 2: sending an e-mailing
After e-mailing has been made, it will be sent. This starts with making a connection between the client and the server. Using an A record and an MX record, this connection is established. These records are included in the DNS data.
Once the connection is accepted by the server, the communication with the receiving mail server to start. This is done using the SMTP protocol. Thus the client to the server of who the mail came (MAIL command) and to whom the e-mail sent (RCPT command).
Both in making the connection as the communication with the receiving mail server, there are several reasons why the (temporary) can go wrong. Resulting in an error message at the sender. For example:
– When an ISP server port (port 25, the default SMTP server port) blocks.
– When the server does not accept the email because the sending mail address on its blacklist.
Step 3: handling bounces
In case the mail is finally accepted by the receiving mail server can still be an error. This has caused a bounce. The server sends the client a message DSN (Delivery Status Notification) with possible explanations of what went wrong. Or there is no explanation given by the server.
Again no clear distinction between a ””hard”” or ””soft”” bounce. If after acceptance still an error, the server can pass it on to the client. In this case, the software will clearly indicate that the receiving mail server has sent a bounce. The statistics is then (possibly) to see which specific error code in question. If the feedback error code is unknown, the software that they are receiving other error messages (emails). These may be out-of-office replies are.
When sending e-mails in other words so much that go wrong in our view is too vague only the difference between hard and soft bounce definition. One is better served when it clearly states what has gone wrong and at what stage this happened.
Canada And USA Wide Moving Network – Vehicle Transport Services– Canadian Moving Company
Processing your request, Please wait....
