Fork of official Bluesky PDS (Personal Data Server).

Section on common SMTP issues

+6
+6
README.md
··· 228 229 _Note: Your PDS will need to be restarted with those variables. This varies depending on your setup. If you followed this installation guide, run `systemctl restart pds`. You might need to restart the server or recreate the container, depending on what you are using._ 230 231 ### Logging 232 233 By default, logs from the PDS are printed to `stdout` and end up in Docker's log. You can browse them by running:
··· 228 229 _Note: Your PDS will need to be restarted with those variables. This varies depending on your setup. If you followed this installation guide, run `systemctl restart pds`. You might need to restart the server or recreate the container, depending on what you are using._ 230 231 + #### Common SMTP issues 232 + 233 + If you find that your test messages using cURL or other sources go out correctly, but you are not receiving emails from your PDS, you may need to URL encode your username and password on `/pds/pds.env` and restart the PDS service. 234 + 235 + If you are migrating an account, Bluesky's UI will ask you to confirm your email address. The confirmation code email is meant to come from your PDS. If you are encountering issues with SMTP and want to confirm the address before solving it, you can find the confirmation code on the `email_token` table on `accounts.sqlite`. 236 + 237 ### Logging 238 239 By default, logs from the PDS are printed to `stdout` and end up in Docker's log. You can browse them by running: