Opened 3 years ago

Last modified 2 years ago

#25536 new defect

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

Reported by: arma Owned by: hiro
Priority: Medium Milestone:
Component: Internal Services/Schleuder Version:
Severity: Normal Keywords:
Cc: dgoulet@… Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


The tor-security@ list is set up using schleuder:

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:

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

Child Tickets

Change History (2)

comment:1 Changed 2 years ago by cypherpunks

When using X-RESEND you need to add also the line X-LIST-NAME line to your email, and send it signed:

X-LIST-NAME: listname@…
X-RESEND: person@…

You could also add their key to your schleuder mailing list, with

X-LIST-NAME: listname@…
[--- PGP armored block--]

And then do:

X-LIST-NAME: listname@…

You can also do:

X-LIST-NAME: listname@…

To see the keys currently on the keyring

and my personal favorite:

X-LIST-NAME: listname@…
X-GET-KEY: someone@…

comment:2 Changed 2 years ago by hiro

This has been now added to the Schleuder service document:

Note: See TracTickets for help on using tickets.