You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GCP had proposed to use NAT to use another port like 465 and 587 instead of 25. But the issue is our kubernetes cluster has loadbalancer type service which is opened to internal. This is not the NAT implementation architecture. Other option GCP had proposed is mail relay. There are free mailrelays we can use our perpose until we build our own one.
We could complete mail sending to external domain using a external mail rellay only. When we try to communicate with standard email ports with external mail servers those outbound traffic is blocked in GCP. So we configured our own mail relay in AWS and connected with it from port 2525. Now external mail sending is ok .
Mails are not sent once it is configured in GCP.
This issue should be investigated
The text was updated successfully, but these errors were encountered: