Exchange 2003 New User and User Mailbox, can send but not receive external, can receive internal, all other mailboxes work properly

Matterofacts
Matterofacts used Ask the Experts™
on
1. Exchange 2003 New User and New User Mailbox, can send to anyone but can not receive from external senders, can receive internal, all other mailboxes work properly except this new one.  Since I did these first two in AD Users and Computers, I deleted the second one also, and then used the SBS Server Management Console to create a new user.  Same symptom with new user created in SBS Server Console.  All of the other old users have no issues.  The bounce back email I get is always the same "Remote host said: 550 5.7.1 No mailbox found [RCPT_TO]"

2. I deleted the user and the mailbox and then created another user with another mailbox.  Same exact symptom, once I get this working, a secondary part of this 500 pointer is that I may want to re-attache the original mailbox that I deleted back to the new user.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
How long are you waiting between the time you create it and the time you try to send email from external?
Viral RathodConsultant

Commented:
Check this

1) Go to the New User Properties - E-mail Address Tab and Make sure you zzz.com E-mail Address is set as primary
Some domain have 2 policy set on the RUS like (first.last@123.com to first.last@zzz.com)

2) Do you have any filter settings is enabled ,You need to probably add the new user to the Filtering so that new user are able to receive the e-mail

Best way is to go to https://www.testexchangeconnectivity.com and check the Inbound SMTP Email Test and check for the errors
Do you relay the mails through ISP? for eg like postini and the mailbox is not configured to relay.
 
Should you be charging more for IT Services?

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Author

Commented:
Have waited long time in reply to 1st comment (more than a day)

on second comment - 1. where do I find the filtering that your referring to?
2. The Inbound SMTP Email test passes for other users but not the problem one - it returns mailbox the following
________________________________________________________________________
      Attempting to send test email message to mcc@goingandplank.com using MX mxin.name-services.com.
       Delivery of the test message failed.
       
      Additional Details
       Server returned status code 550 - Mailbox unavailable. The server response was: 5.7.1 No mailbox found
Exception details:
Message: Mailbox unavailable. The server response was: 5.7.1 No mailbox found
Type: System.Net.Mail.SmtpFailedRecipientException
Stack trace:
at System.Net.Mail.SmtpTransport.SendMail(MailAddress sender, MailAddressCollection recipients, String deliveryNotify, SmtpFailedRecipientException& exception)
at System.Net.Mail.SmtpClient.Send(MailMessage message)
at Microsoft.Exchange.Tools.ExRca.Tests.SmtpMessageTest.PerformTestReally()

________________________________________________________________________

This is interesting, inside Server Manager if I open the user properties, error box says "ID no: 80045005 Microsoft Active Directory - Exchange Extension"  and then clicking ok opens the properties and none of the exchange tabs show for this user - on other users don't get this error and

Viral RathodConsultant
Commented:
Hi,
Filtering is like postini or Spam Filtering Providers like (www.spamstopshere.com)

As per your above error message it clearly states that the MX Provider Server is Blocking your new user
The MX Hosting server does not have any entry for your new user and the same is blocking the mailbox to incraese the Security and Reduced the Spam mail attaks
   
First check who is handling you MX Record (Hosting) ,for this try the following url to find who is your MX provider
http://www.mxtoolbox.com/
http://www.whois.net/

Enter your doamin name and you will get who is youe MX hosting server and Inform him to add the above users in their Database

Actually what is happnning is when you send the e-mail it will first go the MX provider Server and in case if they dont have any entry for your new user it will simply rejected

Hope this helps.

Author

Commented:
It wouldn't be an issue with the MX record if all of the other email addresses on this server are working, right?  And isn't the MX record for the entire domain, there is not individual records for each user as far as the MX is concerned.

Author

Commented:
Also, we are not using any third party filters.  It has to be an issue on this SBS 2003 Server itself.

Author

Commented:
Also, the Exchange System Manager shows that there are items in the mailbox, is there a way to view them?
Viral RathodConsultant
Commented:
There is no issues with MX Record ,The MX host server is blocking your New user since they dont have entery for this new user
--As per you comments new user are able to send and receive mails then there is no issues with SBS 2003 Server itself

Just the do one thing ,
Just telnet to your domain (Eg zzz.com) from outside ,Send the testmail to new user using Telnet commands and check for the error

Sending an e-mail via Telnet
http://www.activexperts.com/activemail/telnet/

Author

Commented:
viralrathod, I think you misunderstood, all of the emails work except this new one.

Author

Commented:
I am not sure how all of the emails have been getting through the verizon firewall because there isn't an existing port forward for 25. But all of the mail gets delivered except this one.

When I opened Port 25 in the firewall and Telnet on Port 25, then it delivered my test email to the problem users mailbox

Author

Commented:
A new person replaced an old person.  I initially tried renaming which worked for the AD user but not the mail box.  It still had the old user name on the mailbox, possibly an easy solution at this point would be rename the AD user to the new name, and then get instructions here to rename the mailbox, How is the mailbox renamed?

Viral RathodConsultant

Commented:
Hi
Nope, Rename the mailbox will not help
Can you please check the Rules on the verizon firewall
May be Verizon is blocking the Trafice for this new users

Verizon Guide
http://www2.verizon.net/micro/vissbusiness/pdf/VOL_UserGuide_firewall.pdf

Author

Commented:
I ended up being configured not only in our Exchange server where I was working but also on the Verizon interface webmail admin interface, the email had to be added there as well.  So the MX record response was some what correct since this MX record would have shown a Verizon server and not our Exchange server.

Viral RathodConsultant

Commented:
Correct Now you got it ,

Now new user are able to send and receive mails right ?

Let us know if you have any further queries.
Apparently with Exchange, you have to login to the mailbox at least once before it works either via Outlook or Outlook Web Access, when Microsoft was contacted on this issue they pointed this out.  Once I logged into the mailbox via OWA it functioned properly after that.

Author

Commented:
Resolved after contacting Microsoft Engineer

Author

Commented:
Resolved after contacting Microsoft Engineer

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial