TPA team issueshttps://gitlab.torproject.org/tpo/tpa/team/-/issues2024-03-28T01:14:48Zhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41539Create an operations email list2024-03-28T01:14:48Zal smithCreate an operations email listThe operations team needs an email list to coordinate its work. (This will help with our grants@torproject.org email issues, as we'll be able to reduce the number of people using that alias once the operations list is established.)
**Re...The operations team needs an email list to coordinate its work. (This will help with our grants@torproject.org email issues, as we'll be able to reduce the number of people using that alias once the operations list is established.)
**Requirements**
1. Does **not** require a moderation queue
2. Allows people who are not subscribed to the list to send email to the list **without friction**
3. Is not archived (for anyone, including members of the list)
4. Is not displayed on lists.torproject.org
Is that something a list can do?
If so, we request `tor-operations@` to be created. :smile:
Note: It's possible that an operations list exits already, per this ticket from 8 years ago, but I don't think so based on my quick test. Just adding for due diligence since I noticed it: https://gitlab.torproject.org/tpo/tpa/team/-/issues/15992Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.org2024-03-31https://gitlab.torproject.org/tpo/tpa/team/-/issues/41399New provider requirements for deliverability2024-02-22T15:43:37Zmicahmicah@torproject.orgNew provider requirements for deliverabilityThe new [google](https://blog.google/products/gmail/gmail-security-authentication-spam-protection/) etc. requirements that [impact deliverability](https://www.validity.com/blog/gmail-yahoo-users-will-be-able-to-stop-spam-emails-with-just...The new [google](https://blog.google/products/gmail/gmail-security-authentication-spam-protection/) etc. requirements that [impact deliverability](https://www.validity.com/blog/gmail-yahoo-users-will-be-able-to-stop-spam-emails-with-just-one-click/) are coming
The [guidance that google provides](https://support.google.com/mail/answer/81126) must be satisfied by February of 2024.
There are a number of things on this that we do, and I think at least one thing that we do not do (one-click unsubscribe), but I am not the best at evaluating if we are going to be ok here.improve mail servicesanarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41268Remove duncan@ as a tor-qa list admin2023-07-19T17:43:41ZdonutsRemove duncan@ as a tor-qa list adminAt some point I was added, but I don't even know the admin password and I don't do anything with the list notifications either (besides delete them for cluttering up my inbox). If you need a new admin, I'd nominate richard :)At some point I was added, but I don't even know the admin password and I don't do anything with the list notifications either (besides delete them for cluttering up my inbox). If you need a new admin, I'd nominate richard :)anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41206new mailing list: team-leads2023-06-09T19:22:59Zanarcatnew mailing list: team-leadsplease make a new mailing list for the team leads to coordinate, team-leads@lists.tpoplease make a new mailing list for the team leads to coordinate, team-leads@lists.tpoJens KubiezielJens Kubiezielhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41150Deal with spam on bad-relays@ mailing list2023-11-08T17:25:30ZGeorg KoppenDeal with spam on bad-relays@ mailing listWe lately got a lot of spam to bad-relays@. That's a private mailing list where folks should be able to send reports to, though. Is there a mailman option or something to get rid of that spam while still allowing to get legit submissions...We lately got a lot of spam to bad-relays@. That's a private mailing list where folks should be able to send reports to, though. Is there a mailman option or something to get rid of that spam while still allowing to get legit submissions as usual? Or do we have to admit defeat here and move on with the status quo? An example spam mail looks like this:
```
From - Tue May 2 06:57:07 2023
X-Account-Key: account19
X-UIDL: 98521d39b4fe4f6493c53a0097f19f0b
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
X-Mozilla-Keys:
Return-Path: <bad-relays-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on vireo.riseup.net
X-Spam-Level:
X-Spam-Pyzor: Reported 0 times.
X-Spam-Status: No, score=-2.3 required=9.0 shortcircuit=no autolearn=disabled
version=3.4.6
X-Spam-Report:
* 0.3 NOMATCH_NICK_FROM From address with no part of name
* 0.1 FROM_ADMIN Common in mailphishing
* 0.0 PSTOCK_PART multipart/mixed possibly PNG attachment
* 0.0 FORWARD_RELAY Appears to be relayed through list or forwarding
* 0.0 ENV_FROM_DIFF0 Envelope From differs from from (eg list)
* -0.0 SPF_HELO_PASS SPF: HELO matches SPF record
* -0.0 SPF_PASS SPF: sender matches SPF record
* -0.0 USER_IN_WELCOMELIST_TO User is listed in 'welcomelist_to'
* 0.2 HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level
* mail domains are different
* 0.0 ODD_PUNCTUATION2 BODY: general bad punctuation as in 419s
* 0.2 EXCITED_PLING BODY: Two adjacent sentences end with exclamation
* marks
* 0.1 PHISH_CGI URI: Common cracked phishing destination
* 0.5 HREF_PHISH6 URI: HTTP link to static consumer address
* 1.6 HTML_IMAGE_ONLY_12 BODY: HTML: images with 800-1200 bytes of
* words
* 0.0 HTML_MESSAGE BODY: HTML included in message
* 0.7 MPART_ALT_DIFF BODY: HTML and text parts are different
* 0.1 HTML_LINK_NR_TOP RAW: Short HTML message with link near top
* 0.1 LINK_NR_TOP RAW: Short message with link near top
* 0.0 HREF_PHISH7 RAW: Very short text accidentally linked
* 0.1 SRC_HTTP RAW: Contains external (tracking) images?
* 0.0 CK_419SIZE typical 419 size - avoid matches in long text
* 0.1 CK_KARD_SIZE short, card virus size - avoid matches in long
* text
* -0.0 T_SCC_BODY_TEXT_LINE No description available.
* 0.8 KAM_INFOUSMEBIZ Prevalent use of
* .info|.us|.me|.me.uk|.biz|xyz|id|rocks|life domains in
* spam/malware
* -0.1 AM_TRUNCATED Compensate on large message for misfiring rules
* 0.0 KAM_DMARC_STATUS Test Rule for DKIM or SPF Failure with Strict
* Alignment
* 0.1 HTML_SHORT_LINK_IMG_1 HTML is very short with a linked image
* -6.0 USER_IN_WHITELIST_TO DEPRECATED: See USER_IN_WELCOMELIST_TO
* -1.0 MAILING_LIST_MULTI Multiple indicators imply a widely-seen list
* manager
* -0.2 TXREP TXREP: Score normalizing based on sender's reputation
Delivered-To: gk-tpo@riseup.net
Received: from mx1.riseup.net (mx1-pn.riseup.net [10.0.1.33])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256
client-signature RSA-PSS (2048 bits) client-digest SHA256)
(Client CN "mx1.riseup.net", Issuer "R3" (not verified))
by vireo.riseup.net (Postfix) with ESMTPS id 4Q99z800Q5z47
for <gk-tpo@riseup.net>; Mon, 1 May 2023 18:02:27 +0000 (UTC)
Received: from eugeni.torproject.org (eugeni.torproject.org [49.12.57.136])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
key-exchange X25519 server-signature RSA-PSS (2048 bits))
(No client certificate requested)
by mx1.riseup.net (Postfix) with ESMTPS id 4Q99z749XtzDqCn;
Mon, 1 May 2023 18:02:27 +0000 (UTC)
Received: from eugeni.torproject.org (localhost [IPv6:::1])
by eugeni.torproject.org (Postfix) with ESMTP id 1BC0EE0524;
Mon, 1 May 2023 18:02:26 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by eugeni.torproject.org (Postfix) with ESMTP id 498C5E0522
for <bad-relays@lists.torproject.org>; Mon, 1 May 2023 18:02:21 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at
Received: from eugeni.torproject.org ([127.0.0.1])
by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id 8Njwl-0BuAvp for <bad-relays@lists.torproject.org>;
Mon, 1 May 2023 18:02:21 +0000 (UTC)
Received: from acrey.alcretemic.com (acrey.alcretemic.com [208.77.145.122])
by eugeni.torproject.org (Postfix) with ESMTP id 15AD0E051F
for <bad-relays@lists.torproject.org>; Mon, 1 May 2023 18:02:20 +0000 (UTC)
From: "Lidl" <Admin@acrey.alcretemic.com>
To: bad-relays@lists.torproject.org
MIME-Version: 1.0
Message-Id: <LYRIS-i.c-__Date@acrey.alcretemic.com>
Date: Mon, 01 May 2023 14:02:13 -0400
Subject: [bad-relays] =?utf-8?q?HERZLICHEN_GL=C3=9CCKWUNSCH!_Sie_sind_der?=
=?utf-8?q?_gl=C3=BCckliche_Online-Gewinner_eines_brandneuen_Gewinnspiels_?=
=?utf-8?q?Monsieur_Cuisine_Connect!?=
X-BeenThere: bad-relays@lists.torproject.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussions about malicious and misconfigured Tor relays
<bad-relays.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/bad-relays>,
<mailto:bad-relays-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <https://lists.torproject.org/cgi-bin/mailman/private/bad-relays/>
List-Post: <mailto:bad-relays@lists.torproject.org>
List-Help: <mailto:bad-relays-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/bad-relays>,
<mailto:bad-relays-request@lists.torproject.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1827440705681709861=="
Errors-To: bad-relays-bounces@lists.torproject.org
Sender: "bad-relays" <bad-relays-bounces@lists.torproject.org>
--===============1827440705681709861==
Content-Type: multipart/alternative; boundary="----=NextPart-dec270cb1eea73e35b74ae24a6eced6c"
------=NextPart-dec270cb1eea73e35b74ae24a6eced6c
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
text message
------=NextPart-dec270cb1eea73e35b74ae24a6eced6c
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64
PGh0bWw+DQo8Ym9keT4NCgk8Y2VudGVyPg0KCQk8YSBzdHlsZT0iZGlzcGxheTpub25lOyIgaHJl
Zj0iaHR0cDovLzIzLTIyNy0xNzQtNjYuc3RhdGljLmh2dmMudXMvNE8wMTA1OW5pYTBpcDU4di1u
ZGZrMnIxcXpoMjR6Mzg0cjRicTAwMDAxIiA+LjwvYT4NCgkJPGEgaHJlZj0iaHR0cDovLzIzLTIy
Ny0xNzQtNjYuc3RhdGljLmh2dmMudXMvMU8wMTA1OW5pYTBpcDU4di1uZGZrMnIxcXpoMjR6Mzg0
cjRicTAwMDAxIiA+DQoJCQk8aDI+QmVlaWxlbiBTaWUgc2ljaCEgRGllIEJlbG9obnVuZ2VuIHNp
bmQgc2Nob24gZGEhPC9oMj4NCgkJPC9hPg0KCQk8YnIgLz4NCgkJPGEgaHJlZj0iaHR0cDovLzIz
LTIyNy0xNzQtNjYuc3RhdGljLmh2dmMudXMvMU8wMTA1OW5pYTBpcDU4di1uZGZrMnIxcXpoMjR6
Mzg0cjRicTAwMDAxIiA+DQoJCQk8aW1nIHNyYz0iaHR0cDovLzIzLTIyNy0xNzQtNjYuc3RhdGlj
Lmh2dmMudXMvMjAvNDYxNy8yMTIzMC9DYlVRYXJlS2Zwdy5qcGciPg0KCQk8L2E+DQoJCTxiciAv
Pg0KCQk8YSBocmVmPSJodHRwOi8vMjMtMjI3LTE3NC02Ni5zdGF0aWMuaHZ2Yy51cy8xTzAxMDU5
bmliMGlwNTh2LW5kZmsycjFxemgyNHozODRyNGJxMDAwMDEiID4NCgkJCTxpbWcgc3JjPSJodHRw
Oi8vMjMtMjI3LTE3NC02Ni5zdGF0aWMuaHZ2Yy51cy8yMC80NjE3LzIxMjMwL1VyTFlTT1dLci5q
cGciPg0KCQk8L2E+DQoJCTxiciAvPg0KCQk8YSBocmVmPSJodHRwOi8vMjMtMjI3LTE3NC02Ni5z
dGF0aWMuaHZ2Yy51cy8xTzAxMDU5bmljMGlwNTh2LW5kZmsycjFxemgyNHozODRyNGJxMDAwMDEi
ID4NCgkJCTxpbWcgc3JjPSJodHRwOi8vMjMtMjI3LTE3NC02Ni5zdGF0aWMuaHZ2Yy51cy84TzAx
MDU5bmlhMGlwNTh2LW5kZmsycjFxemgyNHozODRyNGJxMDAwMDEiPg0KCQk8L2E+DQoJCTxiciAv
Pg0KCTwvY2VudGVyPg0KPC9ib2R5Pg0KPC9odG1sPg==
------=NextPart-dec270cb1eea73e35b74ae24a6eced6c--
--===============1827440705681709861==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
bad-relays mailing list
bad-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/bad-relays
--===============1827440705681709861==--
```
/cc @gman999Georg KoppenGeorg Koppenhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41104Create new alias ac-admins2023-04-13T14:08:44Zmicahmicah@torproject.orgCreate new alias ac-adminsThe anti-censorship team would benefit from an alias that can be used as a sort of 'role' email address for their team. For example, the azure portal for the meek configuration had Sina configured there, and now it has meskio setup there...The anti-censorship team would benefit from an alias that can be used as a sort of 'role' email address for their team. For example, the azure portal for the meek configuration had Sina configured there, and now it has meskio setup there, but it is a bit of a single point of failure, when that could be configured to be `ac-admins@torproject.org` with it pointing to `meskio`, `shelikhoo`, `cohosh` and `micah`.anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41082Each tor-announce@ mail causes 500-1000 yahoo bounces and mailman never disab...2023-02-20T20:44:26ZRoger DingledineEach tor-announce@ mail causes 500-1000 yahoo bounces and mailman never disables the accountsEvery time a tor-announce@ mail goes out, the tor-announce owner gets 500-1000 messages of the form
```
I'm afraid I wasn't able to deliver the following message.
This is a permanent error; I've given up. Sorry it didn't work out.
```
...Every time a tor-announce@ mail goes out, the tor-announce owner gets 500-1000 messages of the form
```
I'm afraid I wasn't able to deliver the following message.
This is a permanent error; I've given up. Sorry it didn't work out.
```
And here is what mailman has to say in those mails:
```
The attached message was received as a bounce, but either the bounce
format was not recognized, or no member addresses could be extracted
from it. This mailing list has been configured to send all
unrecognized bounce messages to the list administrator(s).
```
I did some spot checking, and (a) the address is indeed a current tor-announce@ subscriber, and (b) eugeni's logs show the mail being successfully delivered to yahoo.
So it would seem that the mail is being delivered properly, and then yahoo is sending us mail on its own afterwards saying that our mail never really got anywhere.
And mailman doesn't know any automated way to handle that mail, which means the address stays subscribed and the process happens again on the next post.
It can't be good for our email reputation to bomb yahoo with thousands of known bad attempts each time. I wonder if there's something to be done to let mailman recognize them properly.anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/41025Ask for closing tor-relays-fr mailing list2023-01-09T19:50:00ZChreAsk for closing tor-relays-fr mailing listHi all,
Can you close tor-relays-fr mailing list please? Thanks for help :smile:
Many of us, French relay operators and Tor volunteers, thought it would be useful to restart the tor-relays-fr list, to discuss Tor relays in French.
Ha...Hi all,
Can you close tor-relays-fr mailing list please? Thanks for help :smile:
Many of us, French relay operators and Tor volunteers, thought it would be useful to restart the tor-relays-fr list, to discuss Tor relays in French.
Having lost access to the original list created in 2012, we asked The Tor Project to create a new one. Arma was kind enough to respond, and despite his questions about the relevance of such a list, agreed to play along.
This new tor-relays list was created on 9/22/2020. Thank you Tor Project!
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays-fr
But... after over two years of existence, this list is clearly not very active. Probably because most people running Tor relays are fluent enough in English to discuss directly on... tor-relays.
So we announce the closing of this list at the beginning of this year 2023, and we invite interested people to use on tor-relays (in English) !
Thank you for your help in trying to keep this list alive :smile:anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/40951review and retire old lists2023-06-28T14:38:24Zanarcatreview and retire old listswhile removing the tor-teachers list (#40947) i wondered how many active lists we actually did have left. so i took a look...
we have 65 lists:
```
root@eugeni:/var/lib/mailman# sudo -u list ./bin/list_lists | head -1
65 matching maili...while removing the tor-teachers list (#40947) i wondered how many active lists we actually did have left. so i took a look...
we have 65 lists:
```
root@eugeni:/var/lib/mailman# sudo -u list ./bin/list_lists | head -1
65 matching mailing lists found:
```
out of those, only 54 have archives, so those are the only ones we can guess at how active they are:
```
root@eugeni:/var/lib/mailman# ls -lt $(for list in $(ls lists) ; do echo archives/private/$list.mbox/$list.mbox; done) 2>/dev/null | wc -l
54
```
out of that, only 35 lists have public archives:
```
root@eugeni:/var/lib/mailman# ls -lt $(for list in $(ls lists) ; do echo archives/public/$list/index.html; done) 2>/dev/null | wc -l
35
```
and those are the lists that haven't been posted to since january 2022:
```
root@eugeni:/var/lib/mailman# ls -lt $(for list in $(ls lists) ; do echo archives/public/$list/index.html; done) 2>/dev/null | sed '0,/2022 archives/d'
-rw-rw-r-- 1 www-data list 4518 Jan 19 2022 archives/public/tor-relays-fr/index.html
-rw-rw-r-- 1 root list 9238 Oct 17 2021 archives/public/tor-relays-universities/index.html
-rw-rw-r-- 1 root list 33055 Aug 14 2021 archives/public/tbb-bugs/index.html
-rw-rw-r-- 1 root list 26537 May 28 2021 archives/public/ooni-dev/index.html
-rw-rw-r-- 1 root list 4912 Feb 23 2021 archives/public/ooni-operators/index.html
-rw-rw-r-- 1 root list 3654 Jan 6 2021 archives/public/tor-access/index.html
-rw-rw-r-- 1 root list 1105 Nov 9 2020 archives/public/ooni-bugs/index.html
-rw-rw-r-- 1 root list 6175 Jun 2 2020 archives/public/tor-scaling/index.html
-rw-rw-r-- 1 root list 4095 Sep 24 2019 archives/public/tor-users/index.html
-rw-rw-r-- 1 root list 37721 Sep 17 2018 archives/public/tor-wiki-changes/index.html
-rw-rw-r-- 1 root list 2383 Sep 4 2018 archives/public/regional-nyc/index.html
-rw-rw-r-- 1 root list 17248 Aug 21 2015 archives/public/tor-censorship-events/index.html
```
... it's kind of an arbitrary metric... i wanted to look at "this year", but this was an easier sed pattern.
it's twelve lists. from there, it looksl ike the following lists are prime candidates for removal:
* [x] tbb-bugs: @richard, is that still in use?
* [ ] ooni-dev: do the oon folks still use this?
* [ ] ooni-operators: same
* [ ] ooni-bugs: that one surely isn't relevant anymore
* [ ] tor-users: is that still a thing? no post since 2019!?
* [x] tor-wiki-changes: i bet this is empty since we moved to gitlab
* [ ] regional-nyc: hey what's up NYC?
* [ ] tor-censorship-events: ooni does this now?
i'm not sure what to do about those:
* [ ] tor-relays-fr
* [ ] tor-relays-universities
* [ ] tor-access
* [x] tor-scalinganarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/40884tor-commits bounce emails after push to pluggable-transports/obfs4.git2022-10-31T18:35:34ZDavid Fifielddcf@torproject.orgtor-commits bounce emails after push to pluggable-transports/obfs4.gitThere is a problem with the tor-commits automailer for https://gitweb.torproject.org/pluggable-transports/obfs4.git. After a push, I received bounce messages for 2 commits I authored.
After getting commit access in tpo/tpa/team#40881, m...There is a problem with the tor-commits automailer for https://gitweb.torproject.org/pluggable-transports/obfs4.git. After a push, I received bounce messages for 2 commits I authored.
After getting commit access in tpo/tpa/team#40881, meskio pushed 8 commits to pluggable-transports/obfs4.git, 2 of which were authored by me. I got bounce mails for the 2 authored by me:
* [05/08 Test that public keys are not always on the prime-order subgroup.](https://gitweb.torproject.org/pluggable-transports/obfs4.git/commit/?h=master&id=586fbf43752592ee299233274e3e5d5597bf7f34)
* [06/08 Do not clamp the private key before Elligator inverse map.](https://gitweb.torproject.org/pluggable-transports/obfs4.git/commit/?h=master&id=5fcbb0e14064d41e4fa43013e1f0ede4028f25c5)
```
Subject: Your message to tor-commits awaits moderator approval
From: tor-commits-owner@lists.torproject.org
To: david@bamsoftware.com
Message-ID: <mailman.1562.1662647238.640.tor-commits@lists.torproject.org>
Date: Thu, 08 Sep 2022 14:27:18 +0000
Your mail to 'tor-commits' with the subject
[pluggable-transports/obfs4] 05/08: Test that public keys are not
always on the prime-order subgroup.
Is being held until the list moderator can review it for approval.
The reason it is being held:
Post to moderated list
Either the message will get posted to the list, or you will receive
notification of the moderator's decision. If you would like to cancel
this posting, please visit the following URL:
```
```
Subject: Your message to tor-commits awaits moderator approval
From: tor-commits-owner@lists.torproject.org
To: david@bamsoftware.com
Message-ID: <mailman.1559.1662647237.640.tor-commits@lists.torproject.org>
Date: Thu, 08 Sep 2022 14:27:17 +0000
Your mail to 'tor-commits' with the subject
[pluggable-transports/obfs4] 06/08: Do not clamp the private key
before Elligator inverse map.
Is being held until the list moderator can review it for approval.
The reason it is being held:
Post to moderated list
Either the message will get posted to the list, or you will receive
notification of the moderator's decision. If you would like to cancel
this posting, please visit the following URL:
```anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/40473retire the tor-bugs@ mailing list2022-08-25T15:04:35Zanarcatretire the tor-bugs@ mailing listthe tor-bugs@ list should be retired. it sees no traffic since Trac was retired and we do not plan on re-enabling this in GitLab (see tpo/tpa/gitlab#6). People wanting to get email notifications for issues should register on gitlab and s...the tor-bugs@ list should be retired. it sees no traffic since Trac was retired and we do not plan on re-enabling this in GitLab (see tpo/tpa/gitlab#6). People wanting to get email notifications for issues should register on gitlab and start watching projects they are interested in.old service retirement 2022-Q1/Q2anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/40032Community Guideline reminders on our mailing lists2020-09-28T18:34:49ZAlexander Færøyahf@torproject.orgCommunity Guideline reminders on our mailing listsIn the Community Council, we have discussed whether it could make sense to send an automated email every 3/6 months with a reminder on CoC/Social Contract/etc. This is inspired by our friends from the Tails project.
How would we go abou...In the Community Council, we have discussed whether it could make sense to send an automated email every 3/6 months with a reminder on CoC/Social Contract/etc. This is inspired by our friends from the Tails project.
How would we go about implementing this with our mailing lists? It's our understanding that each email list has its own set of "owners", so we would need to talk to them individually as they are the "service admins" of the given list? Once they approve, we could set up a cronjob somewhere that writes some standard text out?
How do we learn who owns which mailing lists?anarcatanarcathttps://gitlab.torproject.org/tpo/tpa/team/-/issues/34363Allow mail from sysrqb@torproject.org on tor-announce@2020-06-27T14:16:20ZMatthew FinkelAllow mail from sysrqb@torproject.org on tor-announce@Please accept mail from `sysrqb@torproject.org` on tor-announce@ so I can announce new Tor Browser releases.
ThanksPlease accept mail from `sysrqb@torproject.org` on tor-announce@ so I can announce new Tor Browser releases.
ThanksJens KubiezielJens Kubiezielhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/34223Please create a 'translation-admin' mailing list2020-06-27T14:16:22ZMatthew FinkelPlease create a 'translation-admin' mailing listPlease create a private mailing list for 'translation-admin' without archives. I'll be the administrator (for now).
Thanks.Please create a private mailing list for 'translation-admin' without archives. I'll be the administrator (for now).
Thanks.Jens KubiezielJens Kubiezielhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/34117Delete vegas-leads list2020-06-27T14:16:25ZRoger DingledineDelete vegas-leads listThe vegas-leads list:
https://lists.torproject.org/cgi-bin/mailman/listinfo/vegas-leads
has served us well for some years now:
https://lists.torproject.org/pipermail/tor-project/2016-March/000196.html
But with the new plans (more struct...The vegas-leads list:
https://lists.torproject.org/cgi-bin/mailman/listinfo/vegas-leads
has served us well for some years now:
https://lists.torproject.org/pipermail/tor-project/2016-March/000196.html
But with the new plans (more structured interactions between teams), we no longer need a separate list for coordination between teams. So it is time to retire (delete) the list.
It has no archives, so it should be easy to remove.
Thanks!Jens KubiezielJens Kubiezielhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/34112Delete tor-researchers list2020-06-27T14:16:26ZGeorge KadianakisDelete tor-researchers listtor-researchers is a mailing list that was basically never used. It was meant to be a closed list for researchers to facilitate research discussion.
The list was closed, and maintaining its membership was more logistics than we could af...tor-researchers is a mailing list that was basically never used. It was meant to be a closed list for researchers to facilitate research discussion.
The list was closed, and maintaining its membership was more logistics than we could afford for a list that is never used.
Please delete it, and also delete its archives since there is basically no actual threads in there, and the list was secret in the first place.
Thanks!Jens KubiezielJens Kubiezielhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/34097Remove tor-moderators list2020-06-27T14:16:26ZRoger DingledineRemove tor-moderators listThere's a tor-moderators list:
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-moderators
which is completely unused -- no messages ever sent, and nobody ever subscribed. Apparently we made it in legacy/trac#32155.
Let's delet...There's a tor-moderators list:
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-moderators
which is completely unused -- no messages ever sent, and nobody ever subscribed. Apparently we made it in legacy/trac#32155.
Let's delete it, so people don't look at it and think there's a sekrit list where people are conspiring.
(Moderators for various Tor services and forums do talk to each other, but clearly they have developed other ways of doing it rather than using this list.)
Thanks!Jens KubiezielJens Kubiezielhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/34096delete volunteering list2020-06-27T14:16:26ZRoger Dingledinedelete volunteering listThere is a list called "volunteering":
https://lists.torproject.org/cgi-bin/mailman/listinfo/volunteering
which has Damian, Matt Pagan, and Moritz on it.
Damian tells me he doesn't know of anything that points to it, and that it isn't g...There is a list called "volunteering":
https://lists.torproject.org/cgi-bin/mailman/listinfo/volunteering
which has Damian, Matt Pagan, and Moritz on it.
Damian tells me he doesn't know of anything that points to it, and that it isn't getting used.
So we should delete it to remove confusion.
Thanks!Jens KubiezielJens Kubiezielhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/34095delete support-team-private list2020-06-27T14:16:26ZRoger Dingledinedelete support-team-private listhttps://lists.torproject.org/cgi-bin/mailman/listinfo/support-team-private
It was last used in 2016, and also it has members that I recognize from like eight years ago.
I checked with Gus and he thinks shutting it down is a fine plan.
...https://lists.torproject.org/cgi-bin/mailman/listinfo/support-team-private
It was last used in 2016, and also it has members that I recognize from like eight years ago.
I checked with Gus and he thinks shutting it down is a fine plan.
It has archives (private to only subscribers), and we can delete those.
Thanks!Jens KubiezielJens Kubiezielhttps://gitlab.torproject.org/tpo/tpa/team/-/issues/34094delete tor-assistants list2020-06-27T14:16:27ZRoger Dingledinedelete tor-assistants listThere is still a tor-assistants list:
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-assistants
but it has a strange group of past people on it, and I don't see anybody successfully using it, except Micah using it in...There is still a tor-assistants list:
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-assistants
but it has a strange group of past people on it, and I don't see anybody successfully using it, except Micah using it in Nov 2019 and Jan 2020 in response to nextcloud password resets, and I have no idea how that happened but it doesn't seem mission-critical. :)
Long ago we used tor-assistants@tpo (not @lists.tpo) for people to help me answer questions from the outside world, but we long ago stopped successfully doing that, and somebody made a mailman list out of it but it never really got off the ground. Now there is tor-team@lists.tpo for a similar but different role.
In any case, this list is not in use, and nobody has been maintaining its subscriber list. It's a good time to clean it up.
Thanks!Jens KubiezielJens Kubieziel