• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 440
  • Last Modified:

SBS 2003: Exchange and bounces to a specific domain...

Hi All,
This will be wierd.  Using SBS 2003 Standard.   I recently discovered that a value for an internet domain ("domain.com") was present on the SBS box at the client's location.  The client does not use an external domain name.  The 2 or 3 users requiring external email do so via POP3 connectors.  

I found the issue when users trying to send to legitimate email addresses @domain.com were getting bounces with something like:

  ... 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.
  <domain.com #5.1.1>

I ran the CEICW and "domain.com" was present in the box on the 8th page of the wizard (named "E-mail Domain Name").  I blanked that out and continued the CEICW with no issues.

I tried sending to the same legit email address @domain.com and it bounced in the same way again.

Re-ran CEICW and found that 'domain.com' was still there!  Blanked it and finished again.  Message still bounced the same way.

Re-ran CEICW one more time and found 'domain.com' present.  Decied to change it to see if the change would persist.  I changed it to 'blah.blah.blah.blah'  (literally).  Subsequent emails to person@domain.com now began to bounce with the following:

...  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.
  <blah.blah.blah.blah #5.1.1>

I ran the CEICW one more time and blanked the 'blah.blah.blah.blah' thing.  Continued to finish.  Re-ran the CEICW to verify settings persisted, and sure enough, page 8 was blank as hoped ('blah..." had been removed.).  

Sent email to person@domain.com and got the same bounce:

...  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.
  <blah.blah.blah.blah #5.1.1>

Restarted the server and the bounce still happens.  

QUESTIONS:
Where is the value of blah.blah.blah.blah coming from?  
What can I do to re-enable the ability to send to this "domain.com"

I told you it was wierd.  Any help is appreciated.

Thansks,
Terry
0
colepc
Asked:
colepc
  • 3
  • 2
1 Solution
 
mikeleebrlaCommented:
that error comes the server at the other end (ie the email server at domain.com where domain.com is the domain you are trying to send TO)  It means just what it says "The e-mail account does not exist at the organization this message was sent to."  IE you are connected to their email server fine, but this email address doesn't exist.  This is on their end and not yours so the only thing you can do is contact them and see why this email address isn't active anymore.
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Actually, the error could be caused by a number of things... if you want to turn on tracing, that would help you track it down.  Here is a complete overview of NDR's (Non-delivery Reports): http://computerperformance.co.uk/exchange2003/exchange2003_NDR.htm

The question would be... is this the ONLY address that is bouncing?  The test would be that if person@domain.com is bouncing, but person2@domain.com isn't, then it's a mailbox issue on domain.com's side.  Also if person@domain.com is bouncing but somebody@anotherdomain.com isn't then perhaps it's actually the entire server at domain.com.


If what you are saying in your question is that your INTERNAL DOMAIN NAME is the SAME as the EXTERNAL DOMAIN NAME you are attempting to send mail to?  And is this the same server you asked this question for: http:Q_21407784.html ?

If so, you did not want to REMOVE the .local email addresses from your users because that is how mail is delivered internally.  What you wanted to do, most likely, is to ADD the .com address and then make that address the DEFAULT.

Here is the scoop on that:  http://computerperformance.co.uk/exchange2003/exchange2003_recipient_policy.htm

Jeff
TechSoEasy

0
 
colepcAuthor Commented:
Hi Jeff.  Yep same server ("http:Q_21407784.html").  

The only recipients that exhibit this behavior are any 'account' @domain.com.  The bounce is immediate as well.  IE: it doesn't leave the DC.  I make that statement based on observation of how quickly the NDR is rendered and the Message Tracking information for the outbound msg and corresponding, subsquent NDR.

The other killer on this is the presence of the 'blah.blah.blah.blah' text (again, this is literally in the message, not pseudo-text).  Prior to the 'blah...' text, the text "domain.com" was present.  The only place this text ('domain.com') existed in this server was in the E-Mail Domain Name of the CEICW  (represented there anyway...not sure where this value actually exists).  When I changed 'domain.com' to 'blah...' the NDR text changed accordingly.    Sending an email to person1@domain.com or person2@domain.com would not produce a response with the 'blah...' text, therefore, I conclude that it must be in the SBS and the entire transaction (send, then, NDR) is local to the SBS box.

I thought (and haven't ruled out) that it might be a DNS issue, but can't find any reference for the text 'blah..' anywhere.  

This may or may not be significant.   The few AD users that need outside email have that email account (for their POP3 connector involvement) with the domain "@domain.com".  On these users' account properties', in the email tab, the SMTP entry 'user@domain.com' is set as the Primary account (as opposed to user@domain.local for everyone else).

?
0
Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

 
colepcAuthor Commented:
Email to other domains are delivered without issue.
0
 
colepcAuthor Commented:
Just thought of this, hopefully for clarification of my hunch of why this is happening (but still don't know how to fix!!):  

The SBS box (for lack of the correct label, in this case) thinks that it is responsible for mail for users @domain.com.  I believe this is a result of having domain.com as the "Email Domain Name" set within the CEICW at one point.  Lets say person1@domain.local exists, but person2@domain.local does not exist.  Email sent to person2@domain.com would fail and result in an NDR because the server 'knows' no such user exists.  Domain.com is never contacted in that scenario.

Now, I change the CEICW "Email Domain Name" from domain.com to blah.blah.blah.blah.  Send an email to person2@domain.com and the NDR returns with the text from above (as in:  ...  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.
  <blah.blah.blah.blah #5.1.1> ").   Where in the SBS box would domain.com be being related to 'blah.blah.blah.blah'?

0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
I would take a look at your latest CEICW entry by going to C:\Program Files\Microsoft Windows Small Business Server\Networking\ICW\ and looking at the latest log file which is titled IcwdetailsX.htm (X being a sequential number based on how many times you've run the wizard).

That will tell you what settings are in place.

But honestly... you need to put the .local BACK as the primary account in the SMTP entry for your users.  That is not the correct way to accomplish what you are doing.  If they are using POP3 that needs to be configured via the POP3 connector on the server or by adding an ADDITIONAL email account to Outlook.  I would suggest using the server because then the emails can be scanned for viruses better, but that would be up to you.

Jeff
TechSoEasy
0

Featured Post

Fill in the form and get your FREE NFR key NOW!

Veeam is happy to provide a FREE NFR server license to certified engineers, trainers, and bloggers.  It allows for the non‑production use of Veeam Agent for Microsoft Windows. This license is valid for five workstations and two servers.

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