archived somewhere else.
Some people have local news groups which have only a handful of readers.
-These are transported via NNTP, and are therefore news. But we may need
+These are transported via @sc{nntp}, and are therefore news. But we may need
to read and answer a large fraction of the messages very carefully in
order to do our work. And there may not be an archive, so we may need
to save the interesting messages the same way we would personal mail.
@end lisp
If the mail spool file is not located on the local machine, it's best to
-use POP or IMAP or the like to fetch the mail. You can not you ange-ftp
+use POP or @sc{imap} or the like to fetch the mail. You can not you ange-ftp
file names here---it has no way to lock the mail spool while moving the
mail.
@end lisp
@item imap
-Get mail from a IMAP server. If you don't want to use IMAP as intended,
+Get mail from a @sc{imap} server. If you don't want to use @sc{imap} as intended,
as a network mail reading protocol (ie with nnimap), for some reason or
other, Gnus let you treat it similar to a POP server and fetches
-articles from a given IMAP mailbox.
+articles from a given @sc{imap} mailbox.
Keywords:
@table @code
@item :server
-The name of the IMAP server. The default is taken from the
+The name of the @sc{imap} server. The default is taken from the
@code{MAILHOST} environment variable.
@item :port
-The port number of the IMAP server. The default is @samp{143}, or
+The port number of the @sc{imap} server. The default is @samp{143}, or
@samp{993} for SSL connections.
@item :user
-The user name to give to the IMAP server. The default is the login
+The user name to give to the @sc{imap} server. The default is the login
name.
@item :password
-The password to give to the IMAP server. If not specified, the user is
+The password to give to the @sc{imap} server. If not specified, the user is
prompted.
@item :stream
@item :predicate
The predicate used to find articles to fetch. The default,
@samp{UNSEEN UNDELETED}, is probably the best choice for most people,
-but if you sometimes peek in your mailbox with a IMAP client and mark
+but if you sometimes peek in your mailbox with a @sc{imap} client and mark
some articles as read (or; SEEN) you might want to set this to
@samp{nil}. Then all articles in the mailbox is fetched, no matter
what. For a complete list of predicates, see RFC2060 ยง6.4.4.
@end table
-An example IMAP mail source:
+An example @sc{imap} mail source:
@lisp
(imap :server "mail.mycorp.com" :stream kerberos4)
examples.
@item
-@code{(@var{field} @var{value} @var{[- restrict [- restrict [@dots{}]]]}
+@code{(@var{field} @var{value} @code{[-} @var{restrict} @code{[-} @var{restrict} @code{[@dots{}]}@code{]]}
@var{split})}: If the split is a list, the first element of which is a
string, then store the message as specified by @var{split}, if header
@var{field} (a regexp) contains @var{value} (also a regexp). If
mail within spitting distance of Gnus.
The same concept exists for Usenet itself: Though access to articles is
-typically done by NNTP these days, once upon a midnight dreary, everyone
+typically done by @sc{nntp} these days, once upon a midnight dreary, everyone
in the world got at Usenet by running a reader on the machine where the
-articles lay (the machine which today we call an NNTP server), and
+articles lay (the machine which today we call an @sc{nntp} server), and
access was by the reader stepping into the articles' directory spool
area directly. One can still select between either the @code{nntp} or
@code{nnspool} backends, to select between these methods, if one happens
* Directory Groups:: You can read a directory as if it was a newsgroup.
* Anything Groups:: Dired? Who needs dired?
* Document Groups:: Single files can be the basis of a group.
-* SOUP:: Reading @sc{SOUP} packets ``offline''.
+* SOUP:: Reading @sc{soup} packets ``offline''.
* Mail-To-News Gateways:: Posting articles via mail-to-news gateways.
-* IMAP:: Using Gnus as a IMAP client.
+* IMAP:: Using Gnus as a @sc{imap} client.
@end menu
@node IMAP
-@subsection IMAP
+@subsection @sc{imap}
@cindex nnimap
-@cindex IMAP
+@cindex @sc{imap}
-IMAP is a network protocol for reading mail (or news, or ...), think of
-it as a modernized NNTP. Connecting to a IMAP server is much similar to
+@sc{imap} is a network protocol for reading mail (or news, or ...), think of
+it as a modernized @sc{nntp}. Connecting to a @sc{imap} server is much similar to
connecting to a news server, you just specify the network address of the
server.
@item nnimap-address
@vindex nnimap-address
-The address of the remote IMAP server. Defaults to the virtual server
+The address of the remote @sc{imap} server. Defaults to the virtual server
name if not specified.
@item nnimap-server-port
@vindex nnimap-list-pattern
String or list of strings of mailboxes to limit available groups
to. This is used when the server has very many mailboxes and you're only
-interested in a few -- some servers export your home directory via IMAP,
+interested in a few -- some servers export your home directory via @sc{imap},
you'll probably want to limit the mailboxes to those in @file{~/Mail/*}
then.
@item nnimap-expunge-on-close
@cindex Expunging
@vindex nnimap-expunge-on-close
-Unlike Parmenides the IMAP designers has decided that things that
-doesn't exist actually does exist. More specifically, IMAP has this
+Unlike Parmenides the @sc{imap} designers has decided that things that
+doesn't exist actually does exist. More specifically, @sc{imap} has this
concept of marking articles @code{Deleted} which doesn't actually delete
them, and this (marking them @code{Deleted}, that is) is what nnimap
does when you delete a article in Gnus (with @kbd{G DEL} or similair).
closing a mailbox.
@item never
Never actually delete articles. Currently there is no way of showing the
-articles marked for deletion in nnimap, but other IMAP clients may allow
+articles marked for deletion in nnimap, but other @sc{imap} clients may allow
you to do this. If you ever want to run the EXPUNGE command manually,
@xref{Expunging mailboxes}.
@item ask
@node Splitting in IMAP
-@subsubsection Splitting in IMAP
+@subsubsection Splitting in @sc{imap}
@cindex splitting imap mail
Splitting is something Gnus users has loved and used for years, and now
-the rest of the world is catching up. Yeah, dream on, not many IMAP
+the rest of the world is catching up. Yeah, dream on, not many @sc{imap}
server has server side splitting and those that have splitting seem to
-use some non-standard protocol. This means that IMAP support for Gnus
+use some non-standard protocol. This means that @sc{imap} support for Gnus
has to do it's own splitting.
And it does.
@cindex inbox
@vindex nnimap-split-inbox
-A string or a list of strings that gives the name(s) of IMAP mailboxes
+A string or a list of strings that gives the name(s) of @sc{imap} mailboxes
to split from. Defaults to nil, which means that splitting is disabled!
@lisp
this variable.
This variable contains a list of lists, where the first element in the
-sublist gives the name of the IMAP mailbox to move articles matching the
+sublist gives the name of the @sc{imap} mailbox to move articles matching the
regexp in the second element in the sublist. Got that? Neither did I, we
need examples.
@end table
@node Editing IMAP ACLs
-@subsubsection Editing IMAP ACLs
+@subsubsection Editing @sc{imap} ACLs
@cindex editing imap acls
@cindex Access Control Lists
-@cindex Editing IMAP ACLs
+@cindex Editing @sc{imap} ACLs
@kindex G l
@findex gnus-group-nnimap-edit-acl
-ACL stands for Access Control List. ACLs are used in IMAP for limiting
-(or enabling) other users access to your mail boxes. Not all IMAP
+ACL stands for Access Control List. ACLs are used in @sc{imap} for limiting
+(or enabling) other users access to your mail boxes. Not all @sc{imap}
servers support this, this function will give an error if it doesn't.
To edit a ACL for a mailbox, type @kbd{G l}
@item
At least with the Cyrus server, you are required to give the user
"anyone" posting ("p") capabilities to have "plussing" work (that is,
-mail sent to user+mailbox@@domain ending up in the IMAP mailbox
+mail sent to user+mailbox@@domain ending up in the @sc{imap} mailbox
INBOX.mailbox).
@end itemize
@file{.gnus.el} file to get started.
@lisp
-;;; Define how Gnus is to fetch news. We do this over NNTP
+;;; Define how Gnus is to fetch news. We do this over @sc{nntp}
;;; from your ISP's server.
(setq gnus-select-method '(nntp "news.your-isp.com"))
Marks}).
@item
-A new mail-to-news backend makes it possible to post even when the NNTP
+A new mail-to-news backend makes it possible to post even when the @sc{nntp}
server doesn't allow posting (@pxref{Mail-To-News Gateways}).
@item
in the head or body.
@item
-Allow breaking lengthy NNTP commands.
+Allow breaking lengthy @sc{nntp} commands.
@item
gnus-article-highlight-limit, to disable highlighting in big articles.
Set/remove/add marks on articles. Normally Gnus handles the article
marks (such as read, ticked, expired etc) internally, and store them in
-@code{~/.newsrc.eld}. Some backends (such as IMAP) however carry all
+@code{~/.newsrc.eld}. Some backends (such as @sc{imap}) however carry all
information about the articles on the server, so Gnus need to propagate
the mark information to the server.
projects / gnus / commitdiff