From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: info-gnus-english@gnu.org
Subject: Re: gnus-search since: not working for nnimap
Date: Sun, 29 Jan 2023 09:33:49 -0800 [thread overview]
Message-ID: <87a621w8hu.fsf@ericabrahamsen.net> (raw)
Julien Cubizolles <j.cubizolles@free.fr> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> You can play with the bits and pieces to see where things might be going
>> wrong:
>>
>> (gnus-search-query-parse-date "1y") -> (28 1 2022)
>> (gnus-search-parse-query "since:1y") - > ((since 28 1 2022))
>>
>> So far so good.
>>
>> (gnus-search-transform
>> (make-instance 'gnus-search-imap)
>> (gnus-search-parse-query "since:1y")) -> "SINCE 28-Jan-2022"
>>
>> Still looking correct (right?).
>
> Everything is fine up until this point.
>
>> Try doing "C-u G G" on an nnimap group to shut off gnus-search parsing,
>> and enter "SINCE 28-Jan-2022" as the search string. Does that return
>> anything?
>
> Sill nothing:
>
> Group nnselect:nnselect-87cz6x1zv6.fsf contains no messages
We'll have to get closer to the IMAP server, then. If you don't have TLS
enabled on your local dovecot you can probably log in and test with:
telnet localhost 143
Then:
a login <username> <password>
b select "INBOX"
c UID SEARCH SINCE 28-Jan-2022
To confirm that messages are found.
Then it's a matter of seeing that same conversation between Gnus and
Dovecot, to find where things are going wrong. You can set
`nnimap-record-commands' to t, then conduct a search, and also find
which of your " *nnimap localhost nil *nntpd**-373470" buffers
corresponds to this server. That should allow you to reconstruct the
conversation.
Another option would be to edebug the `gnus-search-imap-search-command'
function, and see what we're getting back from Dovecot.
Hopefully something in there will be revealing.
next reply other threads:[~2023-01-29 17:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 17:33 Eric Abrahamsen [this message]
2023-01-30 7:18 ` Julien Cubizolles
2023-01-30 9:32 ` Julien Cubizolles
2023-01-30 10:36 ` Julien Cubizolles
2023-01-30 17:41 ` Eric Abrahamsen
2023-02-01 23:05 ` Björn Bidar
-- strict thread matches above, loose matches on Subject: below --
2023-01-28 12:22 Julien Cubizolles
2023-01-28 18:20 ` Eric Abrahamsen
2023-01-29 8:59 ` Julien Cubizolles
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=87a621w8hu.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).