{"id":3427,"date":"2024-11-29T15:28:39","date_gmt":"2024-11-29T15:28:39","guid":{"rendered":"http:\/\/mclements.net\/blogWP\/?p=3427"},"modified":"2024-11-29T16:02:27","modified_gmt":"2024-11-29T16:02:27","slug":"email-ip-addresses-and-blacklists","status":"publish","type":"post","link":"http:\/\/mclements.net\/blogWP\/index.php\/2024\/11\/29\/email-ip-addresses-and-blacklists\/","title":{"rendered":"Email, IP Addresses and Blacklists"},"content":{"rendered":"<h3>Introduction<\/h3>\n<p>I have a web &amp; email hosting account so my email is on my own domain. A while back I wrote on this topic: <a href=\"http:\/\/mclements.net\/blogWP\/index.php\/2024\/02\/06\/email-send-blacklisting-ip-addresses\/\">http:\/\/mclements.net\/blogWP\/index.php\/2024\/02\/06\/email-send-blacklisting-ip-addresses\/<\/a><\/p>\n<p>That turned out to be a temporary solution and the problem kept recurring. I recently devised a permanent solution. I&#8217;ll describe this solution first, then get into the story of how I discovered it.<\/p>\n<h3>How it Works<\/h3>\n<p>Here&#8217;s what happens when I send an email from my own domain. Consider the email as <strong>foo@bar.com<\/strong> sent using <strong>MyHost<\/strong> SMTP servers.<\/p>\n<ol>\n<li>My email client (Thunderbird on Linux) calls GMail&#8217;s SMTP server to send an email from <strong>foo@bar.com<\/strong><\/li>\n<li>The GMail SMTP server receives the call and says, &#8220;<strong>foo@bar.com<\/strong> isn&#8217;t a GMail email address. Do I recognize this?&#8221;<\/li>\n<li>The GMail SMTP server sees that I have added <strong>foo@bar.com<\/strong> as an external email account and verified it.<\/li>\n<li>The GMail SMTP server sees that I have told it to call the <strong>MyHost<\/strong> SMTP server to send email for<strong> foo@bar.com<\/strong>, and provided <strong>MyHost<\/strong> login credentials.<\/li>\n<li>The GMail SMTP server calls the <strong>MyHost<\/strong> SMTP server to send the email from <strong>foo@bar.com<\/strong><\/li>\n<li>The <strong>MyHost<\/strong> SMTP server sends the email using the IP address of the caller, which is the GMail SMTP server&#8217;s IP address.<\/li>\n<\/ol>\n<p>This ensures that the IP address associated with email sent from the <strong>MyHost<\/strong> account is not my Comcast assigned IP address, but that of GMail&#8217;s SMTP server. Thus, it passes all the various internet email security checks.<\/p>\n<h3>The Symptom<\/h3>\n<p>As I mentioned above, the problem kept recurring. I send email and sometimes it is rejected with a reply that looks like this:<\/p>\n<pre class=\"moz-quote-pre\">host eig-east.smtp.a.cloudfilter.net [18.215.58.191]\r\nSMTP error from remote mail server after end of data:\r\n550 Gk0Tt29WcHdOCGk0UtJxy2 - &lt;foo@bar.com&gt; message rejected AUP#SNDR<\/pre>\n<p>I checked whether this IP address is blacklisted at this site: <a href=\"https:\/\/mxtoolbox.com\/blacklists.aspx\">https:\/\/mxtoolbox.com\/blacklists.aspx<\/a><\/p>\n<p>It shows more than 40 different blacklists, all but 1 of which are green \/ OK. It was blacklisted by Spamhaus ZEN with reason PBL. In their words:<\/p>\n<pre><span id=\"ctl00_ContentPlaceHolder1_lblProblemDescription\"><strong>PBL<\/strong> - Spamhaus PBL is a DNSBL database of end-user IP address ranges that should not be delivering unauthenticated SMTP email to any Internet mail server except those provided for specifically by an ISP for that customer's use<\/span><\/pre>\n<p>In other words, internet SPAM and security has gotten so bad that servers don&#8217;t accept email from any IP address except those pre-cleared as public SMTP servers. When it comes to delivering email, they have shifted from blacklisting to whitelisting.<\/p>\n<p>Previously I thought I could solve this by using the IP for my DNS name, instead of the one assigned by Comcast. But my hosting provider refused to do that and it wouldn&#8217;t help anyway.<\/p>\n<h3>The Solution<\/h3>\n<p>Google has employees whose job is to keep their SMTP servers on all the whitelists and off all the blacklists. When my hosting provider&#8217;s SMTP server sends email, it uses the IP address of whoever called it. If I can get Google&#8217;s SMTP servers to call my hosting provider&#8217;s SMTP server, then my email will deliver with a whitelisted Google IP address.<\/p>\n<p>And Google provides a method to do exactly this!<\/p>\n<p>Before starting, have the information for the SMTP server you want to use: hostname, login name, password, etc.<\/p>\n<p>Point your browser to <a href=\"https:\/\/gmail.com\">https:\/\/gmail.com<\/a>, go to Settings, See all Settings, Accounts and Import.<\/p>\n<p>In the &#8220;Send mail as&#8221; section, check the button for <strong><span class=\"\">Reply from the same address the message was sent to<\/span><\/strong>.\u00a0 Then click the link <strong><span id=\":w1\" class=\"sA\" tabindex=\"0\" role=\"link\">Add another email address<\/span><\/strong>. Follow the instructions in the window that pops up to verify the email account and SMTP provider.<\/p>\n<p>Next, go to your email client settings and tell it to use the GMail SMTP server to send mail for your hosting provider email.<\/p>\n<p>That&#8217;s it &#8211; you&#8217;re done.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Introduction I have a web &amp; email hosting account so my email is on my own domain. A while back I wrote on this topic: http:\/\/mclements.net\/blogWP\/index.php\/2024\/02\/06\/email-send-blacklisting-ip-addresses\/ That turned out to be a temporary solution and the problem kept recurring. I recently devised a permanent solution. I&#8217;ll describe this solution first, then get into the story &hellip; <a href=\"http:\/\/mclements.net\/blogWP\/index.php\/2024\/11\/29\/email-ip-addresses-and-blacklists\/\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">Email, IP Addresses and Blacklists<\/span> <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2,1],"tags":[],"class_list":["post-3427","post","type-post","status-publish","format-standard","hentry","category-tech","category-uncategorized"],"_links":{"self":[{"href":"http:\/\/mclements.net\/blogWP\/index.php\/wp-json\/wp\/v2\/posts\/3427","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/mclements.net\/blogWP\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/mclements.net\/blogWP\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/mclements.net\/blogWP\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/mclements.net\/blogWP\/index.php\/wp-json\/wp\/v2\/comments?post=3427"}],"version-history":[{"count":6,"href":"http:\/\/mclements.net\/blogWP\/index.php\/wp-json\/wp\/v2\/posts\/3427\/revisions"}],"predecessor-version":[{"id":3433,"href":"http:\/\/mclements.net\/blogWP\/index.php\/wp-json\/wp\/v2\/posts\/3427\/revisions\/3433"}],"wp:attachment":[{"href":"http:\/\/mclements.net\/blogWP\/index.php\/wp-json\/wp\/v2\/media?parent=3427"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/mclements.net\/blogWP\/index.php\/wp-json\/wp\/v2\/categories?post=3427"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/mclements.net\/blogWP\/index.php\/wp-json\/wp\/v2\/tags?post=3427"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}