Outlook 2003 won't authonticate.

  • Thread starter Thread starter Eugene Burtsev
  • Start date Start date
E

Eugene Burtsev

I just installed Office 2003, and I seem to be having problems with MS
Outlook. The problem is that outlook does not report account properly
to the servers. When I started outlook I imported all of the accounts
from Outlook express, everything went fine. As you know the passwords
do not get imported and when I was prompted for the passwords to
retrieve email from my three different accounts they came back as
wrong. I've checked everything from the passwords to the account
properties, everything was in order, and no I didn't have my CAPS on.
Just to be sure I've recreated accounts in both MS Outlook and Outlook
express, using same information from email addresses to servers to
usernames and passwords, the difference was that Outlook express got
new emails and MS Outlook started asking me for passwords again and
again and again (this indicates to me that the password is wrong). I
am using IMAP accounts so both MS Outlook and Outlook express should
have gotten the emails; this is not the case with POP3. And just to
make sure I've triple checked CAPS, save passwords check mark,
servers, working offlines, firewall (I have a router) and even changed
the passwords on the servers, nothing worked. Outlook express works
great, MS Outlook 2003 does not.

Any thoughts would be appreciated as I am stuck with Outlook express
for now.

Eugene
 
Jeff Stephenson [MSFT]:

Could you turn on diagnostic logging (see
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q300479) and
post the OPMLog.log file after trying to receive?

Ok, this is pretty much is repeated with all accounts:

Microsoft Internet Messaging API 6.00.2800.1165
IMAP Log started at 12/09/2003 20:07:26
IMAP: 20:07:26 [db] Connecting to 'XXXXXXXX.com' on port 143.
IMAP: 20:07:26 [db] OnNotify: asOld = 0, asNew = 2, ae = 0
IMAP: 20:07:26 [db] srv_name = "XXXXXXX.com" srv_addr = 207.44.XXX.XXX
IMAP: 20:07:26 [db] OnNotify: asOld = 2, asNew = 3, ae = 1
IMAP: 20:07:26 [db] OnNotify: asOld = 3, asNew = 4, ae = 0
IMAP: 20:07:26 [db] OnNotify: asOld = 4, asNew = 5, ae = 2
IMAP: 20:07:26 [db] OnNotify: asOld = 5, asNew = 5, ae = 4
IMAP: 20:07:26 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:07:26 [rx] * OK Courier-IMAP ready. Copyright 1998-2002
Double Precision, Inc. See COPYING for distribution information.
IMAP: 20:07:26 [tx] 0001 CAPABILITY
IMAP: 20:07:26 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:07:26 [rx] * CAPABILITY IMAP4rev1 CHILDREN NAMESPACE
THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT STARTTLS
IMAP: 20:07:26 [rx] 0001 OK CAPABILITY completed
IMAP: 20:07:26 [tx] LOGIN command sent
IMAP: 20:07:31 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:07:31 [rx] 0004 NO Login failed.
IMAP: 20:07:31 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:07:49 [tx] LOGIN command sent
IMAP: 20:07:54 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:07:54 [rx] 0006 NO Login failed.
IMAP: 20:07:54 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:07:58 [tx] LOGIN command sent
IMAP: 20:08:03 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:08:03 [rx] 0008 NO Login failed.
IMAP: 20:08:03 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:08:06 [tx] LOGIN command sent
IMAP: 20:08:11 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:08:11 [rx] 0009 NO Login failed.
IMAP: 20:08:11 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:08:13 [tx] LOGIN command sent
IMAP: 20:08:18 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:08:18 [rx] 000B NO Login failed.
IMAP: 20:08:18 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:08:27 [db] Connection to '' closed.
IMAP: 20:08:27 [db] OnNotify: asOld = 5, asNew = 0, ae = 5

Here I gave up, otherwise I would be prompted again.

Just in case it's relevant here's my system:

OS Name Microsoft Windows XP Professional
Version 5.1.2600 Service Pack 1 Build 2600
OS Manufacturer Microsoft Corporation
System Name MAIN
System Manufacturer System Manufacturer
System Model System Name
System Type X86-based PC
Processor x86 Family 6 Model 6 Stepping 2 AuthenticAMD ~1666 Mhz
Processor x86 Family 6 Model 6 Stepping 2 AuthenticAMD ~1666 Mhz
BIOS Version/Date Award Software, Inc. ASUS A7M266-D ACPI BIOS
Revision 1010, 3/3/2003
SMBIOS Version 2.3
Windows Directory D:\WINDOWS
System Directory D:\WINDOWS\System32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "5.1.2600.1106
(xpsp1.020828-1920)"
User Name MAIN\Eugene
Time Zone Eastern Standard Time
Total Physical Memory 1,024.00 MB
Available Physical Memory 418.26 MB
Total Virtual Memory 3.40 GB
Available Virtual Memory 2.35 GB
Page File Space 2.40 GB
Page File D:\pagefile.sys


Well I hope this was all you needed, I appreciate your help.

-Eugene
 
It looks like you're encountering something I've been fearing. The IMAP
standard was recently revised (in RFC 3501), and one of the things that
changed was the sorts of authentication mechanisms that are allowed.
Outlook can only authenticate using AUTH=LOGIN and AUTH=NTLM (a proprietary
authentication mechanism used by Microsoft). The AUTH=LOGIN mechanism is
now disallowed in IMAP4rev1 compliant servers, and your server doesn't
support NTLM, so I don't see any way that you'll be able to get Outlook to
authenticate to your server.

The possible solutions I see are:

1) See if your mail administrator is willing to configure the server to
accept AUTH=LOGIN. While compliance to the Internet standards requires that
a server *ship* with a default configuration that follows the standards, it
doesn't forbid the server to be configurable in a other ways.
2) Try (just for laughs) checking the "use SSL" option on the Advanced tab
of your account. It may be that the server supports SSL and will allow
AUTH=LOGIN over the secure SSL connection. (What it wants, I think, is
AUTH=PLAIN after STARTTLS...)
3) If neither of the above work, you'll have to use a non-Microsoft mail
client to connect to the server. I warned people here about this issue when
the new standard was being drafted, but couldn't get anybody to commit the
manpower to deal with it. Unfortunately, we in Outlook can't fix this
ourselves - the Windows component that we use to talk to IMAP servers just
doesn't support what we'd need in order to work against an RFC 3501
compliant server. I've already sent this post out to try and light a fire
under people - hopefully we'll get a good result.

Sorry you're hitting this :-(.

--
Jeff Stephenson
Outlook Development
This posting is provided "AS IS" with no warranties, and confers no rights


Eugene Burtsev said:
Jeff Stephenson [MSFT]:

Could you turn on diagnostic logging (see
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q300479) and
post the OPMLog.log file after trying to receive?

Ok, this is pretty much is repeated with all accounts:

