I used 587 port, but I still got some errors as below

[Tue Apr 09 07:19:02 2013] [error] Traceback (most recent call last):
[Tue Apr 09 07:19:02 2013] [error]   File 
"/usr/local/lib/python2.7/dist-packages/ReviewBoard-1.7.6-py2.7.egg/reviewboard/notifications/email.py",
 line 244, in send_review_mail
[Tue Apr 09 07:19:02 2013] [error]     message.send()
[Tue Apr 09 07:19:02 2013] [error]   File 
"/usr/local/lib/python2.7/dist-packages/Django-1.4.5-py2.7.egg/django/core/mail/message.py",
 line 248, in send
[Tue Apr 09 07:19:02 2013] [error]     return 
self.get_connection(fail_silently).send_messages([self])
[Tue Apr 09 07:19:02 2013] [error]   File 
"/usr/local/lib/python2.7/dist-packages/Django-1.4.5-py2.7.egg/django/core/mail/backends/smtp.py",
 line 85, in send_messages
[Tue Apr 09 07:19:02 2013] [error]     new_conn_created = self.open()
[Tue Apr 09 07:19:02 2013] [error]   File 
"/usr/local/lib/python2.7/dist-packages/Django-1.4.5-py2.7.egg/django/core/mail/backends/smtp.py",
 line 48, in open
[Tue Apr 09 07:19:02 2013] [error]     local_hostname=DNS_NAME.get_fqdn())
[Tue Apr 09 07:19:02 2013] [error]   File "/usr/lib/python2.7/smtplib.py", line 
249, in __init__
[Tue Apr 09 07:19:02 2013] [error]     (code, msg) = self.connect(host, port)
[Tue Apr 09 07:19:02 2013] [error]   File "/usr/lib/python2.7/smtplib.py", line 
309, in connect
[Tue Apr 09 07:19:02 2013] [error]     self.sock = self._get_socket(host, port, 
self.timeout)
[Tue Apr 09 07:19:02 2013] [error]   File "/usr/lib/python2.7/smtplib.py", line 
284, in _get_socket
[Tue Apr 09 07:19:02 2013] [error]     return socket.create_connection((port, 
host), timeout)
[Tue Apr 09 07:19:02 2013] [error]   File "/usr/lib/python2.7/socket.py", line 
571, in create_connection
[Tue Apr 09 07:19:02 2013] [error]     raise err
[Tue Apr 09 07:19:02 2013] [error] error: [Errno 111] Connection refused



