Status Update
No update yet.
Comments
ia...@google.com
Like your other issue posted, to be able to proceed, I would require some step-by-step instructions to reproduce the behavior on my end. Thank you for your cooperation.
lo...@crocodile.org
Steps:
- Locate a message in your Gmail account which have '%' as part of Message-ID
- Start IMAP session, authenticate and issue "UID SEARCH" command for this message ID
Expected result: Message UID returned
lo...@crocodile.org
In my case, I already had messages with such message-id in my mailbox. If you do not have
any you may need to generate one, perhaps using a small script as described here:
ia...@google.com
Thank you, though I would need more detailed step-by-step instructions on how to generate the message, how you start the IMAP session, and how you issue the "UID SEARCH".
I would need the step-by-step instructions posted here, including any code, search terms, and tools you use.
Thanks again.
lo...@crocodile.org
The bug is reproducible using standard SMTP and IMAP protocol commands. It is too much to ask me to write a script to make it easier for you to fix it. This is a job for your engineers. If they are too busy, I can quote you a rate for one of my engineers to write this script. :)
ia...@google.com
At the moment the first thing to do is to get together some easy repro steps, which I have taken the liberty of doing here.
Using the Gmail API method users.messages.insert I uploaded some RAW messages with custom message-id field as I was not able to find any existing emails with a %.
Inserting a % into the ID and performing an IMAP SEARCH:
a UID SEARCH HEADER Message-ID "<a000000%tzebKqOzDw@gmail.com>"
* SEARCH
a OK SEARCH completed (Success)
It seems not to have found anything. I assume this the same kind of behavior that you experienced. This is in contrast to a message imported without a %.
a UID SEARCH HEADER Message-ID "<a0000000tzebKqOzDw@gmail.com>"
* SEARCH 25
a OK SEARCH completed (Success)
The 25 indicating that it had been found.
In terms of a workaround, you have already found the X-GM extensions.
I will continue looking into this and will post any updates here.
ia...@google.com
This has been filed internally for review. Updates to follow.
is...@google.com
jp...@google.com
ed...@nmcourts.gov
When running a search, messages with an ID that do not include '%' are found. Messages with an ID that include '%' aren't found.
SND: [00005 SEARCH HEADER MESSAGE-ID <CAHhJpZ724yxOn-cBrZ5NM5kzRb5sZmQWLgt2pHexX7LVwZJMDg@mail.gmail.com>]
RCV: [* SEARCH 3845]
RCV: [00005 OK SEARCH completed (Success)]
...
SND: [00006 SEARCH HEADER MESSAGE-ID <D1165038.54280%SHARE.HCMAlert@state.nm.us>]
RCV: [00006 BAD Could not parse command]
This occurs with X-GM-RAW and Rfc822msgid:, as well.
SND: [00005 SEARCH X-GM-RAW Rfc822msgid:<CAHhJpZ724yxOn-cBrZ5NM5kzRb5sZmQWLgt2pHexX7LVwZJMDg@mail.gmail.com>]
RCV: [* SEARCH 3845]
RCV: [00005 OK SEARCH completed (Success)]
...
SND: [00006 SEARCH X-GM-RAW Rfc822msgid:<D1165038.54280%SHARE.HCMAlert@state.nm.us>]
RCV: [00006 BAD Could not parse command]
Description
This commands fails to find a message which exists:
Using X-GM-RAW Gmail's extension to IMAP's SEARCH command with
"Rfc822msgid:<D7DA993B.B30DC%psztxa@exmail.nottingham.ac.uk>"works.