yes, you are right previous message i rename my domain (stifix) with
'domain', now the real test
tested with gmail (without 2 verification) can work, but when setting it to
my email domain, can not with traceback error:
ERROR:root:email_auth() failed
Traceback (most recent call last):
File "/Users/sugizo/web2py/gluon/contrib/login_methods/email_auth.py",
line 30, in email_auth_aux
server = smtplib.SMTP(host, port)
File
"/Users/sugizo/miniconda3/envs/python2_prod/lib/python2.7/smtplib.py", line
256, in __init__
(code, msg) = self.connect(host, port)
File
"/Users/sugizo/miniconda3/envs/python2_prod/lib/python2.7/smtplib.py", line
317, in connect
self.sock = self._get_socket(host, port, self.timeout)
File
"/Users/sugizo/miniconda3/envs/python2_prod/lib/python2.7/smtplib.py", line
292, in _get_socket
return socket.create_connection((host, port), timeout)
File
"/Users/sugizo/miniconda3/envs/python2_prod/lib/python2.7/socket.py", line
575, in create_connection
raise err
error: [Errno 65] No route to host
*models/db.py*
from gluon.contrib.login_methods.email_auth import email_auth
# the configuration taken from cpanel (tested both return the same error)
# Outgoing Server: mail.stifix.com, SMTP Port: 25
# Outgoing Server: mail.stifix.com, SMTP Port: 465
auth.settings.login_methods.append(
email_auth("mail.stifix.com:465", "@stifix.com"))
"""
auth.settings.login_methods.append(
email_auth("mail.stifix.com:25", "@stifix.com"))
"""
test ping from another terminal return normal
$ ping mail.stifix.com
PING mail.stifix.com (104.24.99.40): 56 data bytes
64 bytes from 104.24.99.40: icmp_seq=0 ttl=56 time=32.708 ms
64 bytes from 104.24.99.40: icmp_seq=1 ttl=56 time=25.990 ms
^C
--- mail.stifix.com ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 25.990/29.349/32.708/3.359 ms
the error said : No route to host
think it means : from web2py server can not reach smtp server which is
tested on the same machine, can ping smtp server through the terminal
perhaps email_auth() just work for gmail, or another famous mail server
(just guess).
you are right, for ldap_auth, it's work after have the correct
configuration for apacheds in web2py (took time because start apacheds from
scratch), not sure why there is no validation on web2py if system engineer
or system admin input the wrong configuration (everything i've seen the
error log from ldap server through running with no daemonize)
best regards,
stifan
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
