Imap4.error
code: Lib/imaplib.py This module defines three classes, IMAP4, IMAP4_SSL and IMAP4_stream, which encapsulate a connection to an IMAP4 server and implement a large subset of the IMAP4rev1 client protocol as defined in RFC 2060. It is backward compatible with IMAP4 (RFC 1730) servers, but note that the STATUS command is not supported in IMAP4. Three classes are provided by the imaplib module, IMAP4 is the base class: class imaplib.IMAP4([host[, port]])¶ This class implements the actual IMAP4 protocol. The connection is created and protocol version (IMAP4 or IMAP4rev1) is determined when the instance is initialized. If host is not specified, '' (the local host) is used. If port is omitted, the standard IMAP4 port (143) is used. Three exceptions are defined as attributes of the IMAP4 class: exception IMAP4.error¶ Exception raised on any errors. The reason for the exception is passed to the constructor as a string. exception IMAP4.abort¶ IMAP4 server errors cause this exception to be raised. This is a sub-class of IMAP4.error. Note that closing the instance and instantiating a new one will usually allow recovery from this exception. exception IMAP4.readonly¶ This exception is raised when a writable mailbox has its status changed by the server. This is a sub-class of IMAP4.error. Some other client now has write permission, and the mailbox will need to be re-opened to re-obtain write permission. There's also a subclass for secure connections: class imaplib.IMAP4_SSL([host[, port[, keyfile[, certfile]]]])¶ This is a subclass derived from IMAP4 that connects over an SSL encrypted socket (to use this class you need a socket module that was compiled with SSL support). If host is not specified, '' (the local host) is used. If port is omitted, the standard IMAP4-over-SSL port (993) is used. keyfile and certfile are also optional - they can contain a PEM formatted private key and certificate chain file for the SSL connection. The second subclass allows for connections created by a child process: class imaplib.IMAP4_stream(command)¶ This is a subclass derived from IMAP4 that connects to the stdin/stdout file descriptors created by passing command to os.popen2(). New in version 2.3. The followin
xyz is not an IMAP4 Server error message, despite the fact the IMAP server supports IMAP v4.1, and had been working okay. It appears to be a generic error message for IMAP accounts, thats sometimes displayed when Thunderbird can't map the error to another error message. While you may see it when it tries to connect to the mail server, its usually a transient error when you do something in quick succession like deleting multiple messages [1] [2]. There appear to be three common causes: Some sort of latency issue - if you repeat whatever you did slower the problem doesn't occur again. [3]. Due to a connection timing out, or some sort of timing/load problem. In this case it might display the popup https://docs.python.org/2/library/imaplib.html error message but still do what its supposed to. [4] Thunderbird asked the mail server what features it has (sent a IMAP Capability command) and got a answer that it didn't expect. This is most likely to occur with a email provider using a IMAP server that is not very compatible, such as Gmail. [5] If none of this helps, you need to enable IMAP logging and look at the log files to understand whats going on. However, normally http://kb.mozillazine.org/Not_an_IMAP4_server its just a transient error that you can ignore. [edit]Wrong port or protocol If you created a new account and always get this error message, that's a different problem. You may have specified a port normally used for POP or SMTP, for IMAP; or, you may have selected TLS or no encryption for a port that requires SSL. Protocol Default port SSL / TLS IMAP 143 993 POP 110 995 SMTP 25 465 / 587 Note: The default ports may also be used for TLS with some providers. Your email provider might support port 23, 2525 or 26 as a workaround for ISP's blocking SMTP port 25. Port 465 is the original port for SMTP over SSL/TLS, most SMTP servers now use 587 though some may support both. [edit]Anti-virus or firewall blocking connections to the IMAP server If your IMAP account used to work okay and you suddenly got this error message it might be due to an automated upgrade of your anti-virus or firewall program blocking connections to the IMAP server due to problems in its heuristics. For example, the real time shield in Avast 5 may block secure connections (use SSL/TLS or STARTTLS) to a mail server unless you reconfigure the account in Thunderbird not to use a secure connection and then reconfigure Avast to specify the name of the mail server (host), protocol, port and encryption type instead per this article. Retrieved from "http://kb.mozillazine.or
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 http://www.courier-mta.org/imap/tutorial.setup.html 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 https://support.microsoft.com/en-us/kb/3025138 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/imapl
360 games PC games Windows games Windows phone games Entertainment All Entertainment Movies & TV Music Business & Education Business Students & educators Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft