{"id":132,"date":"2009-01-03T23:27:16","date_gmt":"2009-01-04T07:27:16","guid":{"rendered":"http:\/\/jaillon.com\/blog\/?p=132"},"modified":"2009-01-03T23:27:16","modified_gmt":"2009-01-04T07:27:16","slug":"mail-delivery-failed-returning-message-to-sender","status":"publish","type":"post","link":"https:\/\/www.jaillon.com\/blog\/2009\/01\/03\/mail-delivery-failed-returning-message-to-sender\/","title":{"rendered":"Mail delivery failed: returning message to sender"},"content":{"rendered":"<p><script type=\"text\/javascript\"><!--\ngoogle_ad_client = \"pub-1654780122218807\";\n\/* 468x60, created 1\/2\/09 *\/\ngoogle_ad_slot = \"7466608983\";\ngoogle_ad_width = 468;\ngoogle_ad_height = 60;\n\/\/-->\n<\/script><br \/>\n<script type=\"text\/javascript\"\nsrc=\"http:\/\/pagead2.googlesyndication.com\/pagead\/show_ads.js\">\n<\/script><\/p>\n<p>If your domain name is hosted by a 3rd party on a shared server, you may already have received this very frustrating email seconds after you pushed the send button:<br \/>\n<i>Mail delivery failed: returning message to sender <\/i><br \/>\n<!--more--><br \/>\nThe typical situation is the following: your hosting provider hosts several customers on the same shared Linux or Windows server and one of these accounts gets infected by a trojan or bot that spams the rest of the world.  Since you are sharing the same IP address, when the IP address becomes blacklisted on <a href=\"http:\/\/www.spamhaus.org\/\">spamhaus <\/a>or <a href=\"http:\/\/cbl.abuseat.org\/\">cbl<\/a>, whenever you try to send a email, the <b>receiving server<\/b> rejects it and you will very likely receive the following message:<\/p>\n<p><code>Subject: Mail delivery failed: returning message to sender<br \/>\nHeader: This message was created automatically by mail delivery software.<br \/>\nA message that you sent could not be delivered to one or more of its<br \/>\nrecipients. This is a permanent error. The following address(es) failed:<br \/>\n  xxxx@yyy.zz<br \/>\n    SMTP error from remote mail server after initial connection:<br \/>\n    host yyy.zz [aaa.bbb.ccc.ddd]: ...<br \/>\n------ This is a copy of the message, including all the headers. ------<br \/>\nReturn-path: <youremailaddress><br \/>\nReceived: from...<br \/>\n<\/youremailaddress><youremailaddress><br \/>\n<\/youremailaddress><\/code><br \/>\nSee <a href=\"http:\/\/www.spamhaus.org\/dnsbl_function.html\">Spamhaus<\/a> for details.<\/p>\n<p><b>What to do next?<\/b><br \/>\nThe first thing that you need to do is to contact the technical support department of your hosting provider to inform them of the situation.  It is very likely that they will ask for the full header of the message you just received back. Save yourself some time and copy\/paste it in your ticket.<\/p>\n<p>Then, you wait&#8230;<\/p>\n<p>If you are frustrated by this situation, you can always visit the following services to check whether the IP address of your server is or not blacklisted:<br \/>\n1. <a href=\"http:\/\/cbl.abuseat.org\/lookup.cgi\">CBL abuseat.org query page<\/a><br \/>\n2. <a href=\"http:\/\/www.spamhaus.org\/sbl\/index.lasso\">Spamhaus.org query page<\/a><\/p>\n<p>I&#8217;d recommend to not try to delist the IP address yourself.  It&#8217;s there for good reasons and your hosting provider may need to see why the IP is blocked.<\/p>\n<p>Usually the IP can be removed within an hour and the email servers sync their lists often (as often as twice an hour). If your provider is efficient you should have the situation resolved within 24h.  In the meantime, gmail and yahoo mail are your friend&#8230;<\/p>\n<p>Good luck!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>If your domain name is hosted by a 3rd party on a shared server, you may already have received this very frustrating email seconds after you pushed the send button: Mail delivery failed: returning&#46;&#46;&#46;<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[6,11,20,21],"tags":[32,61],"class_list":["post-132","post","type-post","status-publish","format-standard","hentry","category-email","category-google","category-spam","category-techno","tag-hosting","tag-techno"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.jaillon.com\/blog\/wp-json\/wp\/v2\/posts\/132","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.jaillon.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.jaillon.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.jaillon.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.jaillon.com\/blog\/wp-json\/wp\/v2\/comments?post=132"}],"version-history":[{"count":0,"href":"https:\/\/www.jaillon.com\/blog\/wp-json\/wp\/v2\/posts\/132\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.jaillon.com\/blog\/wp-json\/wp\/v2\/media?parent=132"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.jaillon.com\/blog\/wp-json\/wp\/v2\/categories?post=132"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.jaillon.com\/blog\/wp-json\/wp\/v2\/tags?post=132"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}