Protocol Error Unidentifiable Command
BMO. For more details see Persona Deprecated. Last Comment Bug357284 - Pointless IMAP protocol error alerts, "The current command did not succeed ... Protocol Error: "Unidentifiable command specified" to two commands, "getacl" and "myrights". Mirapoint Proxy looks to return ACL even though real MAP server doesn't return ACL. Summary: Pointless IMAP protocol error alerts, "The current command did not succeed ..... Status: NEW Whiteboard: Keywords: Product: Thunderbird Classification: Client Software Component: General (show other bugs) Version: Trunk Platform: All All Importance: -- minor (vote) TargetMilestone: --- Assigned To: Nobody; OK to take it and work on it QA Contact: TriageOwner: Mentors: URL: Depends on: 564642 Blocks: Show dependency tree /graph Reported: 2006-10-19 08:36 PDT by Kenneth Herron Modified: 2011-02-22 03:42 PST (History) CC List: 6 users (show) Bruno.Harbulot jwalden+bmo m-wada shopik terry vseerror See Also: Crash Signature: (edit) QA Whiteboard: Iteration: --- Points: --- Tracking Flags: Attachments Sample protocol log (101.83 KB, text/plain) 2006-10-19 08:38 PDT, Kenneth Herron no flags Details Sample alert (8.55 KB, image/gif) 2006-10-19 08:39 PDT, Kenneth Herron no flags Details View All Add an attachment (proposed patch, testcase, etc.) Description Kenneth Herron 2006-10-19 08:36:55 PDT I first experienced this with TB 1.5.0.x. I've just updated to a nightly trunk build and it still occurs. For my corporate email I connect to a Mirapoint IMAP proxy which connects to a backend server. The backend was migrated a few months ago to MS Exchange. Since then, every time TB accesses a folder--including inbox--for the first time after being started, I get two annoying modal alerts about IMAP protocol errors. Typical behavior is as follows: 1) Start TB. It displays a (cached?) copy of my IMAP folder list and a (cached) list of INBOX messages in the message list. Then an alert displays: "The current command did not succeed. The mail server responded: Protocol Error: "Unidentifiable command specified"... This is a modal window so TB stops processing. 2) Click "OK" to dismiss the alert. An identical alert reappears. 3) Click "OK" on the second alert. TB finishes starting up, but doesn't display any new contents of INBOX. 4) Click on another folder. TB displays the old (cached?) contents of the folder, then the same two alerts appear and have to be dismissed. Any new contents of the folder are not displayed. 5) Click on the Inbox folder. The folder contents display normally, including any new messages. 6) Click on the folder from step 4
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20132010Other VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: IMAP Credentials to Exchange Exchange Server > Exchange Server 2013 - Outlook, OWA, POP, and IMAP Clients Question 0 Sign in to vote Hi all, I'm trying to migrate an Exchange 2003 box to Office 365 via IMAP. I enabled the IMAP service and ran Test-MigrationServerAvailability -IMAP -Port 143 successfully. However, I'm getting authentication issues. After Telneting into the server I have ran the login https://bugzilla.mozilla.org/show_bug.cgi?id=357284 commands with every possible credential combination I have seen IMAP responds to: login contoso\user Password --> "Unidentifiable command specified" a1 login contoso\user Password --> BAD Protocol Error: "Expected SPACE not found" The one that seems to be pointing to the right direction is: http://support.microsoft.com/kb/189326/en-au ?login contoso/user/mailbox Password --> a1 NO Logon Failure: unknown user name or bad password https://social.technet.microsoft.com/Forums/office/en-US/33d0e3b4-1ceb-4be6-9c23-fb669cc7ae59/imap-credentials-to-exchange?forum=exchangesvrclients Apparently, the convention is domain/user_name/mailbox_name Password --> But I'm having no love here :( Thanks guys Thursday, August 07, 2014 6:38 AM Reply | Quote Answers 0 Sign in to vote Thanks for your suggestion QuanGD however this is a small company and perform a staged migration is not an option for them. BTW: I managed to solve the problem. It was a silly overlook by me as the server is a very old box migrated from Server 2000 and didn't have the user logon name populated but only the (pre-Windows2000 name). Finally I managed to Telnet into it via 143and can migrate the data via IMAP. Thanks. Marked as answer by Mavis_HuangMicrosoft contingent staff, Moderator Thursday, August 14, 2014 4:44 AM Tuesday, August 12, 2014 2:32 AM Reply | Quote All replies 0 Sign in to vote Hi, I suggest upgrading Exchange 2010 from 2003 first, then migrate to Office 365. Also suggest ask Office 365 forum for help. Link: http://community.office365.com/en-us/f/default.aspx Thanks Monday, August 11, 2014 7:26
a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to https://www.experts-exchange.com/questions/23121135/Testing-IMAP-connectivity.html Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Courses Vendor Services Groups Careers Store Headlines Website Testing Experts Exchange > Questions > Testing IMAP connectivity Want to Advertise Here? http://forums.gfi.com/m900738358-print.aspx Solved Testing IMAP connectivity Posted on 2008-01-29 Windows Server 2003 Exchange 1 Verified Solution 18 Comments 2,001 Views Last Modified: 2011-04-29 Would like to use secure IMAP for Blackberry but having trouble getting it to protocol error work. Testing IMAP locally on port 143 and 993. Below is the log I get when I try to connect ON PORT 143: * OK Microsoft Exchange Server 2003 IMAP4rev1 server version 6.5.7638.1 (Phoenix.Ungerfabrik.local) ready. login bbimap Blackxx login BAD Protocol Error: "Unidentifiable command specified". ON PORT 993: SSL handshake has read 3951 bytes and written 300 bytes --- New, TLSv1/SSLv3, Cipher is RC4-MD5 Server public key is 1024 bit SSL-Session: protocol error unidentifiable Protocol : TLSv1 Cipher : RC4-MD5 Session-ID: 550F0000C9035406ADA10A318A9EEABC9A4FFFA50034045019D36E28FA528DBE Session-ID-ctx: Master-Key: 3B8D0A0B67C02DD4282686308B9B64F09A29771E2168D1EB285CABACE5177A4FDDDBF7879ECAFB5158063BF25708CC76 Key-Arg : None Start Time: 1201645639 Timeout : 300 (sec) Verify return code: 20 (unable to get local issuer certificate) --- * OK Microsoft Exchange Server 2003 IMAP4rev1 server version 6.5.7638.1 (Phoenix.Ungerfabrik.local) ready. login bbimap Black15 * BAD Protocol Error: "Command received without terminating
public folder scanning, error is the one following: The IMAP test failed for the following reason: Could not connect to