No one has responded to this discussion for at least a year, so this information may be out of date. If you're looking for information about this topic, please search for a more recent discussion or post a new question.

I can send but not receive email

  • 3 Followers
  • 3 Replies |
  • This post has 0 verified answers |
Not Answered This question is not answered

Hi - I recently purchased office 365 small business.  This is a brand new domain name which i registered on go daddy.  I went through the setup of the domain on o365 yesterday, and was able to send an email message via web access, but can not receive an email from an external address.  Below is the error message i receive when trying to send to my o365 account  I'm sure i'm missing something easy - any help would be appreciated.  I x' and y'd some of the actual email addresses to protect the innocent.

 

Delivery has failed to these recipients or distribution lists:

derek edson 

An error occurred while trying to deliver this message to the recipient's e-mail address. Microsoft Exchange will not try to redeliver this message for you. Please try resending this message, or provide the following diagnostic text to your system administrator.

The following organization rejected your message: m1pismtp01-014.prod.mesa1.secureserver.net.

Diagnostic information for administrators:

Generating server: bigfish.com

dedson@xxxxxx

m1pismtp01-014.prod.mesa1.secureserver.net #<m1pismtp01-014.prod.mesa1.secureserver.net #5.0.0 smtp;550 #5.1.0 Address rejected dedson@xxxxxxx.com> #SMTP#

Original message headers:

Received: from mail195-tx2-R.bigfish.com (10.9.14.239) by
 TX2EHSOBE002.bigfish.com (10.9.40.22) with Microsoft SMTP Server id
 14.1.225.23; Thu, 29 Dec 2011 14:28:57 +0000
Received: from mail195-tx2 (localhost [127.0.0.1])           by
 mail195-tx2-R.bigfish.com (Postfix) with ESMTP id E08A360026B   for
 <dedson@xxxxxxx.com.FOPE.CONNECTOR.OVERRIDE>; Thu, 29 Dec 2011
 14:27:55 +0000 (UTC)
X-SpamScore: -1
X-BigFish: VPS-1(zz9371Ic85fhzz1202hzz8275bh8275dhz2dh2a8h668h839h61h)
X-Spam-TCS-SCL: 0:0
X-Forefront-Antispam-Report: CIP:65.55.171.153;KIP:(null);UIP:(null);(null);H:VA3DIAHUB087.RED001.local;R:internal;EFV:INT
Received: from mail195-tx2 (localhost.localdomain [127.0.0.1]) by mail195-tx2
 (MessageSwitch) id 1325168874612460_20892; Thu, 29 Dec 2011 14:27:54 +0000
 (UTC)
Received: from TX2EHSMHS004.bigfish.com (unknown [10.9.14.236])        by
 mail195-tx2.bigfish.com (Postfix) with ESMTP id 8107F5C0042       for
 <dedson@xxxxxx.com>; Thu, 29 Dec 2011 14:27:54 +0000 (UTC)
Received: from VA3DIAHUB087.RED001.local (65.55.171.153) by
 TX2EHSMHS004.bigfish.com (10.9.99.104) with Microsoft SMTP Server (TLS) id
 14.1.225.22; Thu, 29 Dec 2011 14:28:56 +0000
Received: from VA3DIAXVS3C1.RED001.local ([10.16.20.114]) by
 VA3DIAHUB087.RED001.local ([10.8.158.146]) with mapi; Thu, 29 Dec 2011
 06:29:18 -0800
From: Derek Edson <derek.edson@yyyyyyy.com>
To: Derek Edson <dedson@xxxxx.com>
Date: Thu, 29 Dec 2011 06:29:18 -0800
Subject: RE: test
Thread-Topic: test
Thread-Index: AczGNhqCOWAL5tC5TbqPCDuorsSJuAAACCRA
Message-ID: <3443930E3E52084DB8A730131A5254500A1F3DB4B7@VA3DIAXVS3C1.RED001.local>
References: <858374C650B4F744AAF53D9A8A29C142C658C0@BL2PRD0504MB131.namprd05.prod.outlook.com>
In-Reply-To: <858374C650B4F744AAF53D9A8A29C142C658C0@BL2PRD0504MB131.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative;
            boundary="_000_3443930E3E52084DB8A730131A5254500A1F3DB4B7VA3DIAXVS3C1R_"
MIME-Version: 1.0
Return-Path: derek.edson@yyyyyy.com
X-OriginatorOrg: accelare.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%0$Dn%UTILITIESWATCH.COM$RO%1$TLS%0$FQDN%$TlsDn%

 

 

  • Post Points: 20
All Replies
  • it appears that maybe the domain has not been verified.  Did you go thru the steps to add the domain and then create a TXT record with your DNS provider to verify the domain?  can you send email to @company.onmicrosoft.com ?

    Sean McNeill

    Blog: http://office365evangelist.com/

    Microsoft MVP - Office 365

    • Top 100 Contributor
    • Post Points: 0
  • Thanks for the response.  I did go through the TXT steps with the DNS provider.  When I look at the admin screen the domain shows as verified.  I only did this last night and there was a note about the process taking 72 hours for the dns changes to propogate through the internet.  Maybe this is the issue.

     

    I was able to log on as an admin and send and receive an email using the @company.onmicrosoft.com.

     

      

    • Not Ranked
    • Post Points: 0
  • Hello Derek,

    There's several possible problems that we may be looking at here.

    1. The MX and/or nameserver records for your vanity domain have not been updated properly.

    2. The MX records have not been completely propogated through the Internet.  This can take 72 hours.

    3. The O365 user to whom you are sending has been created in the O365 Portal, but has not been assigned a license.

    When you get the chance, please provide the name of your vanity domain.  A couple quick checks on my end can determine if the DNS records for the domain have been set properly.

    Finally, @company.onmicrosoft.com should work because the proper DNS values are automatically established.

    Thank you,
    Chase Dahl
    O365 Forum Moderator
    • Top 75 Contributor
    • Male
    • Post Points: 0
Page 1 of 1 (4 items)