# Mailinglists We do have several mailing list for internal and external communication. This page will sort out what lists exists, and how do manage them. *A short reminder: Email is, for now, the most inclusive and reliable (even if everybody hates it). Even if you use instant messaging services, please do consider sending an email.* ## Lists \ Members: the plenum, the core of the Angrezi collective.\ Reachable: Publicly\ New members: By invitation only, sign-out by administrator\ Administration: (These people should also have access to the **Sharepoint group** hosted with the HfK. Remember that **memberships** in the mailing list and the Sharepoint group are now separated and need to be **managed individually**.) **This was previously. Please do NOT use that any more!** \ Members: people that are or were in one way or another involved with Angrezi: Old plenum members, people from courses, people that are interested, externals.\ Reachable: Publicly\ New members: Sign-In and Out yourself\ Administration: **This was previously. Please do NOT use that any more!** \ Members: People that contributed to the programme. That is simple!\ Reachable: Publicly\ New members: by invitation, sign-out yourself\ Administration: \ Members: People that should get our broadcasts announcements: Press departments, cooperation partners, other radios, venues in Bremen. Also Telegram: \ Reachable: Publicly\ New members: by invitation, sign-out yourself\ Administration: \ Members: People that run / keep running / make / develop the studio / the infrastructure. Reachable: Publicly\ New members: by invitation, sign-out yourself\ Administration: \ Members: People that are trained to do engineering, and available. New members: by invitation, sign-out yourself\ Administration: ## Mailman server For a lack of a better solution (or a different domain provider, which is scheduled to change in Jan 2020) the mailing lists are hosted for free with mailman at the University of Bremen. Since Jelko did not like to have addresses ending with `@mailman.zfn.uni-bremen.de` he cheated his way around build forwards form `@radioangrezi.de` to the mailman server. (Due to restrictions with one.com we could not realize list addresses with `@lists.radioangrezi.de` which would make future changes much easier.) DNS MX record for radioangrezi.de: one.com mailserver **All lists are forwarded by hand at one.com!** * → * → * → * → * → * → Schema: → x'@mailman.zfn.uni-bremen.de\ **x and x' need to match!** Because: At each mailman list `radioangrezi.de` is set as `host_name`. This way the list actually seems to be running on radioangrezi.de, and not at the University. It's a hack. Actually it would be nice to have a mailman (or similar) that actually allows CNAMEing at `lists.radioangrezi.de` for example. **Conclusion: If you add lists. You need to add forwards!** -owner and -bounce -request -join -leave are **not forwarded so far**! That might cause a ton of problems. Let's see! ;) In the beginning we created a few more lists. So currently (2019-03-25) we got (freshly signed up, not configured): RA-artists\ RA-communication\ RA-friends\ RA-hq\ RA-plenum\ RA-programme\ RA-promotion\ RA-tech RA-engineers from: ## list configuration cheat sheet Configuration: ### General Options real\_name = RA-… owner = host\_name = radioangrezi.de new\_member\_options = 1: Y 2: N 3: Y 4: Y max\_message\_size = 0 ### Passwords admin pw: (the one mailing list password) ### Language options preferred\_language = english ### Non-digest options msg\_footer: `📻` `THIS IS RADIO ANGREZI` `more specifically the %(real_name)s@%(host_name)s mailing list. list info / unsubsribe at %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s` ### Privacy options... \[Subscription rules] subscribe\_policy = unsubscribe\_policy = \[Sender filters] generic\_nonmember\_action = Accept (Sure?) \[Recipient filters] require\_explicit\_destination = No max\_num\_recipients = 50 topics = Probably no, testing on RA-hq ### Texts Welcome email text file `WELCOME TO RADIO ANGREZI` `You are now a member of the %(real_name)s@%(host_name)s mailing list! %(welcome)s To post to this list, send your message to:` `%(emailaddr)s` `General information about the mailing list is at:` `%(listinfo_url)s` `Any questions? Reach out to radioangrezi@hfk-bremen.de` `Nice to have you!` --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.radioangrezi.de/tech-deep-dive/mailinglists.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.