From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: [nnimap] Is `A T' supposed to work with nnimap backend
Date: Thu, 20 Nov 2003 04:31:15 +0100 [thread overview]
Message-ID: <iluekw3btrw.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m3r804fgb7.fsf@newsguy.com> (Harry Putnam's message of "Wed, 19 Nov 2003 10:56:12 -0600")
Harry Putnam <reader@newsguy.com> writes:
> Is normal for `A T' (`gnus-summary-refer-thread') not to work with
> nnimap backend?
No. What happens? What does *imap-log* contain (after toggling
imap-log)?
next prev parent reply other threads:[~2003-11-20 3:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 16:56 Harry Putnam
2003-11-20 3:31 ` Simon Josefsson [this message]
2003-11-20 4:17 ` Harry Putnam
2003-11-20 4:40 ` Simon Josefsson
2003-11-20 10:54 ` Harry Putnam
2003-11-20 11:57 ` Simon Josefsson
2003-11-20 12:21 ` Harry Putnam
2003-11-20 12:30 ` Simon Josefsson
2003-11-20 13:48 ` Ted Zlatanov
2003-11-20 14:23 ` Derrell.Lipman
2003-11-20 14:24 ` Simon Josefsson
2003-11-20 16:19 ` Ted Zlatanov
2003-11-20 4:20 ` Harry Putnam
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=iluekw3btrw.fsf@latte.josefsson.org \
--to=jas@extundo.com \
--cc=ding@gnus.org \
/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).