beam-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kenneth Knowles <...@google.com.INVALID>
Subject Re: [VOTE] Fixing @yyy.com.INVALID mailing addresses
Date Thu, 23 Nov 2017 00:05:42 GMT
+1

On Wed, Nov 22, 2017 at 3:43 PM, Lukasz Cwik <lcwik@google.com.invalid>
wrote:

> +1
>
> On Wed, Nov 22, 2017 at 3:35 PM, Reuven Lax <relax@google.com.invalid>
> wrote:
>
> > +1
> >
> > On Nov 22, 2017 3:29 PM, "Ben Sidhom" <sidhom@google.com.invalid> wrote:
> >
> > > I'm not a PMC member, but this would be especially valuable if it
> > > propagated DKIM signatures properly.
> > >
> > > On Wed, Nov 22, 2017 at 3:25 PM, Lukasz Cwik <lcwik@google.com.invalid
> >
> > > wrote:
> > >
> > > > I have noticed that some e-mail addresses (notably @google.com) get
> > > > .INVALID suffixed onto it so person@yyy.com become
> > > person@yyy.com.INVALID
> > > > in the From: header.
> > > >
> > > > I have figured out that this is an issue with the way that our mail
> > > server
> > > > is configured and opened https://issues.apache.org/
> > > jira/browse/INFRA-15529
> > > > .
> > > >
> > > > For those of us that are impacted, it makes it more difficult for
> users
> > > to
> > > > reply directly to the originator.
> > > >
> > > > Infra has asked to get consensus from PMC members before making the
> > > change
> > > > which I figured it would be easiest with a vote.
> > > >
> > > > Please vote:
> > > > +1 Update mail server to stop suffixing .INVALID
> > > > -1 Don't change mail server settings.
> > > >
> > >
> > >
> > >
> > > --
> > > -Ben
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message