123456789_123456789_123456789_123456789_123456789_

Class: Net::IMAP::ResponseCode

Relationships & Source Files
Super Chains via Extension / Inclusion / Inheritance
Class Chain:
self, Struct
Instance Chain:
self, Struct
Inherits: Struct
  • Object
Defined in: lib/net/imap/response_data.rb

Overview

ResponseCode represents response codes. Response codes can be retrieved from ResponseText#code and can be included in any “condition” response: any TaggedResponse and UntaggedResponse when the response type is a “condition” (“OK”, “NO”, “BAD”, “PREAUTH”, or “BYE”).

Some response codes come with additional data which will be parsed by ::Net::IMAP. Others return nil for #data, but are used as a machine-readable annotation for the human-readable ResponseText#text in the same response. When ::Net::IMAP does not know how to parse response code text, #data returns the unparsed string.

Untagged response code #data is pushed directly onto #responses, keyed by #name, unless it is removed by the command that generated it. Use #add_response_handler to view tagged response codes for command methods that do not return their TaggedResponse.

IMAP extensions may define new codes and the data that comes with them. The IANA IMAP Response Codes registry has links to specifications for all standard response codes. Response codes are backwards compatible: Servers are allowed to send new response codes even if the client has not enabled the extension that defines them. When unknown response code data is encountered, #data will return an unparsed string.

See [IMAP4rev1] §7.1, “Server Responses - Status Responses” for full definitions of the basic set of IMAP4rev1 response codes:

  • ALERT, the ResponseText#text contains a special alert that MUST be brought to the user’s attention.

  • BADCHARSET, #data will be an array of charset strings, or nil.

  • CAPABILITY, #data will be an array of capability strings.

  • PARSE, the ResponseText#text presents an error parsing a message’s [RFC5322] or [MIME-IMB] headers.

  • PERMANENTFLAGS, followed by an array of flags. System flags will be symbols, and keyword flags will be strings. See Net::IMAP@System+flags

  • READ-ONLY, the mailbox was selected read-only, or changed to read-only

  • READ-WRITE, the mailbox was selected read-write, or changed to read-write

  • TRYCREATE, when #append or #copy fail because the target mailbox doesn’t exist.

  • UIDNEXT, #data is an Integer, the next UID value of the mailbox. See [IMAP4rev1], §2.3.1.1, “Unique Identifier (UID) Message Attribute.

  • UIDVALIDITY, #data is an Integer, the UID validity value of the mailbox See [IMAP4rev1], §2.3.1.1, “Unique Identifier (UID) Message Attribute.

  • UNSEEN, #data is an Integer, the number of messages which do not have the \Seen flag set.

See RFC5530, “IMAP Response Codes” for the definition of the following response codes, which are all machine-readable annotations for the human-readable ResponseText#text, and have nil #data of their own:

  • UNAVAILABLE

  • AUTHENTICATIONFAILED

  • AUTHORIZATIONFAILED

  • EXPIRED

  • PRIVACYREQUIRED

  • CONTACTADMIN

  • NOPERM

  • INUSE

  • EXPUNGEISSUED

  • CORRUPTION

  • SERVERBUG

  • CLIENTBUG

  • CANNOT

  • LIMIT

  • OVERQUOTA

  • ALREADYEXISTS

  • NONEXISTENT

Instance Attribute Summary

  • #data rw

    ResponseCode represents response codes.

  • #name rw

    ResponseCode represents response codes.

Instance Attribute Details

#data (rw)

ResponseCode represents response codes. Response codes can be retrieved from ResponseText#code and can be included in any “condition” response: any TaggedResponse and UntaggedResponse when the response type is a “condition” (“OK”, “NO”, “BAD”, “PREAUTH”, or “BYE”).

Some response codes come with additional data which will be parsed by ::Net::IMAP. Others return nil for #data, but are used as a machine-readable annotation for the human-readable ResponseText#text in the same response. When ::Net::IMAP does not know how to parse response code text, #data returns the unparsed string.

Untagged response code #data is pushed directly onto Net::IMAP#responses, keyed by #name, unless it is removed by the command that generated it. Use Net::IMAP#add_response_handler to view tagged response codes for command methods that do not return their TaggedResponse.

IMAP extensions may define new codes and the data that comes with them. The IANA IMAP Response Codes registry has links to specifications for all standard response codes. Response codes are backwards compatible: Servers are allowed to send new response codes even if the client has not enabled the extension that defines them. When unknown response code data is encountered, #data will return an unparsed string.

