POP3 messages not routed? Can I get access to these messages?

Hello

We have a SBS 2003 server that is configured with POP3 connectors for their mailboxes. The POP3 connectors download mail to an associated mailbox on their exchange. Because of the site requirements, they have not been set up to host their MX record on the SBS server itself

Problem I saw on the 17th has me a bit baffled. A new account was added in the POP3 management, then the mailbox that it was set to download was changed shortly after

We know the download worked as there is no mail messages in the online POP3 mailbox

There are a number of messages with the following

Event Type:      Error
Event Source:      POP3 Connector
Event Category:      Delivery
Event ID:      1025
Date:            17/02/2011
Time:            1:59:44 PM
User:            N/A
Computer:      <server>
Description:
Can not find the routing information for the message <id: {401BA9C6-9052-4B77-AE6A-D4CA2452117B}>. The system administrator must manually deliver the message.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

and then

Event Type:      Error
Event Source:      POP3 Connector
Event Category:      Delivery
Event ID:      1053
Date:            17/02/2011
Time:            1:59:44 PM
User:            N/A
Computer:      <server>
Description:
The delivery process for message <id: {401BA9C6-9052-4B77-AE6A-D4CA2452117B}> finished with one or more errors.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Message tracking has not been set up on this server (its been enabled now) so I dont know how to find these messages or where they have been downloaded to

Does exchange have a default mailbox that it would store these messages in? Or any other means of forwarding these messages to where they need to be?

LVL 1
HeronTechAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
Larry Struckmeyer MVPConnect With a Mentor Commented:
Hi Herontech:
Chances are quite good that you will continue to experience "missing" messages, and the cause and the whereabouts will never be found.  With the built in exchange pop3 connector this is expected behaviour and no one has ever found a cure.  SMTP delivery via a public DNS record is much the better choice, but if that is not possible (for some reason that you haven't explained) then I suggest a third party pop3 connector.  Not recommending any, but a search should turn up a few.
0
 
HeronTechAuthor Commented:
Thanks for your reply

The standard POP3 connector has been operating for about 50 or so hosted email accounts and this is the first time we have seen this particular behaviour

The messages must have ended up somewhere? Is there a way to search all Exchange mailboxes simultaneously?
0
 
Larry Struckmeyer MVPCommented:
ime, sadly, the messages do not "end up somewhere".  that is one of the issues with the built in exchange pop3 connector.  If you search for missing messages pop3 connector you will see that there are lots of occurances and no solution, afaik.
0
 
HeronTechAuthor Commented:
So why would running a 3rd party POP3 connector be better than running the built in one with exchange?
0
 
HeronTechAuthor Commented:
No insight as to why the standard exchange pop3 connector suddenly had an issue like this when it has been functioning correctly for about 6 months now
0
All Courses

From novice to tech pro — start learning today.