Re: Can't send or receive e-mail to POP3 users on same domain--HELP!

Tech-Archive recommends: Fix windows errors by optimizing your registry



Hi Steve,

Thank you for your kind update.

1) Since your ISP does not provide his Smarthost (your with the IP address
of their e-mail server). All they give you is "mail.nrsweb.biz" (nrsweb.biz
is my domain name). This is the same for POP3 and SMTP, when configuring
Outlook. Let's still switch to use DNS to route outbound emails.

2) Please try to Use the following path to locate the queues: Open the
Exchange System Manager -> Servers -> DomainName -> Queues.

3) As you mentioned, the "Microsoft Exchange MTA Stacks" service is not
running, this service Provides Microsoft Exchange X.400 services. Exchange
X.400 services are used for connecting to Exchange 5.5 servers, and by
other connectors (custom gateways). If this service is stopped, Exchange
X.400 services are unavailable. If your network environment does not have
any Exchange 5.5 Servers, the service can be disabled.

4) Please perform the following steps to check if the issue can be
reproduced:

Configure the Default Policy in the Exchange recipient policy to use the
local e-mail domain as the primary address, and then add an additional
recipient policy to apply the POP3 e-mail domain to the local user
accounts. This way, the e-mail domain for the local users will match the
e-mail domain that the POP3 mail server is hosting, but Exchange will not
be the responsible mail server for this e-mail domain.

Be aware that the user accounts must be configured to be updated by
recipient policies. This option is available under the properties for each
user on the Email-Addresses tab.

To configure the recipient policies in Exchange, follow these steps:
1. Click Start, point to Programs or to All Programs, point to Microsoft
Exchange, and then click System Manager.
2. Expand Recipients, and then click Recipient Policies in the left pane.
In the right pane, the Default Policy is listed.
3. Double-click Default Policy, and then click the E-Mail Addresses tab.
4. By default, an SMTP e-mail address that matches your internal domain
name appears in the list of addresses. For example, if your internal domain
name is mycompany.local, the address @mycompany.local will appear in the
list. If the internal domain address is not listed, follow these steps to
add it:
a. Click New.
b. Click to select SMTP Address, and then click OK.
c. In the Address box, type the internal domain address, and then click
OK. For example, type @mycompany.local.

5. Click to select the internal domain address, and then click Set as
Primary.
6. Click to select the POP3 domain address (i.e. @nrsweb.biz), and then
click Edit.
7. Clear the box that says This Exchange Organization is responsible for
all mail delivery to this address, and then click OK.
8. Click OK to apply the changes.
9. Click Yes or OK two times to update all corresponding recipient e-mail
addresses.
10. Right-click Recipient Policies in the left pane, point to New, and then
click Recipient Policy.

Note If you have Exchange Server 2000 Service Pack 1 (SP1) or later, a
dialog box appears that prompts you to select the type of recipient policy
that you want to create. In this case, click to select the E-Mail Addresses
check box, and then click OK.
11. Type a name for the recipient policy, and then click Modify.
12. In the Find Exchange Recipients dialog box, click to select Users with
Exchange mailbox, and clear all the other check boxes.
13. Click OK, and then click OK on the warning message that you receive.
14. Click the E-Mail Addresses tab.
15. Click to select the POP3 domain address (i.e. @nrsweb.biz), and then
click Set as Primary.
16. Click OK to apply the changes.
17. Click Yes or OK two times to update all corresponding recipient e-mail
addresses.

Note Every time that you run the Internet Connection Wizard or the
Configure E-mail and Internet Connection Wizard and set it to modify the
Exchange settings, the wizard will set the e-mail domain address that you
enter in the wizard as the primary address on each recipient policy. After
the wizard is completed, you must repeat the steps that are mentioned in
this article to modify the recipient policy.

I appreciate your time and cooperation. If anything is unclear, please feel
free to let me know. I am looking forward to hearing from you.

Best regards,