See [IMAP4rev1] §7.1, “Server Responses - Status Responses” for full definitions of the basic set of IMAP4rev1 response codes:

  • ALERT, the ResponseText#text contains a special alert that MUST be brought to the user’s attention.

  • BADCHARSET, #data will be an array of charset strings, or nil.

  • CAPABILITY, #data will be an array of capability strings.

  • PARSE, the ResponseText#text presents an error parsing a message’s [RFC5322] or [MIME-IMB] headers.

  • PERMANENTFLAGS, followed by an array of flags. System flags will be symbols, and keyword flags will be strings. See Net::IMAP@System+flags

  • READ-ONLY, the mailbox was selected read-only, or changed to read-only

  • READ-WRITE, the mailbox was selected read-write, or changed to read-write

  • TRYCREATE, when Net::IMAP#append or Net::IMAP#copy fail because the target mailbox doesn’t exist.

  • UIDNEXT, #data is an Integer, the next UID value of the mailbox. See [IMAP4rev1], §2.3.1.1, “Unique Identifier (UID) Message Attribute.

  • UIDVALIDITY, #data is an Integer, the UID validity value of the mailbox See [IMAP4rev1], §2.3.1.1, “Unique Identifier (UID) Message Attribute.

  • UNSEEN, #data is an Integer, the number of messages which do not have the \Seen flag set.

See RFC5530, “IMAP Response Codes” for the definition of the following response codes, which are all machine-readable annotations for the human-readable ResponseText#text, and have nil #data of their own:

  • UNAVAILABLE

  • AUTHENTICATIONFAILED

  • AUTHORIZATIONFAILED

  • EXPIRED

  • PRIVACYREQUIRED

  • CONTACTADMIN

  • NOPERM

  • INUSE

  • EXPUNGEISSUED

  • CORRUPTION

  • SERVERBUG

  • CLIENTBUG

  • CANNOT

  • LIMIT

  • OVERQUOTA

  • ALREADYEXISTS

  • NONEXISTENT

[ GitHub ]

  
# File 'lib/net/imap/response_data.rb', line 200

class ResponseCode < Struct.new(:name, :data)

#name (rw)

ResponseCode represents response codes. Response codes can be retrieved from ResponseText#code and can be included in any “condition” response: any TaggedResponse and UntaggedResponse when the response type is a “condition” (“OK”, “NO”, “BAD”, “PREAUTH”, or “BYE”).

Some response codes come with additional data which will be parsed by ::Net::IMAP. Others return nil for #data, but are used as a machine-readable annotation for the human-readable ResponseText#text in the same response. When ::Net::IMAP does not know how to parse response code text, #data returns the unparsed string.

Untagged response code #data is pushed directly onto Net::IMAP#responses, keyed by #name, unless it is removed by the command that generated it. Use Net::IMAP#add_response_handler to view tagged response codes for command methods that do not return their TaggedResponse.

IMAP extensions may define new codes and the data that comes with them. The IANA IMAP Response Codes registry has links to specifications for all standard response codes. Response codes are backwards compatible: Servers are allowed to send new response codes even if the client has not enabled the extension that defines them. When unknown response code data is encountered, #data will return an unparsed string.

See [IMAP4rev1] §7.1, “Server Responses - Status Responses” for full definitions of the basic set of IMAP4rev1 response codes:

  • ALERT, the ResponseText#text contains a special alert that MUST be brought to the user’s attention.

  • BADCHARSET, #data will be an array of charset strings, or nil.

  • CAPABILITY, #data will be an array of capability strings.

  • PARSE, the ResponseText#text presents an error parsing a message’s [RFC5322] or [MIME-IMB] headers.

  • PERMANENTFLAGS, followed by an array of flags. System flags will be symbols, and keyword flags will be strings. See Net::IMAP@System+flags

  • READ-ONLY, the mailbox was selected read-only, or changed to read-only

  • READ-WRITE, the mailbox was selected read-write, or changed to read-write

  • TRYCREATE, when Net::IMAP#append or Net::IMAP#copy fail because the target mailbox doesn’t exist.

  • UIDNEXT, #data is an Integer, the next UID value of the mailbox. See [IMAP4rev1], §2.3.1.1, “Unique Identifier (UID) Message Attribute.

  • UIDVALIDITY, #data is an Integer, the UID validity value of the mailbox See [IMAP4rev1], §2.3.1.1, “Unique Identifier (UID) Message Attribute.

  • UNSEEN, #data is an Integer, the number of messages which do not have the \Seen flag set.

See RFC5530, “IMAP Response Codes” for the definition of the following response codes, which are all machine-readable annotations for the human-readable ResponseText#text, and have nil #data of their own:

  • UNAVAILABLE

  • AUTHENTICATIONFAILED

  • AUTHORIZATIONFAILED

  • EXPIRED

  • PRIVACYREQUIRED

  • CONTACTADMIN

  • NOPERM

  • INUSE

  • EXPUNGEISSUED

  • CORRUPTION

  • SERVERBUG

  • CLIENTBUG

  • CANNOT

  • LIMIT

  • OVERQUOTA

  • ALREADYEXISTS

  • NONEXISTENT

[ GitHub ]

  
# File 'lib/net/imap/response_data.rb', line 200

class ResponseCode < Struct.new(:name, :data)