Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works

Email sending functionality

email oauth 2.0

  • Please log in to reply



    New Member

  • Member
  • Pip
  • 1 posts
We are developing a desktop app and want to add email sending functionality from within. The problem we now have is that the old smtp libraries are no longer entirely adequate since providers like gmail now call them 'applications that do not meet modern security standards'. They still allow you to enable less secure apps to access your email account, but the user is no doubt going to be put off by this and we want to avoid that. On the other hand, the OAUTH 2 protocol that seems to prevail requires consumer key and security to be provided by the email provider and we cannot surely collect these from every provider that our users may subscribe with.
My question is: What is the standard approach these days to email sending from within desktop applications? Can we just use good old TLS and live with the potential consequences? Surely there are loads of applications that do not implement oauth - every fax machine, photocopier or printer can send emails, it seems quite doubtful to me that they use OAUTH.
Thanks in advance! 

  • 0


Similar Topics

Also tagged with one or more of these keywords: email, oauth 2.0

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP