@@ -1045,7 +1045,7 @@ def capability
1045
1045
# ===== Capabilities
1046
1046
#
1047
1047
# The server's capabilities must include +ID+
1048
- # [RFC2971[https://tools.ietf.org/html/rfc2971]]
1048
+ # [RFC2971[https://tools.ietf.org/html/rfc2971]].
1049
1049
def id ( client_id = nil )
1050
1050
synchronize do
1051
1051
send_command ( "ID" , ClientID . new ( client_id ) )
@@ -1058,7 +1058,7 @@ def id(client_id=nil)
1058
1058
#
1059
1059
# This allows the server to send unsolicited untagged EXPUNGE #responses,
1060
1060
# but does not execute any client request. \IMAP servers are permitted to
1061
- # send unsolicited untagged responses at any time, except for ` EXPUNGE`.
1061
+ # send unsolicited untagged responses at any time, except for + EXPUNGE+:
1062
1062
#
1063
1063
# * +EXPUNGE+ can only be sent while a command is in progress.
1064
1064
# * +EXPUNGE+ must _not_ be sent during #fetch, #store, or #search.
@@ -1143,10 +1143,7 @@ def starttls(**options)
1143
1143
end
1144
1144
1145
1145
# :call-seq:
1146
- # authenticate(mechanism, *,
1147
- # sasl_ir: true,
1148
- # registry: Net::IMAP::SASL.authenticators,
1149
- # **, &) -> ok_resp
1146
+ # authenticate(mechanism, *, sasl_ir: true, registry: Net::IMAP::SASL.authenticators, **, &) -> ok_resp
1150
1147
#
1151
1148
# Sends an {AUTHENTICATE command [IMAP4rev1 §6.2.2]}[https://www.rfc-editor.org/rfc/rfc3501#section-6.2.2]
1152
1149
# to authenticate the client. If successful, the connection enters the
@@ -1330,7 +1327,7 @@ def login(user, password)
1330
1327
# the server may return an untagged "NO" response with a "UIDNOTSTICKY"
1331
1328
# response code indicating that the mailstore does not support persistent
1332
1329
# UIDs:
1333
- # @ responses[ "NO"]. last.code.name == "UIDNOTSTICKY"
1330
+ # imap. responses( "NO", &: last)& .code& .name == "UIDNOTSTICKY"
1334
1331
def select ( mailbox )
1335
1332
synchronize do
1336
1333
@responses . clear
@@ -1420,10 +1417,10 @@ def unsubscribe(mailbox)
1420
1417
# to the client. +refname+ provides a context (for instance, a base
1421
1418
# directory in a directory-based mailbox hierarchy). +mailbox+ specifies a
1422
1419
# mailbox or (via wildcards) mailboxes under that context. Two wildcards
1423
- # may be used in +mailbox+: '*' , which matches all characters *including*
1424
- # the hierarchy delimiter (for instance, '/' on a UNIX-hosted
1425
- # directory-based mailbox hierarchy); and '%' , which matches all characters
1426
- # *except* the hierarchy delimiter.
1420
+ # may be used in +mailbox+: <tt>"*"</tt> , which matches all characters
1421
+ # *including* the hierarchy delimiter (for instance, "/" on a UNIX-hosted
1422
+ # directory-based mailbox hierarchy); and <tt>"%"</tt> , which matches all
1423
+ # characters *except* the hierarchy delimiter.
1427
1424
#
1428
1425
# If +refname+ is empty, +mailbox+ is used directly to determine
1429
1426
# which mailboxes to match. If +mailbox+ is empty, the root
@@ -1471,16 +1468,16 @@ def list(refname, mailbox)
1471
1468
# servers, then folder creation (and listing, moving, etc) can lead to
1472
1469
# errors.
1473
1470
#
1474
- # From RFC2342:
1475
- #
1476
- # Although typically a server will support only a single Personal
1471
+ # From RFC2342[https://tools.ietf.org/html/rfc2342] :
1472
+ # >>>
1473
+ # <em> Although typically a server will support only a single Personal
1477
1474
# Namespace, and a single Other User's Namespace, circumstances exist
1478
1475
# where there MAY be multiples of these, and a client MUST be prepared
1479
1476
# for them. If a client is configured such that it is required to create
1480
1477
# a certain mailbox, there can be circumstances where it is unclear which
1481
1478
# Personal Namespaces it should create the mailbox in. In these
1482
1479
# situations a client SHOULD let the user select which namespaces to
1483
- # create the mailbox in.
1480
+ # create the mailbox in.</em>
1484
1481
#
1485
1482
# Related: #list, Namespaces, Namespace
1486
1483
#
@@ -1668,9 +1665,9 @@ def lsub(refname, mailbox)
1668
1665
# or more attributes whose statuses are to be requested. Supported
1669
1666
# attributes include:
1670
1667
#
1671
- # MESSAGES:: the number of messages in the mailbox.
1672
- # RECENT:: the number of recent messages in the mailbox.
1673
- # UNSEEN:: the number of unseen messages in the mailbox.
1668
+ # MESSAGES:: the number of messages in the mailbox.
1669
+ # RECENT:: the number of recent messages in the mailbox.
1670
+ # UNSEEN:: the number of unseen messages in the mailbox.
1674
1671
#
1675
1672
# The return value is a hash of attributes. For example:
1676
1673
#
@@ -1935,11 +1932,11 @@ def uid_fetch(set, attr, mod = nil)
1935
1932
# to alter data associated with messages in the mailbox, in particular their
1936
1933
# flags. The +set+ parameter is a number, an array of numbers, or a Range
1937
1934
# object. Each number is a message sequence number. +attr+ is the name of a
1938
- # data item to store: ' FLAGS' will replace the message's flag list with the
1939
- # provided one, ' +FLAGS' will add the provided flags, and '-FLAGS' will
1940
- # remove them. +flags+ is a list of flags.
1935
+ # data item to store: <tt>" FLAGS"</tt> will replace the message's flag list
1936
+ # with the provided one, <tt>" +FLAGS"</tt> will add the provided flags, and
1937
+ # <tt>"-FLAGS"</tt> will remove them. +flags+ is a list of flags.
1941
1938
#
1942
- # The return value is an array of FetchData
1939
+ # The return value is an array of FetchData.
1943
1940
#
1944
1941
# Related: #uid_store
1945
1942
#
0 commit comments