You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by Michael McCandless <lu...@mikemccandless.com> on 2015/09/09 14:58:42 UTC
Re: Any clue why I'm being asked to moderate these messages from the
build system?
It looks like the Jenkins build failures from build@elastic.co are
still requiring moderation ...
Upayavira or Uwe, can you re-check and confirm that build@elastic.co
really is successfully subscribed to dev@lucene.apache.org? Thanks.
Mike McCandless
http://blog.mikemccandless.com
On Sun, Jul 12, 2015 at 3:48 PM, Michael McCandless
<lu...@mikemccandless.com> wrote:
> On Sun, Jul 12, 2015 at 3:47 PM, Upayavira <uv...@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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Any clue why I'm being asked to moderate these messages from the
build system?
Posted by Michael McCandless <lu...@mikemccandless.com>.
On Wed, Sep 9, 2015 at 9:28 AM, Upayavira <uv...@odoko.co.uk> wrote:
> build@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 anything of the moderation messages. Any objections?
Yes please! Thank you for helping out Upayavira!
Mike McCandless
http://blog.mikemccandless.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Any clue why I'm being asked to moderate these messages from the
build system?
Posted by Upayavira <uv...@odoko.co.uk>.
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: build@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
> subscription/whitelisting/blacklisting against the SMTP "sender" info
> from
> the SMTP envelope -- it doesn't check the Return-path header directly.
>
> But in all of the cases i looked at where these build@elastic.co are
> stuck
> in the moderation queue, the addr that was being asked for moderation
> (from the envelope) matched the (UUID-ish) Return-Path header (from the
> message).
>
> ie: the variable Return-Path headers appears to be *symptom* of how the
> SMTP sender is being set to a unique addr everytime, but the envelope
> itself needs fixed to use a consistent address, not just the Return-Path.
>
>
> -Hoss
> http://www.lucidworks.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Any clue why I'm being asked to moderate these messages from the
build system?
Posted by Michael McCandless <lu...@mikemccandless.com>.
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 McCandless
<lu...@mikemccandless.com> wrote:
> 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
> <ho...@fucit.org> wrote:
>>
>> : Every individual email "From: build@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
>> subscription/whitelisting/blacklisting against the SMTP "sender" info from
>> the SMTP envelope -- it doesn't check the Return-path header directly.
>>
>> But in all of the cases i looked at where these build@elastic.co are stuck
>> in the moderation queue, the addr that was being asked for moderation
>> (from the envelope) matched the (UUID-ish) Return-Path header (from the
>> message).
>>
>> ie: the variable Return-Path headers appears to be *symptom* of how the
>> SMTP sender is being set to a unique addr everytime, but the envelope
>> itself needs fixed to use a consistent address, not just the Return-Path.
>>
>>
>> -Hoss
>> http://www.lucidworks.com/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Any clue why I'm being asked to moderate these messages from the
build system?
Posted by Michael McCandless <lu...@mikemccandless.com>.
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
<ho...@fucit.org> wrote:
>
> : Every individual email "From: build@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
> subscription/whitelisting/blacklisting against the SMTP "sender" info from
> the SMTP envelope -- it doesn't check the Return-path header directly.
>
> But in all of the cases i looked at where these build@elastic.co are stuck
> in the moderation queue, the addr that was being asked for moderation
> (from the envelope) matched the (UUID-ish) Return-Path header (from the
> message).
>
> ie: the variable Return-Path headers appears to be *symptom* of how the
> SMTP sender is being set to a unique addr everytime, but the envelope
> itself needs fixed to use a consistent address, not just the Return-Path.
>
>
> -Hoss
> http://www.lucidworks.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Any clue why I'm being asked to moderate these messages from
the build system?
Posted by Chris Hostetter <ho...@fucit.org>.
: Every individual email "From: build@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
subscription/whitelisting/blacklisting against the SMTP "sender" info from
the SMTP envelope -- it doesn't check the Return-path header directly.
But in all of the cases i looked at where these build@elastic.co are stuck
in the moderation queue, the addr that was being asked for moderation
(from the envelope) matched the (UUID-ish) Return-Path header (from the
message).
ie: the variable Return-Path headers appears to be *symptom* of how the
SMTP sender is being set to a unique addr everytime, but the envelope
itself needs fixed to use a consistent address, not just the Return-Path.
-Hoss
http://www.lucidworks.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Any clue why I'm being asked to moderate these messages from
the build system?
Posted by Chris Hostetter <ho...@fucit.org>.
: build@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 repeat) the problem is
that the build@elastic.co emails are only using "build@elastic.co" as the
*From* addr -- which is largely meaningless in modern mail software these
days.
Every individual email "From: build@elastic.co" is usually a completley
distinct "Return-Path" header...
Return-Path: <00...@amazonses.com>
...
Return-Path: <00...@amazonses.com>
...
Return-Path: <00...@amazonses.com>
...
...these addresses are what get compared against hte subscription lists
(and auot-alowed whitelists).
This information was already discusssed with simon, who said he would talk
to the relevant people in control of build@elastic.co to get this fixed --
but that was in June and there haven't been any replies (to that
dev-owner thread) since.
-Hoss
http://www.lucidworks.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Any clue why I'm being asked to moderate these messages from the
build system?
Posted by Upayavira <uv...@odoko.co.uk>.
build@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 wrote:
> It looks like the Jenkins build failures from build@elastic.co are
> still requiring moderation ...
>
> Upayavira or Uwe, can you re-check and confirm that build@elastic.co
> really is successfully subscribed to dev@lucene.apache.org? Thanks.
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Sun, Jul 12, 2015 at 3:48 PM, Michael McCandless
> <lu...@mikemccandless.com> wrote:
> > On Sun, Jul 12, 2015 at 3:47 PM, Upayavira <uv...@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
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org