Exchange Pop3 Protocol Error 17
Contents |
Neal (Exclaimer) Sales & Marketing Manager GROUP SPONSORED BY EXCLAIMER See more RELATED PROJECTS Conniel Atham Muscle Booster Supplement Exchange 2003 Migration Exchange, pop3 protocol error 19 Anti Spam, MX, DNS SPF, Exchange Sync, Mimecast! ah! my set up pop3 command is not valid in this state 2008 r2 DC & ADC, 2013 Exchange on 2012. one web server, one file server, one backup server all on
Telnet Pop3 Protocol Error 19
2008 r2 TECHNOLOGY IN THIS DISCUSSION Microsoft Exchange Server 2010 Join the Community! Creating your account only takes a few minutes. Join Now Hello, I'm hoping the SpiceWorks gurus out there can
Telnet Pop3 Err Protocol Error. 19
assist with this head-scratcher... We have an application which requires the ability to log on to an e-mail box using POP3. POP3 logon worked ok on our 2007 Exchange, but now that I have moved the account to Ex2013, this is the first time I am trying POP3 and finding out it doesn't work. Upon connecting to port 110 (using PuTTY), I get the banner:+OK err command is not valid in this state The Microsoft Exchange POP3 service is ready. If I enter 'user xxxxx', the server responds immediately with:-ERR Protocol error 17.In fact, even after connecting, if I just press the enter key, I get -ERR Protocol error 17. I did a lot of Google searches, and none of the solutions people have posted have resolved it my case. Here's what I've done so far: 1.) Applied any updates, rebooted the server2.) Tested this logon at the Exchange Online web interface, success3.) Tested this logon with active directory, success4.) Set up POP3 for plain text logon, restarted POP3 services, terminal session still errors5.) No certificate warnings at the online exchange portal6.) user password is established, and does not need to be changed The user information seems to be irrelevant anyway, since even hitting the enter key gives this 'protocol error'.Anyone have any ideas on what else I can try to get this working? Reply Subscribe RELATED TOPICS: Exchange 2013 POP3 failing, it used to work Exchange 2013 error 1035 from 127.0.0.1 Exchange POP3   10 Replies Habanero OP JoeWilliams Feb 26, 2016 at 12:12 UTC EBS Computer Services is an IT service provider. Tr
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 Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > -ERR Protocol Error. 17 Want to Advertise Here? Solved -ERR Protocol Error. 17 Posted on 2010-05-19 Email Protocols Exchange 3 Verified Solutions 9 Comments 6,473 Views Last Modified: 2013-11-29 I hope someone https://community.spiceworks.com/topic/1464870-pop3-protocol-error-exchange-2013 can help. I need to have a application collect mail from Exchange 2010 via Pop3, i have followed the instructions at: http://www.msexchange.org/articles_tutorials/exchange-server-2007/mobility-client-access/using-pop3-imap4-access-exchange-2007-part1.html But wheneven i telnet to the server i get: +OK The Microsoft Exchange POP3 service is ready. user support -ERR Protocol error. 17 I get the same error no matter what i type in my telnet session. Does any one https://www.experts-exchange.com/questions/26197085/ERR-Protocol-Error-17.html know how to solve this? 0 Question by:Supportteam Facebook Twitter LinkedIn Google Best Solution bySupportteam OK, Sorted... For some reason when using Telnet the first response is always " -ERR Protocol error. 17" On top of that who ever set up the Support user left the account set as "user Go to Solution 9 Comments LVL 33 Overall: Level 33 Exchange 30 Email Protocols 6 Message Assisted Solution by:Busbar2010-05-19 do you have the correct SSL certificate setup. if you are using custom application I will suggest using plain text. from the powershell: set-popsettings - logintype plaintextlogin restart the pop3 service 0 Message Author Comment by:Supportteam2010-05-19 This may be the hurdle I fall at... I have loaded a GoDaddy cert for OWA & OutlookAnywhere reasons, i have assigned the "Post Office Protocol" service. This certificate is also assigned to the Default Web Site in IIS7. I have swapped the certificates arround between all configurations but it still seems to fail. I have also set Pop3 to Plain Text. 0 LVL 33 Overall: Level 33 Exchange 30 Email Protocols 6 Message Expert Comment by:Busbar2010-05-19 did you restart hte pop3 serv
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 https://www.experts-exchange.com/questions/28083232/Can't-get-e-mail-via-POP3-Exchange-2010.html to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Can't get e-mail via POP3 Exchange 2010 Want to Advertise Here? Solved Can't get e-mail via POP3 Exchange 2010 Posted on 2013-04-01 Exchange 1 Verified Solution 16 Comments 3,358 Views Last Modified: 2013-04-04 I'm trying to set up a new exchange protocol error server and have everything configured to send e-mail and receive through outlook web access and standard exchange access. However I can't get the email through POP3. I've enabled the service, added firewall rules. If I set up the account in outlook for POP3 access and do the "Test Account Settings" "Log onto incoming mail server (POP3)" shows as completed as if it works. Once I close this, and do a pop3 protocol error send/receive I get the following error. Task 'email@....net - Receiving' reported error (0x800CCC90) : 'Your incoming (POP3) e-mail server has reported an internal error. If you continue to receive this message, contact your server administrator or Internet service provider (ISP). The server responded: -ERR Server Unavailable. 21' 0 Question by:zer0zer0 Facebook Twitter LinkedIn Google LVL 10 Active 3 days ago Best Solution bycpmcomputers Try from a simple command prompt it seems there is a known issue with putty and exchange 2010 Is your internal domain in the format mydomain.local or my domain.com I take it that it is added Go to Solution 16 Comments LVL 6 Overall: Level 6 Exchange 1 Message Expert Comment by:RaithZ2013-04-01 Do you have the pop3 connector set to require ssl or tls? 0 LVL 10 Overall: Level 10 Exchange 5 Message Active 3 days ago Expert Comment by:cpmcomputers2013-04-02 Pop3 on exchange 2010 does not allow basic password connections by default You can change it but it is considered a security risk To prove if this is your problem If you telnet the server internally Ie telnet serverip 110 You will get a message server not available in this state error 0 Message Author Comment by:zer0zer02013-04-02 I get t