Login No Error In Imap Command Received By Server
Contents |
About Us Contact Us Forum > Digital Publishing / Web Sites > Website and Server Troubleshooting Login problems with IMAP, CentOS Plesk 9 [solved] User Name Remember Me? Password Ask
Error In Imap Command Received By Server Godaddy
Question Join / Register FAQ Today's Posts Basic Search bad error in imap command received by server. Advanced Search How to Support digitalFAQ.com · When Will My Question Be Answered? · How to
Error In Imap Command Received By Server Outlook Mac
Upload/View/Download Images & Attachments Search Site & Forums Custom Search More Forum Searches Advanced Forum-Only Search View Tag Cloud & Search Tags Find All Thanked Posts Go to Page... LinkBack Thread Tools #1 04-29-2010, 05:01 PM kpmedia Site Staff | Web Hosting, Photo Join Date: Feb 2004 Posts: 4,059 Thanks: 205 Thanked 320 Times in 305 Posts Ran into an issue today, setting up courier-imap service on Plesk 9 Linux/CentOS. The docs said to access via SSH (root secure shell), and I use Putty in Windows. Testing the IMAP was easy, Code: telnet localhost 143 and if successful, you'll get this long server response code: Code: Trying 127.0.0.1... Connected to localhost.domains.com (127.0.0.1). Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE ACL ACL2=UNION STARTTLS] Courier-IMAP ready. Copyright 1998-2004 Double Precision, Inc. See COPYING for distribution information. Now, I already have POP+IMAP email accounts set up in Plesk, for my domain. So I'm skipping this step in this forum post. Obviously you have to have an email account setup before you're allowed to log in to one! For account login, it said to use this Code: login test@domains.com password ...but that's not correct. You'll get this: Code: login NO Error in IMAP command received by server. It's not "no errors" but NO as in DENIED LOGIN and the error is "Error in IMAP command received by server" You need to add a number in front of it. Example: Code: 1 login test@domains.com password and then you'll get a successful login: Code: [root@fh ~]# telnet localhost 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES
Post #1 of 4 (227 views) Permalink Can't login on Courier-imap server I have installed Courier-imap on my server and I'm trying to test it, which is not going that well... When I try to telnet in to it I can connect but I can't log in. Am I using the right commands when I test? This is the output from telnet telnet 127.0.0.1 imap http://www.digitalfaq.com/forum/web-tech/2204-login-problems-imap.html Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. * OK [.CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE ACL ACL2=UNION STARTTLS] Courier-IMAP ready. Copyright 1998-2005 Double Precision, Inc. See COPYING for distribution information. login second [at] domain2 login NO Error in IMAP command received by server. Connection closed by http://www.gossamer-threads.com/lists/gentoo/user/151602 foreign host. -- Regards / Venlig hilsen Johannes Skov Frandsen *Address:* Egelundsvej 18, DK-5260 Odense S *Web:* www.omesc.com | *Email:* joe [at] omesc -- gentoo-user [at] gentoo mailing list bss03 at volumehost Jun13,2007,2:08AM Post #2 of 4 (225 views) Permalink Re: Can't login on Courier-imap server [In reply to] On Wednesday 13 June 2007 03:38:58 Johannes Skov Frandsen wrote: > I have installed Courier-imap on my server and I'm trying to test it, > which is not going that well... > > When I try to telnet in to it I can connect but I can't log in. > > Am I using the right commands when I test? Yes, but you are using the wrong format. All IMAP commands and responses are prefixed by a 4-character string and a space. This way a command can have multiple responses and multiple commands can be sent before the response for the first is received. (The client matches
Cookies. Weitere Informationen Fehlermeldung bei courier imap: login NO Error in IMAP command received by server. Dieses Thema im Forum "FreeBSD - http://www.bsdforen.de/threads/fehlermeldung-bei-courier-imap-login-no-error-in-imap-command-received-by-server.23784/ Anwendungen und Ports" wurde erstellt von Mardor, 4 November 2009. Mardor Member Registriert seit: 29 November 2007 Beiträge: 463 Hallo, ich möchte mir einen Mailserver aufsetzen und habe http://www.courier-mta.org/imap/tutorial.setup.html dazu postfix mit courier-imap über eine mysql Datenbank gewählt. Leider bekomme ich beim Aufruf von 127.0.0.1 143 folgende Meldung: telnet 127.0.0.1 143 Trying 127.0.0.1... Connected to localhost. Escape error in character is '^]'. * OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SOR T QUOTA IDLE ACL ACL2=UNION STARTTLS] Courier-IMAP ready. Copyright 1998-2008 Double Precision, I nc. See COPYING for distribution information. login test test login NO Error in IMAP command received by server.Klicke in dieses Feld, um es in vollständiger Größe anzuzeigen. Ich erhalte die Meldung error in imap immer, egal ob ich die richtigen oder die falschen Logindaten eingebe.... Ich habe bereits mehrere Stunden nach dem Fehler gesucht aber absolut keinen Anhaltspunkt gefunden. Es wäre wirklich absolut super, wenn jemand von euch einen Tipp für mich hätte. Meine authdaemonrc: Code: ##VERSION: $Id: authdaemonrc.in,v 1.13 2005/10/05 00:07:32 mrsam Exp $ # # Copyright 2000-2005 Double Precision, Inc. See COPYING for # distribution information. # # authdaemonrc created from authdaemonrc.dist by sysconftool # # Do not alter lines that begin with ##, they are used when upgrading # this configuration. # # This file configures authdaemond, the resident authentication daemon. # # Comments in this file are ignored. Although this file is intended to # be sourced as a shell script, authdaemond parses it manually, so # the acceptable syntax is a bit limited. Multiline variable contents, # with the \ continuation character, are not allowed. Everything must # fit on one line. Do not use any additional whitespace for indentation, # or anything else. ##NAME:
IMAP servers, but the examples reflect output from the Courier IMAP server. The starting point: the Courier IMAP server has just been installed, you start your favorite IMAP mail reader, enter what you think is the correct server configuration, and it does not work. Either your mail software hangs, shows nothing at all, or complains with an error message. There can be many possible reasons, but all of them can be reduced into two categories: a problem with the IMAP server's configuration, or a problem with the mail software's configuration. It may very well be that the server is running properly, however the IMAP configuration in many mail readers often has confusing configuration options, and the correct settings may not be obvious. This tutorial provides step-by-step directions for verifying the Courier IMAP server's basic operation. The following directions should establish whether the server is running correctly, and if not, what the problem might be. Connecting to the Courier IMAP server server The first step is to check if the Courier IMAP server is accepting connections. Open a terminal window and type: telnet hostname 143 Replace hostname with the IMAP server's DNS name. This expected results would look like this: $ telnet imap.example.com 143 Trying 10.0.0.12... Connected to imap.example.com. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THRE AD=REFERENCES SORT QUOTA IDLE AUTH=CRAM-MD5 SMAP1 KEYWORDS ACL ACL2=UNION STARTT LS XMAGICTRASH] Courier-IMAP ready. Copyright 1998-2008 Double Precision, Inc. See COPYING for distribution information. This shows that the IMAP server is running and accepting connections. Your IMAP server may give a slightly difference response. If, on the other hand, the connection fails: $ telnet imap.example.com 143 Trying 10.0.0.12... telnet: connect to address 10.0.0.12: Connection refused There are many reasons for a failed connection, but the two most common are: The IMAP server is not running. Log on to the server and check if the process is running: # ps -ef | grep imap root 30440 30439 0 Jul16 ? 00:00:00 /usr/lib/courier-imap/libexec/co uriertcpd -address=0 -maxprocs=40 -maxperip=10 -nodnslookup -noidentlookup 143 / usr/lib/courier-imap/sbin/imaplogin /usr/lib/courier-imap/bin/imapd Maildir Note that without active IMAP connections only the "couriertcpd" process is running. Different IMAP servers will use different process names. Another (and even better) way is to check if anything is listening on port 143: # /sbin/fuse