Microsoft KB Archive/249408: Difference between revisions

From BetaArchive Wiki
(importing KB archive)
 
m (Text replacement - """ to """)
 
(One intermediate revision by the same user not shown)
Line 63: Line 63:
== MORE INFORMATION ==
== MORE INFORMATION ==


In this scenario, the server should return the &quot;BAD&quot; response, which indicates that the argument is invalid.<br />
In this scenario, the server should return the "BAD" response, which indicates that the argument is invalid.<br />
<br />
<br />
Here are the results you get when you connect to Microsoft Commercial Internet System and Exchange 2000:
Here are the results you get when you connect to Microsoft Commercial Internet System and Exchange 2000:
<pre class="fixed_text">  D:\&gt;tcp MCIS imap4
<pre class="fixed_text">  D:\>tcp MCIS imap4
   * OK mcis.com Microsoft IMAP4Rev1 Server ready at Thu, 16 Mar 2000 19:03:15 -0
   * OK mcis.com Microsoft IMAP4Rev1 Server ready at Thu, 16 Mar 2000 19:03:15 -0
   800 Version: 5.5.1877.377.37
   800 Version: 5.5.1877.377.37
Line 72: Line 72:
   0001 BAD LOGIN Invalid userid argument
   0001 BAD LOGIN Invalid userid argument
                 </pre>
                 </pre>
<pre class="fixed_text">  D:\&gt;tcp EX2000 imap4
<pre class="fixed_text">  D:\>tcp EX2000 imap4
   * OK Microsoft Exchange IMAP4rev1 server version Exchange 2000.4208.3    (EX2000.com) ready.
   * OK Microsoft Exchange IMAP4rev1 server version Exchange 2000.4208.3    (EX2000.com) ready.
   0001 login {}
   0001 login {}

Latest revision as of 12:51, 21 July 2020

Knowledge Base


XFOR: Exchange 2000 Server Accepts NULL Literal String During Internet Message Access Protocol (IMAP) Session

Article ID: 249408

Article Last Modified on 2/26/2007



APPLIES TO

  • Microsoft Exchange 2000 Server Standard Edition



This article was previously published under Q249408


SYMPTOMS

During an IMAP session, when a client sends a literal string where the argument of the login command is NULL, Exchange 2000 accepts the value as a valid entry, and continues to process the next command.

STATUS

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.

MORE INFORMATION

In this scenario, the server should return the "BAD" response, which indicates that the argument is invalid.

Here are the results you get when you connect to Microsoft Commercial Internet System and Exchange 2000:

   D:\>tcp MCIS imap4
   * OK mcis.com Microsoft IMAP4Rev1 Server ready at Thu, 16 Mar 2000 19:03:15 -0
   800 Version: 5.5.1877.377.37
   0001 login {}
   0001 BAD LOGIN Invalid userid argument
                
   D:\>tcp EX2000 imap4
   * OK Microsoft Exchange IMAP4rev1 server version Exchange 2000.4208.3    (EX2000.com) ready.
   0001 login {}
   + Ready for additional command text.
                

Keywords: kbinfo kbinterop KB249408