Posted: 7/13/2010 12:08:38 PM EDT
|
The issue: Lots of #5.5.0 smtp;553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1), #5.5.0 smtp;550 No Such User Here, and #5.5.0 smtp;550 No Such User Here messages. Funny thing is that others user can send to the recipients just fine. This next part has me scratching my head, though. I can run ipconfig /renew on the desktops having problems and the can now send to the recipient.
Our setup: Windows XP desktops on Windows 2003 domain. Exchange 2003 Enterprise. Users using Outlook 2003 on the desktop NOT using pop. IP's obtained via DHCP. I've turned off reverse DNS lookup initially, but it didn't seem to matter (several of the clients had email addresses that didn't match their mail server domain name. that coupled with the 5.7.1 relaying error made me think that their reverse DNS records were hosed or non existant). Any ideas? |
|
The exchange server is obtaining ip via DHCP?
[email protected] can't email [email protected]? I'd start with the MS Best Practices guide, and make sure everything is configured accordingly. |
| Nope. Server has a static IP and has been fine for years now. This is a recent event and we're not sure what's going on. About the only two things that I figure are relate is that we moved the DHCP database from one DC to another and we put up a Freesco DNS server to handle the recursive DNS requests for external domains. Machines have been getting IP's from the moved DHCP scope for a while now and everything appears to work fine with the DNS server - email and web browsing. The issue is definitely related to the PC's and is simple to fix. I just don't know why they go off reservation. About 5 different PC's a day experience this problem. ipconfig /renew and everything's fine. |