Bug 276616 - www mail - Squirrelmail returns fetch error from imap service
Summary: www mail - Squirrelmail returns fetch error from imap service
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-01-25 17:52 UTC by James B. Byrne
Modified: 2024-01-25 20:35 UTC (History)
1 user (show)

See Also:


Attachments
Squirrelmail stable 20240125 (1.01 KB, patch)
2024-01-25 18:29 UTC, Herbert J. Skuhra
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description James B. Byrne 2024-01-25 17:52:24 UTC
FreeBSD-13.2p9
squirrelmail-php83 20230207

Following authentication the following error is displayed in the message pane:

ERROR: Bad or malformed request.
Query: FETCH 1,3:5,7,10,12,18:19,28,50,119,121:123,125,127:128,132:135,138 (FLAGS UID RFC822.SIZE INTERNALDATE BODY.PEEK[HEADER.FIELDS (Date To Cc From Subject X-Priority Importance Priority Content-Type )])
Server responded: Invalid field-name in UID Fetch BODY.PEEK[HEADER.FIELDS

When opening a folder the following is returned:

ERROR: Bad or malformed request.
Query: FETCH 48151,50099,61689,68730,71439,71602,71682,71906,72251,72297,72342,72372,72430:72431,72468:72469,72492,72500,72522,72530,72605,72616 (FLAGS UID RFC822.SIZE INTERNALDATE BODY.PEEK[HEADER.FIELDS (Date To Cc From Subject X-Priority Importance Priority Content-Type )])
Server responded: Invalid field-name in UID Fetch BODY.PEEK[HEADER.FIELDS

Expected response is a list of messages in the folder.
Comment 1 Herbert J. Skuhra 2024-01-25 18:28:12 UTC
Maybe try latest stable snapshot(20240125). It includes some fixes: e.g:
https://sourceforge.net/p/squirrelmail/code/14991/
Not sure if this will resolve your issue. I don't use squirrelmail.
Comment 2 Herbert J. Skuhra 2024-01-25 18:29:47 UTC
Created attachment 247956 [details]
Squirrelmail stable 20240125

Update to stable snapshot 20240125.
Comment 3 James B. Byrne 2024-01-25 20:35:05 UTC
Updating to stable 20240125 fixed the issue.