POP3Connector problems

[Allen Clark]

I don't want to hear ANY responses like "don't use POP3connector" when it IS
supposed to be an option SUPPORTED by Microsoft and included in ONLY the SBS
version of Exchange.

I have a client that has a remote mail server that is used as a BACKUP mail
server. They are running SBS2003 (with all service packs and security
patches applied) and they use a generic mailbox on their backup mail server
to pull messages that get delivered to the backup server instead of the
primary mail server. The POP3connector is only used to pull the messages
from this one "catch all" mailbox. Whenever it feels like it, the
POP3connector downloads the messages, but apparently trashes the header. The
sender of the message receives a DNR with a 5.1.1 error indicating the user
does not exist at the organization the message was sent to. The issue is
that the recipient is listed as
mspop3connecto...@validdomainname.com instead of
validu...@validdomainname.com. It appears to be prepending the
"mspop3connector." to the recipient field. Has anyone seen this behavior,
and does anyone know of a fix or workaround for this problem?

Thanks in advance,
Allen Clark

--

[Maxibo]

Hi Allen

Will this help ? (pinched from Cliff Zhang...lol)

Did you mean when a user receives emails using POP3
Connector, the "IMB Recipient 1" recipient with an email
address of mspop3connector.<username>
@domain.com appear on the To line and when you try to
reply to all, you get a NDR saying email cannot be
delivered to mspop3connector.<username>
@domain.com?

To know why this "IMB Recipient 1" recipient is added to
the To line, we need to know how POP3 connector works:

1. When the pop3 connector downloads email it appends
mspop3connector to the email address of the destination
mailbox and adds this new address as
an envelope recipient. This mail is submitted to SMTP via
CDO.

2. The Pop3 Connector adds an Event Sink to the IIS
metabase that checks all messages on submission for
addresses that start with mspop3connector.

3. Any messages that meet this criteria have the
mspop3connector portion of the address removed and the
message is delivered to the mailbox specified
in the pop3 connector configuration.

Now it seems that the problem is occurs at step 2 that
the POP3 Event Sink has become corrupt which prevented it
from removing the mspop3connector
text from addresses containing it and processing the
message(s). To resolve the issue, we need to re-register
the POP3 Event Sink. To do so, open
Windows Explorer, go to the "C:\Program Files\Microsoft
Windows Small Business Server\Networking\POP3" folder and
double click to run IMBReg.exe.

If you have Antivirus running on the SBS server, make
sure they are not scanning the critical folders. For more
information, see:

823166 Overview of Exchange Server 2003 and Antivirus
Software
[url]http://support.microsoft.com/?id=823166[/url]

822158 Virus Scanning Recommendations on a Windows 2000
or on a Windows Server
[url]http://support.microsoft.com/?id=822158[/url]

815263 Antivirus, Backup, and Disk Optimization Programs
That Are Compatible
[url]http://support.microsoft.com/?id=815263[/url]

Please do not hesitate to let me know if you have any
further concerns.

Sincerely,

Cliff Zhang
Microsoft Partner Online Support
MCSE 2000

"Allen Clark" <nospam...@erols.com.nospam> wrote in message
news:6018F184-1C51-47BF...@microsoft.com...