If you want to get technical details about how Mailrelay manages bounce emails, we have a great post that we recommend, it would be important to read it.<\/p>\n
This time, we want to address the issue from a different point of view, targeted to the commercial and marketing departments.<\/p>\n
In a more informal language, we will detail the reasons for each type of bounce, and perhaps most importantly<\/strong>, – what could be done (if possible, and unfortunately it is not always possible) to recover the subscriber, so that you can try to contact your potential customer or reader of your newsletters.<\/p>\n For a more structured view, we will use the bounce table and the reasons already shown in the first article, with a more detailed description of the reasons and a new column showing possible solutions or actions.<\/p>\n You will need to contact the administrator of the recipient’s server for information about the problem and determine possible solutions. And, you should contact our Customer Service Department to see what could be done to solve this issue.<\/td>\n<\/tr>\n You will also need to contact the administrator of the server to ask for more information on how to solve the problem. And, you should contact our Customer Service Department to see what could be done to solve this issue.<\/td>\n<\/tr>\n You will need to contact the administrator of the recipient’s server for information about the problem and determine possible solutions.<\/p>\n And, you should contact our Customer Service Department to see what could be done to solve this issue.<\/td>\n<\/tr>\n We hope these tips are helpful.<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":" If you want to get technical details about how Mailrelay manages bounce emails, we have a great post that we recommend, it would be important to read it. This time, we want to address the issue from a different point of view, targeted to the commercial and marketing departments. In a more informal language, we […]<\/p>\n","protected":false},"author":7,"featured_media":6996,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_uag_custom_page_level_css":"","footnotes":""},"categories":[16],"tags":[],"class_list":["post-42147","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized-pt"],"yoast_head":"\n\n\n
\n Error Code<\/strong><\/td>\n <\/td>\n Error Message<\/strong><\/td>\n <\/td>\n \u00a0Recommended actions<\/strong><\/td>\n<\/tr>\n \n \u00a0bad-configuration<\/strong><\/td>\n <\/td>\n Messages were rejected due to problems in the remote server configuration. This is a problem on the recipient’s server that has an error in the settings and is not allowing new messages.<\/td>\n <\/td>\n \u00a0You will need to contact the subscriber by phone to talk to the system administrator to try to solve the problem. When the administrator notify that the issue has been solved, you should contact the Mailrelay technical staff.<\/td>\n<\/tr>\n \n bad-connection<\/strong><\/td>\n <\/td>\n \u00a0Messages were rejected due to connection problems with the remote server. It is not possible to connect with the recipient’s\u00a0 domain correctly due to some failure in the connection route. In this case, the problem may not be occurring directly on the recipient’s server, but on some intermediate server that is receiving and forwarding the message.<\/td>\n <\/td>\n \u00a0You sould contact the administrator of the recipient’s server to explain the problem, but also with the internet service provider, so they can analyze and try to locate the problem that is causing this error.<\/td>\n<\/tr>\n \n bad-domain<\/strong><\/td>\n <\/td>\n Messages bounced because the domain is invalid or nonexistent. If the recipient’s domain does not exist, you can receive this error. You need to confirm that the account is valid.<\/td>\n <\/td>\n \u00a0You also will need to contact the subscriber by phone to talk to the system administrator to try to solve the problem. When the administrator notify that the issue has been solved, you should contact the Mailrelay technical staff to validate the email again.<\/td>\n<\/tr>\n \n bad-mailbox<\/strong><\/td>\n <\/td>\n Messages rejected because the recipient’s address is incorrect, is invalid or nonexistent. The email account was not found on the recipient’s server.<\/td>\n <\/td>\n You will need to contact the subscriber by phone to talk to the system administrator to try to solve the problem. When the administrator notify that the issue has been solved, you should contact the Mailrelay technical staff to validate the email again.<\/td>\n<\/tr>\n \n content-related<\/strong><\/td>\n <\/td>\n Messages bounced due to its content (Possible spam, sender is blacklisted, etc)<\/td>\n <\/td>\n you will need to verify that your campaign meets all requirements listed in this article.<\/p>\n \n inactive-mailbox<\/strong><\/td>\n <\/td>\n Messages rejected because the accounts expired, are inactive or have been disabled.<\/td>\n <\/td>\n You will need to confirm that the account is correct and contact the subscriber by phone to talk to the system administrator to try to solve the problem. When the administrator notify that the issue has been solved, you should contact the Mailrelay<\/strong> technical staff.<\/td>\n<\/tr>\n \n message-expired<\/strong><\/td>\n <\/td>\n The message was sent before the maximum time allowed, after previous attempts have failed.<\/td>\n <\/td>\n You can try to send the message again when there is less saturation in the sending queue.<\/td>\n<\/tr>\n \n no-answer-from-host<\/strong><\/td>\n <\/td>\n Messages bounced because the system could not receive any\u00a0 response from the remote server after connecting. This could be a problem on the remote server configuration.<\/td>\n <\/td>\n You will need to contact the administrator of the server to ask for more information on how to solve the problem.<\/td>\n<\/tr>\n \n other<\/strong><\/td>\n <\/td>\n Were rejected due to other reasons<\/td>\n <\/td>\n You will need to contact the administrator of the server to ask for more information on how to solve the problem.<\/td>\n<\/tr>\n \n policy-related<\/strong><\/td>\n <\/td>\n Messages bounced or blocked due to problems with the policy of the recipient’s server.<\/td>\n <\/td>\n Normally due to spam policy. You will need to review the email to make sure you are meeting all the points mentioned in the article you can find by clicking here.<\/p>\n \n protocol-errors\u00a0<\/strong><\/td>\n <\/td>\n The message is being rejected due to syntax errors in the SMTP protocol<\/a>. Mailrelay always uses correct syntax and commands, but there may be an interpretation problem on the recipient’s server.<\/td>\n <\/td>\n You will need to contact the system administrator to try to solve the problem.<\/td>\n<\/tr>\n \n quota-issues<\/strong><\/td>\n <\/td>\n Messages rejected or blocked due to quota issues. The server rejects the message because the account has exceeded the limit of messages.<\/td>\n <\/td>\n You will need to contact the subscriber by phone to talk to the system administrator to try to solve the problem. When the administrator notify that the issue has been solved, you should contact the Mailrelay technical staff to validate the email again.<\/td>\n<\/tr>\n \n relaying-issues<\/strong><\/td>\n <\/td>\n Messages rejected or blocked due to problems when trying to deliver the emails on the remote server. These errors may occur due to various reasons of internal administrative policies of the recipient’s server, for example, some servers will not accept any email with your domain that does not come from your own IP.<\/td>\n <\/td>\n You will need to contact the system administrator to try to solve the problem.<\/td>\n<\/tr>\n \n routing-errors<\/strong><\/td>\n <\/td>\n Messages due to routing problems in the recipient’s domain. That is, the sender server cannot deliver the email correctly due to a failure in an intermediate server.<\/td>\n <\/td>\n You sould contact the administrator of the recipient’s server to explain the problem, but also with the internet service provider, so they can analyze and try to locate the problem that is causing this error.<\/td>\n<\/tr>\n \n spam-related<\/strong><\/td>\n <\/td>\n Messages blocked or rejected due to reasons related to SPAM. There is a problem with the configurations of the sender domain, the contents of the email or spam complaints and the spam filter is blocking the email.<\/td>\n <\/td>\n You will need to verify that your campaign meets all requirements listed in this article.<\/p>\n \n virus-related<\/strong><\/td>\n <\/td>\n Messages blocked or rejected due to reasons related to infected emails. This can be a serious issue. When you attach a file containing a virus or that\u00a0 potentially could contain a threat, for example, Word or Excel, your emails will probably be blocked.<\/td>\n <\/td>\n The best solution in these cases is to scan the attached files using a good antivirus and if the problem occurs because the server rejects the message, marking it as potentially dangerous, you can compress the file using a software like Winzip, Winrar, and upload it to a server. After that, just add a link were your subscribers can download it.<\/td>\n<\/tr>\n \n <\/td>\n <\/td>\n <\/td>\n <\/td>\n <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n