OVERVIEW
This article describes the feature differences between SFU Groups and SFU Maillist.
CHANGED FEATURES
The following features will not be available in SFU Groups (when compared to SFU Maillist):
| |
SFU Groups |
| Deliver Mail to Members by Default |
Always on - users can no longer turn off email delivery from Exchange Distribution Groups they belong in. |
| Delivery Suspended |
No longer available - users can no longer turn off email delivery from Exchange Distribution Groups they belong in. |
| Welcome Message |
No longer available. |
| Change Log |
Only available to IT admins. |
| Delivery History |
No longer available. |
| Sender Restriction ("Allow List") |
Stays available, but emails sent to a sender restricted Distribution Groups have additional security requirements.
With Exchange Distribution Groups, this will require any sender to authenticate to Exchange. This means that users will need to be signed into an SFU's Approved Email Application in order to send emails to an Exchange Distribution Group with Restricted Senders.
If the sender has not authenticated to Exchange, they will receive a bounce-back message saying their email has not been delivered. In most cases, this applies to those you use IMAP/POP (except for Thunderbird with OAuth2), any unapproved email applications, and any unapproved email integrations with M365.
Migration Impact Note:
After migrating these maillists to Exchange Distribution Groups, this setting will be turned off by default. If you wish to continue having restricted senders on your Distribution Group, you will need to re-enable this setting.
Only course/plan groups will have their Restricted Sender setting migrated.
|
| Maillist Nesting |
Since the permissions model is different in SFU Groups, all owners of groups that contain a nested group will require Group Reader Permissions to that nested group.
Migration Impact Note:
If you are an owner of a maillist that contains a nested maillist, you should seek manager role on that nested maillist prior to migration. If you don't have manager role to nested maillists, they will be automatically removed as members from your maillist upon migration.
You will need to ask for Group Reader Permissions from the owner of the nested maillist in order to re-add it as members to your group.
|
| Self-subscribe or unsubscribe |
No longer available. Use SimpleList if you require this feature. |
ADDED FEATURES
The following features will be new to SFU Groups (on Grouper):
| |
SFU Groups |
| Composite Groups (dynamically generated groups) |
Only available to IT admins |
| Creating Permissions and Attributes |
Only available to IT admins |
| Inherited Permissions and Attributes |
Only available to IT admins |
| Role Permissions and Privileges Automation |
Only available to IT admins |
| Audit Logs |
Only available to IT admins |
| Group Types and Folders |
Only available to IT admins |
| Attestation and Group Validation |
Only available to IT admins |
* IT admins refers to those who have access to the full Grouper interface, which may include members of the local IT administrators and other technical group managers.