Autogenerated lists: firstname.lastname@example.org: anyone with a moco address email@example.com: anyone with a mofo address firstname.lastname@example.org: all-moco & all mofo Alias: email@example.com to firstname.lastname@example.org Also - we'd like to replace the email@example.com in Google.
Also - we'd like to replace the firstname.lastname@example.org in Google with email@example.com. But I'll need to coordinate to do that.
Now is probably a good time to define exactly who should be on these lists. For moco, do we just want @mozilla.com, or also @mozilla-japan.org, since those are both in the same org in LDAP.. For Mofo, I'm assuming all @mozillafoundation.org e-mails. I'd propose that we ignore any @mozilla.org e-mails, since those are scattered around o=com, o=org and o=net randomly and are usually not employees. We also need to know where the current all-moco-mofo list is. Is that a mailman list that gets autogenerated? Should firstname.lastname@example.org just be an alias to all-moco-mofo as well?
rtucker just found this: https://support.google.com/a/answer/66338?hl=en It might be the more appropriate action to take here.
Hi Jabba - so I did create a list called email@example.com with the dynamic list mentioned in comment 3. But the problem is that no one likes that it's @mozilla.com. I'll need some help to get firstname.lastname@example.org into Google
can limed just create a forwarder/alias in postfix to send email@example.com to firstname.lastname@example.org ?
jabba; we can't just forward because Mardi and crew like to send calendar invites to these lists. If the lists don't live in Google then the Google invites stop working.
Here's the new proposed solution: email@example.com (Use https://support.google.com/a/answer/66338?hl=en) firstname.lastname@example.org is an alias for email@example.com firstname.lastname@example.org is an alias for email@example.com Get rid of firstname.lastname@example.org Get rid of email@example.com Any thoughts?
So, I'm not sure I feel strongly about what the DLs are but rather what they do. Here's what I need: 1. The ability to communicate to just moco peeps (we can include Japan since they are in there now). 2. The ability to communicate with just mofo peeps 3. The ability to communicate with both at once (and I'm totally okay to have to use two aliases). 4. The ability to invite the above to meetings + to view a Google cal. So, I don't think we can get rid of all-moco / all-mofo, can we?
Per our meeting with justdave: firstname.lastname@example.org - is a postfix alias to all-moco-mofo in mailing list. membership is autogenerated; Script is for mailman3 in Zimbra module in puppet called mailman.list.py Jabba will work on getting all-moco-mofo in LDAP. he will update the list to also have an inclusion list of people who might not be part of the query but should be added anyway. And an exclusion list to remove the shared and vendor accounts.
I've moved the auto-generated lists to LDAP/google. We currently have email@example.com, firstname.lastname@example.org and email@example.com in google, and they are set to internal-only, meaning only members can post to them. They currently have no aliases. I need to know which aliases to add to them.
Hi Mardi - The only thing we're missing is the aliases. Can you tell me which ones we want to keep? I think we want to prune out as much as we can. But I'm thinking: firstname.lastname@example.org --> email@example.com (so that people don't have to remember the order) firstname.lastname@example.org --> email@example.com All the others - everybody@, all@ and anything else I'm missing goes away. What do you think?
So, we have two aliases that do the same thing: 1) firstname.lastname@example.org 2) email@example.com Do we need both? Also, want to make sure we have firstname.lastname@example.org AND email@example.com as well.
I think it'd be less confusing to make firstname.lastname@example.org go away. It was a legacy name, and currently we're being tripped up by the fact that mozilla.org is not hosted on Google, which breaks calendar invites. The safe thing to do is probably force everyone to use all-moco-mofo and just nuked everyone@.
I'm all for making the fewest possible options.
I think this is done already and we just didn't close the bug.