RE: POP 3 Errors/Warnings
- From: v-terliu@xxxxxxxxxxxxxxxxxxxx (Terence Liu [MSFT])
- Date: Thu, 26 Oct 2006 10:37:06 GMT
Hello Customer,
Thank you for posting here.
From your post, I understand that you got Event Log Errors of 1019, 1023,1035 & 1052, 1053 about POP3 connector in SBS 2003 Server environment. If I
am off base, please feel free to let me know.
After analyzing, these Errors log not point to one problem: the main cause
of the 1019, 1023, 1025 issue is most possibly the router incompatibility
with the Windows Server, and issue of 1052 and 1053 is most possibly caused
by some emails are sent to your Global POP3 mail box via BCC.
Please understand that our partner newsgroup is an issue based service,
meaning we usually respond to one question/issue per post. This will lessen
the confusion for both of us, as well as ensure that our results are
accurate and not a result of a test for a different question. Therefore, I
will work with you on the first question in this post. Regarding the
additional question(s), please open a new post so that the dedicated MS
engineer can help you on it in a more efficient manner.
According to my knowledge, the 1019, 1023, 1035 events are mostly caused by
incompatibility between the router and the Windows Server, that is, the
Maximum Transmission Unit (MTU)'s difference on the Windows Server and
hardware router. This issue may appear on Linksys router BEFVP41/BEFSR41
and other similar ones.
Hence, I suggest performing the following steps to determine the MTU
setting:
On the SBS server:
1). To get the MTU Size maximum, you may need to have the following command
on one of internal client connected to SBS server directly.
ping <SBS_IP_address> -f -l <packet_size>
and on SBS server, please ping the POP3 mail server with following command
ping <POP3MailServer_IP_address> -f -l <packet_size>
Being:
<SBS_IP_address or POP3MailServer_IP_address > - the IP address from the
internal network.
<packet_size> - the packet size to test the maximum MTU packet size.
You can use some <packet_size> parameters to get the packet ideal size.
This can be identified by the ping results, for example, ping 192.168.18.8
-f -l 5000
If the ping result is like below:
Pinging [192.168.18.8] with 5000 bytes of data:
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Ping statistics for 192.168.18.8:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
You may need to decrease the <packet_size> until encounter a non fragmented
packet size the link can answer like below:
Pinging [192.168.18.8] with 1472 bytes of data:
Reply from 192.168.18.8: bytes=1472 time<1ms TTL=128
Reply from 192.168.18.8: bytes=1472 time<1ms TTL=128
Reply from 192.168.18.8: bytes=1472 time<1ms TTL=128
Reply from 192.168.18.8: bytes=1472 time<1ms TTL=128
Ping statistics for 192.168.18.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Or else, in this case, the maximum MTU Size is 1472. It is the by default
number for SBS 2k3 server.
If the router Maximum MTU size is smaller than the one on the SBS server,
you may need following steps:
Modifying the MTU Size:
1)Go to the key:
KEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfa
ces
2)Go the key corresponding to the NIC GUID
3) Create a Dword parameter 'MTU' with the value small than router size
4) Restart the client machine
References:
Diagnoses and Treatment of Black Hole Routers
http://support.microsoft.com/?id=159211
TCP/IP and NBT Configuration Parameters for Windows XP
http://support.microsoft.com/?id=314053
If the issue persists, collect some more information for further
investigation:
1. Confirm whether the issue appears on the particular mailbox only.
2. Dump attributes of the problematic user and a good one.
Both CSVDE and LDIFDE can dump user attributes, for your convenience, I
would like to list the following related information for your refer:
XADM: How to Perform a Dump of a Container or Object in Exchange 2000
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q255253
Note: This article is also applied for Exchange 2003.
How to use Csvde to import contacts and user objects into Active
http://support.microsoft.com/?id=327620
3. Check the application log with diagnostic logging enabled for pop3
connector.
To enable the logging:
a. Click Start, and then click Server Management.
b. Expand Advanced Management, and then click POP3 Connector Manager.
c. In the right pane, click Open POP3 Connector Manager.
d. Click the Troubleshooting tab, and then click Maximum in the Logging
level list.
e. In the Exchange mailbox list, click a mailbox where you want
undeliverable e-mail messages sent to, and then click OK.
f. Click Yes on the following message that appears:
Changes to the logging level do not take effect until the Microsoft
Connector for POP3 Mailboxes service is restarted. Restarting the service
temporarily interrupts the download of mail until the service starts again.
To restart the service now, click Yes. Otherwise, click No.
g. Click Open POP3 Connector Manager, and then click the Scheduling tab.
h. Click Retrieve Now, and then click OK on the following message that
appears:
The Microsoft Connector for POP3 Mailboxes will now download and deliver
e-mail. This may take a few moments.
i. Click OK.
j. In the left pane, under Advanced Management, expand Computer Management,
expand System Tools, expand Event Viewer, and then click Application.
k. View the events where POP3 Connector appears in the Source column to
determine whether the mail-flow process is completed successfully.
l. Save the application log as evt file and forward to me at:
v-terliu@xxxxxxxxxxxxx
If you have any questions or concerns related to this issue, please let me
know. I appreciate your time and look forward to hearing from you.
Best regards,
Terence 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.
--------------------
| Thread-Topic: POP 3 Errors/Warnings
| thread-index: Acb4Te8BUSFs+dqUT8SH6oK7IT1ZkQ==
| X-WBNR-Posting-Host: 216.153.227.51
| From: =?Utf-8?B?TEREMTU=?= <LDD15@xxxxxxxxxxxxxxxxxxxxxxxxx>
| Subject: POP 3 Errors/Warnings
| Date: Wed, 25 Oct 2006 08:55:03 -0700
| Lines: 26
| Message-ID: <5F5EE622-BF9C-4310-8EB1-A1AF60567DF7@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
| Newsgroups: microsoft.public.windows.server.sbs
| Path: TK2MSFTNGXA01.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:307881
| NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Please see the following:
|
| In news:2FB129FD-ADC7-4A39-825D-C8862742ABE9@xxxxxxxxxxxxx,
| LDD15 <LDD15@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
| > We are running SBS2003. We are consistently recieving errors 1019,
| > 1023, 1035 & 1053 as well as warning 1052. It seems that most/all of
| > these are regarding one specific user account. The help for warning
| > 1052 indicates that I should reinstall the POP 3 connector. However,
| > I thought that strange since it appears to apply only to one account.
| > This account is still sending and receiving emails.
| >
| > Any ideas?
| >
| > Thanks.
|
| Hi - the POP connector is part of SBS, not Exchange. Try
| microsoft.public.windows.server.sbs.
| However, note that POP connectors are not recommended, and you would have
| much better mail delivery if you switched to hosting your domain's mail
| directly via SMTP.
|
| Any additional comments would be welcomed.
|
| Thanks.
|
|
|
.
- Follow-Ups:
- RE: POP 3 Errors/Warnings
- From: LDD15
- RE: POP 3 Errors/Warnings
- Prev by Date: RE: POP 3 Errors/Warnings
- Next by Date: RE: Spam in Public Folders
- Previous by thread: RE: POP 3 Errors/Warnings
- Next by thread: RE: POP 3 Errors/Warnings
- Index(es):
Relevant Pages
|
Loading