Microsoft Internet Messaging API 6.00.2800.1165
IMAP Log started at 12/09/2003 20:07:26
IMAP: 20:07:26 [db] Connecting to 'XXXXXXXX.com' on port 143.
IMAP: 20:07:26 [db] OnNotify: asOld = 0, asNew = 2, ae = 0
IMAP: 20:07:26 [db] srv_name = "XXXXXXX.com" srv_addr = 207.44.XXX.XXX
IMAP: 20:07:26 [db] OnNotify: asOld = 2, asNew = 3, ae = 1
IMAP: 20:07:26 [db] OnNotify: asOld = 3, asNew = 4, ae = 0
IMAP: 20:07:26 [db] OnNotify: asOld = 4, asNew = 5, ae = 2
IMAP: 20:07:26 [db] OnNotify: asOld = 5, asNew = 5, ae = 4
IMAP: 20:07:26 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:07:26 [rx] * OK Courier-IMAP ready. Copyright 1998-2002
Double Precision, Inc. See COPYING for distribution information.
IMAP: 20:07:26 [tx] 0001 CAPABILITY
IMAP: 20:07:26 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:07:26 [rx] * CAPABILITY IMAP4rev1 CHILDREN NAMESPACE
THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT STARTTLS
IMAP: 20:07:26 [rx] 0001 OK CAPABILITY completed
IMAP: 20:07:26 [tx] LOGIN command sent
IMAP: 20:07:31 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:07:31 [rx] 0004 NO Login failed.
IMAP: 20:07:31 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:07:49 [tx] LOGIN command sent
IMAP: 20:07:54 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:07:54 [rx] 0006 NO Login failed.
IMAP: 20:07:54 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:07:58 [tx] LOGIN command sent
IMAP: 20:08:03 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:08:03 [rx] 0008 NO Login failed.
IMAP: 20:08:03 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:08:06 [tx] LOGIN command sent
IMAP: 20:08:11 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:08:11 [rx] 0009 NO Login failed.
IMAP: 20:08:11 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:08:13 [tx] LOGIN command sent
IMAP: 20:08:18 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:08:18 [rx] 000B NO Login failed.
IMAP: 20:08:18 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:08:27 [db] Connection to '' closed.
IMAP: 20:08:27 [db] OnNotify: asOld = 5, asNew = 0, ae = 5

Here I gave up, otherwise I would be prompted again.

Just in case it's relevant here's my system:

OS Name Microsoft Windows XP Professional
Version 5.1.2600 Service Pack 1 Build 2600
OS Manufacturer Microsoft Corporation
System Name MAIN
System Manufacturer System Manufacturer
System Model System Name
System Type X86-based PC
Processor x86 Family 6 Model 6 Stepping 2 AuthenticAMD ~1666 Mhz
Processor x86 Family 6 Model 6 Stepping 2 AuthenticAMD ~1666 Mhz
BIOS Version/Date Award Software, Inc. ASUS A7M266-D ACPI BIOS
Revision 1010, 3/3/2003
SMBIOS Version 2.3
Windows Directory D:\WINDOWS
System Directory D:\WINDOWS\System32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "5.1.2600.1106
(xpsp1.020828-1920)"
User Name MAIN\Eugene
Time Zone Eastern Standard Time
Total Physical Memory 1,024.00 MB
Available Physical Memory 418.26 MB
Total Virtual Memory 3.40 GB
Available Virtual Memory 2.35 GB
Page File Space 2.40 GB
Page File D:\pagefile.sys


Well I hope this was all you needed, I appreciate your help.

-Eugene
Click to expand...
 
Thanks Jeff for giving me an idea as to what is going on, I was going
mad going over all of the settings, probably reinstalled Office 4
times and rechecked every letter in creation of the account more times
then I care to admit. I am deeply disappointed that I cannot use the
MS Outlook as I think Outlook by use is the most useful application in
Office. I had an understanding that I could count on Microsoft to be
compliant with the latest standards of the important protocols, and I
count IMAP one of them.

What I am curious about though is why can Outlook express support new
standard and MS Outlook not, if I can help in anyway in the
development of the component required please feel free to contact me
at (ms at burtsev dot com).

Thank you

Eugene

Jeff Stephenson said:
It looks like you're encountering something I've been fearing. The IMAP
standard was recently revised (in RFC 3501), and one of the things that
changed was the sorts of authentication mechanisms that are allowed.
Outlook can only authenticate using AUTH=LOGIN and AUTH=NTLM (a proprietary
authentication mechanism used by Microsoft). The AUTH=LOGIN mechanism is
now disallowed in IMAP4rev1 compliant servers, and your server doesn't
support NTLM, so I don't see any way that you'll be able to get Outlook to
authenticate to your server.

The possible solutions I see are:

1) See if your mail administrator is willing to configure the server to
accept AUTH=LOGIN. While compliance to the Internet standards requires that
a server *ship* with a default configuration that follows the standards, it
doesn't forbid the server to be configurable in a other ways.
2) Try (just for laughs) checking the "use SSL" option on the Advanced tab
of your account. It may be that the server supports SSL and will allow
AUTH=LOGIN over the secure SSL connection. (What it wants, I think, is
AUTH=PLAIN after STARTTLS...)
3) If neither of the above work, you'll have to use a non-Microsoft mail
client to connect to the server. I warned people here about this issue when
the new standard was being drafted, but couldn't get anybody to commit the
manpower to deal with it. Unfortunately, we in Outlook can't fix this
ourselves - the Windows component that we use to talk to IMAP servers just
doesn't support what we'd need in order to work against an RFC 3501
compliant server. I've already sent this post out to try and light a fire
under people - hopefully we'll get a good result.

Sorry you're hitting this :-(.

--
Jeff Stephenson
Outlook Development
This posting is provided "AS IS" with no warranties, and confers no rights


Eugene Burtsev said:
Jeff Stephenson [MSFT]:

Could you turn on diagnostic logging (see
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q300479) and
post the OPMLog.log file after trying to receive?

Ok, this is pretty much is repeated with all accounts:

Microsoft Internet Messaging API 6.00.2800.1165
IMAP Log started at 12/09/2003 20:07:26
IMAP: 20:07:26 [db] Connecting to 'XXXXXXXX.com' on port 143.
IMAP: 20:07:26 [db] OnNotify: asOld = 0, asNew = 2, ae = 0
IMAP: 20:07:26 [db] srv_name = "XXXXXXX.com" srv_addr = 207.44.XXX.XXX
IMAP: 20:07:26 [db] OnNotify: asOld = 2, asNew = 3, ae = 1
IMAP: 20:07:26 [db] OnNotify: asOld = 3, asNew = 4, ae = 0
IMAP: 20:07:26 [db] OnNotify: asOld = 4, asNew = 5, ae = 2
IMAP: 20:07:26 [db] OnNotify: asOld = 5, asNew = 5, ae = 4
IMAP: 20:07:26 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:07:26 [rx] * OK Courier-IMAP ready. Copyright 1998-2002
Double Precision, Inc. See COPYING for distribution information.
IMAP: 20:07:26 [tx] 0001 CAPABILITY
IMAP: 20:07:26 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:07:26 [rx] * CAPABILITY IMAP4rev1 CHILDREN NAMESPACE
THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT STARTTLS
IMAP: 20:07:26 [rx] 0001 OK CAPABILITY completed
IMAP: 20:07:26 [tx] LOGIN command sent
IMAP: 20:07:31 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:07:31 [rx] 0004 NO Login failed.
IMAP: 20:07:31 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:07:49 [tx] LOGIN command sent
IMAP: 20:07:54 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:07:54 [rx] 0006 NO Login failed.
IMAP: 20:07:54 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:07:58 [tx] LOGIN command sent
IMAP: 20:08:03 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:08:03 [rx] 0008 NO Login failed.
IMAP: 20:08:03 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:08:06 [tx] LOGIN command sent
IMAP: 20:08:11 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:08:11 [rx] 0009 NO Login failed.
IMAP: 20:08:11 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:08:13 [tx] LOGIN command sent
IMAP: 20:08:18 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:08:18 [rx] 000B NO Login failed.
IMAP: 20:08:18 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:08:27 [db] Connection to '' closed.
IMAP: 20:08:27 [db] OnNotify: asOld = 5, asNew = 0, ae = 5

Here I gave up, otherwise I would be prompted again.

Just in case it's relevant here's my system:

OS Name Microsoft Windows XP Professional
Version 5.1.2600 Service Pack 1 Build 2600
OS Manufacturer Microsoft Corporation
System Name MAIN
System Manufacturer System Manufacturer
System Model System Name
System Type X86-based PC
Processor x86 Family 6 Model 6 Stepping 2 AuthenticAMD ~1666 Mhz
Processor x86 Family 6 Model 6 Stepping 2 AuthenticAMD ~1666 Mhz
BIOS Version/Date Award Software, Inc. ASUS A7M266-D ACPI BIOS
Revision 1010, 3/3/2003
SMBIOS Version 2.3
Windows Directory D:\WINDOWS
System Directory D:\WINDOWS\System32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "5.1.2600.1106
(xpsp1.020828-1920)"
User Name MAIN\Eugene
Time Zone Eastern Standard Time
Total Physical Memory 1,024.00 MB
Available Physical Memory 418.26 MB
Total Virtual Memory 3.40 GB
Available Virtual Memory 2.35 GB
Page File Space 2.40 GB
Page File D:\pagefile.sys


Well I hope this was all you needed, I appreciate your help.

-Eugene
Click to expand...
Click to expand...
 
If you're hitting the problem that I think you're hitting, Outlook Express
won't be able to connect to your server either. If Outlook Express *can*
connect to your server, I've misdiagnosed the problem and we need to
investigate further.

--
Jeff Stephenson
Outlook Development
This posting is provided "AS IS" with no warranties, and confers no rights


Eugene Burtsev said:
Thanks Jeff for giving me an idea as to what is going on, I was going
mad going over all of the settings, probably reinstalled Office 4
times and rechecked every letter in creation of the account more times
then I care to admit. I am deeply disappointed that I cannot use the
MS Outlook as I think Outlook by use is the most useful application in
Office. I had an understanding that I could count on Microsoft to be
compliant with the latest standards of the important protocols, and I
count IMAP one of them.

What I am curious about though is why can Outlook express support new
standard and MS Outlook not, if I can help in anyway in the
development of the component required please feel free to contact me
at (ms at burtsev dot com).

Thank you

Eugene

"Jeff Stephenson [MSFT]" <[email protected]> wrote in
message news: said:
It looks like you're encountering something I've been fearing. The IMAP
standard was recently revised (in RFC 3501), and one of the things that
changed was the sorts of authentication mechanisms that are allowed.
Outlook can only authenticate using AUTH=LOGIN and AUTH=NTLM (a proprietary
authentication mechanism used by Microsoft). The AUTH=LOGIN mechanism is
now disallowed in IMAP4rev1 compliant servers, and your server doesn't
support NTLM, so I don't see any way that you'll be able to get Outlook to
authenticate to your server.

The possible solutions I see are:

1) See if your mail administrator is willing to configure the server to
accept AUTH=LOGIN. While compliance to the Internet standards requires that
a server *ship* with a default configuration that follows the standards, it
doesn't forbid the server to be configurable in a other ways.
2) Try (just for laughs) checking the "use SSL" option on the Advanced tab
of your account. It may be that the server supports SSL and will allow
AUTH=LOGIN over the secure SSL connection. (What it wants, I think, is
AUTH=PLAIN after STARTTLS...)
3) If neither of the above work, you'll have to use a non-Microsoft mail
client to connect to the server. I warned people here about this issue when
the new standard was being drafted, but couldn't get anybody to commit the
manpower to deal with it. Unfortunately, we in Outlook can't fix this
ourselves - the Windows component that we use to talk to IMAP servers just
doesn't support what we'd need in order to work against an RFC 3501
compliant server. I've already sent this post out to try and light a fire
under people - hopefully we'll get a good result.

Sorry you're hitting this :-(.

--
Jeff Stephenson
Outlook Development
This posting is provided "AS IS" with no warranties, and confers no rights


Eugene Burtsev said:
Jeff Stephenson [MSFT]:

Could you turn on diagnostic logging (see
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q300479) and
post the OPMLog.log file after trying to receive?

Ok, this is pretty much is repeated with all accounts:

Microsoft Internet Messaging API 6.00.2800.1165
IMAP Log started at 12/09/2003 20:07:26
IMAP: 20:07:26 [db] Connecting to 'XXXXXXXX.com' on port 143.
IMAP: 20:07:26 [db] OnNotify: asOld = 0, asNew = 2, ae = 0
IMAP: 20:07:26 [db] srv_name = "XXXXXXX.com" srv_addr = 207.44.XXX.XXX
IMAP: 20:07:26 [db] OnNotify: asOld = 2, asNew = 3, ae = 1
IMAP: 20:07:26 [db] OnNotify: asOld = 3, asNew = 4, ae = 0
IMAP: 20:07:26 [db] OnNotify: asOld = 4, asNew = 5, ae = 2
IMAP: 20:07:26 [db] OnNotify: asOld = 5, asNew = 5, ae = 4
IMAP: 20:07:26 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:07:26 [rx] * OK Courier-IMAP ready. Copyright 1998-2002
Double Precision, Inc. See COPYING for distribution information.
IMAP: 20:07:26 [tx] 0001 CAPABILITY
IMAP: 20:07:26 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:07:26 [rx] * CAPABILITY IMAP4rev1 CHILDREN NAMESPACE
THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT STARTTLS
IMAP: 20:07:26 [rx] 0001 OK CAPABILITY completed
IMAP: 20:07:26 [tx] LOGIN command sent
IMAP: 20:07:31 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:07:31 [rx] 0004 NO Login failed.
IMAP: 20:07:31 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:07:49 [tx] LOGIN command sent
IMAP: 20:07:54 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:07:54 [rx] 0006 NO Login failed.
IMAP: 20:07:54 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:07:58 [tx] LOGIN command sent
IMAP: 20:08:03 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:08:03 [rx] 0008 NO Login failed.
IMAP: 20:08:03 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:08:06 [tx] LOGIN command sent
IMAP: 20:08:11 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:08:11 [rx] 0009 NO Login failed.
IMAP: 20:08:11 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:08:13 [tx] LOGIN command sent
IMAP: 20:08:18 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:08:18 [rx] 000B NO Login failed.
IMAP: 20:08:18 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:08:27 [db] Connection to '' closed.
IMAP: 20:08:27 [db] OnNotify: asOld = 5, asNew = 0, ae = 5

Here I gave up, otherwise I would be prompted again.

Just in case it's relevant here's my system:

OS Name Microsoft Windows XP Professional
Version 5.1.2600 Service Pack 1 Build 2600
OS Manufacturer Microsoft Corporation
System Name MAIN
System Manufacturer System Manufacturer
System Model System Name
System Type X86-based PC
Processor x86 Family 6 Model 6 Stepping 2 AuthenticAMD ~1666 Mhz
Processor x86 Family 6 Model 6 Stepping 2 AuthenticAMD ~1666 Mhz
BIOS Version/Date Award Software, Inc. ASUS A7M266-D ACPI BIOS
Revision 1010, 3/3/2003
SMBIOS Version 2.3
Windows Directory D:\WINDOWS
System Directory D:\WINDOWS\System32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "5.1.2600.1106
(xpsp1.020828-1920)"
User Name MAIN\Eugene
Time Zone Eastern Standard Time
Total Physical Memory 1,024.00 MB
Available Physical Memory 418.26 MB
Total Virtual Memory 3.40 GB
Available Virtual Memory 2.35 GB
Page File Space 2.40 GB
Page File D:\pagefile.sys


Well I hope this was all you needed, I appreciate your help.

-Eugene
Click to expand...
Click to expand...
Click to expand...
 
My outlook express can work, I have found the logging option simular
to MS Outlook and here are the results:

IMAP Log started at 12/14/2003 00:31:42

Microsoft Internet Messaging API 6.00.2800.1165
IMAP Log started at 12/14/2003 00:31:42
IMAP: 00:31:48 [db] Connecting to 'XXXXXXX.XXX' on port 143.
IMAP: 00:31:48 [db] OnNotify: asOld = 0, asNew = 4, ae = 0
IMAP: 00:31:48 [db] OnNotify: asOld = 4, asNew = 5, ae = 2
IMAP: 00:31:48 [db] OnNotify: asOld = 5, asNew = 5, ae = 4
IMAP: 00:31:48 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 00:31:48 [rx] * OK Courier-IMAP ready. Copyright 1998-2002
Double Precision, Inc. See COPYING for distribution information.
IMAP: 00:31:48 [tx] 000Y CAPABILITY
IMAP: 00:31:48 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 00:31:48 [rx] * CAPABILITY IMAP4rev1 CHILDREN NAMESPACE
THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT STARTTLS
IMAP: 00:31:48 [rx] 000Y OK CAPABILITY completed
IMAP: 00:31:48 [tx] LOGIN command sent
IMAP: 00:31:48 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 00:31:48 [rx] 000Z OK LOGIN Ok.
IMAP: 00:31:48 [tx] 0010 STATUS "INBOX" (MESSAGES UNSEEN)
IMAP: 00:31:48 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 00:31:48 [rx] * STATUS "INBOX" (MESSAGES 47 UNSEEN 0)
IMAP: 00:31:48 [rx] 0010 OK STATUS Completed.
IMAP: 00:31:48 [tx] Dropping connection, LOGOUT sent
IMAP: 00:31:48 [db] Connection to '' closed.
IMAP: 00:31:48 [db] OnNotify: asOld = 5, asNew = 0, ae = 5

I appreciate your help and would like to help anyway I can, if I can
run more diagnostic functions just ask.

Eugene

Jeff Stephenson said:
If you're hitting the problem that I think you're hitting, Outlook Express
won't be able to connect to your server either. If Outlook Express *can*
connect to your server, I've misdiagnosed the problem and we need to
investigate further.

--
Jeff Stephenson
Outlook Development
This posting is provided "AS IS" with no warranties, and confers no rights


Eugene Burtsev said:
Thanks Jeff for giving me an idea as to what is going on, I was going
mad going over all of the settings, probably reinstalled Office 4
times and rechecked every letter in creation of the account more times
then I care to admit. I am deeply disappointed that I cannot use the
MS Outlook as I think Outlook by use is the most useful application in
Office. I had an understanding that I could count on Microsoft to be
compliant with the latest standards of the important protocols, and I
count IMAP one of them.

What I am curious about though is why can Outlook express support new
standard and MS Outlook not, if I can help in anyway in the
development of the component required please feel free to contact me
at (ms at burtsev dot com).

Thank you

Eugene

"Jeff Stephenson [MSFT]" <[email protected]> wrote in
message news: said:
It looks like you're encountering something I've been fearing. The IMAP
standard was recently revised (in RFC 3501), and one of the things that
changed was the sorts of authentication mechanisms that are allowed.
Outlook can only authenticate using AUTH=LOGIN and AUTH=NTLM (a proprietary
authentication mechanism used by Microsoft). The AUTH=LOGIN mechanism is
now disallowed in IMAP4rev1 compliant servers, and your server doesn't
support NTLM, so I don't see any way that you'll be able to get Outlook to
authenticate to your server.

The possible solutions I see are:

1) See if your mail administrator is willing to configure the server to
accept AUTH=LOGIN. While compliance to the Internet standards requires that
a server *ship* with a default configuration that follows the standards, it
doesn't forbid the server to be configurable in a other ways.
2) Try (just for laughs) checking the "use SSL" option on the Advanced tab
of your account. It may be that the server supports SSL and will allow
AUTH=LOGIN over the secure SSL connection. (What it wants, I think, is
AUTH=PLAIN after STARTTLS...)
3) If neither of the above work, you'll have to use a non-Microsoft mail
client to connect to the server. I warned people here about this issue when
the new standard was being drafted, but couldn't get anybody to commit the
manpower to deal with it. Unfortunately, we in Outlook can't fix this
ourselves - the Windows component that we use to talk to IMAP servers just
doesn't support what we'd need in order to work against an RFC 3501
compliant server. I've already sent this post out to try and light a fire
under people - hopefully we'll get a good result.

Sorry you're hitting this :-(.

--
Jeff Stephenson
Outlook Development
This posting is provided "AS IS" with no warranties, and confers no rights


Jeff Stephenson [MSFT]:

Could you turn on diagnostic logging (see
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q300479) and
post the OPMLog.log file after trying to receive?

Ok, this is pretty much is repeated with all accounts:

Microsoft Internet Messaging API 6.00.2800.1165
IMAP Log started at 12/09/2003 20:07:26
IMAP: 20:07:26 [db] Connecting to 'XXXXXXXX.com' on port 143.
IMAP: 20:07:26 [db] OnNotify: asOld = 0, asNew = 2, ae = 0
IMAP: 20:07:26 [db] srv_name = "XXXXXXX.com" srv_addr = 207.44.XXX.XXX
IMAP: 20:07:26 [db] OnNotify: asOld = 2, asNew = 3, ae = 1
IMAP: 20:07:26 [db] OnNotify: asOld = 3, asNew = 4, ae = 0
IMAP: 20:07:26 [db] OnNotify: asOld = 4, asNew = 5, ae = 2
IMAP: 20:07:26 [db] OnNotify: asOld = 5, asNew = 5, ae = 4
IMAP: 20:07:26 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:07:26 [rx] * OK Courier-IMAP ready. Copyright 1998-2002
Double Precision, Inc. See COPYING for distribution information.
IMAP: 20:07:26 [tx] 0001 CAPABILITY
IMAP: 20:07:26 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:07:26 [rx] * CAPABILITY IMAP4rev1 CHILDREN NAMESPACE
THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT STARTTLS
IMAP: 20:07:26 [rx] 0001 OK CAPABILITY completed
IMAP: 20:07:26 [tx] LOGIN command sent
IMAP: 20:07:31 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:07:31 [rx] 0004 NO Login failed.
IMAP: 20:07:31 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:07:49 [tx] LOGIN command sent
IMAP: 20:07:54 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:07:54 [rx] 0006 NO Login failed.
IMAP: 20:07:54 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:07:58 [tx] LOGIN command sent
IMAP: 20:08:03 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:08:03 [rx] 0008 NO Login failed.
IMAP: 20:08:03 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:08:06 [tx] LOGIN command sent
IMAP: 20:08:11 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:08:11 [rx] 0009 NO Login failed.
IMAP: 20:08:11 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:08:13 [tx] LOGIN command sent
IMAP: 20:08:18 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:08:18 [rx] 000B NO Login failed.
IMAP: 20:08:18 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:08:27 [db] Connection to '' closed.
IMAP: 20:08:27 [db] OnNotify: asOld = 5, asNew = 0, ae = 5

