Lazyweb, help me get un-blocked by Earthlink and Dreamhost

I've convinced the A-list and B-list mail hosts to accept mail from me, but I have customers using a couple of the C-listers who still block me. Can you help?

IP is blocked by EarthLink. Go to for details. (in reply to MAIL FROM command)

That says "email". I have done so four times. Ignored.

host[] said: 550 5.7.1 Reject for policy reason blacklisted (in reply to MAIL FROM command)

I can't even figure out how to contact them. I tried Ignored.

Previously, previously, previously.

Tags: , , , ,

8 Responses:

  1. Dave says:

    At least one problem is that the ip above matches the forward (A) entry for your MX server ( but reverses to www, not mail.

    to wit:

    % dig MX +short

    % dig A +short

    % dig -x +short

    So you'll want to fix the PTR record for that IP to point to, not www.

    • jwz says:

      Since Google, Yahoo and AT&T don't seem to give a shit about that, I'm not convinced that matters.

      • Grego says:

        It matters if your goal is overall deliverability of your email. The credibility of your EC2-based email server is greatly improved (from None) with a matching PTR record.

  2. William says:

    Have you tried calling up the NOCs for these respective ISPs? Looks like its +1-404-815-0770 for Earthlink and +1-714-706-4182 for Dreamhost per whois. Sometimes that to work when you can't otherwise reach a person.

  3. extra88 says:

    Dave's answer about the PTR record sounds pretty plausible.

    I'm a Dreamhost customer. If you send a message to the address on this post and it's blocked, send me the original message and response to another address that's not hosted by them (remove "m." from this address) and I'll contact Dreamhost support.

  4. Koleslaw says:

    Earthlink still exists? Holy crap.

  5. The blocked IP is an Amazon EC2 instance. If you can provide me with the full header from the bounce back you received from us, I can give a definitive answer as to why your message was blocked.

    • jwz says:

      Yes, my mail server is an EC2 instance. Here are the headers. (I'd have mailed you directly instead of posting it here, but I'm not sure it will arrive.) Thank you!

      <[REDACTED]>: host[] said:
          550 5.7.1 Reject for policy reason blacklisted (in reply to end of DATA
      Reporting-MTA: dns;
      X-Postfix-Queue-ID: 5BDF4145ABA
      X-Postfix-Sender: rfc822;
      Arrival-Date: Tue, 18 Dec 2018 18:17:14 -0800 (PST)

      Final-Recipient: rfc822; [REDACTED]
      Action: failed
      Status: 5.7.1
      Remote-MTA: dns;
      Diagnostic-Code: smtp; 550 5.7.1 Reject for policy reason blacklisted
      Return-Path: <>
      Received: by (Postfix, from userid 1010)
            id 5BDF4145ABA; Tue, 18 Dec 2018 18:17:14 -0800 (PST)
      DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;
            s=mail; t=1545185982;
      Old-Return-Path: <>
      From: DNA Lounge <>
      To: DNA Lounge Announcements <>
      Subject: Upcoming DNA Lounge Events: GTA, Acid Rain: Solstice, Bootie: Island of Misfit Toys, Death Guild and more!
      MIME-Version: 1.0
      Content-Type: multipart/alternative; boundary="5c19aa0f.00a8bea600acaf70"
      Message-Id: <>
      Date: Tue, 18 Dec 2018 18:16:47 -0800 (PST)
      Resent-Message-ID: <>
      List-Post: <>
      List-Help: <>
      List-Subscribe: <>
      List-Unsubscribe: <[REDACTED]>
      Precedence: bulk
      Original-Recipient: [REDACTED]
      Resent-Date: Tue, 18 Dec 2018 18:17:14 -0800 (PST)

  • Previously