Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: <ding@gnus.org>
Subject: Re: Retrieving older articles, some missing
Date: Tue, 26 Feb 2013 13:15:10 +0000	[thread overview]
Message-ID: <87bob7qkrl.fsf@pinto.chemeng.ucl.ac.uk> (raw)
In-Reply-To: <877gm2pz4e.fsf@invalid.invalid> (Nuno Silva's message of "Wed, 20 Feb 2013 21:24:33 +0200")

Nuno Silva <nunojsilva@invalid.invalid> writes:

> Hello,
>
> Currently using Gnus with a Microsoft Exchange server through IMAP.
>
> When I try to retrieve older messages with / o, I notice some of the
> messages don't appear. Entering the group with C-u RET or doing A T on a
> thread does show these messages.
>
> Any idea of what may be going on?

I don't know but I am having some very strange behaviour the last few
weeks.  I am using gnus up to date from git and I am accessing emails on
a Microsoft Exchange server (outlook.com).  Right now, I can see (using
Outlook's web access) that I have a number of emails in the INBOX
received in the past two hours.  When I open the INBOX group in gnus,
none of these shows up no matter what I do (including /o to see all old
emails).

This problem seems to be caused by some interaction with the agent
system in gnus.  If I disable the agent, I can see my emails.  If I
enable it, every now and again gnus decides to mark all unseen emails in
my INBOX as read and doesn't actually show them in the Group buffer.

Help!

Any suggestions for debugging this would be most welcome.  I need the
agent because I spend 2 hours on the train every day and that's when I
want to read and process my emails.

Thanks,
eric


-- 
: Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D
: in Emacs 24.3.50.1 + Ma Gnus v0.6 + evil 1.0-dev
: BBDB version 3.02 ($Date: 2013/02/16 14:37:17 $)




           reply	other threads:[~2013-02-26 13:15 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <877gm2pz4e.fsf@invalid.invalid>]

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=87bob7qkrl.fsf@pinto.chemeng.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).