Hi, folks. Jenkins should use BCC instead of To for sending mass emails to avoid emails disclosure. I'd say that it's not a big issue: these emails are present in somewhere in commit history or interacted with Keycloak development some way with high probability. But it's still not a good style of mass email notifications. RedHat guys, could you please bring this issue to attention of your infra team which manages Jenkins? -- Best regards, Konstantin Gribov _______________________________________________ keycloak-dev mailing list keycloak-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-dev

Stian, email from ci-builds(a)redhat.com with subject "keycloak_master_jdk8-windows-TMP - Build # 3 - Failure!" with URL http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/keycloak_master_jdk8-... Full message is attached below. пн, 24 окт. 2016 г. в 7:27, Stian Thorgersen <sthorger(a)redhat.com&gt;: > What emails are you referring to? > > On 21 October 2016 at 13:06, Konstantin Gribov <grossws(a)gmail.com&gt; wrote: > > Hi, folks. > > Jenkins should use BCC instead of To for sending mass emails to avoid > emails disclosure. I'd say that it's not a big issue: these emails are > present in somewhere in commit history or interacted with Keycloak > development some way with high probability. But it's still not a good style > of mass email notifications. > > RedHat guys, could you please bring this issue to attention of your infra > team which manages Jenkins? > > > -- > > Best regards, > Konstantin Gribov > > _______________________________________________ > keycloak-dev mailing list > keycloak-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/keycloak-dev > > > -- Best regards, Konstantin Gribov _______________________________________________ keycloak-dev mailing list keycloak-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/keycloak-dev