##! If your SMTP server does not like the default ‘From: gitlab@gitlab.example.com’
##! can change the ‘From’ with this setting.
gitlab_rails[‘gitlab_email_from’] = ‘abc@gmail.com’
gitlab_rails[‘gitlab_email_display_name’] = ‘Gitlab’
gitlab_rails[‘gitlab_email_reply_to’] = ‘abc@gmail.com’
gitlab_rails[‘gitlab_email_subject_suffix’] = ‘email’
You will have to make sure the firewall doesn’t block outbound ports for the ones you want to connect to. You will need to speak to your network admin for that, or if you are the admin for it, check your router/firewall and unblock the ports required for the particular communication method.
Well since you have connection timed out from your VPS to port 25, it means you cannot send which means AWS is blocking outbound connections to port 25, which I asked for you to make sure the ports are not blocked. That means it’s not using port 587.
After you make config changes you must do gitlab-ctl reconfigure
I been find AWS support and they been review my Account.
here the result: state in the region ‘ap-southeast-1’. I can also see that your Route table, Network ACL and Security Group rules are configured for SMTP access.
that is no issue on AWS Security group blocking.
please advise gitlab part the email, I cant receive?
Please note that Gmail has strict sending limits that can impair functionality as your organization grows. We strongly recommend using a transactional service like SendGrid or Mailgun for teams using SMTP configuration.
You can test whether your configuration is working properly with this: SMTP settings | GitLab
There are also additional outbound email troubleshooting steps here: SMTP settings | GitLab
Note that if the connection is blocked at the network (by a network policy, ACL, custom DNS), this problem will need to be resolved at the network layer.
Logs about outbound emails will be captured in Sidekiq logs (/var/log/gitlab/sidekiq/current)
Please also note that GitLab uses a documentation-first methodology to ensure the documentation remains a complete, accurate, and trusted resource, and makes communicating about the use of GitLab more efficient. "New information that would be useful toward the future usage or troubleshooting of GitLab should not be written directly in a forum or other messaging system, but added to a documentation MR and then referenced, as described above."This is why linking to documentation is a standard response when helping others with GitLab.