• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1070
  • Last Modified:

Why is my SBS 2K3 server's POP3 Connector giving me errors 1053 & 1056?

Hello,

Over the last few months my Application Log has been showing me error messages that state the following:

Source: POP3 Connector
Type: Error
Category: Delivery
Event ID: 1056
User: N/A

Description:  The message <id:{xxxxxx-xxxxxxxx-xxxx-xxxx-xxxx-}> can not be delivered.  The error code is: -2147220979.

For more information....

The xxx are actual numbers and letters and if you need them for some reason let me know and I'll display them.

Right after this error another error shows up in the event log as follows:

Source: POP3 Connector
Category: Delivery
Type: Error
Event ID: 1053
User: N/A

Description:  The delivery process for message <id:{xxxxxx.xxxxx.xx.x.xxx.x.xxx}> finished with one or more errors.

For more information....

NOTE:  The xxx's are the same in both errors so I assuming it's dealing with the same message.

I checked that each POP3 account was associated with a local Exchange Mailbox, made sure the server is completely updated, and rebooted the server.

Does anyone have any ideas on how to troubleshoot this?  Thanks in advance.

- Joshua
0
DatSure
Asked:
DatSure
  • 7
  • 6
1 Solution
 
MesthaCommented:
Corrupt message at the ISP. You will need to login to the ISPs webmail system and remove the message. Failing that it is probably a telnet in to port 110 and then use manual commands to remove the message.

Of course if you were using SBS as it was designed, and email delivered directly by SMTP, then this wouldn't be an issue.

Simon.
0
 
DatSureAuthor Commented:
Simon:

Thank you for your response.  First of all, I'm unable to use SMTP as mail delivery is blocked by the ISP and no the small business won't pay extra for a static IP and open ports.  Secondly, I have used telnet and checked webmail for any messages remaining on the server and there are none.

Does anyone have any further suggestions?  Thanks again for your response Simon.
0
 
MesthaCommented:
The POP3 connector is seeing a message somewhere. If the message is corrupt then it could be that it cannot be seen by telnet either. You would have to ask the ISP to look at the mailbox and ensure that the message is removed.

As for the ISP blocking the port, that is easily worked around using a mail hop service. Anything is better than the POP3 connector.

Simon.
0
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

 
DatSureAuthor Commented:
I'll put in a ticket to my ISP and ask them about it.  I've been using the POP3 Connector for years now and haven't had any problems with it until now.  I'll update the thread as soon as I hear back.
0
 
MesthaCommented:
The POP3 connector isn't designed for long term use. If you have been using it for years without issues then you have been very fortunate and obviously do not use BCC messages, which the POP3 connector struggles with.

Simon.
0
 
DatSureAuthor Commented:
Mestha:

I'm not sure why the POP3 Connector would ever have problems with BCC messages?

When a message is sent to, for example, people as show here:

TO:  Billy@goat.gov
BCC: Obama@SinkingOurShip.gov

The SMTP server on the SENDING side splits the message into two messages and sends them individually to the respective recipients mail server.  My POP3 Connector will then go out and pull that individual email down just as it would a standard TO email.  So how could you have any problems with BCC?

In any case, still waiting to hear back from my ISP.
0
 
DatSureAuthor Commented:
Update:  ISP says there are 0 messages in any of the mailboxes.  The problem must be on my side.  Is it possible that the message is stored locally somewhere (cache?) that it's trying to process each time?  How can I check this?
0
 
MesthaCommented:
The problem the POP3 connector has with BCC messages is because it uses the routing information on the message to deliver the email message. BCC routing information is stripped when the message is delivered to the mailbox at your host.
Therefore the POP3 connector has nothing to work with. It doesn't place the email straight in to your mailbox, it is passed to the SMTP server for delivery.
http://support.microsoft.com/kb/265739
If you are using a one to one mapping of POP3 mailboxes then it isn't an issue.

There is no cache that I am aware of. If a message cannot be delivered then it would be put in to the failed mail folder.

Simon.
0
 
DatSureAuthor Commented:
Mestha:

Thank you for the explanation, however it doesn't help with the problem I'm posted on.  Any ideas?
0
 
MesthaCommented:
I have no further suggestions on the original problem. I would use it as an excuse to move to SMTP delivery.

Simon.
0
 
DatSureAuthor Commented:
I've bumped up the points.  Someone please answer this for me.
0
 
MesthaCommented:
This site doesn't work like a forum. Once the question has gone from the first page no one else will look at the question. You cannot "bump" a question back up the list. Considering the question is a week old, I doubt if anyone else will look at it now.

Simon.
0
 
DatSureAuthor Commented:
Well that sucks.  Thanks for the tip Simon.  I'll close it and reopen it again while referencing this post.  Thanks!
0

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

  • 7
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now