Open grahammcculloch opened 7 years ago
GS doesn’t use nested mailing lists, I presume to prevent delivery loops. It does allow you to add players to lists based on database criteria though, e.g. if “Squad” includes “M1” then add to the Men’s 1s list. What it doesn’t do, which would be handy is allow the use of multiple criteria, but I presume because that was more complicated to implement!
Neil
On 26 Aug 2017, at 22:29, Graham McCulloch notifications@github.com wrote:
Part of the migration away from GroupSpaces
Use our own mail server. Integrate rules etc into the admin interface so anyone can edit them.
Reply to all vs reply to sender setting per group Front-end form to assign users to email groups 'Nested'/'Composite' groups? Built-in email tracking? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/cshc/cshc_website/issues/225, or mute the thread https://github.com/notifications/unsubscribe-auth/AFJp43tuVadpV1N-Tt-KiWruFFhOwXK4ks5scI5IgaJpZM4PDn_B.
Re: nested mailing lists, yep - we prob couldn't do it like men@cambridgesouthhockeyclub.co.uk
includes the email address m1@cambridgesouthhockeyclub.co.uk
. I was thinking more that we'd have logic that said merge all addresses in the M1 list when determining the Men's list
. But this may be an unneccessary complication if we just use logic such as Include all users who are in the M1s Squad when creating the M1s email list
etc.
Even then its tricky because SquadMembership
references Members
(not Users
- to which email addresses are attached). This issue might prompt us to re-think how we deal with Members/Players/Users. Although this would be a big upheaval!
Part of the migration away from GroupSpaces
Use our own mail server. Integrate rules etc into the admin interface so anyone can edit them.