Unterschiede zu Mailman 2

Differences that will affect most customers:

All previous mailman2 passwords (administrator, moderator and members) are now obsolete! To use the new mailman3 web interface, you must first create a new user account using the ‘Register User’ function of the new web interface. (The user administration of mailman3 is independent of the central user administration of the LRZ, as there are many users of the mailing lists who do not have an LRZ ID.)
AFTER creating a user account, the roles a user has with regard to the mailing lists are determined based on the email address(es) associated with the user account. The usual roles are member, moderator and owner. The roles then determine the rights a user has for a mailing list.
This means that the admin and moderator passwords for a list no longer need to be shared if several people are moderators or owners. Each user has their own personal password.


Example:
The following entry was found in the mailing list beispiel@lists.lrz.de in mailman2:
Owner: max.muster@lrz.de
If Max Muster now creates a user account as described below and uses max.muster@lrz.de as his email address, he will automatically be assigned the role of owner for the mailing list beispiel@lists.lrz.de and, after successfully logging in, he will be able to manage the mailing list beispiel@lists.lrz.de as usual. 
Max Muster now also has the alias address muster@lrz.de, which he used for another list. He can then add this address as an additional email address in his user account and will also receive the associated roles and rights for his user account.
The same applies to moderators and members of mailing lists.


Do NOT use a mailing list email address to register a user account! 
A mailing list is not a user.

  • MM3 provides genuine user management:
    • Most activities relating to a list require registration with the list server → see also below.
      • After the migration date, you can register with your email address at https://lists.lrz.de/accounts/signup/.
      • If you are subscribed to lists with other email addresses, you should enter these email addresses in your account after registering – each of these additional email addresses must be verified.
      • You can then manage your lists. Depending on your role (owner, moderator or member) for the respective list, you will have more or fewer functions available to you.
    • Unlike MM2, each user has their own personal password, which means that passwords no longer need to be shared between moderators, for example.
    • This also eliminates the need for monthly password reminder emails.
  • Owners of a list can delete it → Currently, the list CANNOT be restored!
  • For newly created lists, the From: field is replaced by the list address by default in order to send DMARC-compliant emails.
  • What adjustments need to be made to texts and templates during migration (selection of possibilities)
    • Texts that were adjusted in MM2 within the configuration
      • The fields ‘description’ and “info” in MM2 have a counterpart in MM3 → ‘short description’ and ‘long description’
      • The fields ‘msg_footer’ and “digest_footer” have no counterpart in MM3 → however, they can be reconfigured in the ‘Templates’ tab
    • Texts stored in MM2 under ‘Customise texts and public HTML pages’
      • If provided for in MM3, the texts can be reconfigured in the ‘Templates’ tab.
      • The text describing the page found under ‘Info’ → Summary is configured via the ‘Long description’ field.
      • By default, MM3 adds a footer to emails. If you want to disable this, it must be activated via ‘Templates’ with empty content.

Differences that will affect only a few customers:

  • The ‘Umbrella Lists’ feature has not been implemented in MM3: 
    • A simple form of top-down (parent-child) distribution of emails can also be implemented in MM3.
    • Existing umbrella lists must be reconfigured before migration.
    • Make the following settings in the ‘Parent’ list:
      • from_is_list → Conceal sender
      • accept_these_nonmembers → Store sender and (if necessary) remove from list members
      • Enter the address of the ‘Child’ list in the members
      • Remove the address of the ‘Child’ list from the regular_include_lists field
    • Make the following settings in the ‘Child’ list:
      • require_explicit_destination → No OR
      • require_explicit_destination → Yes AND enter the address of the ‘Parent’ list in acceptable_aliases
      • accept_these_nonmbers → enter the address of the ‘Parent’ list
      • The footers should be adjusted or disabled for all levels, see also above

Registration on the list server:

  • Please follow the 8 steps documented below.
  • Choose a unique username – we recommend using your LRZ ID or your email address.
  • You do not need to solve the captcha in step 2 if you access the sign-up page within the MWN.
  • Steps 7 and 8 are only necessary if you are subscribed to different lists with more than one email address.