![]() ![]() However, if the search-text contains certain chars (like & or !), the search-text is truncated at that point. I run a command like this: UID SEARCH HEADER Message-ID succeeds (returns 1 UID of the matching message, or 0 if it doesn't exist). “GET /mail/?_task=mail&_action=search&_interval=&_q=&_headers=body&_layout=widescreen&_filter=ALL&_scope=base&_mbox=INBOX&_remote=1& unlock=loading1590327814408&=1590326452908 HTTP/2.I'm accessing GMail's IMAP interface through python. It’s like MailintheBox / Roundcube isn’t honouring that change to nf timeout properly.Īnd the crazy thing is I know we never had these problems with previous versions of MailintheBox - as I’ve been using the Webclient for all my email for more than a year, and have used the full text search to successfully search bodies of emails before (and my Email mailbox is bigger than hers at 13GB), so I feel a recent upgrade has introduced this bug.īTW, these are the only log outputs (via nginx access and error logs in /usr/log/nginx) that I see: But she immediately ran into this issue trying to search her emails for some personal business info. I got her over to using the WebClient instead until she can afford to buy a new Mac (major purchases are on hold until Corona times are over). This is frustrating more for my wife, as she can’t use her old El Captain based Email client due to the TLS issue. ![]() This error comes up right at 60 seconds after starting any search. ![]() So if I revert it back to “ALL” messages to be searched, it reverts back to “Server Error! (Error)” or “Server Error! (Gateway Timeout)” error states in the Web client. Of course, what I’m looking for is in a Read message, so this doesn’t help me. This takes about 40-50 seconds… just before the 60 second timeout error is produced on larger searches. (BTW, I only have Body defined for the search, nothing else.). I get 173 returned emails, but those are only Unread messages containing that search keyword. If I narrow down a full text search to “Unread” messages, then I have success with the search. Here’s some more reasons why I think it’s a forced timeout issue from the Webclient perspective. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |