Why not just look up the MX record of the destination host and connect to the destination's SMTP server on port 25?
On Thursday, January 3, 2013 11:10:16 PM UTC-6, andjarnic wrote: > > Hi all, > > I am wondering what the general census is on apps that, after installed, > upon initial startup (or in a prefs, config, etc) ask a user for permission > to use their credentials to post to facebook, twitter, flicr, S3, dropbox, > and even to use their gmail account to directly email on their behalf? > > I am playing around with a simple app idea that would like to send out > emails on the user's behalf, but I can't afford a central email service, so > my thought was, if the user grants me access, I can use their credentials > to send email through gmail api on their behalf. > > Thus..my question is.. does this scare end users? If my description on the > market indicates that after initial installation, the app, in order to best > perform what it does to save the user time, requires their permission to > send out emails on their behalf, post to facebook, etc (the app would allow > the user to choose when to post to facebook, send emails, etc),will require > them to authorize my app to act on their behalf.. is this something that > most end users understand and are OK with? This is similar to an app like > yahoo allowing a user to log in with facebook info.. they user has to > accept the permission pop-up from facebook allowing yahoo (or other sites) > to use their facebook info. > > Thanks > -- You received this message because you are subscribed to the Google Groups "Android Discuss" group. To view this discussion on the web visit https://groups.google.com/d/msg/android-discuss/-/M6Fz9_i8EEEJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en.
