Versions Compared

Old Version 10

changes.mady.by.user Benn Oshrin

Saved on

compared with

New Version 11

changes.mady.by.user Benn Oshrin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Registry CO Person Transaction

Changelog Mailman Action

Add

Synchronize the CO Person and their Mailman list subscriptions

Edit

Synchronize the CO Person and their Mailman list subscriptions (this includes CO Group Membership changes)

Enter Grace Period

No changes (unless attributes change as part of grace period)

Expiration / Becomes Inactive

Unsubscribe the CO Person from Mailman lists

Unexpire / Becomes Active

Synchronize the CO Person and their Mailman list subscriptions

Delete

No changes (subscriptions will be removed due to loss of CO Group Memberships)

Manual Provision

Synchronize the CO Person and their Mailman list subscriptions

...

Registry CO Group Transaction

Changelog Mailman Action

Add

No changes

Edit

No changes

(info) If a CO Group is suspended, all of the associated CO Group Members are effectively removed for purposes of subscription synchronization

Delete

No changes

Manual Provision

No changes

...

Registry CO Email List Transaction

Changelog Mailman Action

Add

Create a corresponding Mailman list, and synchronize subscriptions

Edit

Synchronize the corresponding Mailman list, including subscriptions

(info) If the status of the list is Suspended, the list will remain in place but all subscriptions will be removed

(warning) Renaming a list is not supported

Delete

Removes the corresponding Mailman list

Manual Provision

Synchronize the corresponding Mailman list, including subscriptions

...

Note
titleImportant Constraints
  • An address can only be attached to one Mailman user, so if for some reason an address is registered multiple times, only one Mailman user can have it.
  • A CO Person can only have one active address, since the preferred address is used for Mailman message delivery.
  • Mailman Users span domains, so in a multi-tenant instance (or a single tenant instance where more than one provisioner is configured to provision more than one domain), each tenant will likely require its own mailman server, not just its own domain.
  • Registry assumes it has full management of Mailman Users. If an email address is directly added to Mailman, and that email address is subsequently added to a Registry record that is then provisioned to Mailman, the provisioning action will fail, since Mailman will indicate that the address already exists (but Registry won't have any knowledge of it).
  • Renaming a list is not supported. Changing the list name in Registry will not change the list name in Mailman.

...


See Also