在 2009年9月9日星期三UTC+8下午9时52分06秒,Dan Myung写道:
>
> We actually got it working.  To make a long story short, I was using 
> the wrong gmail smtp port (587 good, 465 bad).  I'm putting our full 
> thought process down just in case it might be useful. 
>
> No proxy in our network.  The host has a direct route out.  Clients 
> accessing it directly also have no machinery between it. 
>
> on the email settings tab we got: 
>
> server: smtp.gmail.com 
> port: 465 
> username: rev...@dimagi.com <javascript:> 
> password:blahblah 
>
> use TLS is checked. 
>
>
> When i ran the command (which is send_review_mail, not 
> send_review_email as i have in error in the original post), here's the 
> traceback: 
>
> Traceback (most recent call last): 
>   File "<console>", line 1, in <module> 
>   File "/usr/local/lib/python2.6/dist-packages/ReviewBoard-1.0.1- 
> py2.6.egg/reviewboard/reviews/email.py", line 114, in send_review_mail 
>     message.send() 
>   File "/usr/local/lib/python2.6/dist-packages/Django-1.0.2_final- 
> py2.6.egg/django/core/mail.py", line 271, in send 
>     return self.get_connection(fail_silently).send_messages([self]) 
>   File "/usr/local/lib/python2.6/dist-packages/Django-1.0.2_final- 
> py2.6.egg/django/core/mail.py", line 166, in send_messages 
>     new_conn_created = self.open() 
>   File "/usr/local/lib/python2.6/dist-packages/Django-1.0.2_final- 
> py2.6.egg/django/core/mail.py", line 131, in open 
>     local_hostname=DNS_NAME.get_fqdn()) 
>   File "/usr/lib/python2.6/smtplib.py", line 239, in __init__ 
>     (code, msg) = self.connect(host, port) 
>   File "/usr/lib/python2.6/smtplib.py", line 295, in connect 
>     self.sock = self._get_socket(host, port, self.timeout) 
>   File "/usr/lib/python2.6/smtplib.py", line 273, in _get_socket 
>     return socket.create_connection((port, host), timeout) 
>   File "/usr/lib/python2.6/socket.py", line 512, in create_connection 
>     raise error, msg 
> error: [Errno 111] Connection refused 
>
> Upon testing some more, I was actually able to get it working 
> actually.  Turns out port 465 was the culprit actually for the hanging 
> loading on the web interface.  My command line testing with the 
> local_settings.py worked fine with port 587, and I didn't bother to 
> test 465 from the command line, which reproduced a hanging state from 
> the command line. 
>
> So, I cleared the settings.EMAIL_* properties to let reviewboard work 
> as native, and the web interface worked as expected. 
>
> I then tried the command line email again, and was able to reproduce 
> the same exception.  How are the email settings loaded when an email 
> is initiated from the web interface, as it differs from the command 
> line.  We are interested in this because we'd like some additional 
> emails to go out on comments and such, and thought we might just run 
> the email code ourselves via some signal or something. 
>
> Thanks, 
> Dan 
>
>
>
>
> On Sep 8, 7:09 pm, Christian Hammond <chip...@chipx86.com> wrote: 
> > Hi Dan, 
> > 
> > Are you guys behind a proxy server, by any chance? I could see that 
> > potentially causing this to fail. 
> > 
> > What do you have listed in your e-mail settings for Review Board? 
> > 
> > Christian 
> > 
> > -- 
> > Christian Hammond - chip...@chipx86.com 
> > Review Board -http://www.review-board.org 
> > VMware, Inc. -http://www.vmware.com 
> > 
> > 
> > 
> > On Tue, Sep 8, 2009 at 8:13 AM, Dan Myung <dmy...@dimagi.com> wrote: 
> > 
> > > I've got 1.0.1 setup on my Ubuntu box, and seem to have trouble with 
> > > the email settings. 
> > 
> > > I've input all the TLS settings for gmail smtp using a email in our 
> > > hosted account, setup all the TLS and ports for it. 
> > 
> > > However, whenever we try to submit/publish a new review request, the 
> > > publish spinny just spins indefinitely. 
> > 
> > > For kicks, I tried to run the email code from the command line: 
> > 
> > > from reviewboard.reviews import email 
> > > from reviewboard.reviews.models import * 
> > > from django.contrib.auth.models import User #our admin user with a 
> > > valid email address 
> > > email.send_review_email(User.objects.all()[0], 
> > > ReviewRequest.objects.all()[0], 'test email from command 
> > > line','...@emaildomain.com', [], 'reviews/review_request_email.txt') 
> > 
> > > When I first ran it, it would fail because it would be trying to find 
> > > email login/server information from the django settings, which is 
> > > consistent with the EMAIL_* settings builtin to django (http:// 
> > > docs.djangoproject.com/en/dev/ref/settings/#email-host) that the 
> > > standard email API will try to call.  Because those settings don't 
> > > exist in the settings, it tries to default use localhost smtp which is 
> > > not installed on the box. 
> > 
> > > What confuses me is why the settings I just set in the review admin is 
> > > completely ignored. 
> > 
> > > Seeking a workaround, I manually set all the django EMAIL_* settings 
> > > and the above command line code worked to send an email out. 
> > 
> > > Once the settings were manually set, I went back to the web interface 
> > > to try a new submit, but I got the same spinning Loading indicator 
> > > that spins indefinitely. 
> > 
> > > So far, we've never gotten a single review request submission ever to 
> > > email out from the web interface.  Any suggestions on how to get our 
> > > email alerts going out? 
>

-- 
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~----------~----~----~----~------~----~------~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to