StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>In a nutshell - you will not be able to do that via OAuth. The main reason is that it's generally imposible to (reliably, continuously) send mails in volume on behalf of random users, i.e. users that are not on the domain that you control.</p> <ol> <li><p>If you use OAuth than you will need to ask for access to users profile/email during OAuth procedure. This varies from provider to provider. Some providers never make email available (Twitter). See <a href="https://github.com/leleuj/pac4j" rel="nofollow">pac4j</a> library that provides unified API to retrieve user's OAuth profile from different providers.</p></li> <li><p>When (and if) you get email adress from OAuth, than you will need to send email on behalf of that user. Since your SMTP server is not authorised to send emails on behalf of random users (see <a href="http://en.wikipedia.org/wiki/Sender_Policy_Framework" rel="nofollow">SPF</a> and <a href="http://en.wikipedia.org/wiki/DomainKeys_Identified_Mail" rel="nofollow">DKIM</a>) you will quickly get on spam lists and be blocked. If this was easy then spammers would have easy life.</p></li> <li><p>You can send email on users behalf from AppEngine, but only if users log in via <a href="https://developers.google.com/appengine/docs/java/users/overview" rel="nofollow">Users Java API</a>, which is only available to Gmail or Google Apps accounts.</p></li> <li><p>On GAE you can easily use external SMPT server, via the new <a href="https://developers.google.com/appengine/docs/features#Trusted_Tester_Featureshttp://" rel="nofollow">Outbound Sockets API</a> (this just went from trusted tester feature to experimental feature in sdk 1.7.7). We have this setup and it works with no problem, using a large external SMTP service. But this does not help much with what you want to achieve, considering the point 2 above.</p></li> </ol>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload