 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Server Forum / Exchange Server / Design / April 2006How to find what domains an exchange server tries to deliver mail
I've been getting the below message when trying to send email to domain that used to be hosted by our company. Externaldomain.com was at one time handled by our exchange server but is no longer. I can't find any references to it under recipient policies where all the other domains the exchange server delivers mail to is listed. Does anybody have a list of other places I might check to see why it is trying to deliver this mail locally instead of delivering it to our smtp connector for external delivery? bob@externaldomain.com on 4/25/2006 10:21 AM The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address. <myexchangeserver.mydomain.com #5.1.1> How about in the user properties?  Signature-------- Hope It Helps! dw _______________________________ Don Wilwol Distributed Application Technologies. dwilwol(DELETE)@datbusiness.com http://spaces.msn.com/members/wilwol/ www.datbusieness.com www.skyphere.com > I've been getting the below message when trying to send email to domain > that [quoted text clipped - 13 lines] > directly to find out the correct address. > <myexchangeserver.mydomain.com #5.1.1> There aren't any user properties that would affect delivery of messages to an entire domain. Plus it's not just affecting a single user or group of users. If you had a recipient policy set up, and then unchecked the "allow recipient policy to set email" and then removed the policy, the email would still be set in the user properties to the old domain. If the users email is set incorrectly, email will not be delivered. Signature-------- Hope It Helps! dw _______________________________ Don Wilwol Distributed Application Technologies. dwilwol(DELETE)@datbusiness.com http://spaces.msn.com/members/wilwol/ www.datbusieness.com www.skyphere.com > There aren't any user properties that would affect delivery of messages to > an > entire domain. Plus it's not just affecting a single user or group of > users. Check to make sure that you don't have any internal MX records that point back to your environment. Also, look at the address space tabs of any SMTP connectors you may have defined. Eric Bockelman Principal IT Infrastructure Specialist Windows Platform Engineering Symantec Corporation > I've been getting the below message when trying to send email to domain > that [quoted text clipped - 13 lines] > directly to find out the correct address. > <myexchangeserver.mydomain.com #5.1.1> Eric, I checked dns records by doing an nslookup and found their were no mx records pointing to back to us. They point to the external ip address that they should. The address space for the smtp connector is set to * so that all mail should be sent to the smart host who delivers the mail. The mail isn't reaching the smart host however because exchange believes it can still deliver this mail locally. Don, I'm a little confused by your post. I assume teh check box you are referring to is the "automatically update email addresses based on recipient policy". We no longer have any reference to the external domain in our recipient policies. So are you saying that if there is one user who has the above box unchecked and still has an address at externaldomain.com that this will cause exchange to try and deliver all mail for the entire domain locally instead of to the smtp connector to the smarthost. Because I can make up any address joe@externaldomain.com or ted@externaldomain.com and it will still try to deliver the mail locally on the exchange server. Is it really possible that one user's properties can affect mail delivery for the whole domain? Have you verified that your smart host doesn't have a rule that points the message right back at you? (You can telnet to port 25 and craft a message to the domain in question, or message track the one you already sent to see if it traversed the connector.) > Eric, > [quoted text clipped - 26 lines] > whole > domain? No. If the email address in the user properties does not show the old domain, and the smtp address is set correctly in the user properties you should be ok. What I meant was if all users were updated and then set to not update again, they may still have the old properties. If the users now have mailboxes hosted somewhere else, delete their mailboxes off the exchange server and mail should start moving. If users have a mailbox, Exchange will assume that's where mail is suppose to go, even though the address is wrong. In other words, if you create a mail enabled user, and add his real smtp address, exchange will put the mail in his mailbox, even though it should go elsewhere. Signature-------- Hope It Helps! dw _______________________________ Don Wilwol Distributed Application Technologies. dwilwol(DELETE)@datbusiness.com http://spaces.msn.com/members/wilwol/ www.datbusieness.com www.skyphere.com > Eric, > [quoted text clipped - 26 lines] > whole > domain? |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.