nicely put, tim probably having more alternative ways to verify users is the way to go
On Mon, Sep 12, 2011 at 3:23 AM, Tim Hoffman <[email protected]> wrote: > HI Milosh > Unfortunately there is no guarunteed way to be sure someone has read the > mail sent. > In fact it would in some cases be considered an invasion of privacy ;-) > If's not fundamentally part of email. and read receipt implementations are > very much > mail server dependent. > The most you can say about any sent email (after a number of days) with > correctly operating mail servers is that it was > delivered to a mail server ;-) > And the OP was complaining about not having exceptions raised when > non-existent emails where used to send email. Which is > definately not something I would expect would happen via the mail api. OP > said "I found there are not exceptions thrown even the recipient > email addresses don't exist at all. " I am not sure how the mail api could > possibly do this, as you may not get the fact that the email bounced because > of a non existing email address for days. > Rgds > Tim > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/mjyFNmD05M4J. > 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/google-appengine?hl=en. > -- Milosh Zorica http://www.linkedin.com/in/miloshzorica phone: +44 20 8144 5294 e-mail: [email protected] skype: milosh.zorica -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. 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/google-appengine?hl=en.
