Pop3 Protocol Error 16
Contents |
5 hours Powered by phpBB Forum Software © phpBB Group
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up POP3 netcat protocol error up vote 0 https://www.mantisbt.org/forums/viewtopic.php?f=13&t=21525 down vote favorite I tried to connect to my POP3 school server as part of my assignment. Now, I can connect to the server but the real problem is when I try to log in using the "USER" command. c:/>nc server.pop3.com 110 +OK Microsoft Exchange Server 2003 POP3 server version 6.5.7638.1 (server.pop3.com) ready. USER myuserid -ERR Protocol error Now I'm wondering whether there's an issue on my http://stackoverflow.com/questions/2433574/pop3-netcat-protocol-error side or on the server? Thank you for the time and answers. pop3 netcat share|improve this question asked Mar 12 '10 at 15:04 user292419 add a comment| 2 Answers 2 active oldest votes up vote 1 down vote Exchange expects a CRLF as line termination. Use netcat -C servername pop3 share|improve this answer answered Jun 10 '11 at 8:31 Dr. Tilo Levante 111 add a comment| up vote 0 down vote Use CAPA command just after connection. You'll see what login mechanisms are supported. Exchange usually does not allow clear text mechanisms. Most likely you'll be forced to use SSL+plain text, or APOP login mechanism. share|improve this answer edited Apr 16 '10 at 10:20 answered Apr 16 '10 at 10:03 Pawel Lesnikowski 4,82132735 I'm having the same problem as the original poster. Trying CAPA as the first command also gives '-ERR Protocol error'. –Andreas Jansson May 13 '10 at 11:57 Try connecting using SSL. –Pawel Lesnikowski May 13 '10 at 16:58 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Na
Exchange POP3 access doesn't works... Ask a Question Sign up for Free 141 Experts currently online. Ask Questions for Free! POP3 access doesn't works... - Microsoft http://www.textndata.com/forums/pop3-access-doesnt-works-123302.html Exchange Hi, I'm trying to access my exchange server 2003 with the https://forums.embarcadero.com/message.jspa?messageID=651939 POP3 protocol, but I allways received a logon error "-ERR Protocol error" with the telnet command line, I can reach the server, but I can't be authenticated ! any idea of the problem ? thanks. Jerome.... Results 1 to 5 of 5 LinkBack LinkBack URL About LinkBacks Bookmark & Share protocol error Add Thread to del.icio.usTweet this thread Thread Tools Show Printable Version Email this Page… Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 10-25, 08:55 PM #1 POP3 access doesn't works... Hi, I'm trying to access my exchange server 2003 with the POP3 protocol, but I allways received a logon error "-ERR pop3 protocol error Protocol error" with the telnet command line, I can reach the server, but I can't be authenticated ! any idea of the problem ? thanks. Jerome. Jéjé Reply With Quote 10-26, 01:29 AM #2 Re: POP3 access doesn't works... Make sure the user has been enabled for POP3 and the password is correct. -- This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples (if any) are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm * Please do not send e-mail directly to this alias. This alias is for newsgroup purposes only "Jéjé"
Exchange authtype SASL This question is not answered. Helpful answers available: 2. Correct answers available: 1. Reply to this Thread Search Forum Back to Thread List Replies: 10 - Last Post: Jun 19, 2014 7:00 PM Last Post By: Remy Lebeau (Te... Lukasz Rewak Posts: 15 Registered: 6/10/04 REGRESSION! XE6 idPOP3 Protocol error 16 connect to Exchange authtype SASL Reply Posted: May 8, 2014 7:55 PM error , indy , xe6 , idpop3 , sasl , ssl , exchange Hi, Have a major problem with Dephi XE6. Below code has been tested and working fine on XE3 and XE5 - but fails on XE6! Trying to retrieve emails from a hosted Microsoft Exchange POP3 service (I believe its Exchange 2010). It however works with gmail for example. var IdPOP3: TIdPOP3; SSLHandler: TIdSSLIOHandlerSocketOpenSSL; IdUserPassProvider: TIdUserPassProvider; IdSASLLogin: TIdSASLLogin; IdSASLPlain: TIdSASLPlain; begin IdPOP3 := TIdPOP3.Create(Application); IdPOP3.Host := 'exchange.hosted.com'; IdPOP3.Port := 995; IdPOP3.UserName := 'test@hosted.com'; IdPOP3.Password := '12345'; SSLHandler := TIdSSLIOHandlerSocketOpenSSL.Create(idPOP3); SSLHandler.SSLOptions.Method := sslvTLSv1_2; IdPOP3.IOHandler := SSLHandler; IdPOP3.UseTLS := utUseImplicitTLS; IdPOP3.AuthType := patSASL; IdUserPassProvider := TIdUserPassProvider.Create(IdPOP3); IdUserPassProvider.Username := IdPOP3.UserName; IdUserPassProvider.Password:= IdPOP3.Password; IdSASLPlain := TIdSASLPlain.Create(idPOP3); IdSASLPlain.UserPassProvider := IdUserPassProvider; idPOP3.SASLMechanisms.Add.SASL := IdSASLPlain; IdPOP3.Connect; MessageDlg(IntToStr(IdPOP3.CheckMessages) + ' Messages Found!', mtInformation, [mbOK], 0); Stack trace fails on IdSASLCollection.TIdSASLEntries.LoginSASL Exception class EIdReplyPOP3Error with message 'Protocol error. 16 '. I can see in the Indy source code that there were numerous changes to SASL authentication, which might have caused the errors. Thanks, Lukasz Remy Lebeau (Te... Posts: 6,726 Registered: 12/23/01 Re: REGRESSION! XE6 idPOP3 Protocol error 16 connect to Exchange authtypeSASL Reply Posted: May 9, 2014 6:03 PM in response to: Lukasz Rewak Lukasz wrote: I can see in the Indy source code that there were numerous changes to SASL authentication, which might have caused the errors. Those updates were made to add support for SASL's Initial-Response feature, which avoids some unnecessary