renaming @documentfoundation.org mailing lists

[floeff]

Hello,

quite a while ago, we have renamed the @libreoffice.org mailing lists to @global.libreoffice.org for technical reasons. I'd now like to do the same for the @documentfoundation.org mailing lists, namely

  - announce
  - board-discuss
  - discuss
  - mirrors
  - moderators
  - test

The reason behind is that I'd like to split up our mail system into two instances for reasons of load balancing and security. One should contain all private mailing lists as well as e-mail accounts, the other one should contain all public mailing lists. The fact that all our communication tools are on one system at the moment is quite unfortunate.

At @documentfoundation.org, we not only host public mailing lists, but also e-mail accounts. One way to achieve the distinction on the server side is to create a forwarding/transport in the mail system, but I'm not a friend of that, it has a few drawbacks. The other option is to rename the list part, and - like we did with libreoffice.org before - use @global.documentfoundation.org in the future, so each subdomain can be attached to its own MX record (mail server).

Before doing such a change that affects many users, I wanted to ask about your opinion. From a technical point of view, it is IMHO the best solution. Agreeably, it is a bit annoying to update all the website elements and links, and we can do the rename with enough time in advance, but would you generally support this approach?

Thanks,
Florian

[Charles-H_Schulz]

Hello Florian,

Hello,

quite a while ago, we have renamed the @libreoffice.org mailing lists to
@global.libreoffice.org for technical reasons. I'd now like to do the
same for the @documentfoundation.org mailing lists, namely

  - announce
  - board-discuss
  - discuss
  - mirrors
  - moderators
  - test

The reason behind is that I'd like to split up our mail system into two
instances for reasons of load balancing and security. One should contain
all private mailing lists as well as e-mail accounts, the other one
should contain all public mailing lists. The fact that all our
communication tools are on one system at the moment is quite unfortunate.

At @documentfoundation.org, we not only host public mailing lists, but
also e-mail accounts. One way to achieve the distinction on the server
side is to create a forwarding/transport in the mail system, but I'm not
a friend of that, it has a few drawbacks. The other option is to rename
the list part, and - like we did with libreoffice.org before - use
@global.documentfoundation.org in the future, so each subdomain can be
attached to its own MX record (mail server).

Before doing such a change that affects many users, I wanted to ask
about your opinion. From a technical point of view, it is IMHO the best
solution. Agreeably, it is a bit annoying to update all the website
elements and links, and we can do the rename with enough time in
advance, but would you generally support this approach?

It will be annoying whatever we change
Is there merit in requesting that, instead of naming "global", we use
something like "lists.documentfoundation.org" or
"ml.documentfoundation.org" just to shorten the number of letters?

Thanks,

[floeff]

Hi,

It will be annoying whatever we change

that for sure. However, technically, I think it's the best solution.

Is there merit in requesting that, instead of naming "global", we use
something like "lists.documentfoundation.org" or

lists is already in use by the private mailing lists. I aimed for global, because we also do have this for libreoffice.org (like marketing@global.libreoffice.org). I have a preference on keeping this then also for TDF, but...

"ml.documentfoundation.org" just to shorten the number of letters?

...I'm not really vetoeing.

Florian

[floeff]

Hi,

Is ml a language code like Pt-br?

oh, indeed, a very good point - thanks a lot! Yes, it is, just discovered

Florian