Here I gave up, otherwise I would be prompted again.

Just in case it's relevant here's my system:

OS Name Microsoft Windows XP Professional
Version 5.1.2600 Service Pack 1 Build 2600
OS Manufacturer Microsoft Corporation
System Name MAIN
System Manufacturer System Manufacturer
System Model System Name
System Type X86-based PC
Processor x86 Family 6 Model 6 Stepping 2 AuthenticAMD ~1666 Mhz
Processor x86 Family 6 Model 6 Stepping 2 AuthenticAMD ~1666 Mhz
BIOS Version/Date Award Software, Inc. ASUS A7M266-D ACPI BIOS
Revision 1010, 3/3/2003
SMBIOS Version 2.3
Windows Directory D:\WINDOWS
System Directory D:\WINDOWS\System32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "5.1.2600.1106
(xpsp1.020828-1920)"
User Name MAIN\Eugene
Time Zone Eastern Standard Time
Total Physical Memory 1,024.00 MB
Available Physical Memory 418.26 MB
Total Virtual Memory 3.40 GB
Available Virtual Memory 2.35 GB
Page File Space 2.40 GB
Page File D:\pagefile.sys


Well I hope this was all you needed, I appreciate your help.

-Eugene
Click to expand...
Click to expand...
Click to expand...
 
Let's see if we can track this down, then. If OE can do it, there's no
reason that Outlook shouldn't be able to. I won't be able to get to this
for a few weeks, though - I'm heading out of town tomorrow, and won't be
back until Dec. 29th. If I haven't followed up by the first of the year,
post a gentle reminder ;-).

--
Jeff Stephenson
Outlook Development
This posting is provided "AS IS" with no warranties, and confers no rights


Eugene Burtsev said:
My outlook express can work, I have found the logging option simular
to MS Outlook and here are the results:

IMAP Log started at 12/14/2003 00:31:42

Microsoft Internet Messaging API 6.00.2800.1165
IMAP Log started at 12/14/2003 00:31:42
IMAP: 00:31:48 [db] Connecting to 'XXXXXXX.XXX' on port 143.
IMAP: 00:31:48 [db] OnNotify: asOld = 0, asNew = 4, ae = 0
IMAP: 00:31:48 [db] OnNotify: asOld = 4, asNew = 5, ae = 2
IMAP: 00:31:48 [db] OnNotify: asOld = 5, asNew = 5, ae = 4
IMAP: 00:31:48 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 00:31:48 [rx] * OK Courier-IMAP ready. Copyright 1998-2002
Double Precision, Inc. See COPYING for distribution information.
IMAP: 00:31:48 [tx] 000Y CAPABILITY
IMAP: 00:31:48 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 00:31:48 [rx] * CAPABILITY IMAP4rev1 CHILDREN NAMESPACE
THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT STARTTLS
IMAP: 00:31:48 [rx] 000Y OK CAPABILITY completed
IMAP: 00:31:48 [tx] LOGIN command sent
IMAP: 00:31:48 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 00:31:48 [rx] 000Z OK LOGIN Ok.
IMAP: 00:31:48 [tx] 0010 STATUS "INBOX" (MESSAGES UNSEEN)
IMAP: 00:31:48 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 00:31:48 [rx] * STATUS "INBOX" (MESSAGES 47 UNSEEN 0)
IMAP: 00:31:48 [rx] 0010 OK STATUS Completed.
IMAP: 00:31:48 [tx] Dropping connection, LOGOUT sent
IMAP: 00:31:48 [db] Connection to '' closed.
IMAP: 00:31:48 [db] OnNotify: asOld = 5, asNew = 0, ae = 5

I appreciate your help and would like to help anyway I can, if I can
run more diagnostic functions just ask.

Eugene

"Jeff Stephenson [MSFT]" <[email protected]> wrote in
message news: said:
If you're hitting the problem that I think you're hitting, Outlook Express
won't be able to connect to your server either. If Outlook Express *can*
connect to your server, I've misdiagnosed the problem and we need to
investigate further.

--
Jeff Stephenson
Outlook Development
This posting is provided "AS IS" with no warranties, and confers no rights


Eugene Burtsev said:
Thanks Jeff for giving me an idea as to what is going on, I was going
mad going over all of the settings, probably reinstalled Office 4
times and rechecked every letter in creation of the account more times
then I care to admit. I am deeply disappointed that I cannot use the
MS Outlook as I think Outlook by use is the most useful application in
Office. I had an understanding that I could count on Microsoft to be
compliant with the latest standards of the important protocols, and I
count IMAP one of them.

What I am curious about though is why can Outlook express support new
standard and MS Outlook not, if I can help in anyway in the
development of the component required please feel free to contact me
at (ms at burtsev dot com).

Thank you

Eugene

"Jeff Stephenson [MSFT]" <[email protected]> wrote in
Click to expand...
message news: said:
It looks like you're encountering something I've been fearing. The IMAP
standard was recently revised (in RFC 3501), and one of the things that
changed was the sorts of authentication mechanisms that are allowed.
Outlook can only authenticate using AUTH=LOGIN and AUTH=NTLM (a proprietary
authentication mechanism used by Microsoft). The AUTH=LOGIN
Click to expand...
mechanism
is
now disallowed in IMAP4rev1 compliant servers, and your server doesn't
support NTLM, so I don't see any way that you'll be able to get
Click to expand...
Outlook
to
authenticate to your server.

The possible solutions I see are:

1) See if your mail administrator is willing to configure the server to
accept AUTH=LOGIN. While compliance to the Internet standards
Click to expand...
requires
that
a server *ship* with a default configuration that follows the
Click to expand...
standards,
it
doesn't forbid the server to be configurable in a other ways.
2) Try (just for laughs) checking the "use SSL" option on the
Click to expand...
Advanced
tab
of your account. It may be that the server supports SSL and will allow
AUTH=LOGIN over the secure SSL connection. (What it wants, I think, is
AUTH=PLAIN after STARTTLS...)
3) If neither of the above work, you'll have to use a non-Microsoft mail
client to connect to the server. I warned people here about this
Click to expand...
issue
when
the new standard was being drafted, but couldn't get anybody to
Click to expand...
commit
the
manpower to deal with it. Unfortunately, we in Outlook can't fix this
ourselves - the Windows component that we use to talk to IMAP
Click to expand...
servers
just
doesn't support what we'd need in order to work against an RFC 3501
compliant server. I've already sent this post out to try and light
Click to expand...
a
fire
under people - hopefully we'll get a good result.

Sorry you're hitting this :-(.

--
Jeff Stephenson
Outlook Development
This posting is provided "AS IS" with no warranties, and confers no rights


Jeff Stephenson [MSFT]:

Could you turn on diagnostic logging (see
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q300479) and
post the OPMLog.log file after trying to receive?

Ok, this is pretty much is repeated with all accounts:

