Unlike splitting in IMAP (@pxref{Splitting in IMAP}) it do not clone
the @sc{nnmail} variables (i.e., creating @var{nnimap-expiry-wait})
but reuse the @sc{nnmail} variables. What follows below are the
-variables used by the @sc{nnimap} expiry process and any related notes
-on their usage.
+variables used by the @sc{nnimap} expiry process.
A note on how the expire mark is stored on the @sc{imap} server is
appropriate here as well. The expire mark is translated into a
-@sc{imap} client specific mark @code{gnus-expire} and store on the
-message. This means that only likely only Gnus will understand and
-treat the @code{gnus-expire} mark properly, although other clients may
-allow to view client specific flags on a message. It also means that
-your server must support the permanent storage of client specific
-flags on messages. Most do, fortunately.
+@sc{imap} client specific mark, @code{gnus-expire}, and stored on the
+message. This means that likely only Gnus will understand and treat
+the @code{gnus-expire} mark properly, although other clients may allow
+you to view client specific flags on the message. It also means that
+your server must support permanent storage of client specific flags on
+messages. Most do, fortunately.
@table @code