• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 344
  • Last Modified:

5.7.1 Unable to relay for

Someone in our org (yaddayadda.com) mails another person at (woohoo.com). Here, an NDR is received:

  jsski@whoohoo.com on 6/12/2006 9:56 AM
            You do not have permission to send to this recipient.  For assistance, contact your system administrator.
            <dunsvr06.yaddayadda.com #5.7.1 smtp;550 5.7.1 Unable to relay for jsski@woohoo.com>

Apparently, they have determined somehow that this problem is -not- on their side (woohoo.com). They have a hosted email service that I do not have any details on.

We have Exchange 2003 SP1 Native.

How can this be a problem on our side when we simply send the message to them? The users report that sometimes, the message goes through fine, other times, they get this NDR. This issue appears to be isolated to this particular domain (woohoo.com).

This *could* be related in some way to my other question... http://www.experts-exchange.com/Networking/Q_21901858.html
0
hotcam
Asked:
hotcam
  • 2
  • 2
1 Solution
 
SembeeCommented:
I would like to know what evidence they have that the problem is not on their side.
The fact that it goes through sometimes, and others does not, would tend to indicate the problem is with their end.
If the domain has multiple MX records or multiple servers accepting email from the internet - then I have seen this so many times. It is down to a single server having an issue - either not up to date on information, doesn't have the domain information, etc.

I will ask the standard question - any reason why you haven't updated to SP2 on Exchange 2003? It is rock solid and other than vendor support, there are no reasons why it shouldn't be deployed on all Exchange 2003 servers.

Simon.
0
 
hotcamAuthor Commented:
I haven't updated it yet because we have some specialized apps that integrate with exchange. It is on the todo list however.

You echo my thoughts exactly, but I'm getting squeezed by clients and management so I want to make sure there isn't something I'm missing before I tell them -for certian- it's not a problem on our end.


Thanks for your comments.
0
 
SembeeCommented:
I don't bother with trying to diagnose one domain issues, particularly if they turn round and say that the issue is with my end (when I know it isn't). I simply configure an SMTP Connector and route email out through the ISPs SMTP Server. Much simpler.

If the problem continues, then you can simply tell them that the problem has to be at their end because you are using the ISPs server... or are they telling you that the ISP has made an error.

Simon.
0
 
hotcamAuthor Commented:
I've added an SMTP connector for a couple of problematic domains. Going let that simmer for a few days and see how it goes.
0

Featured Post

[Webinar] Cloud and Mobile-First Strategy

Maybe you’ve fully adopted the cloud since the beginning. Or maybe you started with on-prem resources but are pursuing a “cloud and mobile first” strategy. Getting to that end state has its challenges. Discover how to build out a 100% cloud and mobile IT strategy in this webinar.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now