Microsoft Internet Messaging API 6.00.2800.1165
IMAP Log started at 12/09/2003 20:07:26
IMAP: 20:07:26 [db] Connecting to 'XXXXXXXX.com' on port 143.
IMAP: 20:07:26 [db] OnNotify: asOld = 0, asNew = 2, ae = 0
IMAP: 20:07:26 [db] srv_name = "XXXXXXX.com" srv_addr = 207.44.XXX.XXX
IMAP: 20:07:26 [db] OnNotify: asOld = 2, asNew = 3, ae = 1
IMAP: 20:07:26 [db] OnNotify: asOld = 3, asNew = 4, ae = 0
IMAP: 20:07:26 [db] OnNotify: asOld = 4, asNew = 5, ae = 2
IMAP: 20:07:26 [db] OnNotify: asOld = 5, asNew = 5, ae = 4
IMAP: 20:07:26 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:07:26 [rx] * OK Courier-IMAP ready. Copyright 1998-2002
Double Precision, Inc. See COPYING for distribution information.
IMAP: 20:07:26 [tx] 0001 CAPABILITY
IMAP: 20:07:26 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:07:26 [rx] * CAPABILITY IMAP4rev1 CHILDREN NAMESPACE
THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT STARTTLS
IMAP: 20:07:26 [rx] 0001 OK CAPABILITY completed
IMAP: 20:07:26 [tx] LOGIN command sent
IMAP: 20:07:31 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:07:31 [rx] 0004 NO Login failed.
IMAP: 20:07:31 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:07:49 [tx] LOGIN command sent
IMAP: 20:07:54 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:07:54 [rx] 0006 NO Login failed.
IMAP: 20:07:54 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:07:58 [tx] LOGIN command sent
IMAP: 20:08:03 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:08:03 [rx] 0008 NO Login failed.
IMAP: 20:08:03 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:08:06 [tx] LOGIN command sent
IMAP: 20:08:11 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:08:11 [rx] 0009 NO Login failed.
IMAP: 20:08:11 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:08:13 [tx] LOGIN command sent
IMAP: 20:08:18 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:08:18 [rx] 000B NO Login failed.
IMAP: 20:08:18 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:08:27 [db] Connection to '' closed.
IMAP: 20:08:27 [db] OnNotify: asOld = 5, asNew = 0, ae = 5

Here I gave up, otherwise I would be prompted again.

Just in case it's relevant here's my system:

OS Name Microsoft Windows XP Professional
Version 5.1.2600 Service Pack 1 Build 2600
OS Manufacturer Microsoft Corporation
System Name MAIN
System Manufacturer System Manufacturer
System Model System Name
System Type X86-based PC
Processor x86 Family 6 Model 6 Stepping 2 AuthenticAMD ~1666 Mhz
Processor x86 Family 6 Model 6 Stepping 2 AuthenticAMD ~1666 Mhz
BIOS Version/Date Award Software, Inc. ASUS A7M266-D ACPI BIOS
Revision 1010, 3/3/2003
SMBIOS Version 2.3
Windows Directory D:\WINDOWS
System Directory D:\WINDOWS\System32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "5.1.2600.1106
(xpsp1.020828-1920)"
User Name MAIN\Eugene
Time Zone Eastern Standard Time
Total Physical Memory 1,024.00 MB
Available Physical Memory 418.26 MB
Total Virtual Memory 3.40 GB
Available Virtual Memory 2.35 GB
Page File Space 2.40 GB
Page File D:\pagefile.sys


Well I hope this was all you needed, I appreciate your help.

-Eugene
Click to expand...
Click to expand...
Click to expand...
 
I'm back - let's see if we can get this figured out. Do you perhaps have
the "use Secure Password Authentication (SPA)" option checked in Outlook?
That might explain its behavior, as your IMAP server does not advertise a
secure login mechanism, so Outlook would not try the insecure LOGIN
authentication that OE is using.

--
Jeff Stephenson
Outlook Development
This posting is provided "AS IS" with no warranties, and confers no rights


Jeff Stephenson said:
Let's see if we can track this down, then. If OE can do it, there's no
reason that Outlook shouldn't be able to. I won't be able to get to this
for a few weeks, though - I'm heading out of town tomorrow, and won't be
back until Dec. 29th. If I haven't followed up by the first of the year,
post a gentle reminder ;-).

--
Jeff Stephenson
Outlook Development
This posting is provided "AS IS" with no warranties, and confers no rights


Eugene Burtsev said:
My outlook express can work, I have found the logging option simular
to MS Outlook and here are the results:

IMAP Log started at 12/14/2003 00:31:42

Microsoft Internet Messaging API 6.00.2800.1165
IMAP Log started at 12/14/2003 00:31:42
IMAP: 00:31:48 [db] Connecting to 'XXXXXXX.XXX' on port 143.
IMAP: 00:31:48 [db] OnNotify: asOld = 0, asNew = 4, ae = 0
IMAP: 00:31:48 [db] OnNotify: asOld = 4, asNew = 5, ae = 2
IMAP: 00:31:48 [db] OnNotify: asOld = 5, asNew = 5, ae = 4
IMAP: 00:31:48 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 00:31:48 [rx] * OK Courier-IMAP ready. Copyright 1998-2002
Double Precision, Inc. See COPYING for distribution information.
IMAP: 00:31:48 [tx] 000Y CAPABILITY
IMAP: 00:31:48 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 00:31:48 [rx] * CAPABILITY IMAP4rev1 CHILDREN NAMESPACE
THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT STARTTLS
IMAP: 00:31:48 [rx] 000Y OK CAPABILITY completed
IMAP: 00:31:48 [tx] LOGIN command sent
IMAP: 00:31:48 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 00:31:48 [rx] 000Z OK LOGIN Ok.
IMAP: 00:31:48 [tx] 0010 STATUS "INBOX" (MESSAGES UNSEEN)
IMAP: 00:31:48 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 00:31:48 [rx] * STATUS "INBOX" (MESSAGES 47 UNSEEN 0)
IMAP: 00:31:48 [rx] 0010 OK STATUS Completed.
IMAP: 00:31:48 [tx] Dropping connection, LOGOUT sent
IMAP: 00:31:48 [db] Connection to '' closed.
IMAP: 00:31:48 [db] OnNotify: asOld = 5, asNew = 0, ae = 5

I appreciate your help and would like to help anyway I can, if I can
run more diagnostic functions just ask.

Eugene

"Jeff Stephenson [MSFT]" <[email protected]> wrote in
message news: said:
If you're hitting the problem that I think you're hitting, Outlook Express
won't be able to connect to your server either. If Outlook Express *can*
connect to your server, I've misdiagnosed the problem and we need to
investigate further.

--
Jeff Stephenson
Outlook Development
This posting is provided "AS IS" with no warranties, and confers no rights


Thanks Jeff for giving me an idea as to what is going on, I was going
mad going over all of the settings, probably reinstalled Office 4
times and rechecked every letter in creation of the account more times
then I care to admit. I am deeply disappointed that I cannot use the
MS Outlook as I think Outlook by use is the most useful application in
Office. I had an understanding that I could count on Microsoft to be
compliant with the latest standards of the important protocols, and I
count IMAP one of them.

What I am curious about though is why can Outlook express support new
standard and MS Outlook not, if I can help in anyway in the
development of the component required please feel free to contact me
at (ms at burtsev dot com).

Thank you

Eugene

message It looks like you're encountering something I've been fearing.
Click to expand...
Click to expand...
The
IMAP
Click to expand...
server
to
Click to expand...
think,
is
Click to expand...
non-Microsoft
mail
Click to expand...
light
a
fire
under people - hopefully we'll get a good result.

Sorry you're hitting this :-(.

--
Jeff Stephenson
Outlook Development
This posting is provided "AS IS" with no warranties, and confers no
rights


Jeff Stephenson [MSFT]:

Could you turn on diagnostic logging (see
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q300479) and
post the OPMLog.log file after trying to receive?

Ok, this is pretty much is repeated with all accounts:

Microsoft Internet Messaging API 6.00.2800.1165
IMAP Log started at 12/09/2003 20:07:26
IMAP: 20:07:26 [db] Connecting to 'XXXXXXXX.com' on port 143.
IMAP: 20:07:26 [db] OnNotify: asOld = 0, asNew = 2, ae = 0
IMAP: 20:07:26 [db] srv_name = "XXXXXXX.com" srv_addr = 207.44.XXX.XXX
IMAP: 20:07:26 [db] OnNotify: asOld = 2, asNew = 3, ae = 1
IMAP: 20:07:26 [db] OnNotify: asOld = 3, asNew = 4, ae = 0
IMAP: 20:07:26 [db] OnNotify: asOld = 4, asNew = 5, ae = 2
IMAP: 20:07:26 [db] OnNotify: asOld = 5, asNew = 5, ae = 4
IMAP: 20:07:26 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:07:26 [rx] * OK Courier-IMAP ready. Copyright 1998-2002
Double Precision, Inc. See COPYING for distribution information.
IMAP: 20:07:26 [tx] 0001 CAPABILITY
IMAP: 20:07:26 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:07:26 [rx] * CAPABILITY IMAP4rev1 CHILDREN NAMESPACE
THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT STARTTLS
IMAP: 20:07:26 [rx] 0001 OK CAPABILITY completed
IMAP: 20:07:26 [tx] LOGIN command sent
IMAP: 20:07:31 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:07:31 [rx] 0004 NO Login failed.
IMAP: 20:07:31 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:07:49 [tx] LOGIN command sent
IMAP: 20:07:54 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:07:54 [rx] 0006 NO Login failed.
IMAP: 20:07:54 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:07:58 [tx] LOGIN command sent
IMAP: 20:08:03 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:08:03 [rx] 0008 NO Login failed.
IMAP: 20:08:03 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:08:06 [tx] LOGIN command sent
IMAP: 20:08:11 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:08:11 [rx] 0009 NO Login failed.
IMAP: 20:08:11 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:08:13 [tx] LOGIN command sent
IMAP: 20:08:18 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:08:18 [rx] 000B NO Login failed.
IMAP: 20:08:18 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:08:27 [db] Connection to '' closed.
IMAP: 20:08:27 [db] OnNotify: asOld = 5, asNew = 0, ae = 5

Here I gave up, otherwise I would be prompted again.

Just in case it's relevant here's my system:

OS Name Microsoft Windows XP Professional
Version 5.1.2600 Service Pack 1 Build 2600
OS Manufacturer Microsoft Corporation
System Name MAIN
System Manufacturer System Manufacturer
System Model System Name
System Type X86-based PC
Processor x86 Family 6 Model 6 Stepping 2 AuthenticAMD ~1666 Mhz
Processor x86 Family 6 Model 6 Stepping 2 AuthenticAMD ~1666 Mhz
BIOS Version/Date Award Software, Inc. ASUS A7M266-D ACPI BIOS
Revision 1010, 3/3/2003
SMBIOS Version 2.3
Windows Directory D:\WINDOWS
System Directory D:\WINDOWS\System32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "5.1.2600.1106
(xpsp1.020828-1920)"
User Name MAIN\Eugene
Time Zone Eastern Standard Time
Total Physical Memory 1,024.00 MB
Available Physical Memory 418.26 MB
Total Virtual Memory 3.40 GB
Available Virtual Memory 2.35 GB
Page File Space 2.40 GB
Page File D:\pagefile.sys


Well I hope this was all you needed, I appreciate your help.

-Eugene
Click to expand...
Click to expand...
Click to expand...
 
At the end I do not know what was the matter with my Outlook, I
desided to start over. I've completely formated my hard drive before
I've just reinstalled OS, and reinstalled everything I needed, outlook
works now. What was amaizing about my incident is that outlook was
doing everything perfect, just didn't athenticate. I've got an IMAP
emulation software and found that it was sending different password
then outlook express under the same conditions, can't say I was
surprized.

Jeff I appreciate everything that you have done for me, at the end it
turned out to be some conflict out of your field of experience, I am
sorry that I can not tell you exactly what it was. If I can help you,
just ask.

Take care,

Eugene

Jeff Stephenson said:
I'm back - let's see if we can get this figured out. Do you perhaps have
the "use Secure Password Authentication (SPA)" option checked in Outlook?
That might explain its behavior, as your IMAP server does not advertise a
secure login mechanism, so Outlook would not try the insecure LOGIN
authentication that OE is using.

--
Jeff Stephenson
Outlook Development
This posting is provided "AS IS" with no warranties, and confers no rights


Jeff Stephenson said:
Let's see if we can track this down, then. If OE can do it, there's no
reason that Outlook shouldn't be able to. I won't be able to get to this
for a few weeks, though - I'm heading out of town tomorrow, and won't be
back until Dec. 29th. If I haven't followed up by the first of the year,
post a gentle reminder ;-).

--
Jeff Stephenson
Outlook Development
This posting is provided "AS IS" with no warranties, and confers no rights


Eugene Burtsev said:
My outlook express can work, I have found the logging option simular
to MS Outlook and here are the results:

IMAP Log started at 12/14/2003 00:31:42

Microsoft Internet Messaging API 6.00.2800.1165
IMAP Log started at 12/14/2003 00:31:42
IMAP: 00:31:48 [db] Connecting to 'XXXXXXX.XXX' on port 143.
IMAP: 00:31:48 [db] OnNotify: asOld = 0, asNew = 4, ae = 0
IMAP: 00:31:48 [db] OnNotify: asOld = 4, asNew = 5, ae = 2
IMAP: 00:31:48 [db] OnNotify: asOld = 5, asNew = 5, ae = 4
IMAP: 00:31:48 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 00:31:48 [rx] * OK Courier-IMAP ready. Copyright 1998-2002
Double Precision, Inc. See COPYING for distribution information.
IMAP: 00:31:48 [tx] 000Y CAPABILITY
IMAP: 00:31:48 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 00:31:48 [rx] * CAPABILITY IMAP4rev1 CHILDREN NAMESPACE
THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT STARTTLS
IMAP: 00:31:48 [rx] 000Y OK CAPABILITY completed
IMAP: 00:31:48 [tx] LOGIN command sent
IMAP: 00:31:48 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 00:31:48 [rx] 000Z OK LOGIN Ok.
IMAP: 00:31:48 [tx] 0010 STATUS "INBOX" (MESSAGES UNSEEN)
IMAP: 00:31:48 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 00:31:48 [rx] * STATUS "INBOX" (MESSAGES 47 UNSEEN 0)
IMAP: 00:31:48 [rx] 0010 OK STATUS Completed.
IMAP: 00:31:48 [tx] Dropping connection, LOGOUT sent
IMAP: 00:31:48 [db] Connection to '' closed.
IMAP: 00:31:48 [db] OnNotify: asOld = 5, asNew = 0, ae = 5

I appreciate your help and would like to help anyway I can, if I can
run more diagnostic functions just ask.

Eugene

"Jeff Stephenson [MSFT]" <[email protected]> wrote in
Click to expand...
message news: said:
If you're hitting the problem that I think you're hitting, Outlook Express
won't be able to connect to your server either. If Outlook Express *can*
connect to your server, I've misdiagnosed the problem and we need to
investigate further.

--
Jeff Stephenson
Outlook Development
This posting is provided "AS IS" with no warranties, and confers no rights


Thanks Jeff for giving me an idea as to what is going on, I was going
mad going over all of the settings, probably reinstalled Office 4
times and rechecked every letter in creation of the account more times
then I care to admit. I am deeply disappointed that I cannot use the
MS Outlook as I think Outlook by use is the most useful application in
Office. I had an understanding that I could count on Microsoft to be
compliant with the latest standards of the important protocols, and I
count IMAP one of them.

What I am curious about though is why can Outlook express support new
standard and MS Outlook not, if I can help in anyway in the
development of the component required please feel free to contact me
at (ms at burtsev dot com).

Thank you

Eugene

"Jeff Stephenson [MSFT]" <[email protected]> wrote in
Click to expand...
message news: said:
It looks like you're encountering something I've been fearing.
Click to expand...
The
IMAP
standard was recently revised (in RFC 3501), and one of the things that
changed was the sorts of authentication mechanisms that are allowed.
Outlook can only authenticate using AUTH=LOGIN and AUTH=NTLM (a proprietary
authentication mechanism used by Microsoft). The AUTH=LOGIN
Click to expand...
mechanism
is
now disallowed in IMAP4rev1 compliant servers, and your server doesn't
support NTLM, so I don't see any way that you'll be able to get
Click to expand...
Outlook
to
authenticate to your server.

The possible solutions I see are:

1) See if your mail administrator is willing to configure the
Click to expand...
server
to
accept AUTH=LOGIN. While compliance to the Internet standards
Click to expand...
requires
that
a server *ship* with a default configuration that follows the
Click to expand...
standards,
it
doesn't forbid the server to be configurable in a other ways.
2) Try (just for laughs) checking the "use SSL" option on the
Click to expand...
Advanced
tab
of your account. It may be that the server supports SSL and will allow
AUTH=LOGIN over the secure SSL connection. (What it wants, I
Click to expand...
think,
is
AUTH=PLAIN after STARTTLS...)
3) If neither of the above work, you'll have to use a
Click to expand...
non-Microsoft
mail
client to connect to the server. I warned people here about this
Click to expand...
issue
when
the new standard was being drafted, but couldn't get anybody to
Click to expand...
commit
the
manpower to deal with it. Unfortunately, we in Outlook can't fix this
ourselves - the Windows component that we use to talk to IMAP
Click to expand...
servers
just
doesn't support what we'd need in order to work against an RFC 3501
compliant server. I've already sent this post out to try and
Click to expand...
light
a
fire
under people - hopefully we'll get a good result.

Sorry you're hitting this :-(.
Click to expand...
no
rights
Jeff Stephenson [MSFT]:

Could you turn on diagnostic logging (see
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q300479) and
post the OPMLog.log file after trying to receive?

Ok, this is pretty much is repeated with all accounts:

Microsoft Internet Messaging API 6.00.2800.1165
IMAP Log started at 12/09/2003 20:07:26
IMAP: 20:07:26 [db] Connecting to 'XXXXXXXX.com' on port 143.
IMAP: 20:07:26 [db] OnNotify: asOld = 0, asNew = 2, ae = 0
IMAP: 20:07:26 [db] srv_name = "XXXXXXX.com" srv_addr = 207.44.XXX.XXX
IMAP: 20:07:26 [db] OnNotify: asOld = 2, asNew = 3, ae = 1
IMAP: 20:07:26 [db] OnNotify: asOld = 3, asNew = 4, ae = 0
IMAP: 20:07:26 [db] OnNotify: asOld = 4, asNew = 5, ae = 2
IMAP: 20:07:26 [db] OnNotify: asOld = 5, asNew = 5, ae = 4
IMAP: 20:07:26 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:07:26 [rx] * OK Courier-IMAP ready. Copyright 1998-2002
Double Precision, Inc. See COPYING for distribution information.
IMAP: 20:07:26 [tx] 0001 CAPABILITY
IMAP: 20:07:26 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:07:26 [rx] * CAPABILITY IMAP4rev1 CHILDREN NAMESPACE
THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT STARTTLS
IMAP: 20:07:26 [rx] 0001 OK CAPABILITY completed
IMAP: 20:07:26 [tx] LOGIN command sent
IMAP: 20:07:31 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:07:31 [rx] 0004 NO Login failed.
IMAP: 20:07:31 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:07:49 [tx] LOGIN command sent
IMAP: 20:07:54 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:07:54 [rx] 0006 NO Login failed.
IMAP: 20:07:54 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:07:58 [tx] LOGIN command sent
IMAP: 20:08:03 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:08:03 [rx] 0008 NO Login failed.
IMAP: 20:08:03 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:08:06 [tx] LOGIN command sent
IMAP: 20:08:11 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:08:11 [rx] 0009 NO Login failed.
IMAP: 20:08:11 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:08:13 [tx] LOGIN command sent
IMAP: 20:08:18 [db] OnNotify: asOld = 5, asNew = 5, ae = 3
IMAP: 20:08:18 [rx] 000B NO Login failed.
IMAP: 20:08:18 [db] ERROR: "The server has rejected your login. Please
verify that your user name and password are correct.", hr=0x800CCCD1
IMAP: 20:08:27 [db] Connection to '' closed.
IMAP: 20:08:27 [db] OnNotify: asOld = 5, asNew = 0, ae = 5

Here I gave up, otherwise I would be prompted again.

Just in case it's relevant here's my system:

OS Name Microsoft Windows XP Professional
Version 5.1.2600 Service Pack 1 Build 2600
OS Manufacturer Microsoft Corporation
System Name MAIN
System Manufacturer System Manufacturer
System Model System Name
System Type X86-based PC
Processor x86 Family 6 Model 6 Stepping 2 AuthenticAMD ~1666 Mhz
Processor x86 Family 6 Model 6 Stepping 2 AuthenticAMD ~1666 Mhz
BIOS Version/Date Award Software, Inc. ASUS A7M266-D ACPI BIOS
Revision 1010, 3/3/2003
SMBIOS Version 2.3
Windows Directory D:\WINDOWS
System Directory D:\WINDOWS\System32
Boot Device \Device\HarddiskVolume1
Locale United States
Hardware Abstraction Layer Version = "5.1.2600.1106
(xpsp1.020828-1920)"
User Name MAIN\Eugene
Time Zone Eastern Standard Time
Total Physical Memory 1,024.00 MB
Available Physical Memory 418.26 MB
Total Virtual Memory 3.40 GB
Available Virtual Memory 2.35 GB
Page File Space 2.40 GB
Page File D:\pagefile.sys


Well I hope this was all you needed, I appreciate your help.

-Eugene
Click to expand...
Click to expand...
Click to expand...
 
Back
Top