bemara57
asked on
Can send but not receive emails on Exchange 2003
I just created a primary email for myself in Active Directory. I then added the domain to be handled in Exchange 2003 by adding it to the Default Recipient Policy and made it the primary smtp, and updated the policy. I can send emails fine, but I can't receive. The sender doesn't get any failed delivery report or anything, it's like it disappears into cyberspace. The Exchange queue is zero as well. And another thing is that I can send an email to myself and receive it fine, but I don't get emails from the outside. What could be happening?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I tried restarting the mail attendant, and regiis, then even restarted the Exchange server completely. That didn't work. I used the telnet to check the response and I get:
220 mail.MyMail.com Microsoft ESMTP MAIL Service, Version: 6.0.3790.3959 ready at Thu, 7 Aug 2008 15:34:12 -0400
I also tried sending an email to an outside email address (Yahoo/Hotmail) and it received the email fine. But when I reply back to the email from the Yahoo account, it gets lost in space somewhere. Any other ideas?
220 mail.MyMail.com Microsoft ESMTP MAIL Service, Version: 6.0.3790.3959 ready at Thu, 7 Aug 2008 15:34:12 -0400
I also tried sending an email to an outside email address (Yahoo/Hotmail) and it received the email fine. But when I reply back to the email from the Yahoo account, it gets lost in space somewhere. Any other ideas?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yes the MX record points to my network, and port 25 is pointing the Exchange box. I don't think it's the network settings because I have other email domains handled by the Exchange box that have been working fine for some time now. This is just a new email domain that I added and made the primary email address.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ahh it was the MX record priorities that had to be rearranged. Details, details.. Thanks!
We figured out it was IIS registering incorrectly.
Open a command Prompt
Navigate to the directory of .net 1.1 (should be something like c:\windows\microsoft.net\f
Run aspnet_regiis.exe i
Restart the Microsoft Exchange System Attendant.
that worked for us at least, I am not sure you are having the exact same problem, but its a place to start.