GAL Corruption?

Exchange/WinServer 2003 - supporting about 50 users...  SP2 for Exchange is NOT installed (working through disk space issues)...

We've been having intermittent problems with the following NDR's for the past week:

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

  user@sisterdomain.org
    SMTP error from remote mail server after RCPT TO:<user@sisterdomain.org>:
    host 10.50.204.139 [10.50.204.139]: 550 invalid recipient.

A well trusted consultant informed us that our ISP's SMTP servers were on the fritz and directed us to use DNS to route to each address space on this connector in Exchange/Connector Properties... which we've done.  

Right now the problem seems to have subsided considerably but I'm not convinced there won't be more occurrences.  

This morning one or more users reported mail not being received by their remote recipients.  One of my colleagues spoke to nother consultant who reported seeing these kinds of problems due to a corrupted GAL.

Is this possible?  Is there a way to check the integrity of the GAL?

Thanks.

LTWadminAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
JimboEfxConnect With a Mentor Commented:
Hello LTWadmin,

You can see common GAL issues and solutions here:

http://www.amset.info/exchange/oab-error.asp

Can you give some more information on the NDR.

Do you get this sending out to a customer, or does a customer get this sending in?

Regards,

JimboEfx
0
 
LTWadminAuthor Commented:
Here's a more complete example...  The problem has been largely "inside going out emails" and usually (according to reports I've heard) the same domain.

Subject: Mail delivery failed: returning message to sender

This message was created automatically by mail delivery software.

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

  recipient@otherdomain.org
    SMTP error from remote mail server after RCPT
TO:<recipient@otherdomain.org>:
    host 10.50.204.139 [10.50.204.139]: 550 invalid recipient

------ This is a copy of the message, including all the headers. ------

Return-path: <sender@ourdomain.org>
Received: from [outside IP] (port=55235 helo=ourmachinename.ourdomain.org)  by mx.cbeyond.com with esmtp (Exim 4.62)  (envelope-from <sender@ourdomain.org>)  id 1JJUc1-00049V-Dv  for recipient@otherdomain.org; Mon, 28 Jan 2008 09:05:25 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
 charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject:
Date: Mon, 28 Jan 2008 08:52:43 -0500
Message-ID:
<327FF2C7D6C6AC43B51A4435DAD9555801351A47@machinename.ourdomain.org>
In-Reply-To:
<BBB004A63BF99740B7F461BBFD6220F0033F3135@recipient.otherdomain.local>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Index: Achg+hyXBfvv9V5nQe+CQ6qmhpMWAgAuudcg
References:
<BBB004A63BF99740B7F461BBFD6220F0033F3135@recipient.otherdomain.local>
From: "firstname lastname" <sender@ourdomain.org>
To: "firstname lastname" <recipient@otherdomain.org>
0
 
JimboEfxCommented:
LTWadmin,

Usually when i see this I do a bit of investigation.

Namely can i send an email manually to this offending server?
http://www.yuki-onna.co.uk/email/smtp.html

And then i investigate any anti spam facilities
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_22098983.html

JimboEfx
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
LTWadminAuthor Commented:
OK - The Telnet thing was cool - didn't know you could do that.  Here are the results:

220 machinename.ourdomain.org Microsoft ESMTP MAIL Service, Version: 6.0.3790.1830
ready at  Thu, 31 Jan 2008 17:22:58 -0500
HELO ourdomainname.org
500 5.3.3 Unrecognized command
HELO mail.ourdomain.org
250 machinename.ourdomain.org Hello [192.168.11.8]
MAIL FROM: myname@mydomain.org
250 2.1.0 myname@mydomain.org....Sender OK
RCPT TO: mail@targetserver.org
550 5.7.1 Unable to relay for mail@targetserver.org...

So this indicates the mail server has refused to relay mail for us?
0
 
JimboEfxCommented:
provided you have smtped to their mail server directly (not your own becuase it is usually realy secured!) then this would indicate a smtp error on their end.

Of course to complicate matters some anti spam products will send valid smtp error codes if they want to reject your message - even though it is the incorrect use of that code!

Best to get in touch with their it staff and have a chat.
0
 
LTWadminAuthor Commented:
This part indicates an attempt to send mail to the target server from my own yes?

MAIL FROM: myname@mydomain.org
250 2.1.0 myname@mydomain.org....Sender OK
RCPT TO: mail@targetserver.org
550 5.7.1 Unable to relay for mail@targetserver.org...
0
 
JimboEfxCommented:
when you started the telnet you did

telnet someservername 25
ehlo blah
mail from:blah@
rcpt to: blah@
data
blah
.

the someservername should the recipients mail server, not yours!

To found out their mail server you need to find their mx record http://www.mxtoolbox.com/

telnet to the lowest priority mx record and then try again.

HTH
0
 
LTWadminAuthor Commented:
Turned out to be the ISP...
0
All Courses

From novice to tech pro — start learning today.