Hi - Fairly silently. In the case of running the dev_appserver.py - submitting a correct email and password to login form just shows a very quick response of invalid login (flash message). Compared to running the web2py built in web server the response is too fast to let me believe that my computer talked to the smtp server I am validating against.. i.e. the request just failed as a failed login. But I am testing against my organization's smtp and against the gmail smtp, which work fine with the web2py built in server.
I am not an experienced python debugger, and my attempts to try and step through the smtplib code fail with the GAE - funny errors like non-ascii characters in the source files, which make me think that debugger I tried (winpdb) didn't like the GAE environment. The deployed application also shares the same problem. Somehow debugging whether GAE is letting a TLS request go through correctly seems puzzling. I was fairly interested in using the GAE because it came with an easy https access option, (I don't mind the appspot subdomain). I have a short term app that I wanted security for. Googling I've seen some mentions that sockets are not implemented fully on GAE, but I don't know if that is currently the case. I would be delighted to get an error message or exception - let me know how to turn that on if it exists in inside the smtplib, for example. There could be some silly mistake I am making - I have made a few hundred so far, but because the implementation in this case seems so simple, I think that GAE might be at fault. Is there a workaround do you think? In anycase this development process has really been fun - web2py is a nice environment to work in. On Jan 23, 7:21 pm, Massimo Di Pierro <massimo.dipie...@gmail.com> wrote: > Did you try it? How does it fail? > > On Jan 23, 4:07 am, pattu <itapplicationmanagem...@gmail.com> wrote: > > > Hi - > > > I have found 150 answers to different questions already by googling my > > way through this list, but I didn't find anything addressing > > email_auth (using an smtp server). Here is code that works fine > > running the web2py server, but seems to fail both on the GAE > > development server and also deployed. I might have missed something, > > but I have tried to be exhaustive here: > > > ########################################################################### > > ##### > > #Test this out: Doesn't work on GAE in development or on Appspot... =- > > ( > > ########################################################################### > > ##### > > # > > # > > from gluon.contrib.login_methods.email_auth import email_auth > > > #Try with default - same as auth.settings.login_methods = > > [email_auth(server="gmail.com:587", domain="@gmail.com")] > > > auth.settings.login_methods = [email_auth()] > > auth.settings.actions_disabled=['register','change_password','request_reset > > _password', > > 'profile'] > > > Has anybody used email_auth on gae? Or does anyone know why it fails, > > and any ideas how to start debugging this? > > > Patrick > >
