[Last Call] Learn about multicloud storage options and how to improve your company's cloud strategy. Register Now

x
?
Solved

SMTP 550 Error - Urgent!!

Posted on 2004-08-30
6
Medium Priority
?
453 Views
Last Modified: 2008-02-01
Please help me figure out what is going on.
Exchange 2000 SP3 on a Windows 2000 Server.

I can send email from my domain out to the internet but I am unable to receive any email.

Below is the message you would receive if you tried sending an email to my domain.

Nothing that I know of has changed on the exchange server since it last worked perfectly a few days ago.  I have scanned for viruses, spyware, ect.

Please shoot me in the right direction, not getting email really hurts.
------------------------------------
Delivered-To: tropix@hotmail.com
Received: by 10.11.117.35 with SMTP id p35cs1938cwc;
Mon, 30 Aug 2004 12:23:30 -0700 (PDT)
Received: by 10.38.8.48 with SMTP id 48mr1561411rnh;
Mon, 30 Aug 2004 12:23:30 -0700 (PDT)
Return-Path: <>
Received: from kbsb-fs3.brothers.com ([66.43.215.212])
by mx.hotmail.com with ESMTP id 61si476067rnb;
Mon, 30 Aug 2004 12:23:30 -0700 (PDT)
X-SPF-Guess: softfail 66.48.215.212::kbsb-fs3.brothers.com
From: postmaster@brothers.com
To: tropix@hotmail.com
Date: Mon, 30 Aug 2004 14:23:19 -0500
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
boundary="9B095B5ADSN=_01C48EC6A5BE2ACE00000012kbsb?fs3.b"
X-DSNContext: 7ce717b1 - 1184 - 00000002 - 00000000
Message-ID: <8J8QYCoNJ00000015@kbsb-fs3.brothers.com>
Subject: Delivery Status Notification (Failure)

This is a MIME-formatted message.
Portions of this message may be unreadable without a MIME-capable mail program.

--9B095B5ADSN=_01C48EC6A5BE2ACE00000012kbsb?fs3.b
Content-Type: text/plain; charset=unicode-1-1-utf-7

This is an automatically generated Delivery Status Notification.

Delivery to the following recipients failed.

netadmin@brothers.com

--9B095B5ADSN=_01C48EC6A5BE2ACE00000012kbsb?fs3.b
Content-Type: message/delivery-status

Reporting-MTA: dns;kbsb-fs3.brothers.com
Received-From-MTA: dns;mproxy.hotmail.com
Arrival-Date: Mon, 30 Aug 2004 14:23:18 -0500

Final-Recipient: rfc822;netadmin@brothers.com
Action: failed
Status: 5.7.1
Diagnostic-Code: smtp;550 5.7.1 Unable to relay for netadmin@brothers.com
X-Display-Name: Network Administrator

--9B095B5ADSN=_01C48EC6A5BE2ACE00000012kbsb?fs3.b
Content-Type: message/rfc822

Received: from mproxy.hotmail.com ([216.239.56.245]) by kbsb-fs3.brothers.com with Microsoft SMTPSVC(5.0.2172.1);
Mon, 30 Aug 2004 14:23:18 -0500
Received: by mproxy.hotmail.com with SMTP id w67so48932cwb
for <netadmin@brothers.com>; Mon, 30 Aug 2004 12:23:02 -0700 (PDT)
Received: by 10.11.117.78 with SMTP id p78mr100276cwc;
Mon, 30 Aug 2004 12:23:02 -0700 (PDT)
Received: by 10.11.117.35 with HTTP; Mon, 30 Aug 2004 12:23:02 -0700 (PDT)
Message-ID: <2e926abf04083012233c963319@mail.hotmail.com>
Date: Mon, 30 Aug 2004 14:23:02 -0500
From: Tony Smith <tropix@hotmail.com>
Reply-To: Tony Smith <tropix@hotmail.com>
To: Network Administrator <netadmin@brothers.com>
Subject: Re: 223
In-Reply-To: <16258C6EEABAED4498F98ED96ADDF4620B0827@kbsb-fs3.brothers.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <16258C6EEABAED4498F98ED96ADDF4620B0827@kbsb-fs3.brothers.com>
Return-Path: tropix@hotmail.com
X-OriginalArrivalTime: 30 Aug 2004 19:23:19.0843 (UTC) FILETIME=[CEDC4F30:01C48EC6]

223

On Mon, 30 Aug 2004 14:22:40 -0500, Network Administrator
<netadmin@brothers.com> wrote:
> 223
>

--9B095B5ADSN=_01C48EC6A5BE2ACE00000012kbsb?fs3.b--
0
Comment
Question by:tropix
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
6 Comments
 
LVL 4

Accepted Solution

by:
ehammersley earned 1000 total points
ID: 11937738
Well the first thing out of order is most certainly your DNS records.  If you run brothers.com through www.dnsreport.com you'll see the problem.  First and foremost, your primary MX record doesn't even accept e-mail for your domain, second the secondary MX is set to a loopback address.

You need to get your MX records squared away before anything else can be tested.  Make sure your primary MX record point to your Exchange Server or routers public firewall.  Once that is reported as fixed you should see a lot of other things clear up.  Also, make sure you get the respective PTR (Reverse Lookup) records in place as well.
0
 
LVL 8

Assisted Solution

by:f_umar
f_umar earned 1000 total points
ID: 11939321
0

Featured Post

[Webinar] Lessons on Recovering from Petya

Skyport is working hard to help customers recover from recent attacks, like the Petya worm. This work has brought to light some important lessons. New malware attacks like this can take down your entire environment. Learn from others mistakes on how to prevent Petya like worms.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

New style of hardware planning for Microsoft Exchange server.
Want to know how to use Exchange Server Eseutil command? Go through this article as it gives you the know-how.
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
Suggested Courses

656 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question