Improve company productivity with a Business Account.Sign Up

x
?
Solved

User with multiple email addresses not receiving mail on one of them

Posted on 2007-11-16
6
Medium Priority
?
305 Views
Last Modified: 2010-04-19
We have SBS 2003.  We have several domains registered and each user, when they are created, gets an email address on each one of these domains (listed in the "email address" tab in the active directory properties box.)  For every user, the default address works fine (user@domain1.com)

However, some users cannot receive mail at one of the other domains.  For example, user@domain2.com.  For other users, though, they can receive mail sent to every one of the domains, so I know the domain isn't the problem-- it must be something with the individual user account / settings.

ANy thoughts?
0
Comment
Question by:Edgerock
  • 3
  • 3
6 Comments
 
LVL 104

Expert Comment

by:Sembee
ID: 20301463
Do the senders get NDRs?
What does message tracking show? Does it show the message coming in?

Simon.
0
 

Author Comment

by:Edgerock
ID: 20301991
Sembee, when sent internally I can see it in message tracker because it is sent successfully. When it is sent by an account outside our system it doesn't get that far.  It gets bounced back to the sender with the error I posted.
0
 
LVL 104

Expert Comment

by:Sembee
ID: 20302140
Error? I see no error in your posting above.

Simon.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 

Author Comment

by:Edgerock
ID: 20306539
Sembee, I apologize for posting the question twice. I thought I had closed the window before postig it, thus the secod posting of the same question. I can delte the other if that's best.

I had posted the error message in that second posting as well.  Here it is:

The following is the failed message:

Reporting-MTA: dns; n034.sc1.he.tucows.com
Received-from-MTA: dns; sc1-out06.emaildefenseservice.com (xx.xx.xx.xx)
Arrival-Date: Fri, 16 Nov 2007 20:33:44 +0000
Final-Recipient: rfc822; user2@domain3.com
Action: Failed
Status: 5.1.1 (bad destination mailbox address)
Remote-MTA: dns; mail.domain3.com
Diagnostic-Code: smtp; 550 5.1.1 <user2@domain3.com>... User unknown
0
 
LVL 104

Accepted Solution

by:
Sembee earned 2000 total points
ID: 20308289
The error code means what it says. The server that received the email message doesn't recognise the email address. What it does not mean is that the message was delivered to the correct server. If you have SMTP logging enabled you should see the connection attempt in the logs.
Do you have anything between Exchange and the internet that does recipient filtering? Perhaps something that needs to be updated?
There is always a chance that the email address hasn't been updated correctly in the domain - if you have a user where you know it doesn't work try removing the email address and adding it back in again.

Simon.
0
 

Author Comment

by:Edgerock
ID: 20328710
Simon, I thought about what you wrote regarding the message not going to the correct server and took that course in trying to solve the issue. When pinging all the domains, they resolved to the same IP address-- all of them except the one that wasn't working. That domain was actually pointed at a different server at another facility (our sister company) and then forwarded here. I am not sure why it is set up this way, as it was configured by my predecessor.  So adding the mailbox to my server was needed, but it had to be configured on their end as well (thus the unknown mailbox error message.)
Thanks for pointiong me in the right direction.
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

In an Exchange Crossforest migration, the distribution groups can be a very complex operation that would cause loss of time, lots of issues and continued headaches if not solved in a timely manner. I had to do a similar project so I created a sc…
In migration, Powershell can be a very crucial tool to achieve success and finalize projects within deadline or even fix issues. X500 or Legacy Exchange DN Attribute can cause lots of issue during the migration
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
how to add IIS SMTP to handle application/Scanner relays into office 365.

601 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question