-
-
Notifications
You must be signed in to change notification settings - Fork 226
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
[Bug] Appflowy_cloud tried to connect to SMTP server without any reason. #951
Comments
The connection attempt occurred every minutes.
|
One situation where i have seen this happening, is when AppFlowy Cloud performs any action (magic link, invite user to workspace, invite user to appflowy, notify user when notion import is completed) that requires smtp server, but unable to connect to the server (eg. if the port supports STARTTLS instead of TLS). In which case, the server will keep retrying, in roughly a minute interval. I am not familiar with postfix myself, so i will have to research more about it. |
Hello, The smtp connection is okay because when I invite someone for example, the mail is successfully sent... However, I have no logs on appflowy side. Which container should I look ? |
If there is any log, it should be on Appflowy cloud. Could you give more information on the SMTP setup (i.e. configuration of postfix), so that I can try to see if I can reproduce the issue? |
Hello, Postfix is configured in TLS ( port 587 ) with authentication. There is not any special configuration. My problem is I don't have any logs in appflowy_cloud.( except a warning which happen every hours ) but nothing which trigger every minutes. |
Describe the bug
REgulary, the container
appflowy_cloud
tried to connect to my TLS smtp server ( port 587 ) but does nothing ?To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
The connection is either not started while no mail has to be sent.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: