OK I think we (ES) have fixed the outgoing Jenkins failure emails to
use a "sane" Return-Path SMTP header ... if anyone still sees ES
Jenkins failures emails requiring moderation please let me know!
Thanks.
Mike McCandless
http://blog.mikemccandless.com
On Wed, Sep 9, 2015 at 4:17 PM, Michael
bu...@elastic.co *is* on the allow list for dev, so dunno why it is in
the moderation queue.
If people are okay with it, I'll add myself as a list moderator and see
if I can make anything of the moderation messages. Any objections?
Upayavira
On Wed, Sep 9, 2015, at 01:58 PM, Michael McCandless
On Wed, Sep 9, 2015 at 9:28 AM, Upayavira wrote:
> bu...@elastic.co *is* on the allow list for dev, so dunno why it is in
> the moderation queue.
Phew, we need a mailing-list-debugger.
> If people are okay with it, I'll add myself as a list moderator and see
> if I can make
: bu...@elastic.co *is* on the allow list for dev, so dunno why it is in
: the moderation queue.
As discussed before on the dev-owner list (for the specific purpose of not
distracting the entire dev community with mailing list management issues
-- but alas, since it keeps coming up here i'll
It looks like the Jenkins build failures from bu...@elastic.co are
still requiring moderation ...
Upayavira or Uwe, can you re-check and confirm that bu...@elastic.co
really is successfully subscribed to dev@lucene.apache.org? Thanks.
Mike McCandless
http://blog.mikemccandless.com
On Sun,
Thx Hoss! Seems it is already in hand (or understood at least)
On Wed, Sep 9, 2015, at 03:38 PM, Chris Hostetter wrote:
>
> : Every individual email "From: bu...@elastic.co" is usually a completley
> : distinct "Return-Path" header...
> ...
> : ...these addresses are what get compared
: Every individual email "From: bu...@elastic.co" is usually a completley
: distinct "Return-Path" header...
...
: ...these addresses are what get compared against hte subscription lists
: (and auot-alowed whitelists).
Acctually ... just to clarify: ezmlm verifies
Ahhh, OK thanks for explaining the situation Hoss. I'll talk to Simon
to see how/if we can fix this craziness.
Mike McCandless
http://blog.mikemccandless.com
On Wed, Sep 9, 2015 at 10:38 AM, Chris Hostetter
wrote:
>
> : Every individual email "From:
Due to my (long ago) history with infra, I still have apmail privileges.
I have subscribed bu...@elastic.co to the dev@lucene.apache.org allow
list which should solve this. I could see that it wasn't there before I
did so.
Upayavira
On Sun, Jul 12, 2015, at 07:06 PM, Michael McCandless wrote:
Thanks Upayavira!
Now we wait for a build failure :)
Mike McCandless
http://blog.mikemccandless.com
On Sun, Jul 12, 2015 at 3:21 PM, Upayavira u...@odoko.co.uk wrote:
Due to my (long ago) history with infra, I still have apmail privileges.
I have subscribed bu...@elastic.co to the
On Sun, Jul 12, 2015 at 3:47 PM, Upayavira u...@odoko.co.uk wrote:
I'm sure that's something I could easily bring about, if it helps!
Oh it happens quite effectively on its own :) But thank you for the offer!
Mike McCandless
http://blog.mikemccandless.com
I'm sure that's something I could easily bring about, if it helps!
On Sun, Jul 12, 2015, at 08:32 PM, Michael McCandless wrote:
Thanks Upayavira!
Now we wait for a build failure :)
Mike McCandless
http://blog.mikemccandless.com
On Sun, Jul 12, 2015 at 3:21 PM, Upayavira
I'd like to fix this: it seems silly you all have to moderate these
build failures.
Is it as simple as forcefully subscribing bu...@elastic.co to the
dev list? Does someone know how to do this :)
Except, Uwe mentioned something about maybe needing a specific Jenkins
plugin as well...?
Mike
Hi,
We should simply forcefully subscribe this address to dev@. The reason why
Reply-All does not work is caused by Amazon's mail servers who use a different
header on each mail.
Should I forcefully subscribe this address (have rights to do this)? Just have
to lookup the special mail address
On Sun, Jul 12, 2015 at 1:51 PM, Uwe Schindler u...@thetaphi.de wrote:
We should simply forcefully subscribe this address to dev@. The reason why
Reply-All does not work is caused by Amazon's mail servers who use a
different header on each mail.
Hmm, OK, but we can separately try to address
Clearly they're coming from Elastic..
From: bu...@elastic.co
To: d...@elastic.co, dev@lucene.apache.org, sim...@apache.org
Cc:
Date: Fri, 19 Jun 2015 10:56:46 +
Subject: [CI] Lucene 5x Linux 64 Test Only - Build # 51986 - Failure!
BUILD FAILURE
Build
: Clearly they're coming from Elastic..
pretty sure it's just standard moderatation queue stuff...
the first time a (non-subscribed) addr sends an email to the list, it gets
held in the queue -- if the moderator just hits reply tothe accept
address, then that one message will make it
Right, but I keep getting them even after approving some of them. It's
like the from address keeps changing.
Or I'm just confused. I'll reply-all for a while and we'll see.
On Fri, Jun 19, 2015 at 9:55 AM, Chris Hostetter
hossman_luc...@fucit.org wrote:
: Clearly they're coming from
I’ve reply-all’d to a bunch of these from the moderation queue, but they still
seem to require moderation though.
On Jun 19, 2015, at 1:41 PM, Erick Erickson erickerick...@gmail.com wrote:
Right, but I keep getting them even after approving some of them. It's
like the from address keeps
19 matches
Mail list logo