I have my own business (sole proprietorship) on the side in which I do some information technology consultant work. You can get more information on my website: http://www.DatSure.com
Well, one of my customer's has a Small Business Server 2003 Edition that sends me a weekly report about its overall status (number of emails sent/received, backup report, hard drive space, error messages, etc). Well, last week I received the regular report and it had some errors on it that stated, "The delivery process for message <id: {2F42CBF3-091D-4B99-B961-ACCE5ED7AE82}> finished with one or more errors." & "The message <id:{2F42CBF3-091D-4B99-B961-ACCE5ED7AE82}> can not be delivered. The error code is: -2147220979." Well of course I logged into the server and took a closer look at the logs to figure out what was going on.
Well, in the Application Logs I had 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....
Well, sure looks like the problem is related to the POP3 Connector being unable to deliver a message to one of my users. The problem could have been attributed to downloading the message from the actual mail server (hosted on my server at MochaHost) or if it did download the message than it's having a problem delivering it locally. So I did what any sane person would do... I logged into each account on my mail server via webmail to see if there were any messages stuck on there that the POP3 Connector hadn't downloaded. If I found it, I would have deleted it. But as you can no doubt guess... I didn't find anything. So, on to checking the local Exchange server.
Well, the easiest thing for me to do is to follow the Microsoft KB article that explains how to troubleshoot the POP3 Connector. I found that very article here. But I'll paraphrase some of it for you to save the trip:
POP3 Connector overview
When you use the POP3 Connector to retrieve e-mail, the following mail-flow process occurs:
- The Connector for POP3 Mailboxes service connects to and logs on to the remote POP3 server.
- The Connector for POP3 Mailboxes service downloads e-mail messages and stores them in the following folder:
%PROGRAMFILES%\Microsoft Windows Small Business Server\\Networking\POP3\Incoming Mail
- When all the e-mail has been downloaded from the remote POP3 server, Collaborative Data Objects (CDO) on the Windows Small Business Server-based computer retrieves the e-mail messages from the Incoming Mail folder. The headers of these e-mail messages are modified to indicate that the e-mail messages will be directed to a local Exchange mailbox, and then the e-mail messages are saved to the following folder:
%PROGRAMFILES%\Exchsrvr\Mailroot\vsi 1\PickUp
- If CDO cannot move an e-mail message to the PickUp folder, the e-mail message is put in the following folder instead:
%PROGRAMFILES%\Microsoft Windows Small Business Server\\Networking\POP3\Failed Mail
- If an e-mail message is corrupted, it may not be moved to the Failed Mail folder. In this scenario, the corrupted e-mail message remains in the Incoming Mail folder.
- All the e-mail messages that are in the PickUp folder are processed by the local SMTP service and are delivered to the appropriate recipient.
When you use the POP3 Connector to retrieve e-mail messages, those e-mail messages are not processed by any of the following Microsoft Exchange Server 2003 components:
- Recipient Filtering
- Sender Filtering
- Connection Filtering
- The Intelligent Message Filter add-in
Because the POP3 Connector uses CDO to transfer e-mail messages to the SMTP PickUp folder, these e-mail messages bypass the filtering mechanisms that Exchange 2003 contains.
Well, I navigated to the Failed Mail folder and sure enough there were a bunch of undelivered messaged there. To speed things up for myself I clicked SEARCH within the folder, pasted in the message ID, and sure enough it was in there. I took a quick look at the contents using NotePad++ (I highly recommend this FREE program) and it was nothing but a SPAM email. Well, since there were no other newer messages within the folder I just blew all the contents away (translated - sent all of them to the trash).
After doing this I went to the POP3 Connector management interface and forced another retrieval, waitied a few minutes, and then checked the Applications Log again. TADA!!!! There were no more errors and the problem was solved!
Well, I hope that this helps someone else who might run into these problems. If you need further help on this situation don't hesitate to click on the contact me thingy at the top of the page! Have a great rest of your day!
Subscribe