![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Search this Thread | Display Modes |
|
#1
|
|||
|
|||
![]()
The Outlook 2007 Beta 2 client is giving the 0x800CCC80 "None of the
authentication methods supported by this client are supported by your server" error message when sending for an IMAP configuration running on Windows Vista Beta 2. Is there an enhanced security setting I am missing with the Outlook 2007 client or perhaps with Windows Vista that is preventing messages from being sent? ADDITIONAL INFO: Residential high speed Internet via Cox cable requires the use of their SMTP server for all outgoing SMTP traffic so I use my incoming IMAP server and Cox's outgoing SMTP server. I specify the appropriate credentials for my incoming IMAP server and the appropriate credentials on the Outgoing Server tab for the Cox SMTP server. I've Google'd the error code and didn't get anything useful. The identical configuration works perfectly under Windows XP / Outlook XP (2002) and with Windows Vista / Windows Mail (default email client in Vista). I've configured the email account slowly several times in Outlook 2007 to make sure I was not typing any of the info incorrectly. It seems to be a security "feature" or other setting in Outlook 2007 or Windows Vista that is preventing the connection/authentication. Or perhaps the Cox SMTP server does not recognize commands coming from these Beta products. Thanks for your input and suggestions. Wayne |
#2
|
|||
|
|||
![]()
Out of curiosity I disabled (unchecked) "My outgoing server (SMTP) requires
authentication" on the Outgoing Server tab and that resolved the problem. It appears Cox no longer requires authentication when using their SMTP server for outgoing email with a non-Cox email address. I've confirmed it with Windows XP Pro SP2 / Outlook XP (2002) as well. The only mystery now is why I get an error message when enabling authentication and specifying my Cox credentials for outgoing email in Outlook 2007 and no error message when doing the same with Outlook XP (2002)??? I'm glad it works now, but I have a compulsive need to know why and what the difference is with the new Outlook 2007 client!!! Any additional comments or suggestions are welcome. "Wayne Abruzzo" wrote in message ... The Outlook 2007 Beta 2 client is giving the 0x800CCC80 "None of the authentication methods supported by this client are supported by your server" error message when sending for an IMAP configuration running on Windows Vista Beta 2. Is there an enhanced security setting I am missing with the Outlook 2007 client or perhaps with Windows Vista that is preventing messages from being sent? ADDITIONAL INFO: Residential high speed Internet via Cox cable requires the use of their SMTP server for all outgoing SMTP traffic so I use my incoming IMAP server and Cox's outgoing SMTP server. I specify the appropriate credentials for my incoming IMAP server and the appropriate credentials on the Outgoing Server tab for the Cox SMTP server. I've Google'd the error code and didn't get anything useful. The identical configuration works perfectly under Windows XP / Outlook XP (2002) and with Windows Vista / Windows Mail (default email client in Vista). I've configured the email account slowly several times in Outlook 2007 to make sure I was not typing any of the info incorrectly. It seems to be a security "feature" or other setting in Outlook 2007 or Windows Vista that is preventing the connection/authentication. Or perhaps the Cox SMTP server does not recognize commands coming from these Beta products. Thanks for your input and suggestions. Wayne |
#3
|
|||
|
|||
![]()
I would almost say that Outlook 2007 is stricter than 2003 about SMTP
authentication. It could be the case that 2003 tried automatically to connect without authentication when authentication failed, while 2007 throws an error. Throwing an authentication error is a better approach from a security point of view. Patrick Schmid -------------- http://pschmid.net "Wayne Abruzzo" wrote in message : Out of curiosity I disabled (unchecked) "My outgoing server (SMTP) requires authentication" on the Outgoing Server tab and that resolved the problem. It appears Cox no longer requires authentication when using their SMTP server for outgoing email with a non-Cox email address. I've confirmed it with Windows XP Pro SP2 / Outlook XP (2002) as well. The only mystery now is why I get an error message when enabling authentication and specifying my Cox credentials for outgoing email in Outlook 2007 and no error message when doing the same with Outlook XP (2002)??? I'm glad it works now, but I have a compulsive need to know why and what the difference is with the new Outlook 2007 client!!! Any additional comments or suggestions are welcome. "Wayne Abruzzo" wrote in message ... The Outlook 2007 Beta 2 client is giving the 0x800CCC80 "None of the authentication methods supported by this client are supported by your server" error message when sending for an IMAP configuration running on Windows Vista Beta 2. Is there an enhanced security setting I am missing with the Outlook 2007 client or perhaps with Windows Vista that is preventing messages from being sent? ADDITIONAL INFO: Residential high speed Internet via Cox cable requires the use of their SMTP server for all outgoing SMTP traffic so I use my incoming IMAP server and Cox's outgoing SMTP server. I specify the appropriate credentials for my incoming IMAP server and the appropriate credentials on the Outgoing Server tab for the Cox SMTP server. I've Google'd the error code and didn't get anything useful. The identical configuration works perfectly under Windows XP / Outlook XP (2002) and with Windows Vista / Windows Mail (default email client in Vista). I've configured the email account slowly several times in Outlook 2007 to make sure I was not typing any of the info incorrectly. It seems to be a security "feature" or other setting in Outlook 2007 or Windows Vista that is preventing the connection/authentication. Or perhaps the Cox SMTP server does not recognize commands coming from these Beta products. Thanks for your input and suggestions. Wayne |
#4
|
|||
|
|||
![]()
I am using SBC DSL and have run into same situation. By unchecking "My
outgoing server ....." I too had a positive result. I can now send out e-mail. "Wayne Abruzzo" wrote: Out of curiosity I disabled (unchecked) "My outgoing server (SMTP) requires authentication" on the Outgoing Server tab and that resolved the problem. It appears Cox no longer requires authentication when using their SMTP server for outgoing email with a non-Cox email address. I've confirmed it with Windows XP Pro SP2 / Outlook XP (2002) as well. The only mystery now is why I get an error message when enabling authentication and specifying my Cox credentials for outgoing email in Outlook 2007 and no error message when doing the same with Outlook XP (2002)??? I'm glad it works now, but I have a compulsive need to know why and what the difference is with the new Outlook 2007 client!!! Any additional comments or suggestions are welcome. "Wayne Abruzzo" wrote in message ... The Outlook 2007 Beta 2 client is giving the 0x800CCC80 "None of the authentication methods supported by this client are supported by your server" error message when sending for an IMAP configuration running on Windows Vista Beta 2. Is there an enhanced security setting I am missing with the Outlook 2007 client or perhaps with Windows Vista that is preventing messages from being sent? ADDITIONAL INFO: Residential high speed Internet via Cox cable requires the use of their SMTP server for all outgoing SMTP traffic so I use my incoming IMAP server and Cox's outgoing SMTP server. I specify the appropriate credentials for my incoming IMAP server and the appropriate credentials on the Outgoing Server tab for the Cox SMTP server. I've Google'd the error code and didn't get anything useful. The identical configuration works perfectly under Windows XP / Outlook XP (2002) and with Windows Vista / Windows Mail (default email client in Vista). I've configured the email account slowly several times in Outlook 2007 to make sure I was not typing any of the info incorrectly. It seems to be a security "feature" or other setting in Outlook 2007 or Windows Vista that is preventing the connection/authentication. Or perhaps the Cox SMTP server does not recognize commands coming from these Beta products. Thanks for your input and suggestions. Wayne |
#6
|
|||
|
|||
![]()
I am having exactly the same problems. I am working with a university server
- worked fine before the beta version, can send but not receive emails. Have tried with SSL connection, created new account, run diagnostics - no help "Wayne Abruzzo" wrote: The Outlook 2007 Beta 2 client is giving the 0x800CCC80 "None of the authentication methods supported by this client are supported by your server" error message when sending for an IMAP configuration running on Windows Vista Beta 2. Is there an enhanced security setting I am missing with the Outlook 2007 client or perhaps with Windows Vista that is preventing messages from being sent? ADDITIONAL INFO: Residential high speed Internet via Cox cable requires the use of their SMTP server for all outgoing SMTP traffic so I use my incoming IMAP server and Cox's outgoing SMTP server. I specify the appropriate credentials for my incoming IMAP server and the appropriate credentials on the Outgoing Server tab for the Cox SMTP server. I've Google'd the error code and didn't get anything useful. The identical configuration works perfectly under Windows XP / Outlook XP (2002) and with Windows Vista / Windows Mail (default email client in Vista). I've configured the email account slowly several times in Outlook 2007 to make sure I was not typing any of the info incorrectly. It seems to be a security "feature" or other setting in Outlook 2007 or Windows Vista that is preventing the connection/authentication. Or perhaps the Cox SMTP server does not recognize commands coming from these Beta products. Thanks for your input and suggestions. Wayne |
#7
|
|||
|
|||
![]()
Ha! Now sorted - problem was, surprise surprise, Norton Internet Security.
Had to disable ALL email scanning features as Norton does not support SSL scanning - quite why this was not an issue with Outlook 2003 I've no idea, but following Norton's guide to disable all email scanning has solved the issue. "rmlindley" wrote: I am having exactly the same problems. I am working with a university server - worked fine before the beta version, can send but not receive emails. Have tried with SSL connection, created new account, run diagnostics - no help "Wayne Abruzzo" wrote: The Outlook 2007 Beta 2 client is giving the 0x800CCC80 "None of the authentication methods supported by this client are supported by your server" error message when sending for an IMAP configuration running on Windows Vista Beta 2. Is there an enhanced security setting I am missing with the Outlook 2007 client or perhaps with Windows Vista that is preventing messages from being sent? ADDITIONAL INFO: Residential high speed Internet via Cox cable requires the use of their SMTP server for all outgoing SMTP traffic so I use my incoming IMAP server and Cox's outgoing SMTP server. I specify the appropriate credentials for my incoming IMAP server and the appropriate credentials on the Outgoing Server tab for the Cox SMTP server. I've Google'd the error code and didn't get anything useful. The identical configuration works perfectly under Windows XP / Outlook XP (2002) and with Windows Vista / Windows Mail (default email client in Vista). I've configured the email account slowly several times in Outlook 2007 to make sure I was not typing any of the info incorrectly. It seems to be a security "feature" or other setting in Outlook 2007 or Windows Vista that is preventing the connection/authentication. Or perhaps the Cox SMTP server does not recognize commands coming from these Beta products. Thanks for your input and suggestions. Wayne |
#8
|
|||
|
|||
![]()
I also have had this problem
Was with POP3 I unloaded Norton’s Virus Scan Service and email immediately was able to be sent. I am using Symantec Antivirus Corporate Edition 2005 (v10) I loaded the service again after the email was sent. Oddly even though I am not using Microsoft Exchange by disabling Microsoft Exchange Auto Protection in Symantec the problem went away and outgoing emails are immediate. |
#9
|
|||
|
|||
![]()
MS Exchange Auto Protection is a misnomer. Outlook is meant with it.
Patrick Schmid -------------- http://pschmid.net "Ian" wrote in message : I also have had this problem Was with POP3 I unloaded Norton's Virus Scan Service and email immediately was able to be sent. I am using Symantec Antivirus Corporate Edition 2005 (v10) I loaded the service again after the email was sent. Oddly even though I am not using Microsoft Exchange by disabling Microsoft Exchange Auto Protection in Symantec the problem went away and outgoing emails are immediate. |
#10
|
|||
|
|||
![]()
Ian wrote:
I also have had this problem Was with POP3 I unloaded Norton’s Virus Scan Service and email immediately was able to be sent. I am using Symantec Antivirus Corporate Edition 2005 (v10) As has been posted countless times in this and the other Outlook newsgroups, one should always disable antivirus mail scanning. -- Brian Tillman |
|
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Error 0X90040605 profile error Outlook 2007 Beta2 | Paul Z | Outlook - Installation | 2 | July 10th 06 04:23 PM |
How Outlook 2007 Beta handles IMAP? | Charles Leung | Outlook - General Queries | 5 | June 18th 06 09:30 AM |
2007 Beta 2: IMAP certificate issues | Kenneth Stevenson | Outlook - Installation | 1 | June 14th 06 08:03 PM |
Outlook 2007 Public Beta 2 - 0x80040102 Error on Send/Receive | n1ckn4m3 | Outlook - Installation | 10 | June 13th 06 03:59 PM |
IMAP and 2007 Outlook | EastAsia | Outlook - General Queries | 8 | May 26th 06 03:34 PM |