Outlook 2007: None of the Authentication Methods Supported By This Client Are Supported By Your Server

Can’t send from certain locations and keep having to turn on/off outgoing server SMTP Authentication in outlook 2007? You might see this error too: “None of the Authentication Methods Supported By This Client Are Supported By Your Server

My Answer: Goto Email Accounts, Change the problem account, More Settings, Outgoing Server tab, and check outgoing server require authentication and choose “Log on to incoming mail server before sending mail” instead of “Use same settings as incoming” – Outlook 2007 is the first and only mail program to require any of our mail servers to use this setting. So far I’ve only confirmed the problem to be on older sendmail servers. There can be other solutions to this error message but this is one I find most often resolves it.

The Question: As a systems administrator I take calls for our tech support queue and one user called with a really odd problem. Basically it’s detailed here:


Like the above link describes the user would have to disable SMTP auth in certain locations (That’s a workaround, not the solution), even though all our servers require SMTP authentication. The above link eventually shares the true solution but it’s buried under many comments thanking the poster for the work around. So I decided to help fellow googlers by making this post.

Update: Comments about other people’s experience with this error made me want to add my further experience with it. I’ve seen this error a lot more often since I first made this post and am convinced it’s really some sort of bug with Outlook 2007. Some people cannot get rid of the error and have to continually switch between “Log on to incoming mail server before sending mail” and “Use same settings as incoming” to keep outlook sending correctly. Whereas if they switch to Windows Mail (The Vista and Windows 7 equivalent of outlook express) they never need to do anything but set ‘use same settings as incoming’ and never have any problem sending. If it’s not a ’2007 Bug’ then it’s definitely a Outlook 2007 incompatibility with certain MTAs – specifically (maybe just older) sendmail – our postfix servers don’t seem to have this bug, but like I just said only 2007 has this incompatibility so you can’t entirely blame sendmail.

Be Sociable, Share!
  • Google Reader
  • HackerNews
  • Reddit
  • email
  • StumbleUpon
  • Delicious
  • Posterous

33 thoughts on “Outlook 2007: None of the Authentication Methods Supported By This Client Are Supported By Your Server

  1. This seems to be just badly written error message by MS.

    We solved it by fixing a simple authentication problem – typo in outgoing mail server name – which should have just produced an “authentication failed” message.

    Instead it gave this weird message!

  2. I followed the instructions from the settings tab in Gmail. I could retrieve but not send email from my Outlook client. The port for outgoing was set to 587 per Gmail’s instructions.

    I used telnet command: telnet pop.gmail.com 587

    I received the same error. So my new Windows 7 machine was blocking the port. I added a new rule at the Firewall to allow this port. Now Outlook 2007 can receive and send email.

  3. This fix works with Outlook 2010 Beta as well!
    The beta comes with port settings on 587 for encrypted
    connections and settings as above for outgoing email.
    My POP3 server will only accept them on port 25 and
    when the settings are exactly as above it works perfectly.
    This was a really easy fix, thanks a lot. I looked everywhere
    for some reference to this problem for the 2010 beta but just
    couldn’t get an answer. Thanks again!

  4. Thanks for this. Everything was fine the last couple of months since I set up the new computer and then suddenly… this bizarre message. Your fix fixed it! Really appreciate it, instead of all the doublespeak on other sites.

  5. I just came across this problem for a client. They are using port 2525 for outgoing mail, and are required to authenticate to their POP3 server.

    I tried all combinations of turning off/on various ways of authenticating and whether to use encryption or not.

    In the end, I just ran MS Update and patched everything to the current level. That has resolved the issue with no need to change any settings.

    Maybe MS finally has a fix out for it.

  6. Ladies and Gentleman, the error mentioned above is also cause if either your ip address issued by your provider is spamming, spamhous.com picks up this address and block all outgoing email resulting in this error, the only work around in this case is either to reset the ip address by shutting down your router for sometime, or by using another user id to reset the ip address.

    In the above case, even if you set the protocol to “log before sending”, the email will go from your outbox, but will bounce back to you again.

    Regarding port 587 and 25, port 25 is normally used by spammers for spamming, using port 587 will help in sending emails, provided your email service providers, has enabled this port

    • I strongly disagree because in my experience spam problems get bounce back emails notifying you of your IP’s blacklisting – not outlook errors like this. The latter part about ports is a legitimate point though.

  7. Just want to say that I tried say I tried your fix and didn’t seem to work for me; however, going back to “Change Email Account”, I unchecked “Require logon using using Secure Password Authentication (SPA)” and clicked on Test Account Settings and that worked for me.

  8. An IT friend of mine mentioned that Outlook 2007 is known to have sending issues over WIFI. I just had a customer plug in via ethernet and the problem was solved. When she goes back to wifi it acts up again.


  9. ran across the first issue on a new machine I was setting up to use Outlook from Time Warner POP accounts. Solution worked well. Thank You for the posting…

  10. thanks.. it gave me an idea…
    however it did not work for my cx …
    we’re using msn.com for outgoing and then another email domain for cx’s incoming…

    able to receive, but not able to send a message
    port 25 is not filtered

  11. “Log on to incoming mail server before sending mail” fixed it for me, too. Using Microsoft Office Home & Business 2010 (32-bit) on Windows 7 (64 bit). Thank you, Diginc.

  12. It’s frustrating how many posts on this subject are from non-technical authors (even on Technet) and/or from folks with “me too” or “this didn’t work for me, try this” comments. My company is in a weird position where we have to receive email via one email platform and send out via another – a hybrid position necessitated by a bungled roll-out of an inadequately tested email solution by one of our ISPs (BT).

    Anyway, as far as I can tell, it looks like MS changed the way it implemented SMTP AUTH in Outlook 2007. This change has been carried over into Outlook 2010. Outlook 2010 tries to encode credentials with MD5 or better. When I query BT’s servers, this is what I see:

    [root]# telnet mail.btconnect.com 25
    Connected to mail.btconnect.com.
    Escape character is '^]'.
    220 mail.btconnect.com ESMTP
    ehlo eel.co.uk
    250-mail.btconnect.com Hello eel.co.uk
    250-SIZE 52428800

    The mail server is only offering LOGIN or PLAIN and Outlook apparently isn’t prepared to stoop so low. Furthermore, from what I’ve read, DIGEST-MD5 authentication was broken in Outlook 2007 in any case and remains so in Outlook 2010.

    Most solutions out there depend on using POP before SMTP for implicit authentication but since our POP and SMTP servers are physically separate (provided by different organisations in fact), this is not an option for us. Ironically the “fix” would appear to be to downgrade to Windows Live Mail (or Thunderbird), but given the size of our I.T. estate, that would be a mammoth project.

    I’m still waiting for a proper fix in Outlook, but since no one seems to understand the SMTP RFCs any more, I’m not going to be holding my breath. We just have to live with the fact that the leading email client (for better or worse) has introduced incompatibilities with legacy systems.


Leave a Reply