Re: Can not email to the same domain?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Ed, ok i read the articles on authoritative domains and i can verify my
recipient policy is responsible. I have been looking in my recipient policy
also and found there are 2 smtp settings @mycompany.com and @mycompany.local
both of these have authoritative responsibility. is this correct?

smtp @mycompany.com is set as primary. if i uncheck the authoritive
responsibilty and keep it as primary i still get the NDR 5.1.1. if i set the
primary to @mycompany.local everything works fine except that the reply to
email is incorrect. what is different in these two settings?

I have read article 823158, is it because the unresolved recipients are not
forwarded to the correct place? the current settings for the default smtp
virtual server properties are:

IP Address = (all unassigned) is this correct?

I would be grateful for any assistance

"Ed Crowley [MVP]" wrote:

Look at the recipient policy and verify that your Exchange server is not
responsible all mail for the domain.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"matt808" <matt808@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8F36451B-5607-4630-8F79-F673861BCF52@xxxxxxxxxxxxxxxx
I have just installed sbs2k3 and am using the integrated exchange server.
We
have a small company so am in the process of changing from a peer to peer
system and discovering a large learning curve.

i have set up the sbs and converted 4 of the 6 users onto the domain. we
use
a ISP for our email server and have successfully configured the pop3 and
smpt
connection to the ISP so that external email can be sent and received.

the problem has come with the two other employees who are not currently on
the office domain. when sending an email to name@xxxxxxxxxx from a client
machine I receive an instant non delivery report:

" the following recipient(s) could not be reached
name@xxxxxxxxxx <date>
The email account does not exists at the organisation this message was
sent
to. Check email address or contact recipient directly.
<domain.com #5.1.1>"

I have tested the accounts using external and the accounts exists and work
so I have narrowed the problem to the exchange server or sbs setup. I
would
grateful if someone could help me with this problem.

Thanks Matt



.

Relevant Pages

  • Re: Updating email addresses via recipient policy
    ... Thanks very much Russ... ... I had searched the KB for articles but never saw ... Creating a recipient policy will not overwrite existing addresses you ... >> email addresses there and apply that to all the accounts, ...
    (microsoft.public.exchange.admin)
  • RE: Sending to an external mailbox on our domain
    ... right click the default recipient policy and choose ... Here is the tricky part if you only have one smtp address setup you will ... A dialog box will open and you should see a check box labeled This Exchange ... in your senario you don't want the server to take responsibility for all ...
    (microsoft.public.windows.server.sbs)
  • Re: State of the Wikipedia
    ... All those volunteers who are currently deleting valid entries. ... Of the 200-odd articles on my ... for deletion, twice in fact: the one on James Nicoll, which I did not ... responsibility to make a value judgment about the worth of every ...
    (rec.arts.sf.written)
  • Re: Multiple domains with exchange
    ... Omer Maydan ... > simple as adding a recipient policy specifying the new domain name, ... > To clarify a bit more, I want one exchange server to receive email for ... According to articles I've found online, to add xyz.com, I ...
    (microsoft.public.exchange.admin)
  • Re: SP2 is a problem
    ... but never imagined the articles ... But most computer users will not. ... Microsoft knows that and should service their customers ... >It is, however, the customer's responsibility to read ...
    (microsoft.public.windowsxp.perform_maintain)