Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Wiki Replica
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
The Tor Project
TPA
Wiki Replica
Commits
a500e683
Verified
Commit
a500e683
authored
4 months ago
by
anarcat
Browse files
Options
Downloads
Patches
Plain Diff
add missing bits from puppet
parent
79834171
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Pipeline
#221042
passed with warnings
4 months ago
Stage: build
Stage: test
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
service/lists.md
+41
-17
41 additions, 17 deletions
service/lists.md
with
41 additions
and
17 deletions
service/lists.md
+
41
−
17
View file @
a500e683
...
@@ -695,7 +695,44 @@ details. To migrate a list, the following was used:
...
@@ -695,7 +695,44 @@ details. To migrate a list, the following was used:
fab mailman.migrate-mm2-mm3 tor-relays
fab mailman.migrate-mm2-mm3 tor-relays
The above assumes a
`tpa.mm2_mm3_migration_cleanup`
module in the
The above assumes a
`tpa.mm2_mm3_migration_cleanup`
module in the
Python path, currently deployed in Puppet.
Python path, currently deployed in Puppet. Here's a backup copy:
```
python
from
__future__
import
print_function
def
check_bounce_info
(
mlist
):
print
(
mlist
.
bounce_info
)
def
check_pending_reqs
(
mlist
):
if
mlist
.
NumRequestsPending
()
>
0
:
print
(
"
list
"
,
mlist
.
internal_name
(),
"
has
"
,
mlist
.
NumRequestsPending
(),
"
pending requests
"
)
if
mlist
.
GetSubscriptionIds
():
print
(
"
subscriptions:
"
,
len
(
mlist
.
GetSubscriptionIds
()))
if
mlist
.
GetUnsubscriptionIds
():
print
(
"
unsubscriptions:
"
,
len
(
mlist
.
GetUnsubscriptionIds
()))
if
mlist
.
GetHeldMessageIds
():
print
(
"
held:
"
,
len
(
mlist
.
GetHeldMessageIds
()))
def
list_pending_reqs_owners
(
mlist
):
if
mlist
.
NumRequestsPending
()
>
0
:
print
(
mlist
.
internal_name
()
+
"
-owner@lists.torproject.org
"
)
def
flush_digest_mbox
(
mlist
):
mlist
.
send_digest_now
()
```
It also assumes a
`mm3_tweaks`
on the Mailman 3 server, also in
Python, here's a copy:
```
python
from
mailman.interfaces.mailinglist
import
DMARCMitigateAction
,
ReplyToMunging
def
mitigate_dmarc
(
mlist
):
mlist
.
dmarc_mitigate_action
=
DMARCMitigateAction
.
munge_from
mlist
.
dmarc_mitigate_unconditionally
=
True
mlist
.
reply_goes_to_list
=
ReplyToMunging
.
no_munging
```
The list owners to contact about issues with pending requests was
The list owners to contact about issues with pending requests was
generated with:
generated with:
...
@@ -724,23 +761,10 @@ The following procedure was used for the first test list, to figure
...
@@ -724,23 +761,10 @@ The following procedure was used for the first test list, to figure
out how to do this and help establish the Fabric job. It's kept only
out how to do this and help establish the Fabric job. It's kept only
for historical purposes.
for historical purposes.
To check for anomalies in the mailing lists migrations, the following
To check for anomalies in the mailing lists migrations, with the above
script was used:
`mm2_mm3_migration_cleanup`
script, called with, for example:
```
def check_bounce_info(mlist):
print(mlist.bounce_info)
def check_pending_reqs(mlist):
print(mlist.NumRequestsPending())
def flush_digest_mbox(mlist):
mlist.send_digest_now()
```
and called with for example:
sudo -u list /var/lib/mailman/bin/withlist -l -a -r
check_list_mm3
.check_pending_reqs
sudo -u list /var/lib/mailman/bin/withlist -l -a -r
mm2_mm3_migration_cleanup
.check_pending_reqs
The
`bounce_info`
check was done because of a comment found in
[
this
The
`bounce_info`
check was done because of a comment found in
[
this
post
](
https://docs.debops.org/en/stable-2.1/ansible/roles/mailman/mailman2-migration.html
)
saying the conversion script had problem with those, that
post
](
https://docs.debops.org/en/stable-2.1/ansible/roles/mailman/mailman2-migration.html
)
saying the conversion script had problem with those, that
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment