Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Frank Schmitt <usereplyto2004@Frank-Schmitt.net>
Subject: Re: Incorrect article count
Date: Tue, 09 Mar 2004 20:36:30 +0100	[thread overview]
Message-ID: <m3llm9rewx.fsf@fed1.frank-schmitt.net> (raw)
In-Reply-To: <wn5smghncle.fsf@linhd-2.ca.nortel.com>

Linh Dang <linh@linhdang.home> writes:

> How about nnimap? Doest the above recipe work with nnimap backend too?

Yes it does.

-- 
Did you ever realize how much text fits in eighty columns? If you now consider
that a signature usually consists of up to four lines, this gives you enough
space to spread a tremendous amount of information with your messages. So seize
this opportunity and don't waste your signature with bullshit nobody will read.


      parent reply	other threads:[~2004-03-09 19:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-08 16:11 Peter Lee
     [not found] ` <ubrn75h14.fsf@swbell.net>
2004-03-08 19:04   ` David Hanak
     [not found] ` <m3k71vl0su.fsf@fed1.frank-schmitt.net>
     [not found]   ` <wn5smghncle.fsf@linhd-2.ca.nortel.com>
2004-03-09 19:36     ` Frank Schmitt [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=m3llm9rewx.fsf@fed1.frank-schmitt.net \
    --to=usereplyto2004@frank-schmitt.net \
    --cc=replies@Frank-Schmitt.net \
    /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).