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

Mailtest improvements: Don't rely explicitly on osparc.io SMTP server #873

Open
mrnicegyu11 opened this issue Nov 13, 2024 · 0 comments
Open
Labels
p:mid-prio t:enhancement New feature or request t:infra-ops Adjustments to the way or resources with that microservices are run

Comments

@mrnicegyu11
Copy link
Member

Currently all mail-tests (that mainly test that a mail can be recieved at this point) for sending mails rely in a hardcoded manner on the osparc.io SMTP server.

Ideally all deployments should

  • Have their own SMTP server or one (like mail.speag.com) associated with them. This is easy for aws/tf deployments I guess, but requires coordination for on-prem
  • test that their associated receiving (IMAP) and sending (SMTP) servers work by sending and receiving a mail there (currently only the receiving part works very well, although arguably the sending part is more important for the osparc-simcore platform)

FYI @YuryHrytsuk

@mrnicegyu11 mrnicegyu11 added t:enhancement New feature or request p:mid-prio t:infra-ops Adjustments to the way or resources with that microservices are run labels Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
p:mid-prio t:enhancement New feature or request t:infra-ops Adjustments to the way or resources with that microservices are run
Projects
None yet
Development

No branches or pull requests

1 participant