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 723539 - Use SmtpAuth* properties from org.gnome.OnlineAccounts.Mail
Use SmtpAuth* properties from org.gnome.OnlineAccounts.Mail
Status: RESOLVED FIXED
Product: evolution-data-server
Classification: Platform
Component: general
3.11.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on: 720262
Blocks:
 
 
Reported: 2014-02-03 14:20 UTC by Debarshi Ray
Modified: 2014-02-10 21:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Debarshi Ray 2014-02-03 14:20:15 UTC 
Since 3.11.5 gnome-online-accounts exports the SASL mechanism(s) used by the SMTP server over D-Bus. Currently it knows about LOGIN, PLAIN and XOAUTH2. Please read those properties instead of implicitly assuming PLAIN or XOAUTH2.
Comment 1 Matthew Barnes 2014-02-04 17:29:38 UTC 
Is it guaranteed if the account exports an OAuth2Based interface that the SASL mechanism will be XOAUTH2?  Just wondering whether the property or the interface is more authoritative.
Comment 2 Debarshi Ray 2014-02-04 22:01:16 UTC 
I can imagine a pathological scenario where a provider might use OAuth2 tokens but does not use the XOAUTH2 SASL mechanism for its mail service. Maybe it has some other custom OAuth2 based SASL mechanism. It sounds silly but that is how it is for SMTP's PLAIN and LOGIN mechanisms.
Comment 3 Matthew Barnes 2014-02-04 22:26:56 UTC 
I hear that.  Okay, so I'll take the mechanism name as authoritative and trust that an OAuth2Based interface will always accompany XOAUTH2.  That sounds more foolproof.
Comment 4 Debarshi Ray 2014-02-05 08:15:22 UTC 
(In reply to comment #3)
> I hear that.  Okay, so I'll take the mechanism name as authoritative and trust
> that an OAuth2Based interface will always accompany XOAUTH2.  That sounds more
> foolproof.

Sure. That makes sense.