Re: Can not email to the same domain?

I can't help with any POP3 connector. If you're using one supplied with
SBS, then I suggest you pose your question to an SBS forum. If it's a
third-party tool, then you might use a forum dealing with the tool.

POP3 is a single mailbox client mail retrieval protocol, not a mail
transport protocol. Any attempt to use it as a mail transport protocol is a
great big kludge. Exchange is designed to connect to the Internet using
SMTP.

http://www.swinc.com/resource/exch_smtp_diatribe.htm
http://www.swinc.com/resource/exch_dq.htm

http://www.swinc.com/resource/exch_smtp.htm


--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"matt808" <matt808@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:07391D00-E395-4A0A-B44B-51624D534232@xxxxxxxxxxxxxxxx
Ed, I left it this time for a couple of hours and it has solved the NDR
and
the people receive the email no problems. But i have created a new problem
becuase these user account now do not collect the email from my ISP email
server.

The POP3 connector is correctly configured i can track the emails onto the
email server but when i force a collection from the Exchange server
nothing
happens. Is there anything i have done incorrectly? any help would be
gratefully recieved.

Matt

"Ed Crowley [MVP]" wrote:

How long did you wait after unchecking for the .com domain? It does take
some time for these settings to propagate and for routing to recalculate.

Confirm that your problem is sending mail outside Exchange for a domain
named the same as Exchange uses, right?
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"matt808" <matt808@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3BE2344D-EE25-428A-98E9-21764B26623B@xxxxxxxxxxxxxxxx
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








.

Loading