U:RDoc::AnyMethod[iI"capability:ETI"Net::IMAP#capability;TF:publico:RDoc::Markup::Document:@parts[o:RDoc::Markup::Paragraph;	[I"lSends a {CAPABILITY command [IMAP4rev1 §6.1.1]}[https://www.rfc-editor.org/rfc/rfc3501#section-6.1.1] ;TI"Jand returns an array of capabilities that the server supports.  Each ;TI"capability is a string.;To:RDoc::Markup::BlankLineo;
;	[I"&See the {IANA IMAP4 capabilities ;TI"Nregistry}[http://www.iana.org/assignments/imap4-capabilities] for a list ;TI"<of all standard capabilities, and their reference RFCs.;T@o:RDoc::Markup::BlockQuote;	[o;
;	[
I"=<em>*Note* that Net::IMAP does not currently modify its ;TI"<behaviour according to the capabilities of the server; ;TI"6it is up to the user of the class to ensure that ;TI":a certain capability is supported by a server before ;TI"using it.</em>;T@o;
;	[I"JCapability requirements—other than +IMAP4rev1+—are listed in the ;TI"+documentation for each command method.;T@S:RDoc::Markup::Heading:
leveli
:	textI"!Basic IMAP4rev1 capabilities;T@o;
;	[
I"PAll IMAP4rev1 servers must include +IMAP4rev1+ in their capabilities list. ;TI"<All IMAP4rev1 servers must _implement_ the +STARTTLS+, ;TI"M<tt>AUTH=PLAIN</tt>, and +LOGINDISABLED+ capabilities, and clients must ;TI"Mrespect their presence or absence.  See the capabilites requirements on ;TI"*#starttls, #login, and #authenticate.;T@S;
;i
;I"Using IMAP4rev1 extensions;T@o;
;	[
I"HIMAP4rev1 servers must not activate incompatible behavior until an ;TI"Lexplicit client action invokes a capability, e.g. sending a command or ;TI"Mcommand argument specific to that capability.  Extensions with backward ;TI"Lcompatible behavior, such as response codes or mailbox attributes, may ;TI"be sent at any time.;T@o;
;	[
I"OInvoking capabilities which are unknown to Net::IMAP may cause unexpected ;TI"Pbehavior and errors, for example ResponseParseError is raised when unknown ;TI"Presponse syntax is received.  Invoking commands or command parameters that ;TI"Pare unsupported by the server may raise NoResponseError, BadResponseError, ;TI"(or cause other unexpected behavior.;T@S;
;i
;I"#Caching +CAPABILITY+ responses;T@o;
;	[	I"DServers may send their capability list, unsolicited, using the ;TI"M+CAPABILITY+ response code or an untagged +CAPABILITY+ response.  These ;TI"?responses can be retrieved and cached using #responses or ;TI"#add_response_handler.;T@o;
;	[	I"MBut cached capabilities _must_ be discarded after #starttls, #login, or ;TI"K#authenticate.  The OK TaggedResponse to #login and #authenticate may ;TI"Iinclude +CAPABILITY+ response code data, but the TaggedResponse for ;TI"8#starttls is sent clear-text and cannot be trusted.;T:
@fileI"lib/net/imap.rb;T:0@omit_headings_from_table_of_contents_below000[I"();T@JFI"	IMAP;TcRDoc::NormalClass00