Outlook 2003 and POP3 via SSL

[Kevster555]

Hi

Outlook 2003 connecting to a POP3 mail server via SSL (via tcp/995) fails to
connect properly. It responds with:


Task 'xxxxxx - Receiving' reported error (0x80042108) : 'Outlook is unable
to connect to your incoming (POP3) e-mail server. If you continue to receive
this message, contact your server administrator or Internet service provider
(ISP).'

If I test with Outlook Express there is no problem.

One last thing to note. Due to the SSL Cert not being from a trusted CA,
the first time OE connected a warning dialog was shown. This has never been
seen within Outlook 2003.

Anyone any ideas ? A security setting maybee ?

Kevster

 

[neo [mvp outlook]]

Will the ISP/identity hosting the POP3 server supply you with a copy of the
signing root CA?

 

[Kevster555]

Not at the moment. - however the server is under my control and I
could install the root CA to stop the message. Trouble is at present the
cert is self signed. Ill investigate this however.....

There seems to be diffrences in how OE6 and O2K3 handle this type of
relationship though. As I say OE6 shows a warning dialog, O2K3 plainly
refuses to connect.

Any ideas or is it a bug ?

Kevin

Will the ISP/identity hosting the POP3 server supply you with a copy of the
signing root CA?
--
Neo [MVP Outlook]
Due to the Swen virus, all e-mails sent to this account will be deleted
w/out reading.

Hi

Outlook 2003 connecting to a POP3 mail server via SSL (via tcp/995)

fails

to
connect properly. It responds with:


Task 'xxxxxx - Receiving' reported error (0x80042108) : 'Outlook is unable
to connect to your incoming (POP3) e-mail server. If you continue to receive
this message, contact your server administrator or Internet service provider
(ISP).'

If I test with Outlook Express there is no problem.

One last thing to note. Due to the SSL Cert not being from a trusted CA,
the first time OE connected a warning dialog was shown. This has never been
seen within Outlook 2003.

Anyone any ideas ? A security setting maybee ?

Kevster

 

[neo [mvp outlook]]

I don't think it is a bug, I think it is by design. (same thing happens
when trying to use RPC over HTTPS.) Only way to confirm is to run it by
Microsoft Product Support Services.

Not at the moment. - however the server is under my control and I
could install the root CA to stop the message. Trouble is at present the
cert is self signed. Ill investigate this however.....

There seems to be diffrences in how OE6 and O2K3 handle this type of
relationship though. As I say OE6 shows a warning dialog, O2K3 plainly
refuses to connect.

Any ideas or is it a bug ?

Kevin

Will the ISP/identity hosting the POP3 server supply you with a copy of the
signing root CA?
--
Neo [MVP Outlook]
Due to the Swen virus, all e-mails sent to this account will be deleted
w/out reading.

Hi

Outlook 2003 connecting to a POP3 mail server via SSL (via tcp/995)

fails

to
connect properly. It responds with:


Task 'xxxxxx - Receiving' reported error (0x80042108) : 'Outlook is unable
to connect to your incoming (POP3) e-mail server. If you continue to receive
this message, contact your server administrator or Internet service provider
(ISP).'

If I test with Outlook Express there is no problem.

One last thing to note. Due to the SSL Cert not being from a trusted CA,
the first time OE connected a warning dialog was shown. This has

never
been

seen within Outlook 2003.

Anyone any ideas ? A security setting maybee ?

Kevster

 

[Guest]

I get the same message and the reason I found for that is the following. Every time I reboot the system or restart Outlook 2003, it changes the Incoming Mail Server (POP3) setting to 'localhost'. When I correct the setting to my POP3 server and then click Send/Receive, it works well -- but only until I close Outlook 2003. I have to repeat the exercise when I restart.

Anyone else have a problem like that? Has anyone found a solution? Please share with us.
Thanks

SSharma

----- Kevster555 wrote: -----

Hi

Outlook 2003 connecting to a POP3 mail server via SSL (via tcp/995) fails to
connect properly. It responds with:


Task 'xxxxxx - Receiving' reported error (0x80042108) : 'Outlook is unable
to connect to your incoming (POP3) e-mail server. If you continue to receive
this message, contact your server administrator or Internet service provider
(ISP).'

If I test with Outlook Express there is no problem.

One last thing to note. Due to the SSL Cert not being from a trusted CA,
the first time OE connected a warning dialog was shown. This has never been
seen within Outlook 2003.

Anyone any ideas ? A security setting maybee ?

Kevster

 

[neo [mvp outlook]]

The localhost problem is due to the fact that you have a personal firewall
or antivirus product installed that scans POP3 mail as it is downloaded.
Therfore it sets the mail accounts settings to point to your own machine
(localhost = loop back to your machine) where the firewall/antivirus product
is acting as a go between. Disable this feature and you will find that you
settings stick.


As for the SSL problem that Kevster555 writes about, this is normal for
Outlook 2003 to not prompt the user to accept the certificate. You computer
must hold the root CA in order for you to establish that SSL connection.
See if the site you are connecting to will provide you with a copy of their
Root CA. (Then can export it w/out giving you their private key.) This is
generally not a problem for sites that develop internal only PKI
infrastructures or go with a public CA like Verisign.

--
Neo [MVP Outlook]
Due to the Swen virus, all e-mails sent to this account will be deleted
w/out reading.

I get the same message and the reason I found for that is the following.

Every time I reboot the system or restart Outlook 2003, it changes the
Incoming Mail Server (POP3) setting to 'localhost'. When I correct the
setting to my POP3 server and then click Send/Receive, it works well -- but
only until I close Outlook 2003. I have to repeat the exercise when I
restart.