Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #25536

Closed (moved)
(moved)
Open
Created Mar 18, 2018 by Roger Dingledine@arma

Build (and document) a set of habits around our schleuder replies

The tor-security@ list is set up using schleuder: https://trac.torproject.org/projects/tor/wiki/doc/emailLists#AdministrativeLists

Generally people send mail to it unencrypted and unsigned, I guess because pgp is hard.

When I reply to the mails, I've been manually pasting the original sender onto the To: address, and switching my reply from the default encrypted back to unencrypted so the mail can go to the original sender (I don't have their key after all). It looks like other people are following a similar pattern.

But intrigeri tells me that there are secret directives you can give to schleuder, like x-resend, that might allow me to ask schleuder to handle the mail delivery: https://schleuder.nadir.org/docs/#using-a-list

Should we be using that directive and then encrypting the mail to schleuder? Does it work? is there something better we should be doing?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking