-
Notifications
You must be signed in to change notification settings - Fork 45
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
Comments
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.
…On Sat, Dec 21, 2024, 6:23 AM ErikTeik ***@***.***> wrote:
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.png (view on web)
<https://github.com/user-attachments/assets/cec45cfe-85a1-48cd-8af4-5e0cc0c547cc>
Screenshot.2024-12-21.121219.png (view on web)
<https://github.com/user-attachments/assets/084ab845-5b01-4435-a250-ccabb4f7c57d>
—
Reply to this email directly, view it on GitHub
<#262>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADRDNC5G2NARO2FWT26EPJ32GVFR5AVCNFSM6AAAAABUAREMCSVHI2DSMVQWIX3LMV43ASLTON2WKOZSG42TGOJRGM4DOOI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
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. |
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. |
The info I used to set up Proton to host email for my mod service is here |
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)
The text was updated successfully, but these errors were encountered: