Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Account association fails (Digital Ocean: SMTP banned system-wide) #262

Open
ErikTeik opened this issue Dec 21, 2024 · 4 comments
Open

Account association fails (Digital Ocean: SMTP banned system-wide) #262

ErikTeik opened this issue Dec 21, 2024 · 4 comments

Comments

@ErikTeik
Copy link

Since a VPS at Digital Ocean is listed as recommended provider, please note that SMTP is banned on all accounts. This results in associating the service running at DO with your moderation account won´t work.

Is there a workaround for that, as we´ve even installed postfix with google as relay. Testmails via the SSH are working, but ozone seems unable to use postfix. (We´re not IT people)

Screenshot 2024-12-21 121609
Screenshot 2024-12-21 121219

@SteveTownsend
Copy link

SteveTownsend commented Dec 21, 2024 via email

@garbagecans
Copy link

I'm running Ozone at Digital Ocean with the admin email served in the same
domain via Proton. Proton provided detailed instructions on how to do this.

Hi there - do you have a link to these detailed instructions? I have SMTP servers available, but I am at a loss to see how to give the details to Ozone to help get the association email out of my Ozone container.

@garbagecans
Copy link

Since a VPS at Digital Ocean is listed as recommended provider, please note that SMTP is banned on all accounts. This results in associating the service running at DO with your moderation account won´t work.

Is there a workaround for that, as we´ve even installed postfix with google as relay. Testmails via the SSH are working, but ozone seems unable to use postfix. (We´re not IT people)

Screenshot 2024-12-21 121609 Screenshot 2024-12-21 121219

Hi Erik -

I ran into the same issue as you, or what felt like the same issue (same error generated).

On review, I noted that I was using an app password to try to log in; using the direct password got me past the error.

It wasn't my Ozone droplet attempting to send an email; it was that Bluesky failed to send me an email with a confirmation code. It failed, I assume, because it was not able to retrieve my registered email address.

@SteveTownsend
Copy link

The info I used to set up Proton to host email for my mod service is here
https://proton.me/support/custom-domain
I manage my domain's DNS in Digital Ocean, idk if this works if you do that elsewhere - probably can be done (?), but an extra complication.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants