Email getting rejected due to bad RDNS

[#1]

I have my plusnet email addresses redirected to an account at inbox.com
This has worked fine for over a year
Now I'm getting failures due to an RDNS issue
It's not clear whether this is something that inbox.com have done, or plusnet/postini
BUT
I can get mail redirected my gmail.com account to inbox.com JUST FINE !
I only noticed this because all the SPAM had stopped !
Amazing - who'd have thought that SPAM actually serves as a useful "service working" indication 😉

---

This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
  zzzzz@inbox.com
    (generated from yyyyy@zzzdomainzzz.com)
    SMTP error from remote mail server after MAIL FROM:<xxxxx@yahoo.com> SIZE=3028:
    host inc.inbox.com [64.135.83.90]: 551 Server access forbidden by invalid RDNS record of your mail server.
------ This is a copy of the message, including all the headers. ------
Return-path: <xxxxx@yahoo.com>
Received: from exprod5mx247.postini.com ([64.18.0.167] helo=psmtp.com)
      by pih-sunmxcore13.plus.net with smtp (PlusNet MXCore v2.00) id 1KenQr-000019-Lx
      for yyyyy@zzzdomainzzz.com; Sun, 14 Sep 2008 09:58:14 +0100
Received: from source ([206.190.36.203]) by exprod5mx247.postini.com ([64.18.4.10]) with SMTP;
    Sun, 14 Sep 2008 04:58:12 EDT
Received: (qmail 16617 invoked by uid 60001); 14 Sep 2008 08:58:11 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
  b=GBrheu188sD2OG/U6U5QTTM6ougiiLbgvrLekLhVdHrU3722V39MPe+NfHO30Hxx3ITnBxd3JiEevlta48aU5CDUwKf5FD2lhoLJjNMZPAUaXDMWI+OKaE9qW25P6rfSP0INOdqJAdI4gbRWeAJmvKCQoM7mw9EGhWEcsQ09cdY=;
X-YMail-OSG: N17vBZkVM1kxufblgjQaLGoRB5je400nqV1FHoj1ZN.7Jwg7QdyfNWactJi_Ac7B_B5Vkt.VBY2NI2WcqEh1SjYyA3PIjilQcQLMdT96weaNuG.qNpNBheBLxP.jCDU.gTNr8uU_WSccRgOV95TTk8Y-
Received: from [212.159.100.223] by web53808.mail.re2.yahoo.com via HTTP; Sun, 14 Sep 2008 01:58:11 PDT
X-Mailer: YahooMailWebService/0.7.218.2
Date: Sun, 14 Sep 2008 01:58:11 -0700 (PDT)
From: MY NAME <xxxxx@yahoo.com>
Reply-To: xxxxx@yahoo.com
Subject: test11
To: yyyyy@zzzdomainzzz.com
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-ID: <906105.16111.qm@web53808.mail.re2.yahoo.com>
X-pstn-neptune: 1/1/1.00/95
X-pstn-levels:     (S:30.72994/99.90000 CV:99.9999 )
X-pstn-settings: 1 (0.1500:0.1500) cv gt3 gt2 gt1
X-pstn-addresses: from <xxxxx@yahoo.com> [db-null]

[#2]

You may care to edit you personal e-mail addresses in your message above, replace the sensitive bits with xxxxxx or whatever otherwise you may get spammed to death.

[#3]

Quote from: Anotherone

You may care to edit you personal e-mail addresses in your message above, replace the sensitive bits with xxxxxx or whatever otherwise you may get spammed to death.

Thanks for the tip, have done ... though I already do, Plusnet saw to that themselves last year when they allowed the old webmail to get hacked.
The email losses and hacking of the past couple of years are precisely why I do all this redirection away from 'em.

[#4]

bit pointless as by the look of it your mail goes through the machines that were hacked last year

[#5]

Do you have SPF Records set up for your domain?
If so, you will need to change them as the Plusnet inbound relays moved IP recently behind new load balancers.  This may be causing the problem.
B.

[#6]

Quote from: edrandall

Thanks for the tip, have done ... though I already do, Plusnet saw to that themselves last year when they allowed the old webmail to get hacked.

Not quite the same thing. The problem last year was that someone hacked in to a server. This forum can be read by anybody without having to log in, so spambots can still pick up any email addresses they find here.

[#7]

That bounce message appears to have come from a Yahoo server from what I can tell (206.190.36.203).
The reason for the failure I suspect is something to do with the inbox.com mail server having no reverse DNS entry.

bpullen@pvs-csctools:~$ host inc.inbox.com
inc.inbox.com has address 64.135.83.90

bpullen@pvs-csctools:~$ host 64.135.83.90
Host 90.83.135.64.in-addr.arpa not found: 3(NXDOMAIN)

I'd suggest contacting inbox.com and asking why 64.135.83.90 has no reverse DNS entry (ideally it should be set to inc.inbox.com).