Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: info-gnus-english@gnu.org
Subject: Re: groups not being scanned
Date: Thu, 17 Aug 2017 15:41:43 -0700	[thread overview]
Message-ID: <874lt54y1k.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87o9reem4o.fsf@delle7240.chemeng.ucl.ac.uk>

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> On Wednesday, 16 Aug 2017 at 12:21, Eric Abrahamsen wrote:
>> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>>
>>> Hello all,
>>>
>>> Long story short for background: I have had to move back to Outlook
>>> exchange server for my emails.  I used to use this server before and
>>> everything (sort of) worked.  Moved 1.5 years ago to gmail for speed
>>> (especially search) but I have had to move back.
>>>
>>> For some reason that I cannot fathom, when I ask for new email, only my
>>> INBOX is scanned.  Other groups on that server are not even though their
>>> levels are low enough (with respect to gnus-activate-level).  Multiple
>>> group scanning works on my gmail servers.
>>>
>>> Is there a server specific setting that would affect this?
>>
>> Not that I'm aware of... Can you explicitly scan other groups with M-g
>> in the *Group* buffer?
>
> I can scan any group from that server manually, with M-g.
>
> My OP was wrong, by the way: none of the groups get scanned.  Somehow I
> convinced myself that INBOX was being scanned but it wasn't.

Then the function to edebug is `gnus-get-unread-articles'. That's going
to be a long boring slog (if you have many other servers, maybe close
them first), but it ought to show you what's going on.

I'd recommend starting the edebug, then jumping to line 1701 (in Emacs
master), and checking out the value of the "type-cache" variable (got to
love Gnus' impenetrably-named variables). That should hold a list of all
the servers that Gnus is going to check groups for. Either the Exchange
server won't be in there (in which case start over and follow from the
top), or it will be (in which case follow on from there, and see what
happens).

Wish I had a better solution!

Eric



      reply	other threads:[~2017-08-17 22:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-16 17:54 Eric S Fraga
2017-08-16 19:21 ` Eric Abrahamsen
2017-08-17  6:36   ` Eric S Fraga
2017-08-17 22:41     ` Eric Abrahamsen [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=874lt54y1k.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=info-gnus-english@gnu.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).