We need a mailing list to allow public discussion and news

[ydahhrk]

^ Title ^

Currently requesting a certificate for the registration site.

[patybarron]

Hola, compañero!

Pero como, sino estuviera registrado jool.mx pues no sería accesible a todo mundo. Bueno, en el servidor de nombres. Oh, a que te refieres mi estimado?

Paty

2015-03-18 9:48 GMT-06:00 Alberto Leiva Popper notifications@github.com:

^ Title ^

Currently requesting a certificate for the registration site.

— Reply to this email directly or view it on GitHub https://github.com/NICMx/NAT64/issues/143.

[patybarron]

Ah! En Github, para que no se maneje como una carpeta dentro de NICMx?

2015-03-18 10:10 GMT-06:00 Elvia Patricia Barron Cano <epatybarron@gmail.com

:

Hola, compañero!

Pero como, sino estuviera registrado jool.mx pues no sería accesible a todo mundo. Bueno, en el servidor de nombres. Oh, a que te refieres mi estimado?

Paty

2015-03-18 9:48 GMT-06:00 Alberto Leiva Popper notifications@github.com:

^ Title ^

Currently requesting a certificate for the registration site.

— Reply to this email directly or view it on GitHub https://github.com/NICMx/NAT64/issues/143.

[ydahhrk]

What do you mean, if it wasn't registered jool.mx would not be accessible by everyone. Well, in the name server. Oh, what do you mean?

I'm talking about the Public key certificate.

NIC's mailing lists are hosted under nic.mx; it would be a little awkward operation-wise to use jool.mx.

[ydahhrk]

This one is intended to be used to announce new versions coming out: https://mail-lists.nic.mx/listas/listinfo/jool-news

This is for public discussion (though I'll also post news here so people don't have to subscribe to both lists - unless someone objects): https://mail-lists.nic.mx/listas/listinfo/jool-list

Unfortunately, the archives are unavailable, which is counterproductive. This is going to be looked into, though it's a TODO of low priority, and it might take a while. Though the lists are usable, I will not close this issue until the archives are public.

The alias jool@nic.mx can still be used to reach us developers only.

[toreanderson]

I'm not sure if the mailing list actually works; I sent a message to it this morning (about six hours ago), but I still haven't received it back from the list. I am subscribed, and the Receive your own posts to the list? Mailman setting is enabled.

[ydahhrk]

-banging my head against the wall-

OK, thank you; checking.

[ydahhrk]

BTW: In the last mail Tore sent, it said "jool-list@jool-lists.nic.mx" in the "To:" field. I had to manually change it to "jool-list@nic.mx" to reply correctly.

I don't know if I should blame the server for this. Somebody please complain if my answer also had the the destination renamed to "jool-list@jool-lists.nic.mx".

[toreanderson]

That was probably because my message was originally sent to "jool-list@jool-lists.nic.mx" (which didn't work). When I learned of the new address, I used my MUA's "redirect" feature on the already sent e-mail, which probably just changes the envelope recipient address, while leaving the To header intact.

[ydahhrk]

https://mail-lists.nic.mx/pipermail/jool-list/