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 692904 - Do not call camel_service_disconnect during connection phase
Do not call camel_service_disconnect during connection phase
Status: RESOLVED FIXED
Product: evolution-data-server
Classification: Platform
Component: Mailer
3.6.x (obsolete)
Other Linux
: Normal major
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[pop3]
: 702628 704313 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2013-01-30 21:36 UTC by Brian J. Murrell
Modified: 2013-08-09 12:26 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
eds patch (6.72 KB, patch)
2013-07-19 10:05 UTC, Milan Crha
committed Details | Review

Description Brian J. Murrell 2013-01-30 21:36:24 UTC
For one of my accounts, I pop3 my mail from the mail server.

I frequently get an orange warning box below the toolbar that says:

Error while Fetching Mail.
Command is not valid in this state.

It's rather annoying since it consumes vertical real-estate from the message summary.  Given the widespread movement to 16x9 screens, vertical real-estate is becoming ever more valuable.

Any idea why this warning is continuing to pop (NPI) up over and over again?
Comment 1 Milan Crha 2013-02-06 16:56:35 UTC
I saw it too, when I switched my POP account to GSSAPI (not that the server understood it, though), thus I guess it's about GSSAPI authentication.
Comment 2 Brian J. Murrell 2013-07-18 14:29:17 UTC
Here's what CAMEL_DEBUG=pop3 has to say about it:

POP3_STREAM_LINE (49): '+OK The Microsoft Exchange POP3 service is ready.'
POP3_STREAM_WRITE (6):
CAPA

POP3_STREAM_LINE (3): '+OK'
Got + response
cmd_capa
POP3_STREAM_LINE (3): 'TOP'
POP3_STREAM_LINE (4): 'UIDL'
POP3_STREAM_LINE (4): 'STLS'
POP3_STREAM_LINE (END)
POP3_STREAM_WRITE (6):
STLS

POP3_STREAM_LINE (26): '+OK Begin TLS negotiation.'
Got + response
POP3_STREAM_WRITE (6):
CAPA

POP3_STREAM_LINE (3): '+OK'
Got + response
cmd_capa
POP3_STREAM_LINE (3): 'TOP'
POP3_STREAM_LINE (4): 'UIDL'
POP3_STREAM_LINE (22): 'SASL NTLM GSSAPI PLAIN'
scanning tokens 'NTLM GSSAPI PLAIN'
got auth type 'NTLM'
got auth type 'GSSAPI'
got auth type 'PLAIN'
POP3_STREAM_LINE (4): 'USER'
POP3_STREAM_LINE (END)
POP3_STREAM_WRITE (13):
AUTH GSSAPI

POP3_STREAM_LINE (2): '+ '
POP3_STREAM_WRITE (3):
*

POP3_STREAM_LINE (59): '-ERR The AUTH protocol exchange was canceled by the client.'
opening pop3 INBOX folder
POP3_STREAM_WRITE (6):
LIST

POP3_STREAM_LINE (40): '-ERR Command is not valid in this state.'
POP3_STREAM_WRITE (6):
UIDL

POP3_STREAM_LINE (40): '-ERR Command is not valid in this state.'
POP3_STREAM_WRITE (6):
QUIT

POP3_STREAM_LINE (59): '+OK Microsoft Exchange Server 2010 POP3 server signing off.'
Got + response

This was an open evolution, send/receive for the pop server account and then exit evolution.
Comment 3 Milan Crha 2013-07-19 07:59:12 UTC
Nice, I see the same when using STARTTLS in Receiving Options. Changing encryption method doesn't help, as long as I use also GSSAPI. Changing to NTLM/SPA makes it work, thus this can be some error in GSSAPI authentication handling in POP3.
Comment 4 Milan Crha 2013-07-19 10:05:52 UTC
Created attachment 249595 [details] [review]
eds patch

for evolution-data-server;

The main issue is that the provider called "disconnect" during the connection phase, which makes the service think it's connected, instead of disconnected, thus it tries to do the conversation with the server, which produces those errors with commands being invoked in a wrong state.

Another thing was that the actual error from the authentication was ignored in POP3, thus I made it propagate into UI.
Comment 5 Milan Crha 2013-07-19 10:09:56 UTC
Created commit 3e789c9 in eds master (3.9.5+)
Created commit 0ed53b4 in eds gnome-3-8 (3.8.4+)
Comment 6 Milan Crha 2013-08-01 11:15:30 UTC
Follow-up change at bug #705273.
Comment 7 Milan Crha 2013-08-09 09:32:58 UTC
*** Bug 704313 has been marked as a duplicate of this bug. ***
Comment 8 Milan Crha 2013-08-09 12:26:57 UTC
*** Bug 702628 has been marked as a duplicate of this bug. ***