From: Dan Poirier <no_spam_please@this.domain.is.invalid>
Subject: Re: Gnus nnimap, Multiple Machines
Date: Fri, 20 Sep 2002 15:11:53 -0400 [thread overview]
Message-ID: <yujbs6slbly.fsf@percival.raleigh.ibm.com> (raw)
In-Reply-To: <6e4rckv92z.fsf@door.stick.lan>
Chris Richards <chrisr@sloth.yi.org> writes:
> I have two machines that use gnus and access my home nnimap server.
> Whenever I read a message from one machine and then go to the other,
> the unread count in the *Group* buffer is unchanged (i.e., it looks
> like I have new mail to read). However, upon entering the group, all
> of the messages are shown as read ('O').
It's been like this for years, including in the latest development
version. I finally got tired of Gnus's chronic inaccuracy in
reporting what was in my IMAP mailboxes, and switched to using
Mulberry for my email. (http://www.cyrusoft.com/mulberry) I still use
Gnus for news, though.
--
Dan Poirier -- Email: my last name at pobox dot com
next parent reply other threads:[~2002-09-20 19:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6e4rckv92z.fsf@door.stick.lan>
2002-09-20 19:11 ` Dan Poirier [this message]
2002-09-20 20:15 ` Chris Richards
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=yujbs6slbly.fsf@percival.raleigh.ibm.com \
--to=no_spam_please@this.domain.is.invalid \
/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).