After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 714902 - Server rejects FETCH BODY command with space in header specifier (was: Incompatible with imap.mail.ru)
Server rejects FETCH BODY command with space in header specifier (was: Incomp...
Status: RESOLVED FIXED
Product: geary
Classification: Other
Component: server-support
0.4.2
Other All
: High normal
: 0.6.1
Assigned To: Geary Maintainers
Geary Maintainers
: 715034 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2012-10-17 08:48 UTC by Jim Nelson
Modified: 2014-08-12 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Charles Lindsay 2013-11-21 23:13:04 UTC


---- Reported by jim@yorba.org 2012-10-17 13:48:00 -0700 ----

Original Redmine bug id: 5997
Original URL: http://redmine.yorba.org/issues/5997
Searchable id: yorba-bug-5997
Original author: Jim Nelson
Original description:

First reported at https://bugs.launchpad.net/geary/+bug/1067809

The key line in the debug log is:

    
    
    Unable to fetch status for INBOX: No STATUS response line: "a004 BAD Unknown status field: messages" 
    

This is odd, because MESSAGES is a standard field for the STATUS command.



---- Additional Comments From geary-maint@gnome.bugs 2013-10-19 15:01:00 -0700 ----

### History

####

#1

Updated by Jim Nelson 10 months ago

  * **Category** changed from _engine_ to _server-support_

####

#2

Updated by Jim Nelson 9 months ago

  * **Target version** changed from _0.3.0_ to _0.4.0_

####

#3

Updated by Jim Nelson 3 months ago

  * **Target version** changed from _0.4.0_ to _0.5.0_

####

#4

Updated by Jim Nelson about 1 month ago

A user has supplied me with credentials for mail.ru, so I should be able to
debug this soon.

####

#5

Updated by Jim Nelson about 1 month ago

I took a look at this today. The "Unknown status field: messages" error is no
longer a problem (I suspect it was fixed on the server). Now the error message
is this:

    
    
    BAD [PARSE] Syntax error while reading parenthesized list
    

when submitting any request formed something like this:

    
    
    fetch 1 body.peek[header.fields (references)]
    

The problem is the space between "header.fields" and "(references)". If the
space is removed, Geary works just fine with this server. However, without
that space, other servers choke (including Gmail).

It looks to me that the space is required (see
http://tools.ietf.org/html/rfc3501#section-9, "section-msgtext") so I think
the mail.ru server is at fault here. I don't know why Thunderbird doesn't
choke as well; looking at their source code, it appears the space is
hardcoded. Perhaps they never issue a "header.fields" for this server.

I need to think more about how to work around this. The best solution is for
the server software to be fixed, but I couldn't begin to read the mail.ru
site, find the bug reporting system, and let the admins know. The server
reports a support-url of http://help.mail.ru/mail-help

The other solution would be for Geary to probe the server, see if this problem
exists, and modify its behavior accordingly. So far we've avoided having to do
that -- it'd be nice not to have to go down that path.



--- Bug imported by chaz@yorba.org 2013-11-21 23:13 UTC  ---

This bug was previously known as _bug_ 5997 at http://redmine.yorba.org/show_bug.cgi?id=5997

Unknown milestone "unknown in product geary. 
   Setting to default milestone for this product, "---".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Resolution set on an open status.
   Dropping resolution 

Comment 1 Jim Nelson 2013-11-25 21:16:42 UTC
Bug #715034 looks very similar to this bug.
Comment 2 Jim Nelson 2013-12-10 00:18:40 UTC
*** Bug 715034 has been marked as a duplicate of this bug. ***
Comment 3 Jim Nelson 2013-12-10 00:20:21 UTC
There are now two reports of servers in the wild with this problem.  We need to attack this for 0.6.
Comment 4 Tomasz Woźniak 2013-12-21 13:22:10 UTC
When could I expect that this bug will be fixed? Is there simple way to join as developer for help?
Comment 5 Jim Nelson 2013-12-23 20:03:02 UTC
We would like to have this fixed for 0.6, but we can't give an ETA as of right now.

If you'd like to attack the problem, you can always submit a patch here.
Comment 6 Tomasz Woźniak 2013-12-23 21:36:56 UTC
Ok. I'm going to look on VALA during holidays.
Comment 7 Jim Nelson 2014-04-21 20:53:52 UTC
Fixed in master, commit 3940bf