Bug 1193908
| Summary: | Ignores GOA (gnome-online-accounts) configuration regarding SMTP AUTH | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Grega Bremec <gregab> | ||||
| Component: | evolution-data-server | Assignee: | Matthew Barnes <mbarnes> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Desktop QE <desktop-qa-list> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 7.1 | CC: | mbarnes, mcrha, vbenes | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-05-05 15:36:33 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Grega Bremec
2015-02-18 14:34:46 UTC
Thanks for a bug report. I guess this will need to backport the below upstream patches: - https://git.gnome.org/browse/evolution-data-server/commit/?id=f3575e798878 - https://git.gnome.org/browse/evolution-data-server/commit/?id=462a170ff99b - https://git.gnome.org/browse/evolution-data-server/commit/?id=44160d305887 - https://git.gnome.org/browse/evolution-data-server/commit/?id=e2bda892fd36 Even the last patch requires GOA 3.11.5 and newer to be fully used. Created attachment 993453 [details]
evolution-data-server-3.8.5-goa-smtp-auth.patch
A patch, which contains all the above commits at once.
I made a test build with the above patch included at [1]. Feel free to install it and check out whether the fix works. You might restart the machine (or re-login) after it's installed. [1] https://people.gnome.org/~mcrha/rh1193908/ Perfect, Milan, this works like a charm. :) Thanks a lot for the *very* quick response and solution. After about two weeks of testing the proposed fix, there is now another problem with Gmail that pops up instead of the original one. Upon sending a message using a GOA-configured Gmail account, I get an error message from Evolution saying: "An error occurred while sending. How do you want to proceed?" "The reported error was "Bad authentication response from server." I have previously been able to use Gmail normally (at least as far as I can remember), but if you want me to, I can revert the package to the original RHEL 7.1 beta version and test. (In reply to Grega Bremec from comment #6) > Upon sending a message using a GOA-configured Gmail account, I get an error > message from Evolution saying: > > "An error occurred while sending. How do you want to proceed?" > "The reported error was "Bad authentication response from server." Thanks for the update. The GOA configured account uses OAuth(/OAuth2) authentication, with the token taken from GOA. These tokens can expire, though I do not know for how long they are given. Could you open Online Accounts in Settings to see whether it doesn't claim an expired token error there, please? Also, could you run evolution from a terminal as follows: $ CAMEL_DEBUG=smtp evolution and then reproduce the error, please? It'll show what was sent and what was received when trying to send the message, which may give more detailed error description. Hi, Milan, thanks for the quick update. Upon checking, everything seems OK in the GOA control panel applet (no errors, I also tried checking off "Use google for: mail" and then back on again, no complaints). The result of CAMEL_DEBUG=smtp is fairly terse and does not really reveal anything except the client works as it should if it were a normal SMTP client (so no OAuth here, apparently): sending : EHLO [192.168.144.140] sending : STARTTLS sending : EHLO [192.168.144.140] sending : AUTH PLAIN base64encodedusernameandpassword= Immediately after this, I get the "Bad authentication response from server." error. When using openssl s_client to connect directly to port 465 of 173.194.65.108 (smtp.gmail.com, it won't accept connections to 25/tcp), I obviously got a rejection from Gmail because I use app-specific passwords (which I can not specify in GOA). I just realized that this fix is already included in 3.12.11, to which the evolution packages will be rebased for RHEL 7.2, thus I'm marking this as a duplicate of the rebase bug. *** This bug has been marked as a duplicate of bug 1174414 *** |