RE: email notification

2010-09-16 Thread Tim Pinet
Trying using the "submit-as" parameter. http://www.reviewboard.org/docs/manual/dev/users/tools/post-review/#automati ng-post-review I have a common "post" user account and pass the username in the submit-as param. tim -Original Message- From: reviewboard@googlegroups.com [mailto:reviewb

Re: email notification

2010-09-16 Thread Timothy Pinet
Well that URL got mangled... http://www.reviewboard.org/docs/manual/dev/users/tools/post-review/#automating-post-review tim On Sep 16, 12:51 pm, "Tim Pinet" wrote: > Trying using the "submit-as" parameter. > > http://www.reviewboard.org/docs/manual/dev/users/tools/post-review/#a... > ng-post-re

Re: email notification

2010-09-16 Thread Madhavi Gupta
Hi Tim, Thanks for the response. I am setting the parameter "submit-as" and giving the name of actual user who is committing. When the request is created, I can see the submitter as that user. The email body also contains that user's name as a signature. However email is sent from common user's

Re: email notification

2010-09-16 Thread Jan Koprowski
Yeap and You can't change this behavior, unfortunately :( On Fri, Sep 17, 2010 at 7:11 AM, Madhavi Gupta wrote: > Hi Tim, > > Thanks for the response. > > I am setting the parameter "submit-as" and giving the name of actual user > who is committing. > > When the request is created, I can see the

Re: email notification

2010-09-16 Thread Christian Hammond
Hi Madhavi, This is a known bug that we'll likely fix in a 1.5.x point release (and possibly backport to 1.0.x, but we're hoping to migrate people onto 1.5.x). See http://code.google.com/p/reviewboard/issues/detail?id=1795 Christian -- Christian Hammond - chip...@chipx86.com Review Board - http

Re: email notification

2010-09-16 Thread Madhavi Gupta
Okay. Thanks. On Fri, Sep 17, 2010 at 11:34 AM, Christian Hammond wrote: > Hi Madhavi, > > This is a known bug that we'll likely fix in a 1.5.x point release (and > possibly backport to 1.0.x, but we're hoping to migrate people onto 1.5.x). > See http://code.google.com/p/reviewboard/issues/detail

Re: Email notification and webserver port?

2009-08-04 Thread Lars Olsson
Responding to my self. Restarting of the webserver did the trick. I think it could be worth looking into which settings that needs a webserver restart to become active, and see if we can remove the restart dependency. cheers, lars 2009/8/4 Lars Olsson > Hi, > > I am running my reviewboard ser

Re: Email notification : test email not sent & no trace in logging file

2014-10-30 Thread David Trowbridge
It sounds like it's just timing out trying to contact your mail server. I don't think there's any existing logging that would help here. We should probably add more, but a lot of the mail plumbing happens in django, where we can't add additional logging. -David On Thu, Oct 30, 2014 at 5:59 AM, w

Re: Email notification : test email not sent & no trace in logging file

2014-10-31 Thread fabrice . aupert
Hi David, Thanks for the quick answer. We're using GMail SMTP server via TLS on port 465 to send our emails. Test SMTP access from bash (openssl s_client -connect ...) on the same machine works fine. Are you aware of any trouble accessing GMail SMTP via TLS from Django and/or ReviewBoard ? Ch

Re: Email notification : test email not sent & no trace in logging file

2014-10-31 Thread fabrice . aupert
I finally managed to make it work by changing port to 587. Thanks for your time. Fabrice Le vendredi 31 octobre 2014 09:03:22 UTC+1, fabrice...@tma-asp.com a écrit : > > Hi David, > > Thanks for the quick answer. > > We're using GMail SMTP server via TLS on port 465 to send our emails. Test > S