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 <[email protected]> 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 > <[email protected]> wrote: >> >> : Every individual email "From: [email protected]" 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 [email protected] 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: [email protected] >> For additional commands, e-mail: [email protected] >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
