list of aliases taken partly from https://www.gnu.org/software/mailman/mailman-admin.pdf

service/lists.md

@@ -596,8 +596,23 @@ migration documentation](https://docs.mailman3.org/en/latest/migration.html#befo
 
    Warn list operator one last time if matches.
 
-3. block mail traffic on the mm2 list
-4. resync the list data (archives and pickle file)
+3. block mail traffic on the mm2 list by adding, for example, the
+   following the eugeni's transport map:
+
+```
+test@lists.torproject.org       error:list being migrated to mailman3
+test-admin@lists.torproject.org error:list being migrated to mailman3
+test-owner@lists.torproject.org error:list being migrated to mailman3
+test-join@lists.torproject.org  error:list being migrated to mailman3
+test-leave@lists.torproject.org error:list being migrated to mailman3
+test-subscribe@lists.torproject.org     error:list being migrated to mailman3
+test-unsubscribe@lists.torproject.org   error:list being migrated to mailman3
+test-request@lists.torproject.org       error:list being migrated to mailman3
+test-bounces@lists.torproject.org       error:list being migrated to mailman3
+test-confirm@lists.torproject.org       error:list being migrated to mailman3
+```
+
+4. resync the list data (archives and pickle file at least)
 5. create the list in mm3
 6. migrate the list pickle file to mm3
 7. migrate the archives to hyperkitty
@@ -607,7 +622,7 @@ migration documentation](https://docs.mailman3.org/en/latest/migration.html#befo
 The above assumes the presence of a `mm3_cleanup.py` script with the
 contents:
 
-```
+```python
 from __future__ import print_function
 
 def check_bounce_info(mlist):
@@ -630,3 +645,7 @@ def list_pending_reqs_owners(mlist):
 def flush_digest_mbox(mlist):
     mlist.send_digest_now()
 ```
+
+The list owners to contact were generated with:
+
+    sudo -u list /var/lib/mailman/bin/withlist -l -a -r mm3_cleanup.list_pending_reqs_owners -q