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 778562 - Yahoo! POP3 PIPELINING extension breaks message receive
Yahoo! POP3 PIPELINING extension breaks message receive
Status: RESOLVED NOTGNOME
Product: evolution-data-server
Classification: Platform
Component: Mailer
3.20.x (obsolete)
Other Linux
: Normal major
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
: 778860 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2017-02-13 15:46 UTC by Edward
Modified: 2017-02-28 15:13 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
log file produced when starting evolution with "CAMEL_DEBUG=pop3 evolution >&/misc/evol.logfile (16.10 KB, text/x-emacs-lisp)
2017-02-15 15:54 UTC, Edward
Details

Description Edward 2017-02-13 15:46:55 UTC
I'm running Fedora 24 with gnome shell version 3.20.4 and evolution 3.20.5. Each time my client connects with the email provider server it only retrieves one email message and give the following error:

Error while Fetching mail from 'att secure'.
Cannot get message AJp2imIAB5XhWKBVsQNrACIqoxw: Socket I/O timed out

The message identified changes with each new error. My Evolution worked fine until approximately February 1. 

From suggestions in Ask Fedora I backed up my evolution from the menu. I deleted evolution using "dnf remove evolution evolution-bogofilter evolution-data-server evolution-ews evolution-help evolution-perl".  I then removed the .cache/evolution and .config/evolution directories with "rm -rf".  I re-installed the evolution packages removed from above, configured my email provider and gave it a run.  I had the same problem.

Next, I installed thunderbird, configured my email provider and retrieved 28 messages in a flash.

I'm not sure how to go about troubleshooting any further.  Since this I have restored my backup to evolution so I have all my email history.
Comment 1 Milan Crha 2017-02-14 09:43:57 UTC
Thanks for a bug report. There is clearly something wrong with the connection to the server, maybe it's proxy related. I do not think there is any problem about "retrieving one message", thus I'm changing the bug summary.

Pretty important, what is the account type, please? Is it IMAP, POP, EWS, ...?

Being it about proxy settings, what is set in Edit->Preferences->Network Preferences, please?
Comment 2 Edward 2017-02-14 14:25:17 UTC
You are probably correct about the one message retrieval. This morning I received 7 messages before the error leaving 22 on the server.

This is a POP account and in the network preferences I have "Defer to Desktop Setting" which is proxy "NONE".
Comment 3 Milan Crha 2017-02-15 08:51:09 UTC
Okay. I would try to disable proxy in the evolution completely, just to avoid one more thing.

Also, a version of glib2, glib-networking and gnutls may be useful, because those are the bits which do the actual connection. Did any of those packages change recently? What is you downgrade to the previous version?

You can also run evolution with POP debugging to see what it does in the background. The command is:

   $ CAMEL_DEBUG=pop3 evolution
Comment 4 Milan Crha 2017-02-15 08:53:59 UTC
I see that Fedora 24 had only an update of gnutls to version 3.4.17-2. Try to downgrade it to the previous version, for example with:

   # dnf downgrade gnutls
Comment 5 Edward 2017-02-15 14:35:01 UTC
I have set the proxy to "No Proxy" in network settings in evolution.  The versions of software mentioned are as follows:

glib2.x86_64 2.48.2-1.fc24
glib-networking.x86_64 2.48.2-1.fc24
gnutls.x86_64 3.4.17-2.fc24 

I will update again in a few hours to see if the network settings change had any effect. If not I will downgrade the gnutls package.
Comment 6 Edward 2017-02-15 15:54:01 UTC
Created attachment 345846 [details]
log file produced when starting evolution with "CAMEL_DEBUG=pop3 evolution >&/misc/evol.logfile
Comment 7 Edward 2017-02-15 15:57:35 UTC
After changing the "Network Preferences" to "No Proxy" the error message has changed.  I'm now getting:

Cannot get POP summary: Socket I/O timed out

Even if I change the "Network Preferences" back to "Defer to Desktop Setting" I still get the same error.

I have attached a logfile from "CAMEL_DEBUG=pop3 evolution >&/misc/evol.logfile"
Comment 8 Edward 2017-02-15 15:58:40 UTC
I will downgrade the gnutls package and see if anything changes.
Comment 9 Edward 2017-02-15 16:16:42 UTC
After downgrade of gnutls (dnf downgrade gnutls --allowerasing) the problem remains the same as after Network Preferences changs.
Comment 10 Milan Crha 2017-02-16 09:41:06 UTC
Thanks for the update. I'm afraid I aim this in a wrong direction. There is a thread opened on the evolution-list [1], which claims similar issue and the common part seems to be when contacting certain Yahoo! (or its derivatives) POP3 servers. Thus this might be in conjunction with this? Is your account a Yahoo! related account too?

[1] https://mail.gnome.org/archives/evolution-list/2017-February/msg00053.html
Comment 11 Milan Crha 2017-02-16 13:56:17 UTC
(In reply to Milan Crha from comment #10)
> I'm afraid I aim this in a wrong direction.

Of course I do. The problem was elsewhere. As the reporter on the evolution-list realized, the trick is to Disable all POP3 extensions, because the Yahoo! server advertises PIPELINING, but then fails to operate properly for some reason. More can be seen in the thread I pasted a link to in the previous comment.

Long story short:

Edit->Preferences->Mail Accounts-><Yahoo POP account>->Receiving Options tab->check Disable support for all POP3 extensions. Then it works.
Comment 12 Edward 2017-02-16 14:29:34 UTC
You are correct!  The provider is AT&T which uses Yahoo! mail.  The strange thing is that it has worked for years without that setting. Thanks for the help, I've learned a good bit about troubleshooting evolution. I've put everything back to the way they were and added the "Disable support for all POP3 extensions" and I received 88 messages this morning on one connection.
Comment 13 Milan Crha 2017-02-20 14:40:38 UTC
*** Bug 778860 has been marked as a duplicate of this bug. ***
Comment 14 Milan Crha 2017-02-28 08:02:42 UTC
I decided to disable all POP3 extensions by default, which will affect only newly created accounts. The correct fix is to report this to Yahoo! support centre, if there is anyone able to do it.

Created commit d56b81e in eds master (3.23.92+)
Created commit 911d13f in eds gnome-3-22 (3.22.6+)
Comment 15 Phil Sherman 2017-02-28 15:13:16 UTC
There is no way to directly contact YAHOO about issues like this. I was able to get ATT to (supposedly) file a trouble ticket with Yahoo about this problem over a week ago but it appears that YAHOO has little interest in fixing this.

Yahoo's response doesn't surprise me. I found a severe password management problem at Yahoo and it took them over a month to fix it. Unfortunately, their "fix" involved ignoring all password changes made while the problem existed.