451 Could not load relay DRD error

I have a group of users that tell me that they get this error message when they send email to a distribution list email address in Exchange 2003 that contains emails outside of the Exchange's domain.

Any ideas if this is fixable or not?

Below is a breakdown of some of the full error messages:

From: Mail Delivery System
Sent: Tuesday, September 27, 2005 11:09
To: Ken Ell
Subject: Mail delivery failed

Follow Up Flag: Follow up
Flag Status: Completed

This message was created automatically by mail delivery software.

A message that you have sent could not be delivered to one or more
recipients.  This is a permanent error.  The following address(es) failed:

  <support@ti-logy.com>: 451 Could not load relay DRD

Included is a copy of the message header:
Received: from unknown [] (EHLO drake.opssdc.org)
      by p02m144.mxlogic.net (mxl_mta-2.12.2-01)
      with ESMTP id 0e7e2334.1502280624.95692.p02m144.mxlogic.net (envelope-from <ken@ti-support.com>);
      Thu, 22 Sep 2005 11:20:32 -0600 (MDT)
Received: from p02m151.mxlogic.net ([]) by drake.compassdc.local with Microsoft SMTPSVC(6.0.3790.211);
       Thu, 22 Sep 2005 13:24:46 -0400
Received: from unknown [] (EHLO mail28.sea5.speakeasy.net)
      by p02m151.mxlogic.net (mxl_mta-2.12.2-01)
      with ESMTP id ed7e2334.1467214768.76902.p02m151.mxlogic.net (envelope-from <ken@ti-support.com>);
      Thu, 22 Sep 2005 11:20:30 -0600 (MDT)
Received: (qmail 28599 invoked from network); 22 Sep 2005 17:20:30 -0000
Received: from dsl093-129-203.sfo4.dsl.speakeasy.net (HELO dev.tierratechnology.com) ([])
          (envelope-sender <ken@ti-support.com>)
          by mail28.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <tfce@cmeiinoiy.com>; 22 Sep 2005 17:20:29 -0000
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
Content-Transfer-Encoding: quoted-printable
Subject: RE: Error Log
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Date: Thu, 22 Sep 2005 10:29:12 -0700
Message-ID: <73FAEF3F17F1374EAE4E5A6C29EA41AE198ACD@server.TierraTechnology.local>
Thread-Topic: Error Log
thread-index: AcW/luvN7hBNHRCJTCS7L5VEKCC+LAAAqkHA
X-Message-Flag: Follow up
From: "Kenneth Ellis" <ken@ti-support.com>
To: "Titus France" <trance@cmeiinoiy.com>,
      "SFSupport" <SFSupport@cmeiinoiy.com>
X-Spam: exempt
X-MAIL-FROM: <ken@ti-support.com>
Return-Path: ken@ti-support.com
X-OriginalArrivalTime: 22 Sep 2005 17:24:46.0533 (UTC) FILETIME=[87465750:01C5BF9A]
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

That isn't an Exchange message, so it is being generated by another server.

Looking at the header my guess would be the email server for the domain "ti-logy.com" or "opssdc.org".

edentoneAuthor Commented:
Right, but what does that error mean? I have not been able to see what exactly the message means. And which server is the 'fix' supposed to be applied to? Our server or one of the servers in the middle?

It isn't your server as that isn't an Exchange server message.

It is probably a server in the middle somewhere - something that has to relay the message to another server. Can't find the exact cause... various hits on Google pointing towards sendmail, but not much else.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Ensure Business Longevity with As-A-Service

Using the as-a-service approach for your business model allows you to grow your revenue stream with new practice areas, without forcing you to part ways with existing clients just because they don’t fit the mold of your new service offerings.

edentoneAuthor Commented:
It turned out to be MXLogic blocking a distribution type email coming from an outside sourse and emailing another outside sorce, kind of like relay..

Thanks for your help.
Edentone, can you explain more about how you resolved this issue? I am receiving the same error and looked up the MX record of the email domain I am trying to email to.

What actually needed to be done to resolve this and by who?
dsngroup - this is a very old question. Unlike a forum it is not possible to "bump" questions back up the list. The only people who will see your post are those that have already participated. Instead you should post your question as a new question in the Exchange Server Zone which will allow other experts the chance to see the question and respond.


Exchange Server Zone Advisor.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.