<div dir="ltr">Hi all,<div>So it seems that we will keep the VerifyClient configuration for <a href="https://mailman.egi.eu/pipermail/announcement/">https://mailman.egi.eu/pipermail/announcement/</a> as it is actually configured, the cert being optional it's not really a problem: as it's optional people without a certificate won't see a prompt, and people with one are already used to this.</div><div><br></div><div>Best,</div><div>Baptiste</div><div><br><div class="gmail_quote"><div dir="ltr">On Wed, 5 Dec 2018 at 13:35 Mischa Salle <<a href="mailto:msalle@nikhef.nl">msalle@nikhef.nl</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Baptiste,<br>
<br>
On Wed, Dec 05, 2018 at 01:06:48PM +0100, Baptiste Grenier wrote:<br>
> Hi,<br>
> So I've added Mátyás and Mischa as administrators, please check if you can<br>
> access the administration interface:<br>
> <a href="https://mailman.egi.eu/mailman/admin/announcement/general" rel="noreferrer" target="_blank">https://mailman.egi.eu/mailman/admin/announcement/general</a><br>
> <br>
> X509 is being used to authenticate the admins (so it may be more complex to<br>
> disable it for archives, especially as it's used for other mailing lists),<br>
> let me know if it works for you.<br>
works fine for me, thanks!<br>
<br>
> Otherwise, we will have to check with the mailman admins what could be done.<br>
Not sure if mailman is using real directories or not. If it does,<br>
disabling via an .htaccess SSLVerifyClient for<br>
<a href="https://mailman.egi.eu/mailman/announcement" rel="noreferrer" target="_blank">https://mailman.egi.eu/mailman/announcement</a> is probably doable.<br>
<br>
Best wishes,<br>
Mischa<br>
<br>
> On Wed, 5 Dec 2018 at 11:36 Mischa Salle <<a href="mailto:msalle@nikhef.nl" target="_blank">msalle@nikhef.nl</a>> wrote:<br>
> <br>
> > Hi Baptiste,<br>
> ><br>
> > I don't know how many admins you think is reasonable, but I don't mind<br>
> > being one.<br>
> > Concerning the cert prompt, I have no strong opinions but no prompt is<br>
> > probably indeed easier.<br>
> ><br>
> > Best wishes,<br>
> > Mischa<br>
> ><br>
> > On Tue, Dec 04, 2018 at 02:35:57PM -0600, Mátyás Selmeci wrote:<br>
> > > I can be an admin.<br>
> > ><br>
> > > If it's not a lot of work, it would be nice if we could turn off the<br>
> > > cert prompt. It has no effect but might confuse people.<br>
> > ><br>
> > > Thanks,<br>
> > > -Mat<br>
> > ><br>
> > > ----------------------------------------------------------------------<br>
> > > *From:* Baptiste Grenier [mailto:<a href="mailto:baptiste.grenier@egi.eu" target="_blank">baptiste.grenier@egi.eu</a>]<br>
> > > *Sent:* Tue, Dec 4, 2018 7:20 AM CST<br>
> > > *Subject:* [Gt-eos] GridCF communication channels<br>
> > ><br>
> > > > Hi all,<br>
> > > > I'm happy to do so, but it would also probably be appropriate to<br>
> > > > appoint some additional administrators. Who should/want to be an admin?<br>
> > > ><br>
> > > > So the archives are now publicly<br>
> > > > accessible: <a href="https://mailman.egi.eu/pipermail/announcement/" rel="noreferrer" target="_blank">https://mailman.egi.eu/pipermail/announcement/</a>.<br>
> > > > A client cert can be provided but it's not required, even without it<br>
> > > > access will be granted.<br>
> > > > Is it a problem to have this client cert prompt?<br>
> > > ><br>
> > > > Best,<br>
> > > > Baptiste<br>
> > > ><br>
> > > > On Mon, 3 Dec 2018 at 18:26 Mátyás Selmeci via Gt-eos<br>
> > > > <<a href="mailto:gt-eos@mailman.egi.eu" target="_blank">gt-eos@mailman.egi.eu</a> <mailto:<a href="mailto:gt-eos@mailman.egi.eu" target="_blank">gt-eos@mailman.egi.eu</a>>wrote:<br>
> > > ><br>
> > > > Hi everyone,<br>
> > > ><br>
> > > > The mailing list <a href="mailto:announcement@gridcf.org" target="_blank">announcement@gridcf.org</a><br>
> > > > <mailto:<a href="mailto:announcement@gridcf.org" target="_blank">announcement@gridcf.org</a>> has been created, with<br>
> > > > Baptiste as the administrator.<br>
> > > ><br>
> > > > The web interface is at<br>
> > > > <a href="https://mailman.egi.eu/mailman/listinfo/announcement" rel="noreferrer" target="_blank">https://mailman.egi.eu/mailman/listinfo/announcement</a>.<br>
> > > ><br>
> > > > Baptiste, could you make the mailing list archive public?<br>
> > > ><br>
> > > > Thanks,<br>
> > > > -Mat<br>
> > > ><br>
> > > ><br>
> > > > -------- Original Message --------<br>
> > > > From: Mischa Salle [mailto:<a href="mailto:msalle@nikhef.nl" target="_blank">msalle@nikhef.nl</a><br>
> > > > <mailto:<a href="mailto:msalle@nikhef.nl" target="_blank">msalle@nikhef.nl</a>>]<br>
> > > > Sent: Sun, Nov 18, 2018 6:48 AM CST<br>
> > > > Subject: [Gt-eos] GridCF communication channels<br>
> > > ><br>
> > > > Hi all,<br>
> > > ><br>
> > > > For now we probably should announce things also on the standard<br>
> > > > channels, but for the next steps:<br>
> > > > How about:<br>
> > > > - configuring the <a href="http://gridcf.org" rel="noreferrer" target="_blank">gridcf.org</a> <<a href="http://gridcf.org" rel="noreferrer" target="_blank">http://gridcf.org</a>> domain to have<br>
> > > > <a href="http://relay.muni.cz" rel="noreferrer" target="_blank">relay.muni.cz</a> <<a href="http://relay.muni.cz" rel="noreferrer" target="_blank">http://relay.muni.cz</a>> as its MX (see<br>
> > > > also the quoted GGUS ticket).<br>
> > > > - making a few addresses available, such as<br>
> > > > * <a href="mailto:gct-announce@gridcf.org" target="_blank">gct-announce@gridcf.org</a> <mailto:<a href="mailto:gct-announce@gridcf.org" target="_blank">gct-announce@gridcf.org</a>><br>
> > > > * <a href="mailto:gct-security@gridcf.org" target="_blank">gct-security@gridcf.org</a> <mailto:<a href="mailto:gct-security@gridcf.org" target="_blank">gct-security@gridcf.org</a>><br>
> > > > * <a href="mailto:gct-users@gridcf.org" target="_blank">gct-users@gridcf.org</a> <mailto:<a href="mailto:gct-users@gridcf.org" target="_blank">gct-users@gridcf.org</a>> /<br>
> > > > <a href="mailto:gct-developers@gridcf.org" target="_blank">gct-developers@gridcf.org</a> <mailto:<a href="mailto:gct-developers@gridcf.org" target="_blank">gct-developers@gridcf.org</a>><br>
> > > > which would require configuring egi to accept also for the<br>
> > > > <a href="http://gridcf.org" rel="noreferrer" target="_blank">gridcf.org</a> <<a href="http://gridcf.org" rel="noreferrer" target="_blank">http://gridcf.org</a>><br>
> > > > domain.<br>
> > > ><br>
> > > > gct-announce would be sort of an open list for receiving, but<br>
> > > > only a<br>
> > > > few could post. gct-security the opposite (but probably still<br>
> > > > moderated for posting) and gct-users would be open for<br>
> > > > receiving and<br>
> > > > posting (probably also moderated or we'll get spammed to I<br>
> > > > don't know<br>
> > > > where).<br>
> > > ><br>
> > > > Mischa<br>
> > > ><br>
> > > > On Fri, Nov 16, 2018 at 08:54:54PM +0100, End of Support of Globus<br>
> > > > Toolkit wrote:<br>
> > > > > Hi Mat, all,<br>
> > > > ><br>
> > > > > Perhaps we can disseminate this through OSG, CERN and EGI<br>
> > > > publicity<br>
> > > > > channels in a similar manner? I guess they can all carry<br>
> > > > similar text,<br>
> > > > > pointing to the release and saying a few words about the<br>
> > > > background of the<br>
> > > > > project.<br>
> > > > ><br>
> > > > > Matt<br>
> > > > ><br>
> > > > > On Fri, 16 Nov 2018 at 17:56, Mátyás Selmeci via Gt-eos <<br>
> > > > > <a href="mailto:gt-eos@mailman.egi.eu" target="_blank">gt-eos@mailman.egi.eu</a> <mailto:<a href="mailto:gt-eos@mailman.egi.eu" target="_blank">gt-eos@mailman.egi.eu</a>>wrote:<br>
> > > > ><br>
> > > > >> Hi everyone,<br>
> > > > >><br>
> > > > >> Where does this stand? We now have an official release that<br>
> > > > we should<br>
> > > > >> announce.<br>
> > > > >><br>
> > > > >> Thanks,<br>
> > > > >> -Mat<br>
> > > > >><br>
> > > > >> On 10/26/18 2:38 AM, Baptiste Grenier via Gt-eos wrote:<br>
> > > > >><br>
> > > > >> Hi all,<br>
> > > > >> So is it possible to update the MX server record in the DNZ<br>
> > zone?<br>
> > > > >> There is a GGUS ticket to discuss this with the mailman admins:<br>
> > > > >> <a href="https://ggus.eu/index.php?mode=ticket_info&ticket_id=137738" rel="noreferrer" target="_blank">https://ggus.eu/index.php?mode=ticket_info&ticket_id=137738</a><br>
> > > > >><br>
> > > > >> Best,<br>
> > > > >> Baptiste<br>
> > > > >><br>
> > > > >> On Mon, 15 Oct 2018 at 16:13 Baptiste Grenier<br>
> > > > <<a href="mailto:baptiste.grenier@egi.eu" target="_blank">baptiste.grenier@egi.eu</a> <mailto:<a href="mailto:baptiste.grenier@egi.eu" target="_blank">baptiste.grenier@egi.eu</a>><br>
> > > > >> wrote:<br>
> > > > >><br>
> > > > >>> Hi,<br>
> > > > >>> So It should be possible to use a different domain name with<br>
> > > > our mailman<br>
> > > > >>> instance, to do so you could start by changing the<br>
> > > > <a href="http://gridcf.org" rel="noreferrer" target="_blank">gridcf.org</a> <<a href="http://gridcf.org" rel="noreferrer" target="_blank">http://gridcf.org</a>> MX to use<br>
> > > > >>> <a href="http://relay.muni.cz" rel="noreferrer" target="_blank">relay.muni.cz</a> <<a href="http://relay.muni.cz" rel="noreferrer" target="_blank">http://relay.muni.cz</a>> (as our mailman uses<br>
> > > > this SMTP server, mailman emails are<br>
> > > > >>> not sent through Google's SMTP) instead of the actual default<br>
> > MX<br>
> > > > >>> configuration of the <a href="http://gridcf.org" rel="noreferrer" target="_blank">gridcf.org</a> <<a href="http://gridcf.org" rel="noreferrer" target="_blank">http://gridcf.org</a>> domain<br>
> > > > (pointing to<br>
> > > > >>> <a href="http://eforward5.registrar-servers.com" rel="noreferrer" target="_blank">eforward5.registrar-servers.com</a><br>
> > > > <<a href="http://eforward5.registrar-servers.com" rel="noreferrer" target="_blank">http://eforward5.registrar-servers.com</a>>).<br>
> > > > >>><br>
> > > > >>> This would redirect all <a href="http://gridcf.org" rel="noreferrer" target="_blank">gridcf.org</a> <<a href="http://gridcf.org" rel="noreferrer" target="_blank">http://gridcf.org</a>><br>
> > > > emails to the relay server at CESNET,<br>
> > > > >>> then we could add as many as required mailing lists, with<br>
> > needed<br>
> > > > >>> admin/moderators.<br>
> > > > >>><br>
> > > > >>> If it's not possible/acceptable we could use a subdomain<br>
> > > > (like what we do<br>
> > > > >>> with <a href="http://mailman.egi.eu" rel="noreferrer" target="_blank">mailman.egi.eu</a> <<a href="http://mailman.egi.eu" rel="noreferrer" target="_blank">http://mailman.egi.eu</a>>).<br>
> > > > >>><br>
> > > > >>> Best,<br>
> > > > >>> Baptiste<br>
> > > > >>><br>
> > > > >>> On Fri, 12 Oct 2018 at 19:08 Brian Bockelman<br>
> > > > <<a href="mailto:bbockelm@cse.unl.edu" target="_blank">bbockelm@cse.unl.edu</a> <mailto:<a href="mailto:bbockelm@cse.unl.edu" target="_blank">bbockelm@cse.unl.edu</a>><br>
> > > > >>> wrote:<br>
> > > > >>><br>
> > > > >>>><br>
> > > > >>>> Hi,<br>
> > > > >>>><br>
> > > > >>>> Let's go ahead and check with the <a href="http://egi.eu" rel="noreferrer" target="_blank">egi.eu</a> <<a href="http://egi.eu" rel="noreferrer" target="_blank">http://egi.eu</a>><br>
> > > > folks and see what they<br>
> > > > >>>> believe is possible.<br>
> > > > >>>><br>
> > > > >>>> If not, I'll be happy to setup a GSuite subscription for<br>
> > > > <a href="http://gridcf.org" rel="noreferrer" target="_blank">gridcf.org</a> <<a href="http://gridcf.org" rel="noreferrer" target="_blank">http://gridcf.org</a>>;<br>
> > > > >>>> we've done this for other projects (<a href="http://scitokens.org" rel="noreferrer" target="_blank">scitokens.org</a><br>
> > > > <<a href="http://scitokens.org" rel="noreferrer" target="_blank">http://scitokens.org</a>>, <a href="http://iris-hep.org" rel="noreferrer" target="_blank">iris-hep.org</a> <<a href="http://iris-hep.org" rel="noreferrer" target="_blank">http://iris-hep.org</a>>,<br>
> > > > >>>> <a href="http://sand-ci.org" rel="noreferrer" target="_blank">sand-ci.org</a> <<a href="http://sand-ci.org" rel="noreferrer" target="_blank">http://sand-ci.org</a>>) and that has worked out<br>
> > well.<br>
> > > > >>>><br>
> > > > >>>> Brian<br>
> > > > >>>><br>
> > > > >>>> On Oct 12, 2018, at 3:23 AM, Baptiste Grenier<br>
> > > > <<a href="mailto:baptiste.grenier@egi.eu" target="_blank">baptiste.grenier@egi.eu</a> <mailto:<a href="mailto:baptiste.grenier@egi.eu" target="_blank">baptiste.grenier@egi.eu</a>><br>
> > > > >>>> wrote:<br>
> > > > >>>><br>
> > > > >>>> Hi,<br>
> > > > >>>> I agree that a <a href="http://gridcf.org" rel="noreferrer" target="_blank">gridcf.org</a> <<a href="http://gridcf.org" rel="noreferrer" target="_blank">http://gridcf.org</a>> domain is<br>
> > > > preferable. If it works with a free<br>
> > > > >>>> Google subscription it may probably be the most<br>
> > > > straightforward.<br>
> > > > >>>> If it's not an option then we can check with <a href="http://egi.eu" rel="noreferrer" target="_blank">egi.eu</a><br>
> > > > <<a href="http://egi.eu" rel="noreferrer" target="_blank">http://egi.eu</a>> IT guys to see if<br>
> > > > >>>> we could get a mailing list with a custom domain name.<br>
> > > > >>>><br>
> > > > >>>><br>
> > > > >>>> _______________________________________________<br>
> > > > >> Gt-eos mailing list<br>
> > > > >> <a href="mailto:Gt-eos@mailman.egi.eu" target="_blank">Gt-eos@mailman.egi.eu</a> <mailto:<a href="mailto:Gt-eos@mailman.egi.eu" target="_blank">Gt-eos@mailman.egi.eu</a>><br>
> > > > >> <a href="http://mailman.egi.eu/mailman/listinfo/gt-eos" rel="noreferrer" target="_blank">http://mailman.egi.eu/mailman/listinfo/gt-eos</a><br>
> > > > >><br>
> > > ><br>
> > > > > _______________________________________________<br>
> > > > > Gt-eos mailing list<br>
> > > > > <a href="mailto:Gt-eos@mailman.egi.eu" target="_blank">Gt-eos@mailman.egi.eu</a> <mailto:<a href="mailto:Gt-eos@mailman.egi.eu" target="_blank">Gt-eos@mailman.egi.eu</a>><br>
> > > > > <a href="http://mailman.egi.eu/mailman/listinfo/gt-eos" rel="noreferrer" target="_blank">http://mailman.egi.eu/mailman/listinfo/gt-eos</a><br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > ><br>
> > > > _______________________________________________<br>
> > > > Gt-eos mailing list<br>
> > > > <a href="mailto:Gt-eos@mailman.egi.eu" target="_blank">Gt-eos@mailman.egi.eu</a> <mailto:<a href="mailto:Gt-eos@mailman.egi.eu" target="_blank">Gt-eos@mailman.egi.eu</a>><br>
> > > > <a href="http://mailman.egi.eu/mailman/listinfo/gt-eos" rel="noreferrer" target="_blank">http://mailman.egi.eu/mailman/listinfo/gt-eos</a><br>
> > > ><br>
> > > > --<br>
> > > > Baptiste Grenier<br>
> > > > EGI Foundation - Operations Officer<br>
> > > > Phone: +31 627 860 852<br>
> > > > Skype: baptiste.grenier.egi<br>
> ><br>
> ><br>
> ><br>
> > --<br>
> > Nikhef Room H155<br>
> > Science Park 105 Tel. <a href="tel:+31%2020%20592%205102" value="+31205925102" target="_blank">+31-20-592 5102</a> <+31%2020%20592%205102><br>
> > 1098 XG Amsterdam Fax <a href="tel:+31%2020%20592%205155" value="+31205925155" target="_blank">+31-20-592 5155</a> <+31%2020%20592%205155><br>
> > The Netherlands Email <a href="mailto:msalle@nikhef.nl" target="_blank">msalle@nikhef.nl</a><br>
> > __ .. ... _._. .... ._ ... ._ ._.. ._.. .._..<br>
> ><br>
> -- <br>
> Baptiste Grenier<br>
> EGI Foundation - Operations Officer<br>
> Phone: +31 627 860 852<br>
> Skype: baptiste.grenier.egi<br>
<br>
-- <br>
Nikhef Room H155<br>
Science Park 105 Tel. <a href="tel:+31%2020%20592%205102" value="+31205925102" target="_blank">+31-20-592 5102</a><br>
1098 XG Amsterdam Fax <a href="tel:+31%2020%20592%205155" value="+31205925155" target="_blank">+31-20-592 5155</a><br>
The Netherlands Email <a href="mailto:msalle@nikhef.nl" target="_blank">msalle@nikhef.nl</a><br>
__ .. ... _._. .... ._ ... ._ ._.. ._.. .._..<br>
</blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br></blockquote></div></div></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Baptiste Grenier</div><div>EGI Foundation - Operations Officer</div><div>Phone: +31 627 860 852</div><div>Skype: baptiste.grenier.egi</div></div></div>