Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: <ding@gnus.org>
Subject: Re: All non-marked messages unread
Date: Mon, 12 Jan 2015 18:14:53 +0000	[thread overview]
Message-ID: <87h9vvg92a.fsf@ucl.ac.uk> (raw)
In-Reply-To: <upzcmw5o302i.fsf@dod.no> (Steinar Bang's message of "Mon, 12 Jan 2015 08:55:17 +0100")

On Monday, 12 Jan 2015 at 08:55, Steinar Bang wrote:
>>>>>> Eric S Fraga <e.fraga@ucl.ac.uk>:
>
>> I have no idea but I have had the same thing happen (in terms of
>> non-marked articles being made unread) 2 or 3 times in the past 2 years,
>> but only with IMAP to an MS Exchange Server and never with other IMAP
>> servers (just in an attempt to add a data point).  Incredibly
>> annoying.
>
> With two gnusen open on the same group, the last one to quit the group
> will win.  Could that be what was happening...?

not in my case; maybe relevant for the OP.  I never have more than one
gnus running at any time.

I personally think there's a problem (well, many) with MS Exchange...  I
wish I didn't have to use it but all attempts at local copies with
synchronisation (isync, offlineimap) have failed due to strange errors
with the server.

Anyway, not a problem.  I've learned to live with this and I have more
serious issues to address than the shortcomings of MS Exchange...  I
simply wanted to add a datat point for the OP's benefit.

thanks,
eric

-- 
: Eric S Fraga, GnuPG: 0xFFFCF67D
: in Emacs 24.4.1 + Ma Gnus v0.12 + evil-git-d432ec2
: BBDB version 3.0.50 (2013-11-16 11:30:49 -0600)



  reply	other threads:[~2015-01-12 18:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87387iad7o.fsf@Equus.decebal.nl>
2015-01-11 14:04 ` Eric S Fraga
2015-01-12  7:55   ` Steinar Bang
2015-01-12 18:14     ` Eric S Fraga [this message]
2015-01-12 19:52       ` Adam Sjøgren
2015-01-15  8:08         ` e.fraga

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=87h9vvg92a.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --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).