Hello,
I am the test user, mentioned by Tom.
Since some months, and unfortunately still now after your mentioned
upgrade, I get the error "Spam is detected on your post - sorry if it
was a mistake." if I want to comment a post or if I want to create a new
post. It is independent of the conte
On 05/01/17 23:26, Jeremy Stanley wrote:
On 2017-01-02 23:03:07 + (+), Jeremy Stanley wrote:
[...]
We're basically ready to retry the previous upgrade now that some
issues have been identified/corrected by Marton. Change
https://review.openstack.org/408657 to trigger it is waiting on
htt
On 2017-01-02 23:03:07 + (+), Jeremy Stanley wrote:
[...]
> We're basically ready to retry the previous upgrade now that some
> issues have been identified/corrected by Marton. Change
> https://review.openstack.org/408657 to trigger it is waiting on
> https://review.openstack.org/416072 to
On 2017-01-03 10:54:48 +0800 (+0800), Tom Fifield wrote:
[...]
> If you check for a POST after a GET of:
>
> /admin/auth/user/2253/delete/
>
> Around
>
> 2017-02-03 02:52
>
> from
>
> 1.169.254.207
>
> that should be it.
Assuming you mean 2017-01-03 then yes, I see one from that IP
address a
On 03/01/17 07:03, Jeremy Stanley wrote:
On 2016-12-30 12:38:02 +0800 (+0800), Tom Fifield wrote:
This problem (legitimate users having all posts flatly rejected as
spam) is still happening. Any progress?
We're basically ready to retry the previous upgrade now that some
issues have been identi
On 2016-12-30 12:38:02 +0800 (+0800), Tom Fifield wrote:
> This problem (legitimate users having all posts flatly rejected as
> spam) is still happening. Any progress?
We're basically ready to retry the previous upgrade now that some
issues have been identified/corrected by Marton. Change
https://
On 10/11/16 22:23, Jeremy Stanley wrote:
On 2016-11-10 09:19:32 + (+), Marton Kiss wrote:
Jeremy, I can apply and test this patch in a current test environment, it
was sitting there for a while. Usually the config changes of askbot broke
the site.
[...]
If you get a chance, that would
On 2016-11-10 09:19:32 + (+), Marton Kiss wrote:
> Jeremy, I can apply and test this patch in a current test environment, it
> was sitting there for a while. Usually the config changes of askbot broke
> the site.
[...]
If you get a chance, that would be a big help. I have logs from the
fai
Jeremy, I can apply and test this patch in a current test environment, it
was sitting there for a while. Usually the config changes of askbot broke
the site.
Marton
On Wed, Nov 9, 2016 at 10:26 PM Jeremy Stanley wrote:
> On 2016-11-09 19:53:27 + (+), Jeremy Stanley wrote:
> > On 2016-11
On 2016-11-09 19:53:27 + (+), Jeremy Stanley wrote:
> On 2016-11-09 18:11:39 + (+), Jeremy Stanley wrote:
> > On 2016-11-08 19:12:32 +0800 (+0800), Tom Fifield wrote:
> > [...]
> > > Upstream apparently revamped the spam system in the version marked
> > > to upgrade to in:
> > > htt
On 2016-11-09 18:11:39 + (+), Jeremy Stanley wrote:
> On 2016-11-08 19:12:32 +0800 (+0800), Tom Fifield wrote:
> [...]
> > Upstream apparently revamped the spam system in the version marked
> > to upgrade to in:
> > https://review.openstack.org/#/c/274032/
>
> I've gone ahead and approved
On 2016-11-08 19:12:32 +0800 (+0800), Tom Fifield wrote:
[...]
> Upstream apparently revamped the spam system in the version marked
> to upgrade to in:
> https://review.openstack.org/#/c/274032/
I've gone ahead and approved this just now... I was unaware it was
out there waiting for approval. Sorr
Hi infra,
I've got another live report from someone whose post on Ask OpenStack is
being flatly rejected as spam. This is despite the fact we have Ask set
up to send spam to a moderation queue, and I've bumped up the account
karma to a level which should bypass that anyway. Checking on the
Ak
13 matches
Mail list logo
