#30103 closed defect (duplicate)

Make email address for bridges consistent

Reported by: phw Owned by: hiro
Priority: Medium Milestone:
Component: Webpages/Website Version:
Severity: Minor Keywords: bridges, email
Cc: traumschule Actual Points:
Parent ID: Points: 0.1
Reviewer: Sponsor:


BridgeDB claims that users should email bridges[at]torproject.org but our website mentions bridges[at]bridges.torproject.org. This confused at least one user over at #18076 and, frankly, me too.

I created a patch in the following GitHub branch:

It makes our documentation consistent by changing the email address to bridges[at]torproject.org.

Child Tickets

Change History (2)

comment:1 Changed 16 months ago by arma

These two addresses are actually slightly different from each other, in that they run different mail servers with different ways of handling spam, verifying senders, etc.

The @tpo one is the same as the mailserver for developers receiving mail about Tor things. It uses postgrey to delay new requests for dozens of minutes, etc.

Whereas the @bridges.tpo one is whatever the bridgedb service is running.

So by telling users to use @tpo, we need *both* services to be working, for users to be able to get their bridges via email. And we inherit antispam measures that we use for our individual mailboxes, like the greylisting and I'm not sure what else.

The reasons to tell people bridges@tpo are because it is simpler, shorter, more intuitive, and easier to remember. Those are a lot of good reasons, and I think it turns it into a net positive. But we should be aware of the underlying mechanisms so we know and accept the tradeoffs.

(For a similar service with a similar decision to make, compare to how we run our mailman lists at @lists.tpo, rather than just having them all be @tpo.)

comment:2 Changed 15 months ago by hiro

Resolution: duplicate
Status: newclosed
Note: See TracTickets for help on using tickets.