action #27901

[qam] test fails in evolution_smoke - imap aol not responding

Added by pcervinka over 4 years ago. Updated over 4 years ago.

Enhancement to existing tests
Target version:
Start date:
Due date:
% Done:


Estimated time:



openQA test in scenario sle-12-SP3-Desktop-DVD-Updates-x86_64-qam-regression-message@64bit fails in


Fails since (at least) Build 20171109-1

Expected result

Last good: 20171108-1 (or more recent)

Further details

Always latest result in this scenario: latest


#1 Updated by pcervinka over 4 years ago

  • Status changed from New to In Progress

There was definitely change on AOL side. I manually checked mailbox, and there is note about change, which will begin after 7.11. Test stopped working 9.11.
Hi nooops_test3,

AOL is committed to protecting the privacy and security of our customers. This is why we're writing to inform you that your current third party email application is not using the latest, secure mail connection settings. In order to continue sending and receiving AOL Mail via your application, you must update your connection settings by November 7, 2017.

Please visit our help site for instructions on how to update your settings.

To avoid having to make changes in the future and to ensure you are using up-to-date security settings, we recommend that you download the AOL app or use to send and receive your AOL Mail.

#2 Updated by pcervinka over 4 years ago

According to new AOL documentation port 993 should be used for connection, but our test use auto configuration based on domain Auto configuration is downloaded from Gnome servers, but it still serves old data
I compared(and manually tested) it with Mozilla Thunderbid .
Mozilla runs fine and their data doesn't contain any reference to port 143.

#4 Updated by okurz over 4 years ago

Very cool investigation :) You could check for that error condition within the test and apply the settings "manually" with a "record_soft_failure"

#5 Updated by pcervinka over 4 years ago

I'm just thinking to switch it from AOL to Gmail to avoid this situation. It will use same autodiscovery, just for different domain. Or I can softfail AOL and add Gmail to have more smoke. What do you think?

#6 Updated by okurz over 4 years ago

Hm, I don't know which one will be more stable so at best I would in the test try one and if it fails try the second, if both fail, then fail the test.

#7 Updated by pcervinka over 4 years ago

Fix created and submitted
It tries configure, if it fails (hang on folder scanning), test will terminate evolution and try another email provider.

#8 Updated by pcervinka over 4 years ago

Upstream just fixed their bug and evolution_smoke works as before:

But I don't want throw away fix which I did, because it is failover for not responding AOL anyway.
I will just change soft-failure message to contain network error.
Or should I cancel my pull/merge requests?

#9 Updated by okurz over 4 years ago

keep it open. I will comment there.

#10 Updated by pcervinka over 4 years ago

  • Category changed from Bugs in existing tests to Enhancement to existing tests

Upstream bug was solved, the discussion is about enhancement for failover in case of unreachable server.

#11 Updated by pcervinka over 4 years ago

  • Status changed from In Progress to Resolved

Pull request was merged.

Also available in: Atom PDF