6.0.0-beta1
▾
Tasks
New Task
Search
Photos
Wiki
▾
Tickets
New Ticket
Search
dev.horde.org
Toggle Alerts Log
Help
11/7/25
H
istory
A
ttachments
C
omment
W
atch
Download
Comment on [#11946] No headers when viewing unread message
*
Your Email Address
*
Spam protection
Enter the letters below:
.__ .___.._. .. . | \ _/ | ||__| |__/./__._|_\__|| |
Comment
> Ahh... this is a broken IMAP response. You did not provide the > entire IMAP log but I am guessing that this response: > > S: * 1 FETCH (UID 9 BODY[HEADER] {1409} > S: <<<FULL HEADERS>>> > S: ) > S: * 1 FETCH (FLAGS (\Seen)) > > Was caused by this command: > > a UID FETCH 9 (BODY[HEADER]) > > A correct response would look like: > > S: * 1 FETCH (UID 9 BODY[HEADER] {1409} > S: <<<FULL HEADERS>>> > S: ) FLAGS (\Seen)) > > --or-- > > S: * 1 FETCH (UID 9 BODY[HEADER] {1409} > S: <<<FULL HEADERS>>> > S: ) > S: * 1 FETCH (UID 9 FLAGS (\Seen)) > > So the problem is that we are asking for UID fetch results, but the > server is throwing in some sequence-only results instead. And this > is not allowed if, in fact, this is called from a UID FETCH command. > From RFC 3501 [6.8]: > > However, server implementations MUST implicitly > include the UID message data item as part of any FETCH response > caused by a UID command, regardless of whether a UID was specified > as a message data item to the FETCH. > > Can you verify the command that caused these responses and the IMAP > software version used?
Attachment
Watch this ticket
N
ew Ticket
M
y Tickets
S
earch
Q
uery Builder
R
eports
Saved Queries
Open Bugs
Bugs waiting for Feedback
Open Bugs in Releases
Open Enhancements
Enhancements waiting for Feedback
Bugs with Patches
Enhancements with Patches
Release Showstoppers
Stalled Tickets
New Tickets
Horde 5 Showstoppers