From: Amos Gouaux <amos+lists.ding@utdallas.edu>
Subject: Re: nnimap better than advertised
Date: 22 Apr 2000 00:55:29 -0500 [thread overview]
Message-ID: <q6mpuri8ysu.fsf@spartacus.utdallas.edu> (raw)
In-Reply-To: Bruce Stephens's message of "11 Apr 2000 22:54:29 +0100"
>>>>> On 11 Apr 2000 22:54:29 +0100,
>>>>> Bruce Stephens <bruce+gnus@cenderis.demon.co.uk> (bs) writes:
bs> Is my understanding correct? If so, then this looks like it's exactly
bs> what I'd expect based on my experiences of nnml (say), so why is the
bs> manual warning me to expect something unexpected?
I think this comes from past discussions (mainly on the nnimap list)
about the delete model typical with many IMAP clients. That is,
traditionally one would flag messages to be deleted, then perform an
expunge to physically blow them away. Until the expunge was
performed, one could revisit that folder at any time and still see
those messages flagged to be deleted.
Since gnus doesn't display messages flagged to be deleted, this
doesn't translate literally. Instead, I think most folks use
expiration to achieve similar (though more powerful) results.
Amos
prev parent reply other threads:[~2000-04-22 5:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-11 21:54 Bruce Stephens
2000-04-22 5:55 ` Amos Gouaux [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=q6mpuri8ysu.fsf@spartacus.utdallas.edu \
--to=amos+lists.ding@utdallas.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).