Two things: a) is there a single ldap group that controls firstname.lastname@example.org email distribution? If so, is that the same group that controls who has access to build vpn? If so, does that mean everyone we add to that group to access loaner machines receives email@example.com email? b) (unrelated, but related to the filing of this bug) the default assignee and qa contact appears to be broken in bmo.
Assignee: network-operations → server-ops
a) no, distribution lists are manually maintained outside of ldap, with the exception of certain HR related lists like mv-all@, contractors@, employees@, etc. Furthermore, I think there are about three different ldap bits that Releng employees get, of which only one is used for the build-vpn and I'm not aware of anything else that uses that bit. CC'ing jlazaro to correct me if I'm wrong about that. for b), I'm changing summary and assigning to justdave to see what might be broken about the default assignee and qa contact. What was it set to vs. what it was supposed to be set to?
Assignee: server-ops → justdave
Summary: firstname.lastname@example.org email list based on release ldap group? → default assignee and qa contact appears to be broken in bmo
b) is being handled elsewhere.
Assignee: justdave → jdow
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WONTFIX
Summary: default assignee and qa contact appears to be broken in bmo → email@example.com email list based on release ldap group?
Component: Server Operations: RelEng → RelOps
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.