Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 300
  • Last Modified:

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

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
Edgerock
Asked:
Edgerock
  • 3
  • 3
1 Solution
 
SembeeCommented:
Do the senders get NDRs?
What does message tracking show? Does it show the message coming in?

Simon.
0
 
EdgerockAuthor Commented:
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
 
SembeeCommented:
Error? I see no error in your posting above.

Simon.
0
What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

 
EdgerockAuthor Commented:
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
 
SembeeCommented:
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
 
EdgerockAuthor Commented:
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

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now