Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Some imap accounts not updating in 24.4
Date: Fri, 19 Dec 2014 22:07:25 -0500	[thread overview]
Message-ID: <87bnmzt3wy.fsf@lifelogs.com> (raw)
In-Reply-To: <87r3vw4sgj.fsf@eps142.cdf.udc.es>

On Thu, 18 Dec 2014 21:24:12 +0100 Alberto Luaces <aluaces@udc.es> wrote: 

AL> Ted Zlatanov <tzz@lifelogs.com> writes:
>> On Tue, 25 Nov 2014 23:55:26 +0100 Alberto Luaces <aluaces@udc.es> wrote: 
>> 
AL> since updating from 24.3 to 24.4, one of my imap accounts stopped being
AL> updated automatically.  It doesn't show new messages for that server,
AL> even I press 'g'.  The only way to get those messages is to directly
AL> press 'Meta-g' on that group.
>> 
>> I am far from expert on that, but would guess that logs (`nnimap-debug'
>> for instance) would be very helpful to see what's different at the
>> protocol level.

AL> I am setting nnimap-debug through (setq nnimap-debug t), but I am not
AL> able to get any log buffer for imap.

I see my debug logs in " *nnimap imap.gmail.com 993  *nntpd**" for
instance.  I think this is all I did:

(setq imap-log t ; obsolete, I think
      nnimap-debug t)

Perhaps you didn't see that buffer because it starts with a space, so
it's hidden by default?  That's by design in Emacs IIRC.

Ted




  reply	other threads:[~2014-12-20  3:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-25 22:55 Alberto Luaces
2014-12-08 16:53 ` Ted Zlatanov
2014-12-18 20:24   ` Alberto Luaces
2014-12-20  3:07     ` Ted Zlatanov [this message]
2014-12-22 19:48       ` Alberto Luaces
2015-02-04 11:48         ` Ted Zlatanov
2015-02-05  3:14         ` Lars Ingebrigtsen
2015-02-18 19:39           ` Alberto Luaces
2015-02-19  5:56             ` Lars Ingebrigtsen

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=87bnmzt3wy.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --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).