fix resolution for the mspop3connector problem
|
From: John on 4 Mar 2010 15:57 Although this is a very old problem, it's one that just started popping up for me late last year and the imbreg.exe 'fix' did not work for me, so I imagine that some people might still experience this problem. I ultimately solved the problem and wanted to share my solution. I finally realized that the problem appeared to start not long after I installed a new antivirus on the server. I won't be specific on the name of the antivirus because I don't want to bag on any particular vendor. The solution to the mspop3connector prefix problem is to exclude the C:\Program Files\Microsoft Windows Small Business Server directory from active or realtime scans. The reason is that email coming in through the POP3 connector passes through the following directory: C:\Program Files\Microsoft Windows Small Business Server\Networking\POP3\Incoming Mail It appears that my antivirus was holding this file while scanning, and causing an error to kick out, resulting in the email getting 'stuck' at the mspop3connector stage and getting kicked back to the sender. I suppose that the realtime scanning exclusion could be more specific to exclude only this directory, but just to avoid any other possible future 'collisions' I cut the path off at the root of the SBS directory. Maurice Bishop wrote: Bounce messages with mspop3connector 03-Oct-08 If I send en email to this server with two or more recipients, I get the bounce message as below. --snip, snip-------- Your message did not reach some or all of the intended recipients. Subject: RE: Second test message - please ignore - thanks - Maurice Sent: 02/10/2008 18:16 The following recipient(s) cannot be reached: mspop3connector.emailaddress1(a)customer-domain.com on 02/10/2008 18:16 The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address. <customer-domain.com #5.1.1> mspop3connector.emailaddress2(a)customer-domain.com on 02/10/2008 18:16 The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address. <customer-domain.com #5.1.1> mspop3connector.emailaddress3(a)customer-domain.com on 02/10/2008 18:16 The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address. <customer-domain.com #5.1.1> mspop3connector.emailaddress4(a)customer-domain.com on 02/10/2008 18:16 The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address. <customer-domain.com #5.1.1> --snip, snip-------- Efforts made (unsuccessfully) in trying to resolve the problem include: 1. Registering the POP3 connector. \Program Files\Microsoft Windows Small Business Server\Networking\POP3\imbreg.exe 2. Rerunning the 'Connect to the internet' wizard. My customer is running SBS 2003 with Exchange Server SP2 applied. TX in advance for all help, suggestions and advice. Maurice Previous Posts In This Thread: On Friday, October 03, 2008 2:29 AM Maurice Bishop wrote: Bounce messages with mspop3connector If I send en email to this server with two or more recipients, I get the bounce message as below. --snip, snip-------- Your message did not reach some or all of the intended recipients. Subject: RE: Second test message - please ignore - thanks - Maurice Sent: 02/10/2008 18:16 The following recipient(s) cannot be reached: mspop3connector.emailaddress1(a)customer-domain.com on 02/10/2008 18:16 The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address. <customer-domain.com #5.1.1> mspop3connector.emailaddress2(a)customer-domain.com on 02/10/2008 18:16 The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address. <customer-domain.com #5.1.1> mspop3connector.emailaddress3(a)customer-domain.com on 02/10/2008 18:16 The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address. <customer-domain.com #5.1.1> mspop3connector.emailaddress4(a)customer-domain.com on 02/10/2008 18:16 The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address. <customer-domain.com #5.1.1> --snip, snip-------- Efforts made (unsuccessfully) in trying to resolve the problem include: 1. Registering the POP3 connector. \Program Files\Microsoft Windows Small Business Server\Networking\POP3\imbreg.exe 2. Rerunning the 'Connect to the internet' wizard. My customer is running SBS 2003 with Exchange Server SP2 applied. TX in advance for all help, suggestions and advice. Maurice On Friday, October 03, 2008 7:54 AM Merv Porter [SBS-MVP] wrote: After you ran imbreg.exe, did you issue an iisreset from a command prompt? After you ran imbreg.exe, did you issue an iisreset from a command prompt? Have you tried reinstalling the POP3 Connector? How to reinstall POP3 connector in SBS 2003 http://groups.google.com/group/microsoft.public.windows.server.sbs/browse_thread/thread/172607b7fd245069/eab90fdd2cf82b52?hl=en&lnk=st&q=reinstall+POP3+connector#eab90fdd2cf82b52 -- Merv Porter [SBS-MVP] ============================ "Maurice Bishop" <nospamhereplease(a)thankyou.com> wrote in message news:SaednULszqFFJnjVnZ2dnUVZ8qydnZ2d(a)posted.plusnet... On Monday, October 06, 2008 5:08 AM v-robme wrote: Hello Maurice,Thanks for your post and Merv's suggestions. Hello Maurice, Thanks for your post and Merv's suggestions. I also would like to know that does this issue occur to other senders besides you? If the issue happens to all of the senders, it may be caused by the POP3 mailbox issue or the POP3 connector is corrupted. Then, please consider the following: On the Troubleshooting tab of the POP3 Connector Manager, specify an Exchange mailbox where undeliverable mail should be sent. Have the sender then send a message directly to this user and if it is undeliverable, it should be sent to this specified mailbox where the message can then be examined for problems. Is "customer-domain.com" your client's Exchange server email domain? If so, can you resolve this email domain from your side?(I assume you are trying to send emails to your clients POP3 mailbox and expected to get them in your cleints Exchange mailbox). Please use NSlookup.exe command from your side(the sender side) to see if it can find "customer-domain.com" MX record. I have tried to resolve the "customer-domain.com" MX records from my side and could not resolve any MX records. Hope this helps. Best regards, Robbin Meng(MSFT) Microsoft CSS Online Newsgroup Support Submitted via EggHeadCafe - Software Developer Portal of Choice WPF Custom Validation Using the Enterprise Library http://www.eggheadcafe.com/tutorials/aspnet/9af7ac1a-d7f3-4e00-9aec-33ef1ec7d1a3/wpf-custom-validation-usi.aspx
|
Pages: 1 Prev: Eventid 3760 error Next: SBS 2008 RWW "No computers are available" |