The ONAP Project uses Groups.io list management tools to configure and maintain the mailing lists associated with the project. Groups.io is free software for managing electronic mail discussion and e-newsletter lists. Groups.io is integrated with the web, making it easy for users to manage their accounts and for list owners to administer their lists. Groups.io supports built-in archiving, automatic bounce processing, content filtering, digest delivery, spam filters, and more. See the Grouos.io Help for additional information.

The following things will cause your message to be Moderated. Your message will be delayed and maybe even deleted.

Be sure that you belong to a mailing list before sending email to it. Frequently people will be cc'd on a mailing list email and will "Reply" without checking if they are registered member.

DO NOT have more than 10 recipients. If you do the system will consider your message to be spam and it will be held for moderation

Join the onap-lf-announce list

It is strongly recommended that everyone joins the onap-lf-announce list.This distribution list is used exclusively for official out-bound communications from the Linux Foundation to the ONAP community regarding issues such as service outages. Please do not select the "Digest" option when subscribing to this particular list

We have seen on some occasions that subscribe verification notices end up either getting blocked by company level spam filters or end up in someone's junk folder,

If you try using the LIST-NAME-join email and still do not get a reply, please send an email to helpdesk@onap.org indicating the list you would like to join and noting that repeted attempts have failed and someone will add you by hand.

It seems that there is no defined nor followed netiquette for ONAP mailing lists.

I see that a lot of people respond using top-posting, html content, fancy html footers which are hard to strip from the message etc.

html content and footers are really annoying for people (like me) who intentionally disable html content in their mail client.

Additionally html footers which are not separated with a typical – are hard to strip out and they mix with email content.

Above two together with common top-posting practice makes emails and especially mailing list archives very hard to read. I don't wanna to blame anyone so I don't provide any link to the archive but I recommend to just try to open any longer (above 10 messages) topic and then try to read, understand and guess who wrote which part of the email.

That's why I would like to kindly suggest to define and follow ONAP mailing lists netiquette which follows good USENET practices described for example here.

Well of course bottom posting is not sth you can easily enforce, you need to educate participants and remind them.

But html stuff is sth that should be quite easy to do. I saw a lot of mailing lists which siply rejects the message if it's not a plain text. I expect that ONAP lists could be also configured in that way