Still Invalid mail addresses, and unassociated commits at GH

Magnus Ihse Bursie magnus.ihse.bursie at
Fri Feb 19 08:27:14 UTC 2021

On 2021-02-19 08:19, Thomas Stüfe wrote:
> Hi Magnus,
> Thanks a lot for helping! Answers inline below.
> On Thu, Feb 18, 2021 at 5:31 PM Magnus Ihse Bursie 
> <magnus.ihse.bursie at <mailto:magnus.ihse.bursie at>> 
> wrote:
>     On 2021-02-18 15:38, Thomas Stüfe wrote:
>     > Hi guys,
>     >
>     > It has been six months now.
>     >
>     >
>     <>
>     > - we still have invalid mail addresses like
>     stuefe at <mailto:stuefe at>, which
>     > cannot be replied to, read or verified in GitHub. They clutter
>     the mailing
>     > list archive with invalid mail addresses too.
>     I do believe this works now. At least I get mails to
>     ihse at <mailto:ihse at> delivered to
>     my Oracle mail address. Maybe the
>     mapping for non-Oracle mail address is not finished yet..?
>     (I also get mails to ihse at <mailto:ihse at>,
>     but that seems to work only from
>     Oracle's SMTP servers, not from outside servers)
> Yes, seems this started working for us too. At least for 
> stuefe at <mailto:stuefe at>. 
> stuefe at <mailto:stuefe at> and both org variants 
> don't get through. Remaining nit is that Github still marks 
> stuefe at <mailto:stuefe at> as 
> undeliverable, but I can live with that.
>     >
>     <>
>     > - we also still have this issue, which may linked to the invalid
>     mail
>     > addresses, that a large number of the developers has no real
>     link between
>     > their GitHub user and their commits to openjdk are not linked to
>     their user
>     > name. The proposed workaround of adding the unverified openjdk
>     mail address
>     > to GH did not work, at least not in my case.
>     >
>     > Is there any hope that these issues will be resolved? Should I
>     open bugs to
>     > track these?
>     Once again, it works for me. See e.g.
>     <>
>     I have added "ihse at <mailto:ihse at>" as a
>     mail address to my Github account.
>     I think the trick is to use <>, not
> <> -- maybe
>     that is what you have done?
> I tried, in the past, <> and 
> <>, without success. I'll 
> retry with your suggestion (leaving out the java part).

There are only two domains that are of interest here -- 
(which we have traditionally been using) and (which we would 
like to transition to, but things are moving slowly for this kind of 
changes within Oracle). There is no nor, so you 
don't need to test those.

Skara is creating commits for OpenJDK projects with the form 
<openjdk-id>, so that is what you need to add to your github 
profile to get commits connected to your profile.

The PR comment mail bridge bot sends mail with the sender specified as 

The reason for this disconnect is, I assume, the fact that commits will 
be Forever<tm>, and there we want it to look right from the start. But 
the mails are sent right now, and for practical reasons it was simpler 
(if not "simple") to get mail working, than for

I assume the long-term goal here is to make the bots send mail using 
<openjdk-id> as well, and to get that MTA working. I believe 
Tim is working as well as he can to push this forward, but this is an 
unusual request within Oracle and that unfortunately makes it painful 
and slow to go through with. :(


>     Unverified
>     >
>     > Thanks & Cheers, Thomas
> Thanks again,
> Thomas

More information about the skara-dev mailing list