Re: Can't send or receive e-mail to POP3 users on same domain--HELP!
- From: Steve <webmasvc@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 20 Aug 2005 07:32:52 GMT
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.
.
- Follow-Ups:
- Re: Can't send or receive e-mail to POP3 users on same domain--HELP!
- From: "Nathan Liu [MSFT]"
- Re: Can't send or receive e-mail to POP3 users on same domain--HELP!
- References:
- Can't send or receive e-mail to POP3 users on same domain--HELP!
- From: Steve
- RE: Can't send or receive e-mail to POP3 users on same domain--HELP!
- From: "Nathan Liu [MSFT]"
- Can't send or receive e-mail to POP3 users on same domain--HELP!
- Prev by Date: Re: To Exchange or not to Exchange
- Next by Date: Re: Remote Client VPN access.
- Previous by thread: RE: Can't send or receive e-mail to POP3 users on same domain--HELP!
- Next by thread: Re: Can't send or receive e-mail to POP3 users on same domain--HELP!
- Index(es):
Relevant Pages
|