Email not getting through.


Recommended Posts

We have a issue at work and cant work it out, we have one group of people, anyone using a email client program like MICROSOFT OUTLOOK, with one ISP Xtra, anyone using these two things together, and trying to email us at work cannot send, and are they getting a "Email address doesnt exist". email header below. the MX record is incorrect and we have had it updated, but i looks like the ISP xtra are still using a old one (and we dont know where this came from).

Any tip or thoughts on what we should be looking at would be great.

From: Mail Administrator

Date: 6 December 2012 3:09:58 PM NZDT

To:

Subject: Mail System Error - Returned Mail

Reply-To: <Postmaster@>

x-apparently-to: @xtra.co.nz via 124.108.96.84; Wed, 05 Dec 2012 18:09:58 -0800

received-spf: none (domain of mta02.xtra.co.nz does not designate permitted sender hosts)

x-ymailisg: NDvE6hwWLDtmS6aH.dKaAgr_gD8LU76HakISh2FrkeGhBg2Y Pfrc1msCn0YLkF0SrvgjkroXvHpq5Vo1NbL8GmYNsmJp29JFe1nIK8DuxtBZ P2gZY87WIheF3FhUfL879a4Um7FNSfSmptA6.kkqXzVfnDGLEylOycY0UzZN U0cViDDU8g_HDIlecTTB65pbmI7IN.tNoTOKnUhy0PTwt.e8eintKP6ceJPZ S8MqIwhEifEtyPXbMHL89xm02_ALiCsWfYy7MUXdcfCE21fVtciknUhWkt_K MvWi8gy5MwwXEsybiZQVPX8T1A8TBGxOxeUNGjvvWOrKqjHm.YSBhx3uuiLp sjQaLyyZjwjIAEZl7SeGdk2OYiQHWEDX

x-originating-ip: [210.54.141.250]

authentication-results: mta1008.tnz.mail.aue.yahoo.com from=ero.govt.nz; domainkeys=neutral (no sig); from=ero.govt.nz; dkim=neutral (no sig)

received: from 127.0.0.1 (EHLO mta02.xtra.co.nz) (210.54.141.250) by mta1008.tnz.mail.aue.yahoo.com with SMTP; Wed, 05 Dec 2012 18:09:58 -0800

message-id: <20121206020958.FONK6031.mta02.xtra.co.nz@mta02>

mime-version: 1.0

content-type: multipart/report; report-type=delivery-status; Boundary="===========================_ _= 6259460(6031)1354759798"

This is a system generated message. Please DO NOT REPLY.

Your message was not delivered for the following reason:

The following destination addresses were unknown (please check the

addresses and re-mail the message):

<****@*******>

Kind regards.

The Xtra Messaging Team

Reporting-MTA: dns; sf1431.xtra.co.nz

Arrival-Date: Thu, 6 Dec 2012 15:09:58 +1300

Received-From-MTA: dns; [125.236.222.142]

Final-Recipient: RFC822; <****@******>

Action: failed

Status: 5.1.1

Link to comment
https://www.neowin.net/forum/topic/1124144-email-not-getting-through/
Share on other sites

Well I am guessing that you blanked out the most important information regarding the error....

The following destination addresses were unknown (please check the

addresses and re-mail the message):

Take a look at the To: line in the header and see where it is going to. Make sure it is the correct address as well as having correct spelling. I have seen issues where the cached address in outlook is corrupt or is going to the wrong place and either the entire cache or the individual email in the cache has to be deleted. If you didn't blank it out, well the email client can't send to <blank>

Well I am guessing that you blanked out the most important information regarding the error....

The following destination addresses were unknown (please check the

addresses and re-mail the message):

Take a look at the To: line in the header and see where it is going to. Make sure it is the correct address as well as having correct spelling. I have seen issues where the cached address in outlook is corrupt or is going to the wrong place and either the entire cache or the individual email in the cache has to be deleted. If you didn't blank it out, well the email client can't send to <blank>

yes i did blank it out, the email address are correct, we have tested deleted the cache email address and the problem still there, and it is also happening to people that have never email us before.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Was it too much to ask to show the icon in this article?
    • Frankly, I blame whoever is writing such articles. "A big improvement/update and/or new feature is now available to everyone! Also, use this unofficial tweak tool to enable it because it actually isn't available to you yet officially and might not in fact even be entirely ready or whatever, hence why it is perhaps not enabled for you*. But it's great and you should enable it!" I mean there's nothing wrong with sharing info about some feature you might need to enable via unofficial means, of course. It's just that these articles tend to essentially end up being two news pieces in one, and one of them tends to be a bit misleading. (*Yes, yes, the "it's a controlled rollout!" thing. Not a fan of that one either. The argument, not the actual rollout.)
    • Thank you. Will do. I read in the release notes that editor config might be at play here.
    • Actually, I think even Microsoft doesn't know how to control it
    • OpenAI is making Codex more useful in Chrome and the cloud by Pradeep Viswanathan OpenAI's Codex now has more than 5 million users, up nearly 4x from earlier this year. To further accelerate Codex's growth among developers, OpenAI today announced that it has agreed to acquire Ona, a company that builds secure cloud execution and orchestration technology for developers. Ona will enable developers to run Codex with persistent and controlled cloud infrastructure for long-running agentic workflows. Right now, most Codex execution happens locally on developers' laptops and PCs, and the agents work continuously for hours. Through Ona, OpenAI aims to make Codex agents keep working for days without being tied to a user’s local machine or an active session. This will be an important capability for enterprises that want to deploy AI agents in production while maintaining control over infrastructure, data, security boundaries, credential scope, logging, and review workflows. Like any acquisition, the deal is still subject to customary closing conditions, including regulatory approvals. Until the deal closes, OpenAI and Ona will continue to operate as separate companies. After closing, Ona’s team will join the Codex team to improve developer workflows. Alongside the Ona acquisition announcement, OpenAI today introduced a few Codex updates. Developers can now save Codex rate limit resets and use them later instead of losing them when they are not needed immediately. OpenAI is also adding a referral option where users can invite a friend to Codex and get a saved rate limit reset. OpenAI today also announced a developer mode for browser use in Chrome and the Codex in-app browser. With this mode, Codex can use the Chrome DevTools Protocol to debug web apps, inspect pages, and work more directly with browser-based development workflows. Developers can use this when they want Codex to profile JavaScript, inspect console output and network traffic, examine web page states including the DOM and applied styles, and more.
  • Recent Achievements

    • Week One Done
      davidbazooked earned a badge
      Week One Done
    • One Month Later
      Jamswaz earned a badge
      One Month Later
    • Week One Done
      Jamswaz earned a badge
      Week One Done
    • Rookie
      Marzoid went up a rank
      Rookie
    • Community Regular
      coch went up a rank
      Community Regular
  • Popular Contributors

    1. 1
      +primortal
      509
    2. 2
      PsYcHoKiLLa
      186
    3. 3
      +Edouard
      157
    4. 4
      Steven P.
      83
    5. 5
      ATLien_0
      75
  • Tell a friend

    Love Neowin? Tell a friend!