Opened 7 years ago

Last modified 6 weeks ago

#3780 new enhancement

GetTor and BridgeDB should share email processing code

Reported by: kaner Owned by: kaner
Priority: Medium Milestone:
Component: Applications/GetTor Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: #28152 Points:
Reviewer: Sponsor:

Description

Both GetTor and BridgeDB seem have a lot of requirements in common when it comes to email processeing and configuration. (For instance, mail filtering, DKIM checks and so on)

Maybe we should sync the email processing code into something like a python tor email library for both at some point in the future.

Child Tickets

Change History (4)

comment:1 Changed 7 years ago by phobos

Do you mean they should work the same way or rely on the same codebase running on a shared server?

comment:2 Changed 7 years ago by arma

I assume he means that they should both link in the same library. That way there's one place (sort of like how torctl is the central library for arm, torflow, etc), where we write and maintain the code to handle incoming and outgoing emails, check dkim, enforce policies, etc.

Then the gettor deployment has a checkout of the tor email library, and calls it with its chosen configuration parameters; and the bridgedb deployment has a checkout of it too.

I don't think mixing the deployment side (e.g. a shared server) is going to make our lives more fun.

comment:3 Changed 12 months ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

comment:4 Changed 6 weeks ago by traumschule

Parent ID: #28152

Group GetTor refactoring issues

Note: See TracTickets for help on using tickets.