I've been having ongoing issues with my e-mail system. I recently set up
multiple POP accounts at my ISP , and account for each of the 8 users on my
SBS2000 network. I configured the POP3 connector to pull the e-mail down and
all seemed to go fine. Unfortunately, no e-mail ever gets to the mailboxes
of the users. I've worked through the troubleshooting steps from Microsoft
and it seems that the POP3 connector is downloading the messages properly
and tries to deliver them to Exchange but encounters an error. It then
proceeds to purge the undelivered mail. The message that I'm getting form
the POP3 Connector in the event viewer is:

"The SMTP session transcript was: <G>:220 vickery01.VICKERY.local Microsoft
ESMTP MAIL Service, Version: 5.0.2195.6713 ready at Sat, 10 Sep 2005
22:30:09 -0400

<C>: EHLP vickery01.VICKERY.local
<S>: 500 Failed to exchange X-LSA info, closing transmission channel
<C>: HELO vickery01.VICKERY.local"

The POP3 Connector then generates a NDR status code 400

What am I missing?? I've searched everywhere I could think of and can't
figure this out. I could just pull the e-mail directly into Outlook on each
workstation but this is not what I want since I want to be able to scan each
e-mail for viruses and spam ( I use Trend )

Thanks
Cal

Re: Pop3 Connector Problem by Cal

Cal
Tue Sep 20 15:24:08 CDT 2005

No one has any ideas? I tried going in using telnet and running the
connection dialogue and as soon as I enter the EHLO command my connection is
terminated. If I use the HELO command I can proceed normally.

It look to me that the problem is with Exchange. Is there any way to force
Exchange/POP3 connector to not use the enhanced command?

Cal
"Cal Vickery" <cvickery> wrote in message
news:%23MGeHLxtFHA.2912@TK2MSFTNGP09.phx.gbl...
> I've been having ongoing issues with my e-mail system. I recently set up
> multiple POP accounts at my ISP , and account for each of the 8 users on
> my SBS2000 network. I configured the POP3 connector to pull the e-mail
> down and all seemed to go fine. Unfortunately, no e-mail ever gets to the
> mailboxes of the users. I've worked through the troubleshooting steps from
> Microsoft and it seems that the POP3 connector is downloading the messages
> properly and tries to deliver them to Exchange but encounters an error. It
> then proceeds to purge the undelivered mail. The message that I'm getting
> form the POP3 Connector in the event viewer is:
>
> "The SMTP session transcript was: <G>:220 vickery01.VICKERY.local
> Microsoft ESMTP MAIL Service, Version: 5.0.2195.6713 ready at Sat, 10 Sep
> 2005 22:30:09 -0400
>
> <C>: EHLO vickery01.VICKERY.local
> <S>: 500 Failed to exchange X-LSA info, closing transmission channel
> <C>: HELO vickery01.VICKERY.local"
>
> The POP3 Connector then generates a NDR status code 400
>
> What am I missing?? I've searched everywhere I could think of and can't
> figure this out. I could just pull the e-mail directly into Outlook on
> each workstation but this is not what I want since I want to be able to
> scan each e-mail for viruses and spam ( I use Trend )
>
> Thanks
> Cal
>
>
>



Re: Pop3 Connector Problem by Duncan

Duncan
Tue Sep 20 22:52:11 CDT 2005

In article <O3gcRBivFHA.3756@tk2msftngp13.phx.gbl>, "Cal Vickery"
<cvickery> says...
> No one has any ideas? I tried going in using telnet and running the
> connection dialogue and as soon as I enter the EHLO command my connection is
> terminated. If I use the HELO command I can proceed normally.
>
> It look to me that the problem is with Exchange. Is there any way to force
> Exchange/POP3 connector to not use the enhanced command?

Yep, Advanced tab of the Properties of the SMTP Connector.

--
Duncan

Re: Pop3 Connector Problem by Cal

Cal
Wed Sep 21 15:48:22 CDT 2005

Thanks Duncan,
I've tried that but I think it only changes the setting when Exchange is
initiating the connection. My problem is when Exchange gets the EHLO from
the POP3 connector it terminates the connection before POP3 drops back to
the HELO command.

Cal
"Duncan McC" <hard@work.ok> wrote in message
news:MPG.1d9ba018f823bb989897d9@news.microsoft.com...
> In article <O3gcRBivFHA.3756@tk2msftngp13.phx.gbl>, "Cal Vickery"
> <cvickery> says...
>> No one has any ideas? I tried going in using telnet and running the
>> connection dialogue and as soon as I enter the EHLO command my connection
>> is
>> terminated. If I use the HELO command I can proceed normally.
>>
>> It look to me that the problem is with Exchange. Is there any way to
>> force
>> Exchange/POP3 connector to not use the enhanced command?
>
> Yep, Advanced tab of the Properties of the SMTP Connector.
>
> --
> Duncan