Opened 5 weeks ago

Last modified 5 weeks ago

#32109 assigned task

tor-community-council@torproject.org email alias does not exist

Reported by: pili Owned by: dgoulet
Priority: High Milestone:
Component: Internal Services/Schleuder Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by pili)

We were recently made aware that the tor-community-council 'at' torproject.org email alias listed on
our Community Council Policies: https://gitweb.torproject.org/community/policies.git/tree/community_council.txt#n84 does not in fact work.

The correct email address is tor-community-council 'at' lists.torproject.org

Rather than going through the process to amend the Community Council Policy, would it be possible to create an email alias to point tor-community-council 'at' torproject.org to tor-community-council 'at' lists.torproject.org?

Also, does anyone know if there would there be any implications when encrypting messages to this list given that the email alias does not match the uids on the gpg key?

Also, not sure if I've created this under the correct component, so please feel free to move to the correct one.

Thanks!

Child Tickets

Change History (4)

comment:1 Changed 5 weeks ago by pili

Description: modified (diff)

comment:2 Changed 5 weeks ago by gaba

Component: Internal Services/Service - listsInternal Services/Tor Sysadmin Team
Owner: changed from qbi to tpa
Priority: MediumHigh

comment:3 Changed 5 weeks ago by anarcat

Owner: changed from tpa to anarcat
Status: newassigned

Rather than going through the process to amend the Community Council Policy, would it be possible to create an email alias to point tor-community-council 'at' torproject.org to tor-community-council 'at' lists.torproject.org?

Makes sense, and will do shortly.

Also, does anyone know if there would there be any implications when encrypting messages to this list given that the email alias does not match the uids on the gpg key?

Yes, there are. Most email clients will not find the right key and will refuse to send an encrypted mail.

There are a few solutions for this:

  1. client-side solutions: some clients will allow you to pick an arbitrary key for encryption (not great, requires user knowledge)
  2. "server-side" solutions: the other UID could just be added to the key

Also, not sure if I've created this under the correct component, so please feel free to move to the correct one.

Since this is an encrypted list, i think schleuder might be a better place, especially for the UID change. But this is a good start. :)

comment:4 Changed 5 weeks ago by anarcat

Component: Internal Services/Tor Sysadmin TeamInternal Services/Schleuder
Owner: changed from anarcat to dgoulet

fix is in eb3e915c and will propagate in a few hours.

i'm leaving this open for the schleuder folks to consider adding the UID to the key.

Note: See TracTickets for help on using tickets.