Re: Review Request Email Sender as Submitter Blocked by AWS SES.

Hi Barret, The domain is verified. Based on http://docs.aws.amazon.com/ses/latest/DeveloperGuide/verify-domains.html, it should be okay to send email from any email address with the domain. I just submitted a support case to AWS to check if this is the case. I will post the feedback here. Is

Re: Review Request Email Sender as Submitter Blocked by AWS SES.

Hi Tiger, Are you sure you have verified noreply.reviewbo...@mydomain.net ? It should work if you do that. See: http://stackoverflow.com/questions/13699933/how-can-i-use-my-users-non-verified-addresses-as-senders-with-amazon-ses

Re: Review Request Email Sender as Submitter Blocked by AWS SES.

Hi Barret, I set 'SYSTEM SETTINGS/E-Mail/E-MAIL DELIVERY SETTINGS/Sender e-mail address' to noreply.reviewbo...@mydomain.net (mydomain.net is verified), but it is still been blocked. It seem I the From: field is the issue. Is there way to have the From: file be set to same a sender? .

Re: skipping or excluding versions within a range

Aaron, Here is how I do this for SVN, it's not the cleanest but it works. The key is not to post-review on the branch explicitly, but pseudo-post-review (for lack of a better term) on the branch relative to trunk. Make all your changes to your branch and commit, as you are doing. Eventually

Re: Review Request Email Sender as Submitter Blocked by AWS SES.

Hi Tiger, In the Admin panel, under e-mail, there is a setting for the sender’s e-mail address. You can set this to, for example, nore...@mydomain.com and then authorize only that e-mail with SES. E-mails will still appear to be from the user who submitted the

Review Request Email Sender as Submitter Blocked by AWS SES.

Hello, I'd like to use AWS SES as SMTP server for my reviewboard (being migrated/update from 1.7.7.1 to 2.5.4). When I submit review request (through pre-commit), the email is blocked as the submitter's email address is not verified with SES. I do not want each user to verify their email for

Re: skipping or excluding versions within a range

Aaron, There's no good way to skip intermediate revisions when posting a change. Probably your best bet is to use rbtools to post the range, but use the -I or -X flags to specifically include or exclude whole files. -David On Mon, May 9, 2016 at 10:24 AM Aaron Lager

skipping or excluding versions within a range

Is there a way to skip or exclude one or more revisions when generating the diffs? Or some other way to remove unwanted diffs within a range? The use case I'm in is I was working on a new feature branch, while the rest of the team was working on trunk. Once a day I would sync to trunk and