Literally the title - emails never arrive and there seems to be no provided information in the documentation on debugging, configuring, or in any way making the email verification functional.
This is actually ridiculous - the fact that I can't forcibly verify the email when my own server is supposed to send it is asinine and deceptive.
If Bluesky's email servers were sending the email, it might make some tiny amount of sense, but that's not the case, so I can't see any rational reason for this.
Also doesn't help that half of the administrative commands from pdsadmin are broken too, and when literally copy-pasted exactly as shown in the help dialogue (which only displays if you type the command with no arguments, but somehow FUCKING 404s if you try to use the --help flag) will simply say that the command is not found, as shown below:
root@DietPi:~# pdsadmin account list
/tmp/pdsadmin.account.Nw9HWR: line 43: column: command not found
So it turns out I'm stupid and glossed over the SMTP details in the github readme. Big L for me tbh
Definitely my fault and I should have been less quick to assume it was someone else's error, regardless of other issues I had with BSky stuff, will be closing the issue. You have my apologies.
Literally the title - emails never arrive and there seems to be no provided information in the documentation on debugging, configuring, or in any way making the email verification functional.
This is actually ridiculous - the fact that I can't forcibly verify the email when my own server is supposed to send it is asinine and deceptive. If Bluesky's email servers were sending the email, it might make some tiny amount of sense, but that's not the case, so I can't see any rational reason for this.
Also doesn't help that half of the administrative commands from pdsadmin are broken too, and when literally copy-pasted exactly as shown in the help dialogue (which only displays if you type the command with no arguments, but somehow FUCKING 404s if you try to use the --help flag) will simply say that the command is not found, as shown below:
So it turns out I'm stupid and glossed over the SMTP details in the github readme. Big L for me tbh Definitely my fault and I should have been less quick to assume it was someone else's error, regardless of other issues I had with BSky stuff, will be closing the issue. You have my apologies.