Nathan Liu (MSFT)
Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
>From: Steve <webmasvc@xxxxxxxxxxxxxxxxxxxxxx>
>Newsgroups: microsoft.public.windows.server.sbs
>Subject: Re: Can't send or receive e-mail to POP3 users on same
domain--HELP!
>Message-ID: <jnfdg1dc2fchrso5q7gcsobq9tafesm2e2@xxxxxxx>
>References: <auu7g19kca0pg58h1o066vif7l6s4nv379@xxxxxxx>
<vBxU73HpFHA.3672@xxxxxxxxxxxxxxxxxxxxx>
>X-Newsreader: Forte Agent 2.0/32.652
>MIME-Version: 1.0
>Content-Type: text/plain; charset=ISO-8859-1
>Content-Transfer-Encoding: 8bit
>Lines: 311
>Date: Sat, 20 Aug 2005 07:32:52 GMT
>NNTP-Posting-Host: 68.200.67.144
>X-Complaints-To: abuse@xxxxxx
>X-Trace: tornado.tampabay.rr.com 1124523172 68.200.67.144 (Sat, 20 Aug
2005 03:32:52 EDT)
>NNTP-Posting-Date: Sat, 20 Aug 2005 03:32:52 EDT
>Organization: Road Runner High Speed Online http://www.rr.com
>Path:
TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-onli
ne.de!border2.nntp.dca.giganews.com!nntp.giganews.com!newscon06.news.prodigy
com!prodigy.net!news-east.rr.com!news-feed-01.rdc-kc.rr.com!news.rr.com!cyc
lone2.kc.rr.com!news2.kc.rr.com!news-post.tampabay.rr.com!tornado.tampabay.r
r.com.POSTED!53ab2750!not-for-mail
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:146178
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>Nathan,
>Thanks for replying. My answers to your comments and questions are
>below them, offset by asterisks.
>
>Steve
>
>******************
>Hello Steve,
>
>Thank you for posting in the SBS newsgroup.
>
>According to your description, I understand that you cannot
>send/receive email to POP3 users on the same email domain. If I have
>misunderstood your concern, please don?t hesitate to let me know. You
>are correct.
>
>***Technically, they are users who are all using the same Exchange
>server, since they're in the same building. I'll explain in more
>detail below.***
>
>To narrow down this issue, please answer and perform the below
>questions and steps:
>
>1. As you mentioned, "It can't seem to send messages to ANY POP3
>users on its own domain. What's worse, I no longer get notifications
>bounced back to the sender--they think the message has gone, but it
>hasn't, and the recipient doesn't even know there was a message", can
>I assume you send messages to other POP3 users, the recipients cannot
>receive the messages and you also don't receive any Non-Delivery
>Report (NDR)?
>
>***I have no problems sending to other POP3 users on any other domain.
>Those messages are sent and received properly. And if I use my home
>e-mail address (which is on a different domain, of course), we all can
>send and receive without problems. It's only messages that stay within
>the domain--and specifically, ones that go through the Exchange e-mail
>gateway. We have four employees who do not work in the building, and
>thus do not use the Exchange server (or log in to the network) at all.
>I am one of those employees. If I send a message from me@xxxxxxxxxxx
>to jim@xxxxxxxxxxx (he also does not work in the building), he gets it
>without any problems, and he can initiate a message to me without
>problems. Only the people who are inside the building and using the
>Exchange e-mail gateway are having this problem.***
>
>2. As you mentioned, can I assume you have 5 individual user POP3
>mailboxes on ISP? After you have installed the SBS 2003 Server, did
>you add the all individual user POP3 mailboxes into the POP3 Connector
>on the SBS 2003 Server?
>
>***I actually have 7 individual POP3 mailboxes on the ISP. Three of
>these people are in the building and using SBS/Exchange server. These
>7 people do get their mail from that ISP with no problems--as long as
>it comes from outside the building (as I explained above). For the
>three "internal" people, I had the POP3 mailboxes in the POP3
>Connector, but that was generating hundreds of errors daily when it
>went to check them (and they still couldn't get mail from each other),
>so I removed them all. Other users in this newsgroup also suggested
>not using the POP3 Connector. I thought it was necessary, but if not,
>please let me know.***
>
>3. Did you setup the all users' Exchange user account into the
>Outlook? As you mentioned, there are certain users don't logon the SBS
>2003 Domain, we strongly recommend all users logon the SBS Domain, so
>the Outlook can better cooperate with Exchange Server.
>
>***Since four of us don't actually work in the building we don't log
>on to the SBS Domain. We get Internet access at home (or wherever).
>I'm not sure what you mean by "setup the all users' Exchange user
>account into the Outlook". We're all using Outlook and checking our
>own accounts. Other than that, I'm not sure what you mean.***
>
>4. Since the Error 1015 for the POP3 Connector still occurs every 15
>minutes, and the Error 1015 means "Microsoft Connector for POP3
>Mailboxes can not verify the Internet connection but will still
>attempt to download messages". It seems the POP3 Connector cannot
>download any mails, let's perform the below steps to check it:
>
>This is most likely due to blocked network traffic, authentication
>problems, or ISP issues. Some steps to use here would include:
>
>1) Go to a command prompt on the server. Telnet to port 110 of the
>server that you are having problems with. If you do not get a
>response, then the issue is likely network related. To try to further
>identify the source of the problem, see if you can ping the IP address
>of the server that you want to connect to. If you can?t, then that
>server may be down, or you may have network problems. Try to ping a
>different external server to see if your network connection is ok. If
>you can ping other internet servers, try to telnet to port 110 on a
>different known POP3 mail server. If you can at least get a response,
>then the problem is most likely at the ISPs end.
>
>***I can get e-mail to all accounts, just not from specific accounts,
>so I don't think this applies.***
>
>2) If the problem is not network related, the next most likely
>problem is authentication. Check the event viewer Application log for
>event viewer messages, as long as diagnostic logging is set to at
>least minimal, you should see errors with authentication issues. This
>is most likely a username or password problem. It could also occur if
>the POP3 ISP requires SPA for authentication. This can be enabled for
>the mailbox in the POP3 Connector properties.
>
>***There are no errors in the Application event log (since I turned
>off the POP3 Connector) other than this one for the backup: "Event
>Type: Error
>Event Source: ESENT
>Event Category: Logging/Recovery
>Event ID: 215
>Date: 8/18/2005
>Time: 11:01:29 PM
>User: N/A
>Computer: NRS-SERVER
>Description:
>certsrv.exe (1504) The backup has been stopped because it was halted
>by the client or the connection with the client failed."
>
>I get this one every night, but the backup seems to run anyway, and
>since it's a USB device that's always connected and always on, I don't
>know why I get this.***
>
>5. Please refer to the below information to enable Diagnostic
>Logging on POP3 Connector:
>
>***Since the POP3 Connector is disabled, none of this applies. While
>checking the System manager settings, though, I noticed this:
>"Exchange System Manager failed to retrieve queues for the X400
>protocol (error code = 0x800706D9). Check the event log and verify
>that the required services are running." We do nothing specifically
>with X400, and there are no entries in the Application event log. And
>again, if you think I should be using the POP3 connector, I can enable
>it, fill it with all the e-mail addresses again...but I'd only do this
>for troubleshooting, since it fills the Event log quickly with
>hundreds of errors.***
>
>1) Click Start, point to Programs, point to Microsoft Exchange,
>and then click System Manager.
>2) In the left pane, expand the Connectors node.
>3) Right-click "Connector for POP3 Mailboxes", and then click
>Properties.
>4) In the "Connector for POP3 Mailboxes Properties" dialog box,
>click Diagnostic Logging.
>5) Verify that the "Enable event logging on the services" check
>box is selected.
>6) Under the Services box, click Delivery Service, and under
>Logging Level click Maximum.
>7) Click OK to apply changes.
>8) Close the System Manager console.
>9) Click Start, point to Programs, point to Administrative
>Tools, and then click Services.
>10) In the left pane, right-click "Microsoft Connector for
>POP3", and then click Restart. After the service restarts, close the
>Services Management console.
>
>After the problem occurs again, the events of POP3 connector will be
>created in Application event log. Please check the Application event
>log whether there are any error messages noted on this issue, then
>paste the full context in your reply.
>
>6. To troubleshoot the problem of sending outbound email, please
>refer to the below KB article to enable the Message Tracking logs,
>then let a user send a testing outbound email, and open the Exchange
>System Manager (ESM), go to Tools -> Message Tracking Center, type the
>appropriate information in the Sender, Server, Recipients box and
>click Find Now, check the testing e-mail's delivery status, you can do
>a screen capture and attach it in your reply.
>
>***I can try this, but since the problems only occur when sending to
>other users on the same domain and within the same building (i.e.,
>using the same Exchange server), I'm not sure this applies. I'll look
>into it, though.***
>
>823864 Improved Message Tracking Features in Exchange Server 2003
>http://support.microsoft.com/?id=823864
>
>7. Please refer to the below steps to enable SMTP logging:
>
>1) Open the properties page of the Default SMTP Virtual Server
>in Exchange System Manager.
>2) On the General tab, check the "Enable logging" box.
>3) Click Properties, click the Extended Properties tab and
>check all the boxes on the list.
>4) Click OK twice.
>5) Stop and restart the SMTP virtual server.
>6) Reproduce the issue.
>7) Stop the SMTP virtual server.
>8) Go to the C:\WINDOWS\system32\LogFiles\SMTPSVC1 folder and
>check the latest two (if there are many) log files.
>
>To get additional information, you may refer to the below KB article:
>
>821910 How to troubleshoot for Exchange Server 2003 transport issues
>http://support.microsoft.com/?id=821910
>
>885685 How to troubleshoot the POP3 Connector in Windows Small
>Business Server 2003
>http://support.microsoft.com/?id=885685
>
>300681 E-mail to external recipients with the same e-mail domain
>causes NDR messages when using the Connector for POP3 Mailboxes
>http://support.microsoft.com/?id=300681
>
>***I tried the first suggestion listed on this page, but it didn't
>help.***
>
>I am appreciated your time and cooperation. If anything is unclear,
>please feel free to let me know. I am looking forward to hearing from
>you.
>
>Best regards,
>
>Nathan Liu (MSFT)
>Microsoft CSS Online Newsgroup Support
>
>Get Secure! - www.microsoft.com/security
>======================================================
>This newsgroup only focuses on SBS technical issues. If you have
>issues regarding other Microsoft products, you'd better post in the
>corresponding newsgroups so that they can be resolved in an efficient
>and timely manner. You can locate the newsgroup here:
>http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>
>When opening a new thread via the web interface, we recommend you
>check the "Notify me of replies" box to receive e-mail notifications
>when there are any updates in your thread. When responding to posts
>via your newsreader, please "Reply to Group" so that others may learn
>and benefit from your issue.
>
>Microsoft engineers can only focus on one issue per thread. Although
>we provide other information for your reference, we recommend you post
>different incidents in different threads to keep the thread clean. In
>doing so, it will ensure your issues are resolved in a timely manner.
>
>For urgent issues, you may want to contact Microsoft CSS directly.
>Please check http://support.microsoft.com for regional support phone
>numbers.
>
>Any input or comments in this thread are highly appreciated.
>======================================================
>This posting is provided "AS IS" with no warranties, and confers no
>rights.
>******************
>
>If you are unable to view the reply to your thread, please send me an
>email with a description of the problem and what newsreader you are
>using.
>
>Have a nice day.
>
>Sincerely,
>
>Nathan Liu
>Microsoft Online Partner Support
>
>Get Secure! - www.microsoft.com/security
>
>=====================================================
>When responding to posts, please "Reply to Group" via your newsreader
>so that others may learn and benefit from your issue.
>=====================================================
>
>This posting is provided "AS IS" with no warranties, and confers no
>rights.
>
>More Information
>===========
>Please be informed that we have released The Microsoft Baseline
>Security Analyzer (MBSA) 1.2 to the public; the download link is
>http://www.microsoft.com/technet/treeview/default.asp?url=/technet/security
/tools/mbsahome.asp.
>
>The Microsoft? Baseline Security Analyzer (MBSA) is a tool that allows
>users to scan one or more Windows?-based computers for common security
>misconfigurations.
>
>Microsoft has published information, that details the tool and
>instructs customers how to use the tool:
>
> - Microsoft? Baseline Security Analyzer (MBSA) Home Page
>
> - Microsoft Baseline Security Analyzer (MBSA) Version 1.2 Is
>Available (320454)
>
> - Microsoft Baseline Security Analyzer (MBSA) Version 1.2 Q&A
>
>MBSA 1.2 now includes new support for the following Products:
>
> - Exchange Server 2003
>
> - Microsoft Office (Note: MBSA can only be used for to perform a
>local scans for Microsoft Office. Please see the above referenced
>documents for more information).
>
> - Microsoft Data Access Components (MDAC) 2.5, 2.6, 2.7, and 2.8
>
> - Microsoft Java Virtual Machine
>
> - MSXML 2.5, 2.6, 3.0, and 4.0
>
> - BizTalk Server 2000, 2002, and 2004
>
> - Commerce Server 2000 and 2002
>
> - Content Management Server (CMS) 2001 and 2002
>
> - SNA Server 4.0, Host Integration Server (HIS) 2000 and 2004
>
>If you have any questions regarding the tool or its implementation
>after reading the above resources, you should contact Product Support
>Services in the United States at 1-866-PCSafety (1-866-727-2338).
>International customers should contact their local subsidiary.
>
>
>

.



Relevant Pages

  • RE: Cant send or receive e-mail to POP3 users on same domain--HELP!
    ... Run the CEICW and go through the Internet and firewall option. ... If you choose to forward emails to the ISP's email server (smart ... Connector for POP3 Mailboxes' option, ... The Mailbox type is User Mailbox, and select the appropriate Exchange ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange not receiving email from Internet
    ... Recieved email for that domain from internet. ... I understand that your exchange unable to ... permission to send to this recipient". ... The Exchange server Directory Access tab error may not related to ...
    (microsoft.public.windows.server.sbs)
  • Re: Cant send or receive e-mail to POP3 users on same domain--HELP!
    ... they are users who are all using the same Exchange ... "It can't seem to send messages to ANY POP3 ... thus do not use the Exchange server at all. ... you add the all individual user POP3 mailboxes into the POP3 Connector ...
    (microsoft.public.windows.server.sbs)
  • Sending email to mydomain.com
    ... They do not offer an smtp server, ... different from the user account names for the exchange ... I added one user account in the POP3 Mailbox Accounts ...
    (microsoft.public.windows.server.sbs)
  • RE: Exchange "Light" setup opinions wanted...
    ... If you use POP3 connector, it may download e-mails from ISP every 15 mins. ... Microsoft CSS Online Newsgroup Support ... Monitoring the Exchange server. ...
    (microsoft.public.windows.server.sbs)