From: Xiyue Deng <manphiz@gmail.com>
To: Greg Troxel <gdt@lexort.com>
Cc: ding@gnus.org
Subject: Re: Gnus sometimes reports new messages but not showing them on IMAP server
Date: Fri, 10 May 2024 13:06:29 -0700 [thread overview]
Message-ID: <87plttctyy.fsf@debian-hx90.lan> (raw)
In-Reply-To: <rmiv83lyhv8.fsf@s1.lexort.com> (Greg Troxel's message of "Fri, 10 May 2024 08:24:43 -0400")
Greg Troxel <gdt@lexort.com> writes:
> Xiyue Deng <manphiz@gmail.com> writes:
>
>> Hi Greg,
>>
>> Greg Troxel <gdt@lexort.com> writes:
>>
>>> Xiyue Deng <manphiz@gmail.com> writes:
>>>
>>>> This makes much sense. I'll try M-g the next time this happens. Thanks
>>>> everyone!
>>>
>>> I had a situation where a message arrived in INBOX. I could see it in
>>> the filesystem dovecot reads, and in other clients. It was as if it did
>>> not exist in gnus.
>>>
>>> M-g on the group in *Group* buffer seems to have resolved that.
>>> It is interesting that moving out and back resolved what I think is the
>>> same situation in the past.
>>>
>>> Just making up stuff without basis: It's like a missing wakeup in a
>>> synchronization protocol.
>>
>> Unfortunately, it looks like it doesn't fix it for me, presumably
>> because I'm using nnimap instead of reading from a local mailbox.
>> Therefore it feels natural to assume a bug in nnimap, though it's still
>> years earlier before I can figure it out from the code, if that ever
>> happens :P
>
> This was nnimap in my case, with emacs and dovecot on the same machine
> if that matters.
>
>
Ah I see. Then probably the IMAP implementation of Outlook is just bad
;-)
--
Xiyue Deng
next prev parent reply other threads:[~2024-05-10 20:11 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 0:57 Xiyue Deng
2024-04-17 0:03 ` Greg Troxel
2024-04-17 6:47 ` Xiyue Deng
2024-04-17 19:51 ` Dan Christensen
2024-04-18 12:13 ` Greg Troxel
2024-04-19 22:55 ` Dan Christensen
2024-04-21 12:08 ` Arash Esbati
2024-04-21 12:43 ` Dan Christensen
2024-04-21 13:14 ` Andreas Schwab
2024-04-21 16:18 ` Eric Abrahamsen
2024-04-21 18:16 ` Arash Esbati
2024-04-22 0:00 ` Greg Troxel
2024-04-22 2:35 ` Eric Abrahamsen
2024-04-27 19:46 ` Xiyue Deng
2024-05-02 5:47 ` Xiyue Deng
2024-05-02 15:08 ` Eric Abrahamsen
2024-05-02 17:24 ` Xiyue Deng
2024-05-02 17:41 ` Dan Christensen
2024-05-02 18:41 ` Xiyue Deng
2024-05-05 20:18 ` Xiyue Deng
2024-05-05 21:01 ` Dan Christensen
2024-05-05 22:10 ` Xiyue Deng
2024-05-08 18:36 ` Xiyue Deng
2024-05-08 18:41 ` Xiyue Deng
2024-05-09 23:11 ` Andrew Cohen
2024-05-10 7:45 ` Xiyue Deng
2024-05-10 8:16 ` Andrew Cohen
2024-05-10 8:26 ` Xiyue Deng
2024-05-10 9:13 ` Andreas Schwab
2024-05-10 0:43 ` Greg Troxel
2024-05-10 1:20 ` Xiyue Deng
2024-05-10 12:24 ` Greg Troxel
2024-05-10 20:06 ` Xiyue Deng [this message]
2024-05-11 19:08 ` Greg Troxel
2024-05-11 22:33 ` Eric Abrahamsen
2024-05-12 11:14 ` Gnus sometimes fails to see a message that is actually in IMAP Greg Troxel
2024-05-13 14:39 ` Eric Abrahamsen
2024-05-24 15:58 ` Eric Abrahamsen
2024-05-24 17:29 ` Eric Abrahamsen
2024-04-24 15:23 ` Gnus sometimes reports new messages but not showing them on IMAP server James Thomas
2024-04-25 2:59 ` Eric Abrahamsen
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=87plttctyy.fsf@debian-hx90.lan \
--to=manphiz@gmail.com \
--cc=ding@gnus.org \
--cc=gdt@lexort.com \
/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).