Email white list

Hi

After the up’s and down’s of the email service, I have taken the decision to continue to use the web-hosting that you are good at and move the email to another host.

Sorry, I was loosing too many vital mails.

I now seem to have a problem that emails from a particular provider “One” do not get through, others do.

My MX record is correct and has propagated throughout the world in all but a few servers (mail-02.dd24.net). The One provider has suggested it is on the Infinity Free side and that the email routing is being blocked. I am quite skeptical about this explanation, however, since it looks like mailboxes were restored from a backup recently perhaps a whitelist has not been restored fully somewhere in the Infinity system.

I have included the failed transcription below.

Your thoughts please.

Many thanks in advance

Jason

==============================

Return-Path: <>
Delivered-To: cebu@testdomainet.com
Received: from mx2.pub.mailpod5-cph3.one.com ([10.27.28.12])
by mailstorage5.cst.mailpod5-cph3.one.com with LMTP id +GAaD0UUT1w9ugAAfZ6Ccw
for <cebu@testdomainet.com>; Mon, 28 Jan 2019 14:40:05 +0000
X-HalOne-ID: 99edde51-230a-11e9-af6e-ec0d9a6ed4c6
Received: from mailrelay1-1.pub.mailoutpod1-cph3.one.com (unknown [46.30.210.182])
by mx2.pub.mailpod5-cph3.one.com (Halon) with ESMTPS
id 99edde51-230a-11e9-af6e-ec0d9a6ed4c6;
Mon, 28 Jan 2019 14:40:05 +0000 (UTC)
From: Postmaster <support@one.com>
To: cebu@testdomainet.com
Date: Mon, 28 Jan 2019 14:40:05 +0000
Message-ID: <99e5dab8-230a-11e9-b4de-d0431ea8a283@one.com>
Subject: Undeliverable: One.com TEST
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
boundary=“99e5dab8-230a-11e9-b4de-d0431ea8a283”

  • This is a multipart message in MIME format.
  • –99e5dab8-230a-11e9-b4de-d0431ea8a283
    Content-Description: Delivery Status Notification
    Content-Type: text/plain; charset=UTF-8
    Content-Transfer-Encoding: 7bit
  • This is the mail system at host mailrelay1-2.pub.mailoutpod1-cph3.one.com.
  • I’m sorry to have to inform you that your message could not
    be delivered to one or more recipients. It’s attached below.
  • <jason.drew@fizzytiger.com> failed: fizzytiger.com:
    554 5.7.1 <jason.drew@fizzytiger.com>: Relay access denied
  • –99e5dab8-230a-11e9-b4de-d0431ea8a283
    Content-Description: Delivery Status Report
    Content-Type: message/delivery-status
  • Reporting-MTA: dns; mailrelay1-2.pub.mailoutpod1-cph3.one.com
    Received-from-MTA: smtp; onecom-webmail2 46.30.211.25 (46.30.211.130)
    Original-Envelope-Id: 98d7c204-230a-11e9-b4de-d0431ea8a283
    Arrival-Date: Mon, 28 Jan 2019 14:40:04 +0000
  • Final-Recipient: rfc822; jason.drew@fizzytiger.com
    Action: failed
    Status: 5.7.1 (<jason.drew@fizzytiger.com>: Relay access denied)
    Remote-MTA: dns; fizzytiger.com
    Diagnostic-Code: smtp; 554 5.7.1 <jason.drew@fizzytiger.com>: Relay access denied
  • –99e5dab8-230a-11e9-b4de-d0431ea8a283
    Content-Description: Undelivered Message Headers
    Content-Type: text/rfc822-headers
  • Received: from onecom-webmail2 46.30.211.25 (unknown [46.30.211.130])
    by mailrelay1.pub.mailoutpod1-cph3.one.com (Halon) with ESMTPSA
    id 98d7c204-230a-11e9-b4de-d0431ea8a283;
    Mon, 28 Jan 2019 14:40:03 +0000 (UTC)
    X-Originating-IP: 46.30.211.25
    User-Agent: One.com webmail 29.1.7
    Date: Mon, 28 Jan 2019 22:40:02 +0800
    MIME-Version: 1.0
    Message-ID: <1548686402665.104824.1362@webmail5>
    To: <jason.drew@fizzytiger.com>
    From: “TEST EMAIL” <cebu@testdomainet.com>
    Reply-To: <cebu@testdomainet.com>
    Subject: One.com TEST
    Content-Type: multipart/alternative; boundary="----------1360-1548686402665-1"
  • –99e5dab8-230a-11e9-b4de-d0431ea8a283–

Moving the email away from InfinityFree for now was a great call! It’s probably going to take a while for the email system to be reliable again, but I can’t say the email service was ever reliable enough to pass as a business email service.

However, when you changed your domain’s email settings away from InfinityFree, you also made it impossible for us to fix any email issues as well. So if you moved your email to another provider, you need to ask that provider why incoming email doesn’t work.

The trace you sent clearly shows that the mail server from one.com is rejecting the messages. I don’t know why, but I know that the people from one.com should be able to answer that question.

Hi Admin

Thanks for the speedy response.

I had a suspicion this might be a circular hunt. I have checked with Moniker who are now hosting the email. They confirmed the MX record was correct as was the A record. They could send an email to the address, I could from my gmail. They said contact “One”. “One” they said it wasn’t them and to contact Infinity Free and you said … :slight_smile:

I am not sure if they have somehow cached the old MX record and it needs time to update, I was able to send email from my One account to this email address when it was hosted by yourselves so I am suspicious it has anything to do with you.

I realise it is out of your control, I was just wondering if anything might have changed after the last email outage?

Could you point me to where you see “that the mail server from one.com is rejecting the messages”, I am not the best at reading traces?

Thanks again

Jason

There are a few lines in the email trace which caught my attention.

<jason.drew@fizzytiger.com> failed: fizzytiger.com: 554 5.7.1 <jason.drew@fizzytiger.com>: Relay access denied

This code means that the “recipient” refused to pass on the message to the actual target mail server.

But who is the recipient here? According to the trace, there are many different email systems involved, like mailrelay1-2.pub.mailoutpod1-cph3.one.com, mailrelay1-1.pub.mailoutpod1-cph3.one.com and mailrelay1.pub.mailoutpod1-cph3.one.com. What’s so important about that? These are all systems from One.com. Your own email provider, dd24.net isn’t mentioned anywhere.

That makes me suggest that this error code is being generated in One.com’s systems, and that the message is rejected before ever being offered to your real email provider. So I suspect that One.com is the party which can fix this issue.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.