Quoting David Fifield (2022-02-28 17:33:51)
On Mon, Feb 28, 2022 at 12:43:24PM +0100, meskio wrote:
Quoting David Fifield (2022-02-28 09:54:28)
On Mon, Feb 28, 2022 at 01:45:50AM -0700, David Fifield wrote:
On Tue, Feb 08, 2022 at 06:17:47PM +0100, meskio wrote:
How to access the different distributors:
- email. Just write an email to bridges-test@torproject.org from your @torproject.org email, and should get a reply with bridges.
I sent 2 emails from dcf@torproject.org and did not get any reply. One email had subject "get bridges" and an empty body; the other had an empty subject and "get transport obfs4" in the body.
I spoke too soon. I got a reply to the first email (the one with a subject of "get bridges" and an empty body) after about 6 minutes. (The email's Date header was the same second I sent the message, but the Delivery-date header was 6 minutes later. Date: Mon, 28 Feb 2022 08:38:53 +0000 Delivery-date: Mon, 28 Feb 2022 08:45:09 +0000
This is pretty weird. I have tested it many times and I always get content in the body. I just tested it and it looked good here :(
Might it be that the changes we did to the text[0] are breaking your client (it does now contain some UTF-8 characters)? Can you try to open the email with a text editor or another email client? Does it look empty? Do you mind forwarding me the email?
Sorry, I wasn't clear. The email I *sent* had an empty body. The email I *received* from bridges-test had bridges and instructions in the body as expected.o
Ok, I'm happy it worked as expected. Thank you for testing it.
I tested sending an empty body, and separately an empty subject because, as I recall, in the past there was some confusion about whether BridgeDB should reply to such messages.
I see the code having something about that. But now bridgedb should always reply with obfs4 unless other commands provided, so no valid commands will still work to get bridges :)
BTW, bridgedb+rdsys is already in production.